Sapphire Radeon HD 6850 is screwing me over. and over again.

[MyBrains]

Originally Posted by CoreyPL

Still, his computer wouldn't crash and that is what is happening. Plus he also had crashes in windowed mode.

It was just a thought

[ludde06]

Originally Posted by connta

change your ram.

it is a) faulty b) incompatible with mobo c) dunno why but its a memory thing

it is not ati issue, same thing happened to me some time ago and really screwed me over ended up going from ati to nvidia just to have nvidia drivers report the same exact thing, changing even the mobo to find out it were ram modules (that were as in your case in a brand new comp)...

the issue is really ****ed up cuz it logically points you to the gpu (which i guarantee is not making the issue), when i had it it was 1200Mhz ddr2 modules on P45 mobo and setting them to 800Mhz really helped and thats how i figured out it was memory related so go and try something similar i bet it will work.


P.S. latter on i encountered some conclusive posts on couple of forums that "driver has stoped working but is recovered" is almost always a memory issue.

This does seem possible since it crashes more frequently when alt+tabbing, but just 2 questions;
1) If I'm buying new RAM, what type/brand do you recommend? Mine are currently at 1333 MHz.

2) How do I set them to a lower speed?

Edit: Oh by the way, ran memtest for 2 hours, and it showed no errors. Might be running it over night aswell just to make sure..

[CoreyPL]

Originally Posted by ludde06

This does seem possible since it crashes more frequently when alt+tabbing, but just 2 questions;
1) If I'm buying new RAM, what type/brand do you recommend? Mine are currently at 1333 MHz.

2) How do I set them to a lower speed?

Edit: Oh by the way, ran memtest for 2 hours, and it showed no errors. Might be running it over night aswell just to make sure..

I have Kingston HyperX 1600MHz CL9 DDR3 - one of the cheapest DDR3 i could find actually No problems with it running at 1600MHz.

You can lower the speed in BIOS. Just take them from auto and adjust speed accordingly. But if your memory is running in agreement with the specification, you shouldn't lower the speed - maybe just for the test.

It is important to set all parameters of the memory that are given by the manufacturer - speed, voltage, timings. If you don't set them by hand they will probably use SPD settings which will set RAM according to JEDEC specification for DDR3.

[connta]

Originally Posted by ludde06

This does seem possible since it crashes more frequently when alt+tabbing, but just 2 questions;
1) If I'm buying new RAM, what type/brand do you recommend? Mine are currently at 1333 MHz.

2) How do I set them to a lower speed?

Edit: Oh by the way, ran memtest for 2 hours, and it showed no errors. Might be running it over night aswell just to make sure..

dont immediately go for new ram solution, im sure you have a buddy with ddr3 setup that you can switch your ram with for a week and see if it helps, then you will also have your recommendation for purchase of new ram

in my case it was Geil that caused the issue, top of the line too next one, OCZ Reaper worked flawless, used some kingston for a while since reapers went to rma once also worked normally... some friends also had issues with Geil so i guess dont go with them but all this is my experience that very easy will not apply to your situation... you will not know until you try unfortunately...

and dont bother with memtest, mine didnt show anything either for 24h testing time... actually no test revealed the fault and i did a lot of them, whole agony lasted a month for me

Originally Posted by CoreyPL

You can lower the speed in BIOS. Just take them from auto and adjust speed accordingly. But if your memory is running in agreement with the specification, you shouldn't lower the speed - maybe just for the test.

It is important to set all parameters of the memory that are given by the manufacturer - speed, voltage, timings. If you don't set them by hand they will probably use SPD settings which will set RAM according to JEDEC specification for DDR3.

as said, look for your memory settings in bios... i recommend leaving everything about memory on default/spd/jedec settings and only change the frequency for testing... im not sure hows that going to play out since i never tangled with ddr3 and im not sure if setting it lower is possible or is it going to do any good in your case...

sadly all i have to conclude is that you have to change your memory and use it for a while before you will be sure it works for you... if your memory is new go to the retailer and ask him for a change, explain your problem and you might surprise on the help you get... hopefully

[ludde06]

Originally Posted by connta

dont immediately go for new ram solution, im sure you have a buddy with ddr3 setup that you can switch your ram with for a week and see if it helps, then you will also have your recommendation for purchase of new ram

in my case it was Geil that caused the issue, top of the line too next one, OCZ Reaper worked flawless, used some kingston for a while since reapers went to rma once also worked normally... some friends also had issues with Geil so i guess dont go with them but all this is my experience that very easy will not apply to your situation... you will not know until you try unfortunately...

and dont bother with memtest, mine didnt show anything either for 24h testing time... actually no test revealed the fault and i did a lot of them, whole agony lasted a month for me



as said, look for your memory settings in bios... i recommend leaving everything about memory on default/spd/jedec settings and only change the frequency for testing... im not sure hows that going to play out since i never tangled with ddr3 and im not sure if setting it lower is possible or is it going to do any good in your case...

sadly all i have to conclude is that you have to change your memory and use it for a while before you will be sure it works for you... if your memory is new go to the retailer and ask him for a change, explain your problem and you might surprise on the help you get... hopefully

Will try with other RAMs, but starting to look like a memory-issue more and more... When playing the game windowed now, I got the usual screen-freeze and then it got black. Luckily, I got back to windows, and recieved an error saying;

ERROR #132 (0x85100084) Fatal Exception
Program: C:\Program Files (x86)\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:006FA0D3

The instruction at "0x006FA0D3" referenced memory at "0x00000004".
The memory could not be "read".

This looks like there's something wrong with the memory, yes? Or is it just me wanting it to be faulty memory, so i can feel like the issue is solved?

[connta]

does not have to be faulty at all, it just does not agree with your motherboard... another batch of same ram could have different chips on them and behave normally...

the root of your issue is in the message "display driver has stopped working and has recovered" that comes after black screen... every other message you get from the application in question is caused by that issue which is caused as i believe by incompatible memory...

theres a sea of topics with this issue, just type "display driver has stopped working and has recovered nvidia/amd" on google and you will find endless topics about ppl changing cards, moding registry and what not (same as i did) and no one having any definite answer or solution (since its not gpu related and thats where 99% of ppl look), consider your self lucky if you havent already wasted a lot of time on this and get some memory to test...

[CoreyPL]

Originally Posted by ludde06

ERROR #132 (0x85100084) Fatal Exception
Program: C:\Program Files (x86)\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:006FA0D3

The instruction at "0x006FA0D3" referenced memory at "0x00000004".
The memory could not be "read".

This looks like there's something wrong with the memory, yes? Or is it just me wanting it to be faulty memory, so i can feel like the issue is solved?

Yep, this points to RAM fault. Try to run your PC with only 1 stick of RAM at a time. If RAM has physical fault, chances are 1 stick is good. If it is compatibility error, this probably won't help, but also won't hurt.

[ludde06]

Originally Posted by connta

does not have to be faulty at all, it just does not agree with your motherboard... another batch of same ram could have different chips on them and behave normally...

the root of your issue is in the message "display driver has stopped working and has recovered" that comes after black screen... every other message you get from the application in question is caused by that issue which is caused as i believe by incompatible memory...

theres a sea of topics with this issue, just type "display driver has stopped working and has recovered nvidia/amd" on google and you will find endless topics about ppl changing cards, moding registry and what not (same as i did) and no one having any definite answer or solution (since its not gpu related and thats where 99% of ppl look), consider your self lucky if you havent already wasted a lot of time on this and get some memory to test...

I thank you deeply. I do consider myself lucky, since 2 weeks isn't a lot of time when comparing to people having the same issue for months.

Also, CoreyPL, I tried to run it with only 1 stick of RAM (testing both sticks individually), but the problem persists.

The only thing now is that I don't know what RAM to get, to make sure it's not failing with my mobo. Seems like it's not supported with 1600 MHz, so should I get 1333 Mhz or 1066?

Anyhow, I really appriciate the time you guys have taken to help me out, and hopefully (crossing my fingers) it will turn out to be solved with the memory-replacement.

[connta]

physical fault on the ram should be detected within 2 hours of memtest he already did... also physically faulty ram really makes the system unstable, he should be BOSDing left and right...

but hey, trying something is always useful if nothing than to rule it out of the equation...

edit: you posted while i was writing good luck man and test that ram before you finalize the purchase if possible

[ludde06]

This might just be stupid to ask, but ran memtest each stick individually again, and I just have a quick question;




Is it anything out of the normal in the memtest picture? Should the memory be running at 584 MHz, and isn't it a DDR-3? (noting the DDR-1 in the picture)

Just got a little second thoughts, that maybe it is the motherboard or whatever causing trouble... Anyhow, I'll try to ask some friends if I can borrow their RAM-sticks just to try out for a while, but if I cant, I'd like to be almost 100% sure that spending 90$ on new memories will help.

[connta]

no, should be running at 667 and also your CAS table looks ridiculous to me 2.5-1-0-5 (it must be some reading error or something i doubt that settings would boot at all), shouldn't it be more like 7-7-7-16? as i said i never really handled ddr3 memory but really there isn't much difference, its still same ddr1 with more passes per clock, higher frequency and lower power... anyway, you should really revise your bios and your memory settings before doing anything, dont know did you overclock and how you did it but 584Mhz is not a "rounded" frequency it seems as custom set... maybe load bios defaults and go from there ,change only the frequency to 1333 or 667 depends on the bios, leave everything else on default...

Originally Posted by ludde06

Anyhow, I'll try to ask some friends if I can borrow their RAM-sticks just to try out for a while, but if I cant, I'd like to be almost 100% sure that spending 90$ on new memories will help.

even the planes are falling from the sky, nothing is really 100%... find a way to test before you buy beyond that advice i cant help...

[Black_ice_Spain]

just one thing.


wow gives ram fault for every error in a PC.

Try winXp, if it works, its the GPU, like for the other guys i know.

[ludde06]

Originally Posted by connta

no, should be running at 667 and also your CAS table looks ridiculous to me 2.5-1-0-5 (it must be some reading error or something i doubt that settings would boot at all), shouldn't it be more like 7-7-7-16? as i said i never really handled ddr3 memory but really there isn't much difference, its still same ddr1 with more passes per clock, higher frequency and lower power... anyway, you should really revise your bios and your memory settings before doing anything, dont know did you overclock and how you did it but 584Mhz is not a "rounded" frequency it seems as custom set... maybe load bios defaults and go from there ,change only the frequency to 1333 or 667 depends on the bios, leave everything else on default...




even the planes are falling from the sky, nothing is really 100%... find a way to test before you buy beyond that advice i cant help...

Never really changed any memory-settings in BIOS. Although I did start up CPU-z, and it showed the memory as 668 MHz and 9-9-9-24. So I guess the memtest-info must be misleading?

Edit: okay found where to change it, and I changed the clock speed to 1066 MHz. Going to see if this gives any improvement

Last try will be to install win XP then, just to exclude the GPU. If that doesn't help, I'll buy new ram-memories and hopefully i'll come to peace with this.

[connta]

trust cpu-z, all is well with your memory settings

go with xp theory even tho im not sure how a gpu that performs on one system and not some other is faulty... maybe vista/7 call some power managment functions or something, worth a try...

[ludde06]

Originally Posted by connta

trust cpu-z, all is well with your memory settings

go with xp theory even tho im not sure how a gpu that performs on one system and not some other is faulty... maybe vista/7 call some power managment functions or something, worth a try...

Yeah might be skipping that XP after all... Changed clocks to 1066 MHz, and ran 3Dmark11. Came a bit further than yesterday, and instead of freezing, I got the regular black screen and then came back to windows. There I got an error message saying "3DMark11 has stopped responding something something".

This do indeed seem like memory related, since I remember using a bad RAM in an old system. As soon as I would open an application I got the "stopped responding"-box.

[giri.placid]

Originally Posted by ludde06

Hi,

2 weeks ago I bought a brand new computer, and the graphic card I chose was Sapphire Radeon HD 6850 1 GB, which seems like a big mistake.

Ever since I assembled the computer I've had issues when trying to benchmark or play fullscreen games on it (mostly world of warcraft). The screen turns either black and a "input not supported" box is jumping around on my monitor. When this happens I have to do a hard restart.

The weird part about it is, that the same game with exact same settings, runs often fine in windowed mode. Only when I installed catalyst 10.11 windowed mode also crashed, so I jumped back to 10.10e.

The other scenario is when the screen freezes / turns black, i hit windows logo + L and If I'm lucky the screen wakes up and shows the log-in screen. When I log in again, I get the message "AMD graphics driver stopped responding and was restored".

I've been troubleshooting and trying everything I could think of and a little bit more. I have:
Installed latest drivers to everything, and tested different graphic drivers.
Used Memtest86+ showing no errors,
Disabling windows aero (thought it would work, since fullscreen actually worked for a while, but then the crashes came when i rebooted the system) <-- this was also interesting, because when It worked fullscreen I had only the original drivers, not any version of catalyst. Unfortunately this didn't work the next day.

I haven't got much hair left on my head, so please help me!

The reason I'm not RMAing the card, is because I'll have to wait for the reseller to test it (which takes 2-3 weeks) and if they don't find any hardware errors i'll have to pay them 50$ for the testing.

Hey, This is a driver bug. My PC is brand too, its about 3 weeks old. I had this problem (No Signal + Stutter Sound) after playing with the afterburner settings. I had to underclock the card to 500/700 and it stopped crashing. Then I uninstalled 10.10e and re installed it and it gamed fine (Crysis Warhead) even at 850/1150 at 1.172V. I have no I idea wtf is going as now the problem is back only when MLAA is used. This is crappy drivers IMHO. 10.12 made things worse by bringing the crash to few seconds.

My RAM is overclocked, CPU is overclocked and undervolted. GPU is just wierd.

[ludde06]

Okay just tried with a friend's RAM, runs perfectly fine.

I'll go and buy new sticks tomorrow then, thanks everyone

[connta]

told ya

btw before buying stick with the switch for a week to be sure its really resolved also chances are your ram is going to work normally in his comp and vice versa...

[alexpap10]

I have exactly the same problem...was it solved with the new memory?Thanks in advance..

[mduffman25]

Hi new to these forums. I picked up the sapphire radeon hd 6850 1gb off newegg about a week ago and ever since i've been unable to view youtube videos without a horrendous amount of waiting due to buffering issues. My previous video card was a radeon hd 5450 and this card experienced 0 trouble with the same videos. I know for a fact my card is better than the last because it plays anything i want on full specs. please help

[mduffman25]

Need solutions, my sapphire radeon 6850 doesnt play youtube videos for anything. but my previous graphics card a 5450 play them flawlessly. Now it takes 3 hours to buffer a 10 min video

[Pill Monster]

You sure it's the card? Buffering is related to internet....do you have hardware acceleration enabled in your browser?

[mduffman25]

Originally Posted by Pill Monster

You sure it's the card? Buffering is related to internet....do you have hardware acceleration enabled in your browser?

Well I haven't had any problems with anything else. Besides Youtube everything is flawless. Neftlix buffers like a rocket so it has to be.

[Pill Monster]

Originally Posted by mduffman25

Besides Youtube everything is flawless. Neftlix buffers like a rocket so it has to be.

Well then it should be fairly obvious the problem lies with YouTube....