Sapphire Tri-X R9 290 Problem

[crashtech]

Every time I reboot my R9 290 gets stuck at 300MHz under any load.

Sapphire Tri-X R9 290

Win 10 Pro Tech Preview 10061

If I flash to a fresh BIOS image, clocks (and frame rates) will return to normal until a reboot. Then it's back to unplayable again. Interestingly enough, lately my card is identified as an engineering sample even though I bought it new from Newegg. I'm at a loss at this point. I'm ready to revert to an older OS in order to troubleshoot, any help appreciated.

That screenie includes a 60 sec in-game benchmark to show the GPU at 100% load and 300MHz. So weird.

 

[master_shake_]

turn off ulps.

 

[crashtech]

Presumably it is disabled, but I don't know how to verify it.

 

[Termie]

Can you test this on a system running Win8.1? I wouldn't trust Win10 for anything serious at this point. I gave up on it because none of my wireless networking adapters would work with it.

 

[crashtech]

I might if that is the consensus view. I thought I must be overlooking something; an OS problem that writes bad info to a GPU BIOS is kinda nasty, imo. But I know if I write the old BIOS back to the card it will reboot once and be fine until the next reboot.

 

[crashtech]

I still haven't had any luck fixing this.

 

[guskline]

Have you tried the newest build? 10074?

 

[crashtech]

Getting that now.

 

[EightySix Four]

Every time I reboot my R9 290 gets stuck at 300MHz under any load.

Sapphire Tri-X R9 290

Win 10 Pro Tech Preview 10061

If I flash to a fresh BIOS image, clocks (and frame rates) will return to normal until a reboot. Then it's back to unplayable again. Interestingly enough, lately my card is identified as an engineering sample even though I bought it new from Newegg. I'm at a loss at this point. I'm ready to revert to an older OS in order to troubleshoot, any help appreciated.

That screenie includes a 60 sec in-game benchmark to show the GPU at 100% load and 300MHz. So weird.

The latest Win10 driver causes my card to ID as an engineering sample as well. It's not writing that info to the bios, it's just that the driver is responding with different information to queries. Not sure about your other issue, my 290x lightning has not had the same problem.

 

[crashtech]

Thanks for the input, at least there is one less thing to worry about. I have 10074 on there now and have reflashed the GPU BIOS one more time. Testing will have to wait until tonight.

 

[crashtech]

Well now it seems stuck at 300Mhz for good. I suppose I am gonna have to load 8.1 and see what happens.

 

[crashtech]

It's a problem with Windows 10, as far as I can tell. I found my old 8.1 drive and threw it back in:

Too bad. I liked Windows 10 better than 8.1, but this problem is a bit of a deal killer. Certainly it will get fixed, but in the meantime, 8.1 it is.

Thanks for the help, all.

 

[LTC8K6]

Did you ever benchmark it to see if it was actually running slow?

 

[crashtech]

Oh, yes. That's how it all started. I couldn't believe how low I was having to set things to have a playable experience. Then I saw benchmarks in the twenties that had been nearly one hundred before. Whatever happened, it was real.