• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Display driver stopped responding

well i don't have any asus junk on my machine. i have a gigabyte mobo but still have the same problem. i might consider whacking 2.2v through my ram. although it's been perfectly happy with 2.1v so far (2x2gb kit). :)

i'm not disabling aero. the vista basic theme is fugly.... and windows classic is even worse. :(
 
Maybe nothing......

Easiest way to explain.......

As you push more volts through ram you can eventually get diminishing results, The voltage slowly kills the ram meaning you need to apply more voltage to get ram back stable or at worse working at all

Maybe nothing to do with the ram volts, But always where/when possible run ram at lowest voltage you can

Ciao

Def
 
I dont really see much difference!

well i do. :p

anyway, how long have been running multiple screens. surely you must have been ok in the past with previous drivers? or have you always had problems? as i mentioned, i only got dual screens a few weeks back and have the same problems with the 8.4s/8.5s. haven't tried the 8.6s admittedly. i fear i will be wasting my time anyway. :(
 
well i do. :p

anyway, how long have been running multiple screens. surely you must have been ok in the past with previous drivers? or have you always had problems? as i mentioned, i only got dual screens a few weeks back and have the same problems with the 8.4s/8.5s. haven't tried the 8.6s admittedly. i fear i will be wasting my time anyway. :(

I have been running dual/triple monitors for a while, but i've just recently upgraded my machine and moved to vista 64bit at the same time. I have had this problem since the I got the new system up and running about a month ago. I tried the 8.6s and the problem still occured in the same way.
 
Just to follow this up, I havent had the atikmdag error occur since i disabled the aero theme.

well balls to that. i'd rather ditch my 2nd screen than go without aero. shallow as i am, vista basic/classic is just too damn ugly to use everyday. :p

anyway, i've just upgraded my 3850 to a 4850.... time to plug in my 2nd screen and see if it affects this card too? i hope not.....:)
 
Id rather go back to classic before i traded down from triple/dual monitors!

well as i mentioned earlier, i never intended to use a dual monitor setup. it's only because my old monitor is too crap to sell that i've tried it. :p

i can imagine this is quite frustrating for those who need a multi monitor setup..... :o

Im interested to know if this error still occurs with the new 4800 cards on dual monitors.

i'll post back in awhile once i've tested mine. i don't have much faith at the moment though.......
 
I've been getting this with Crysis its been doing my head in!

I quickly concluded that the '175.19_geforce_winvista_32bit_english_whql' Drivers sucked and went on to download the '177.40-vista-32-bit-[Guru3D.com]' Drivers.

No more issues......... for the moment!
 
I've been suffering badly from this..

Everytime I try to view a video the screen freezes.. goes black and then I get a BSOD.
Everytime!!!

I now cannot play any games or watch any videos on my machine.

This was happening a few weeks ago so I figured I'd reinstall Vista..

Still has not fixed the error.

Upon booting I too am getting funny coloured sections and symbols on POST.. kinda makes me wonder if this is actually a MB issue.
Oh and I get loads of wonderfully coloured pixels all over the screen too..

I'm going to be building a new machine within a fortnight.. unless I wait for i7.. but atm this is giving me a massive headache.
 
Does the error get forced with people here upon playing Crysis gpu_benchmark on a high detail?

This might help people

Seem to be suffering from the same problem - XP might be calling.
 
Last edited:
Taking out a stick of RAM has completely fixed it for me (like a lot of other people). Now have only 1 stick of 2gbs - lost about 5-10fps on all games as far as I can tell plus loading time takes a lot longer. Bit niffed....
 
I was getting this issue in Vista when my card was dead, it wouldn't play any games at all. You would launch a game, and within 5 minutes it would boot you to desktop with this error.

I took my GFX card round to a mates house who runs XP and it just BSOD his machine after 5 minutes in a game (pixels and stuff as well yet I didnt get the pixels on vista), So XP does not handle the broken hardware as good.

This error imo means something in your hardware is about to die or at least something is stuggling.

My poor 8800GTX :(
 
Get my new 64bit operating system today (currently running on a 30day trial vista 32bit) so will install that and give it a try - dont think it will though.

Aero doesnt appear to be the cause of the problem but just causes the problem to be worse because of the enhanced graphics needed to run it. Those that have "mild" errors to start off with can usually fix them with disabling aero - but those that have major problems (crashing as soon as you enter games) usually cant be fixed by aero or the msconfig "cpu/memory quantity" fix.

Might be something to do with the north bridge being stressed if it can be fixed by removing memory etc...

what did you do with your 8800gtx wizzkidy?
 
Last edited:
I was getting this issue in Vista when my card was dead, it wouldn't play any games at all. You would launch a game, and within 5 minutes it would boot you to desktop with this error.

I took my GFX card round to a mates house who runs XP and it just BSOD his machine after 5 minutes in a game (pixels and stuff as well yet I didnt get the pixels on vista), So XP does not handle the broken hardware as good.

This error imo means something in your hardware is about to die or at least something is stuggling.

My poor 8800GTX :(

Not always, for some they run flawlessly in XP, for myself it was moving from VGA to HDMI (sounds bizarre but it's worked and when I accidentally yanked the VGA cable out it invoked the stupid error, also constantly changing screen setups sometimes BSOD'd for me, now with my new PC TV over HDMI this never happens and I switch profiles on screens constantly to play games on the big screen), BIOS update reduced the frequency when I got it massively, newer drivers etc.

I think it's a very generic error which does not necessarily mean it's 100% the GPU, just like BSODs are quite generic and anything really can cause them, there is no 100% sure reason.
 
Back
Top Bottom