CCminer(SP-MOD) Modded GPU kernels.

[Ayers]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Oh dear, I've seen this too much. Here is what I know.

Sometimes when a miner stops and restarts, usually to switch algos, it will exhibit any of the following symptoms:
    - it will fail to start with the same parameters
    - it will start with reduced intensity (-i)
    - it will start in a degraded state, low clock

A reboot will correct the problem.
The occurrance appears to be random. Sometimes a card will get hit multiple times per day, sometimes not for several days
Only some cards are affected, some never exhibit the problem.
There is no pattern to the affected cards, Maxwell and Kepler have both been affected.
It occurs on Windows and linux.
It does not appear to be driver related.
It appears to affect only specific individual cards.

There was discussion about this several months ago. A search on "degraded" might find something.
The bottom line is it was never solved. It's possibly a HW issue.

I do have some new information, It may be heat related, possibly heat stressing a marginal component.
I recently moved an affected card to the basement where it's cooler. It had been crashing often when
profit switching. Since the move it has been more stable but I have not been profit switching with it. I only
switch manually every few days. I may setup profit switching on this PC to try to recreate the problem.

Well there ya go. It's one of those things that has been nagging me for a while. I feel better now.
You could try swapping the cards to see if the problem moves.

what i know is, it only appear with x15 algo and maybe other xX algo, all other algo are working right, so i think it's not so much hardware related, i've already swapped the card and the same problem is occuring
only one card is running at full speed(the one not in the first slot, in other words, the one that is not mining is always the one near the cpu on the x16-x16 riser, at this point it could be the riser, but i doubt because the other algo are running)
therefore this strengthens the fact that it might not be HW related, also one of the two card was recently rmaed because i thought it was the card causing this, but nothing, the problem is still there, now i'm running 361 drivers version, i'll try with 364 tomorrow to see if it change something

[1714951000]

1714951000

[1714951000]

1714951000

[1714951000]

1714951000

[1714951000]

1714951000

[joblo]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Oh dear, I've seen this too much. Here is what I know.

Sometimes when a miner stops and restarts, usually to switch algos, it will exhibit any of the following symptoms:
    - it will fail to start with the same parameters
    - it will start with reduced intensity (-i)
    - it will start in a degraded state, low clock

A reboot will correct the problem.
The occurrance appears to be random. Sometimes a card will get hit multiple times per day, sometimes not for several days
Only some cards are affected, some never exhibit the problem.
There is no pattern to the affected cards, Maxwell and Kepler have both been affected.
It occurs on Windows and linux.
It does not appear to be driver related.
It appears to affect only specific individual cards.

There was discussion about this several months ago. A search on "degraded" might find something.
The bottom line is it was never solved. It's possibly a HW issue.

I do have some new information, It may be heat related, possibly heat stressing a marginal component.
I recently moved an affected card to the basement where it's cooler. It had been crashing often when
profit switching. Since the move it has been more stable but I have not been profit switching with it. I only
switch manually every few days. I may setup profit switching on this PC to try to recreate the problem.

Well there ya go. It's one of those things that has been nagging me for a while. I feel better now.
You could try swapping the cards to see if the problem moves.

what i know is, it only appear with x15 algo and maybe other xX algo, all other algo are working right, so i think it's not so much hardware related, i've already swapped the card and the same problem is occuring
only one card is running at full speed(the one not in the first slot, in other words, the one that is not mining is always the one near the cpu on the x16-x16 riser, at this point it could be the riser, but i doubt because the other algo are running)
therefore this strengthens the fact that it might not be HW related, also one of the two card was recently rmaed because i thought it was the card causing this, but nothing, the problem is still there, now i'm running 361 drivers version, i'll try with 364 tomorrow to see if it change something

You probably have a different problem then. As I mentioned the problem I'm seeing is always the same card regardless
of the MB, slot, riser, OS or drivers.

[tbearhere]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Oh dear, I've seen this too much. Here is what I know.

Sometimes when a miner stops and restarts, usually to switch algos, it will exhibit any of the following symptoms:
    - it will fail to start with the same parameters
    - it will start with reduced intensity (-i)
    - it will start in a degraded state, low clock

A reboot will correct the problem.
The occurrance appears to be random. Sometimes a card will get hit multiple times per day, sometimes not for several days
Only some cards are affected, some never exhibit the problem.
There is no pattern to the affected cards, Maxwell and Kepler have both been affected.
It occurs on Windows and linux.
It does not appear to be driver related.
It appears to affect only specific individual cards.

There was discussion about this several months ago. A search on "degraded" might find something.
The bottom line is it was never solved. It's possibly a HW issue.

I do have some new information, It may be heat related, possibly heat stressing a marginal component.
I recently moved an affected card to the basement where it's cooler. It had been crashing often when
profit switching. Since the move it has been more stable but I have not been profit switching with it. I only
switch manually every few days. I may setup profit switching on this PC to try to recreate the problem.

Well there ya go. It's one of those things that has been nagging me for a while. I feel better now.
You could try swapping the cards to see if the problem moves.

Ccminer crashes on me on one rig profit switching. I haven't been able to figure it out yet.
But I'm going to put a timer in my conf file for MinerControl KBomba 1.6.5.1.
But the conf validates but doesn't work and I need help to get it working.
Anyone interested in helping me I will pay a little  BTC for as soon as I mine more.

[bathrobehero]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Oh dear, I've seen this too much. Here is what I know.

Sometimes when a miner stops and restarts, usually to switch algos, it will exhibit any of the following symptoms:
    - it will fail to start with the same parameters
    - it will start with reduced intensity (-i)
    - it will start in a degraded state, low clock

A reboot will correct the problem.
The occurrance appears to be random. Sometimes a card will get hit multiple times per day, sometimes not for several days
Only some cards are affected, some never exhibit the problem.
There is no pattern to the affected cards, Maxwell and Kepler have both been affected.
It occurs on Windows and linux.
It does not appear to be driver related.
It appears to affect only specific individual cards.

There was discussion about this several months ago. A search on "degraded" might find something.
The bottom line is it was never solved. It's possibly a HW issue.

I do have some new information, It may be heat related, possibly heat stressing a marginal component.
I recently moved an affected card to the basement where it's cooler. It had been crashing often when
profit switching. Since the move it has been more stable but I have not been profit switching with it. I only
switch manually every few days. I may setup profit switching on this PC to try to recreate the problem.

Well there ya go. It's one of those things that has been nagging me for a while. I feel better now.
You could try swapping the cards to see if the problem moves.

What you're describing is basically a card crashing without the driver not recovering.
The GPU clocks are stuck at 405 Mhz, right?

If so then yes, the card crashed and switched to the lowest and safest power state (P8 state) and the driver recovery didn't reset the card.
Driver recovery usually only starts if the card doesn't respond for a while (TDR timeout) but this is not the case and the driver doesn't care which power state a card is in.

Basically the card poops itself because of one the following:
- too much OC;
- not enough GPU memory (usually from too high intensity);
- too high intensity;
- low quality or faulty riser or power cable or PSU;
- low quality card (increasing voltage a bit helps stabilize the card)
and then it goes into safe mode.

To solve this you have to restart the PC or more conveniently disable the card in device manager (if it's not your primary card with a monitor pluged in) and re-enable it to force the driver to reinitialize the card.
Or you can use a bat with:
nvidiainspector.exe -restartdisplaydriver
to reset all cards.

It's mostly caused by too much overclock and it can crash even after days of being stable. I have a couple of cards that I know can't handle the same OC as the others so I always have lower clocks on them. Otherwise they'd always crash eventually.
Also different algos have different levels of taxing the GPU so the same card will not necessarily be able to handle all algos with the same overclock.
Some algos are overclock friendly while others will crash the card even with a mild overclock.
So if you're using a profit switching solution you have to use an overclock that works for all cards.
This is why it'd be nice to be able to set clock speeds from within the .bat file for each algo but nvidia-smi only changes the memory clocks for some reason.

[grendel25]

@sp - have you heard about the release of Pascal at all?  is there a promising date?

There was some more news yesterday, but no release dates.

http://www.extremetech.com/extreme/226032-nvidias-pascal-gp100-gpu-massive-bandwidth-enormous-double-precision-performance

Tesla GP100 3584 cuda cores. 1328MHZ core clock.

The tesla cards are too expensive for mining. I expect the gp100 to be 25% faster than the 980ti. (based on cuda core count and clockrate.)

The gigabyte G1 980ti is mining decred stable @ 1600MHZ core clock.

Only 25% faster? Nvidia has been claiming 10x performance gains.  I'm sure that could be a niche scenario or situational.  Still though, I don't think we should make mining estimates on core count and clocks alone given new architecture and enhanced materials. 

Other NVIDIA claims to consider:

– 16nm FinFET process that enables more features, higher performance, and improved power efficiency.
– NVLink, a new high speed, high bandwidth interconnect for maximum application scalability.
– HBM2 video memory, a faster and higher capacity, extremely efficient stacked GPU memory architecture.
– Unified Memory and Compute Preemption — significantly improved programming model.

Some of these features may benefit specific coins more than others.  (i.e memory consumptive algos)

I guess we'll wait and see.

I heard they could be up for sale in May.

[pokeytex]

@sp - have you heard about the release of Pascal at all?  is there a promising date?

There was some more news yesterday, but no release dates.

http://www.extremetech.com/extreme/226032-nvidias-pascal-gp100-gpu-massive-bandwidth-enormous-double-precision-performance

Tesla GP100 3584 cuda cores. 1328MHZ core clock.

The tesla cards are too expensive for mining. I expect the gp100 to be 25% faster than the 980ti. (based on cuda core count and clockrate.)

The gigabyte G1 980ti is mining decred stable @ 1600MHZ core clock.

Only 25% faster? Nvidia has been claiming 10x performance gains.  I'm sure that could be a niche scenario or situational.  Still though, I don't think we should make mining estimates on core count and clocks alone given new architecture and enhanced materials. 

Other NVIDIA claims to consider:

– 16nm FinFET process that enables more features, higher performance, and improved power efficiency.
– NVLink, a new high speed, high bandwidth interconnect for maximum application scalability.
– HBM2 video memory, a faster and higher capacity, extremely efficient stacked GPU memory architecture.
– Unified Memory and Compute Preemption — significantly improved programming model.

Some of these features may benefit specific coins more than others.  (i.e memory consumptive algos)

I guess we'll wait and see.

I heard they could be up for sale in May.

Exciting - eagerly following - I have a feeling my 750ti's will be going up for sale soon! LOL

[crysx]

@sp - have you heard about the release of Pascal at all?  is there a promising date?

There was some more news yesterday, but no release dates.

http://www.extremetech.com/extreme/226032-nvidias-pascal-gp100-gpu-massive-bandwidth-enormous-double-precision-performance

Tesla GP100 3584 cuda cores. 1328MHZ core clock.

The tesla cards are too expensive for mining. I expect the gp100 to be 25% faster than the 980ti. (based on cuda core count and clockrate.)

The gigabyte G1 980ti is mining decred stable @ 1600MHZ core clock.

Only 25% faster? Nvidia has been claiming 10x performance gains.  I'm sure that could be a niche scenario or situational.  Still though, I don't think we should make mining estimates on core count and clocks alone given new architecture and enhanced materials. 

Other NVIDIA claims to consider:

– 16nm FinFET process that enables more features, higher performance, and improved power efficiency.
– NVLink, a new high speed, high bandwidth interconnect for maximum application scalability.
– HBM2 video memory, a faster and higher capacity, extremely efficient stacked GPU memory architecture.
– Unified Memory and Compute Preemption — significantly improved programming model.

Some of these features may benefit specific coins more than others.  (i.e memory consumptive algos)

I guess we'll wait and see.

I heard they could be up for sale in May.

more than likely to be correct ... judging by the cores and speeds involved ... but that depends on the cuda version also and whether nvidia have fixed the issues in the previous cuda releases ...

dont forget that when nvidia came out with the fabled '10x performance over maxwell' - they were talking about THEIR testing - NOT mining ... their texture and shading test are far different from the way mining works with the gpu ... so a 25% or therabouts is actually a damned good increase when basically nothing is done to the code except recompiled for the card with the new cuda 8 ( and as seen with the jump from cuda 6.5 to 7.5 - initially can be less performance until the coders get their heads around new cuda code ) ...

obviously when that happens - there will be those devs that can ( and most likely will ) 'tinker' with the new instruction sets and 'tap into' the new performance tweaks of the pascal architecture - pushing the mining performance even further ...

pascal cards will obviously be a costly at first - and the initial versions will be improved within a few months of release ( as well as encounter price price drops ) ... so as usual - ill be doing what i normally do when nvidia bring their marketing machine to the world ... wait and watch ...

#crysx

[crysx]

@sp - have you heard about the release of Pascal at all?  is there a promising date?

There was some more news yesterday, but no release dates.

http://www.extremetech.com/extreme/226032-nvidias-pascal-gp100-gpu-massive-bandwidth-enormous-double-precision-performance

Tesla GP100 3584 cuda cores. 1328MHZ core clock.

The tesla cards are too expensive for mining. I expect the gp100 to be 25% faster than the 980ti. (based on cuda core count and clockrate.)

The gigabyte G1 980ti is mining decred stable @ 1600MHZ core clock.

Only 25% faster? Nvidia has been claiming 10x performance gains.  I'm sure that could be a niche scenario or situational.  Still though, I don't think we should make mining estimates on core count and clocks alone given new architecture and enhanced materials. 

Other NVIDIA claims to consider:

– 16nm FinFET process that enables more features, higher performance, and improved power efficiency.
– NVLink, a new high speed, high bandwidth interconnect for maximum application scalability.
– HBM2 video memory, a faster and higher capacity, extremely efficient stacked GPU memory architecture.
– Unified Memory and Compute Preemption — significantly improved programming model.

Some of these features may benefit specific coins more than others.  (i.e memory consumptive algos)

I guess we'll wait and see.

I heard they could be up for sale in May.

Exciting - eagerly following - I have a feeling my 750ti's will be going up for sale soon! LOL

yup - same ...

all my gigabyte 750ti oc lp cards will be going up for sale next week ...

im only keeping the gigabyte 980ti g1 and / or extreme ...

#crysx

[Ayers]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Oh dear, I've seen this too much. Here is what I know.

Sometimes when a miner stops and restarts, usually to switch algos, it will exhibit any of the following symptoms:
    - it will fail to start with the same parameters
    - it will start with reduced intensity (-i)
    - it will start in a degraded state, low clock

A reboot will correct the problem.
The occurrance appears to be random. Sometimes a card will get hit multiple times per day, sometimes not for several days
Only some cards are affected, some never exhibit the problem.
There is no pattern to the affected cards, Maxwell and Kepler have both been affected.
It occurs on Windows and linux.
It does not appear to be driver related.
It appears to affect only specific individual cards.

There was discussion about this several months ago. A search on "degraded" might find something.
The bottom line is it was never solved. It's possibly a HW issue.

I do have some new information, It may be heat related, possibly heat stressing a marginal component.
I recently moved an affected card to the basement where it's cooler. It had been crashing often when
profit switching. Since the move it has been more stable but I have not been profit switching with it. I only
switch manually every few days. I may setup profit switching on this PC to try to recreate the problem.

Well there ya go. It's one of those things that has been nagging me for a while. I feel better now.
You could try swapping the cards to see if the problem moves.

What you're describing is basically a card crashing without the driver not recovering.
The GPU clocks are stuck at 405 Mhz, right?

If so then yes, the card crashed and switched to the lowest and safest power state (P8 state) and the driver recovery didn't reset the card.
Driver recovery usually only starts if the card doesn't respond for a while (TDR timeout) but this is not the case and the driver doesn't care which power state a card is in.

Basically the card poops itself because of one the following:
- too much OC;
- not enough GPU memory (usually from too high intensity);
- too high intensity;
- low quality or faulty riser or power cable or PSU;
- low quality card (increasing voltage a bit helps stabilize the card)
and then it goes into safe mode.

To solve this you have to restart the PC or more conveniently disable the card in device manager (if it's not your primary card with a monitor pluged in) and re-enable it to force the driver to reinitialize the card.
Or you can use a bat with:
nvidiainspector.exe -restartdisplaydriver
to reset all cards.

It's mostly caused by too much overclock and it can crash even after days of being stable. I have a couple of cards that I know can't handle the same OC as the others so I always have lower clocks on them. Otherwise they'd always crash eventually.
Also different algos have different levels of taxing the GPU so the same card will not necessarily be able to handle all algos with the same overclock.
Some algos are overclock friendly while others will crash the card even with a mild overclock.
So if you're using a profit switching solution you have to use an overclock that works for all cards.
This is why it'd be nice to be able to set clock speeds from within the .bat file for each algo but nvidia-smi only changes the memory clocks for some reason.

i think that you're right, it may be an overclock thing, i doubt is the card itself, because this problem has occured with 4 different gpu, are they all faulty? no way
therefore the only thing is the oc with some algo, it seems that the 970 does not work well with ehavy oc when mining x15, because other algo are all fine

[tbearhere]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Try this.
Make sure all cards are in the p0 state....then oc at NO MORE then 1340 core speed.... check that while mining they are in the p0 state..... if that doesn't work then something else is wrong.
My cards do the same thing because of oc to high for that card.
Do one thing at a time to fix the problem.

[pallas]

pascal has big floating point improvements which we, miners, do not care about.
integer performance is probably very similar to maxwell, but clocks will be higher and efficiency better, because of the 16 nm process.
if it ends up like amd, the new memory will not bring any improvements, or it will even be slower for mining, as is the case of the fury cards.

[Ayers]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Try this.
Make sure all cards are in the p0 state....then oc at NO MORE then 1340 core speed.... check that while mining they are in the p0 state..... if that doesn't work then something else is wrong.
My cards do the same thing because of oc to high for that card.
Do one thing at a time to fix the problem.

you're right, i tried now and it was the oc, no more stopping, apparently for some algo you can not overclock too much

[tbearhere]

pascal has big floating point improvements which we, miners, do not care about.
integer performance is probably very similar to maxwell, but clocks will be higher and efficiency better, because of the 16 nm process.
if it ends up like amd, the new memory will not bring any improvements, or it will even be slower for mining, as is the case of the fury cards.

Thx  and  great    ROI......

[tbearhere]

i'm having a problem when running more than one gpu, on a old algo like x15, the second gpu do not run at full speed, but it's not throttling, it simply sit there at low core speed, why this?
when i restart the machine for the first few seconds it begin to run at full speed, then the miner close and when i restart it once again it run at slow speed, tried also with the Yimp fork but nothing

Try this.
Make sure all cards are in the p0 state....then oc at NO MORE then 1340 core speed.... check that while mining they are in the p0 state..... if that doesn't work then something else is wrong.
My cards do the same thing because of oc to high for that card.
Do one thing at a time to fix the problem.

you're right, i tried now and it was the oc, no more stopping, apparently for some algo you can not overclock too much

I was watching the miner that crashes and noticed that when it switched to qubit or x15, is when it crashed the most. I backed off the oc and that smoothed it out.

[tbearhere]

Ok I need some help please.
When I reboot, my 980ti and 970 gigabyte g1 need their clocks set.
Ok no problem on the 980ti... but when I give the cmd to see the 970's clocks, the readout scrolls off the screen. I mean I can't see the top of the screen where it has the time stamp.
With the 980ti I can see it but not when I cmd nvidia-smi -q -d SUPPORTED_CLOCKS -i 1.
I can't scroll to the top of the cmd window.
Any help plz.
Thx

[Strannik-74]

Ok I need some help please.
When I reboot, my 980ti and 970 gigabyte g1 need their clocks set.
Ok no problem on the 980ti... but when I give the cmd to see the 970's clocks, the readout scrolls off the screen. I mean I can't see the top of the screen where it has the time stamp.
With the 980ti I can see it but not when I cmd nvidia-smi -q -d SUPPORTED_CLOCKS -i 1.
I can't scroll to the top of the cmd window.
Any help plz.
Thx

Use MSI afterburner and you will have happiness.

[pallas]

Ok I need some help please.
When I reboot, my 980ti and 970 gigabyte g1 need their clocks set.
Ok no problem on the 980ti... but when I give the cmd to see the 970's clocks, the readout scrolls off the screen. I mean I can't see the top of the screen where it has the time stamp.
With the 980ti I can see it but not when I cmd nvidia-smi -q -d SUPPORTED_CLOCKS -i 1.
I can't scroll to the top of the cmd window.
Any help plz.
Thx

if you are on linux, just add "| less" to the end of the command line.
"less" is more "more" than "more"... it's a "pager"
if on windows, use "| more"

[tbearhere]

Ok I need some help please.
When I reboot, my 980ti and 970 gigabyte g1 need their clocks set.
Ok no problem on the 980ti... but when I give the cmd to see the 970's clocks, the readout scrolls off the screen. I mean I can't see the top of the screen where it has the time stamp.
With the 980ti I can see it but not when I cmd nvidia-smi -q -d SUPPORTED_CLOCKS -i 1.
I can't scroll to the top of the cmd window.
Any help plz.
Thx

Use MSI afterburner and you will have happiness.

Will that set the clocks to a p0 state automatically ?
I use nvidia inspector.

[tbearhere]

Ok I need some help please.
When I reboot, my 980ti and 970 gigabyte g1 need their clocks set.
Ok no problem on the 980ti... but when I give the cmd to see the 970's clocks, the readout scrolls off the screen. I mean I can't see the top of the screen where it has the time stamp.
With the 980ti I can see it but not when I cmd nvidia-smi -q -d SUPPORTED_CLOCKS -i 1.
I can't scroll to the top of the cmd window.
Any help plz.
Thx

if you are on linux, just add "| less" to the end of the command line.
"less" is more "more" than "more"... it's a "pager"
if on windows, use "| more"

This is my commands to get the clocks ... where do I add that pallas on windows 8.1  plz.

cd C:\Program Files\NVIDIA Corporation\NVSMI
nvidia-smi -q -d SUPPORTED_CLOCKS -i 1 "| more"   is this correct ?

[pallas]

Ok I need some help please.
When I reboot, my 980ti and 970 gigabyte g1 need their clocks set.
Ok no problem on the 980ti... but when I give the cmd to see the 970's clocks, the readout scrolls off the screen. I mean I can't see the top of the screen where it has the time stamp.
With the 980ti I can see it but not when I cmd nvidia-smi -q -d SUPPORTED_CLOCKS -i 1.
I can't scroll to the top of the cmd window.
Any help plz.
Thx

if you are on linux, just add "| less" to the end of the command line.
"less" is more "more" than "more"... it's a "pager"
if on windows, use "| more"

This may commands to get the clocks ... where do I add that pallas on windows 8.1  plz.

cd C:\Program Files\NVIDIA Corporation\NVSMI
nvidia-smi -q -d SUPPORTED_CLOCKS -i 1 | more

https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/redirection.mspx?mfr=true