13 Feb
Posted by i.nconspicuo.us as Tech/Web
So after installing Windows Vista, I’ve been getting the following error occassionally: Display Driver Stopped Responding and Has Recovered. Sometimes my system will freeze for a little while then the screen will go black and reappear, sometimes the screen will just go black and come then come back up. Either way, when the screen comes back up, the Windows Vista Aero theme is no longer enabled – all window transparency is gone.
I’m starting to wonder if my video card just doesn’t have enough juice to hack the Windows Vista Aero theme – 256MB PCIE 7300GS card should be able handle it though, right?
Has anyone else encountered problems with the nvlddmkm nVidia driver?
Display driver nvlddmkm stopped responding and has successfully recovered.
Okay, I haven’t found a fix yet, but my computer has been running perfectly lately. Knock on wood. Only occassionally, will I start it up and see little dots all over the login screen – this is when I know that I might as well not even login because Windows Vista will just hang, freeze, and or Blue Screen.
Be sure to check out the nvlddmkm display driver solutions at this dedicated website.
366 Responses
CyberCT
February 21st, 2007 at 3:45 pm
1Same thing is happening to me.
So annoying, and I have tried everything I can think of.
Dave Hobbis
March 3rd, 2007 at 5:38 am
2I am having the same prob when using a Fusion TV tuner card or playing MPG2 files in WMP (under Vista 32). It sure looks like an Nvidia driver bug.
James Snell
March 12th, 2007 at 9:44 am
3I’m having the same problem. It seems to be co-incident with security prompts (allow or continue). Maybe it can’t handle the flash when UIC kicks in.
Still looking for a solution.
i.nconspicuo.us
March 12th, 2007 at 4:57 pm
4I just read a couple posts that suggest that it could be a problem with the video card not having enough on board memory – I really don’t think this is the problem however, because Vista runs fine on my office computer with 128MB of video RAM, and my home PC is the one having the problem with 256MB of video RAM.
It appears that it’s not only the nVidia driver that is having a problem –
Display driver igfx stopped responding and has successfully recovered
Has anyone found a solution yet? Whether it be for nVidia, Intel or something else?
Arpad
March 15th, 2007 at 1:44 am
5YES, I FOUND A SOLUTION.
I suffered from the same problem (nvlddmkm errors) for month.
I have a pc with
AMD ATHLON64 X2 4600+,
3GB DDR400 RAM,
s939 NFORCE4 SLI mobo,
GEFORCE 7300GT graphics card.
The problem appeared after I pushed more than 2GB RAM into my mobo and I dared to set it to its own 400MHz RAM speed. When I pulled out 1GB ram or the 3GB ran 333MHz speed everything was fine. First I did not know which part of my computer caused my problem. My mobo, not being able to deal with more than 2GB RAM or the graphics card. After I read a lot of forums I realized that they have one thing in common: All who suffer from the nvlddmkm errors HAVE some kind of GEFORCE GARPHICS CARD. So I decided to buy a card HAVING A NON-NVIDIA CHIP ON IT. I chose Sapphire Ultimate Radeon x1950pro card.
Believe it or not THE PROBLEM DISAPPEARED!!! It cost me 250USD but it is worth the money. It flies!
So, it’s nvidia who causes the problem no doubt, NOT MICROSOFT AND WINDOWS VISTA!!! And not Intel or AMD! It seems Nvidia is unable to write a correct driver for the new operating system.
Arpad from Hungary
Arpad
March 15th, 2007 at 2:01 am
6I FOUND A SOLUTION.
I suffered from the same problem (nvlddmkm errors) for month.
I have a pc with
AMD ATHLON64 X2 4600+,
3GB DDR400 RAM,
s939 NFORCE4 SLI mobo,
GEFORCE 7300GT graphics card.
The problem appeared after I pushed more than 2GB RAM into my mobo and I dared to set it to its own 400MHz RAM speed. When I pulled out 1GB ram or the 3GB ran 333MHz speed everything was fine. First I did not know which part of my computer caused my problem. My mobo, not being able to deal with more than 2GB RAM or the graphics card. After I read a lot of forums I realized that they have one thing in common: All who suffer from the nvlddmkm errors HAVE some kind of GEFORCE GARPHICS CARD. So I decided to buy a card HAVING A NON-NVIDIA CHIP ON IT. I chose Sapphire Ultimate Radeon x1950pro card.
Believe it or not THE PROBLEM DISAPPEARED!!! It cost me 250USD but it is worth the money. It flies!
So, it’s nvidia who causes the problem no doubt, NOT MICROSOFT AND WINDOWS VISTA!!! And not Intel or AMD! It seems Nvidia is unable to write a correct driver for the new operating system.
Arpad from Hungary
i.nconspicuo.us
March 15th, 2007 at 5:33 pm
7Wow… I had thought about buying a new (non-nVidia) video card, but I didn’t want to fork out the extra cash until I knew for sure. The only thing that puzzles me is this: I have an nVidia video card in my office computer and there are no problems with it on Windows Vista… any suggestions?
Dono
March 17th, 2007 at 9:33 pm
8LOL. Or you could just want for Nvidia to release an updated driver. I’m not that impatient that I’m going to throw away a perfectly good video card
Carly
March 19th, 2007 at 12:31 pm
9It isn’t anything to do with Nvidia graphics card I’m using 256mb memory ATI Radeon card and I’m having this error! Only just started after using Vista for around a month not using any other programs to usual.
i.nconspicuo.us
March 19th, 2007 at 11:30 pm
10You can’t have the same error with an ATI card – nvlddmkm is an nVidia graphics driver, isn’t it?
Am I wrong here?
Nvidia Windows Vista Driver Update - Will it Solve nvlddmkm Driver Issue? | i.nconspicuo.us
March 21st, 2007 at 11:36 pm
11[...] Check out my previous article on the nVidia / Windows Vista nvlddmkm driver problems: Display Driver Stopped Responding and Has Recovered – nvlddmkm nVidia Driver [...]
i.nconspicuo.us
March 21st, 2007 at 11:59 pm
12Updated driver has been released… works for me so far:
http://i.nconspicuo.us/2007/03/21/nvidia-windows-vista-driver-update-will-it-solve-nvlddmkm-driver-issue/
Carly
March 22nd, 2007 at 9:01 am
13Yes the error I had is slightly different as relates to a different driver of course, however I am very sure this is not an error caused by the graphics card or drivers as many people with many different graphics cards are having a similar problem. The problem is windows vista not sure what’s wrong but it is, I had been using it for 2 months without and problems (graphics related at least) and all of a sudden I had that error no new software/drivers caused this as nothing had changed on my system. What I did to solve it was restored vista to the very earliest point it had – one good thing about vista is you dont have to set them yourself if you dont want to it seems to create one whenever a program or updates are installed. It didn’t work straight away but when I turned my pc on again the next day the error had gone.
David
March 23rd, 2007 at 10:43 am
14For me it is exclusively an Nvidia problem. I swapped out my 7800 GTX for an older ATI card and the problem goes away completely but its no where near as powerful so I just deal with it until I have the extra cash to grab a new ATI card. This is in Windows Vista as well. I must say it happened in XP with the Nvidia card as well though.
Atleast with vista it has a chance to recover (small but it happens), It never did in XP.
nunzio
March 25th, 2007 at 6:40 am
15FIX!!!
Install and install only the original Nvidia Vista drivers 96.33 from http://www.guru3d.com, section Download.
Hi.
i.nconspicuo.us
March 26th, 2007 at 12:29 am
16This article will solve your problems:
http://i.nconspicuo.us/2007/03/21/nvidia-windows-vista-driver-update-will-it-solve-nvlddmkm-driver-issue/
Cory
March 30th, 2007 at 4:56 pm
17Well guys, I have had the same issue on a new PC I just got with Windows Vista. The issue I am having is that when I run World of Warcraft, the symptoms show, but during normal use, the system is fine. When I play World of Warcraft, the screen goes completely black for about 5 seconds and then goes back to the game. I have an Intel graphics card that came with my laptop.
Caleb
April 8th, 2007 at 12:28 pm
18If it helps the conversation, my computer is 3 days old with an Intel graphics card, and it gives me the error message only when the computer wakes up from sleep mode.
i.nconspicuo.us
April 12th, 2007 at 6:56 pm
19Do you get the same nvlddmkm error? Or is it a different error?
ssaine
April 25th, 2007 at 11:46 am
20hello,
intel Q6600 Quad at 2.4
2GB @800
Nvidia 8800 GTX driver 100.65
Vista 64 Bit Ultimate
I never had the problem for almost a month now, I was trying to change the background to the anamated one which you can download if you have ultimate (Windows DreamScene). this is where the error messege started. change the backround to normal wallpaer and restart the pc every thing is fine.
I have no idea if it’s the driver or Vista or The 700 USD graphic card. hope there is a real solution for this problem.
Display driver stopped responding
May 7th, 2007 at 2:40 pm
21Hi there my computer is an Dell Inspiron 6000 and when ever Im playing on my sims 2 game it comes up with ‘Display driver stopped responding’ . It just comes up randomly through out the game. Is there anything anyone can tell me I can do for it?! Even if its buying software? Just anything ! thankyou
xx
i.nconspicuo.us
May 7th, 2007 at 3:34 pm
22That’s exactly what was happening to me… I don’t know what changed, but my system has been running stable ever since I installed the most recent Nvidia display driver package.
George V
May 14th, 2007 at 12:07 am
23I had the exact same problem (on my loaded system) and solved it by replacing my old 550w Q-Tech psu with a new 750W Silencer. So I think it all comes down to powering up your system properly.
Moobs
May 29th, 2007 at 9:48 am
24I have a similar sounding problem (same symptoms) using an ATI Radeon X1650 under Vista 64,
Cartephilus
June 3rd, 2007 at 7:23 am
25I just solved the same problem. In my case it was defective memory. I replaced the Mushkin XP2-8500s with Patriot 8500s and not a single video problem since.
i.nconspicuo.us
June 3rd, 2007 at 8:12 am
26That’s funny… my problem has completely subsided since I installed the latest release of the nvidia driver set.
billy
June 7th, 2007 at 10:33 am
27i have Intel graphics and have the same problem
GamerPro
June 22nd, 2007 at 11:09 pm
28well i recently bought a PC package that comes with an on board Intel chip and its been working great but i only recently recieved this error. This isnt just Nvidia, its something thats troubling all gfx cards alike. My personal believe is that this is due to Vista still being new and still has a few kinks where graphic cards are concerned. Either Microsoft will fix this with a patch or the Graphic Card companies will. Untill then we’ll have to be patient. The reason for older graphic cards working is due to the fact they do not require as much attention as the new gfx cards do. Thus if you have an older card i believe it will work fine with Vista.
jaxx
July 4th, 2007 at 4:01 am
29I have a ATI X700 and the same problem.
I found this link
ATI Support
It’s sad actually…
WhirmWhood
July 11th, 2007 at 3:11 pm
30I bought my pc on 06-25-07 brand new and updated it with a better vid card (geforce 8600 gts) and just started getting the error on 07-10-07 I did just install new updates last night 07-10-07 but have no idea if that has anything to do with it
i.nconspicuo.us
July 11th, 2007 at 8:07 pm
31My computer had been running completely smoothly for awhile (though I had this error before) but I did notice that one particular set of windows updates (I can’t remember which ones) cause the error to become more prevalent. I ended up doing a system restore and the error really seemed to subside.
It’s got to be a conflict with windows drivers and nvidia display drivers
jaxx
July 12th, 2007 at 9:57 pm
32oh man .. turns out vista is not the problem .. and the drivers are not the problem … it was simply the hardware… my video card cooler was failing and the card crashed from the heat.. I put on a new and bigger cooler and now all my games run smooth in vista..
i.nconspicuo.us
July 13th, 2007 at 12:48 pm
33Really? Do you think that everyone who is having this problem does not have enough cooling power on their video cards?
My case is very well ventilated, I can’t imagine that this is what is causing the problem for me… especially because of the fact that I get this error right when I turn my computer on sometimes.
Tlaca
July 21st, 2007 at 12:36 am
34i dont think is that i have a very cold room and my pc is always opened and was having the same problem now is fixed i dont know for sure what fixed the problem but my computer was restarting after getting this error and i was getting it as soon as i was in the main window so i got into the bios and changed all agp settings i just changed them to auto so you could try doing that, i will try setting stuff one by one to see what’s causing the problem and will let you know guys
jon the horrible
July 24th, 2007 at 4:56 am
35I have the nvlddmkm.dll driver has stopped working and recovered error too
tried going down to 1 stick of ram, not the problem, tried changing bios clocks to underspec my ram as it is sold, no fix
also tried all the latest 3 sets of nvidia drivers and beta driver, no fix!!!
I get it about 2 seconds after pretty much any game starts
My card does seem to get hot just before it happens and if l let it coool sometimes i get liek 20 seconds of gameplay on eg Lost Planet Extreme DX10, but also the same running it in DX9 mode, please help, I built this awesome rig and cant use it lol
Spec
Core 2 duo E6600
Gigabyte GA-965p-DQ6 rev 1 mobo
8gb OCZ DDR2 (4×2gb)
X-Fi Fatality sound
ELGWretched
July 24th, 2007 at 5:20 pm
36Hope this helps guys. Its not a sollution, but atleast its something.
http://forums.nvidia.com/index.php?showtopic=31913
Send the TDR error with your system info to this address:
https://surveys.nvidia.com/index.jsp?pi=7498eac864dc1950c8f09e040b4a437a
mick
July 24th, 2007 at 11:44 pm
37I recently bought a ASUS notebook F3 series and it has a intel graphics card…when ever i got to play my game world of warcraft, the screen continuesly blackens for like 5 seconds and then a message pops up saying ‘display driver stoppped responding and has recovered.’ not any of that ‘nvlddmkm’ stuff. no idea what may cause it… please help!
keep in mind:
- It us a laptop
- I dont use nvidia
- I use vista
- I play a game that demands decent computer parts ie: good graphics card
- It is a new ‘laptop’
jaxx
July 27th, 2007 at 9:38 am
38No man, I’m not saying everyone has a cooling problem, I’m just saying it’s not software related (drivers,os), it’s rather a hardware issue. In XP the pc would freeze, in vista you get that error. That’s it..
Dennis van der Pool
August 4th, 2007 at 11:01 pm
39It is definitly software related… I got a laptop, never got any BSOD or any problem, after switching to Vista it came… I solved problem on my laptop by disabling powermanagement in BIOS (ACPI & APM)… I still have the problem on my main desktop machine… I’m still trying to figure out how to solve it…
SAM
August 5th, 2007 at 3:51 pm
40I have the New Dell XPS with the ATI X1800 on Vista and I am also getting this error when I am trying to render in 3d.. has anyone found a solution for the ATI??
david
August 15th, 2007 at 1:30 am
41It happens with Vista and XP
It happens with Nvidia Cards and ATI cards
It happens with Nvidia based mobos and Intel and others.
It is related to overheating but will happen when a system is cold.
It happens in 3d intense apps or it can happen when browsing or just scrolling down a list.
Changing drivers, turning off Aero in Vista, downloading latest Microsoft updates, turning fans up 100% all may seem to fix it temporarily for some, but then it returns.
Some people say they have fixed it by adding more cooling to the chipsets and downclocking RAM.
kevin
August 16th, 2007 at 1:49 pm
42i had my ram overclocked and was getting the same error. set my ram to default clock speed and timings and it doesn’t happen anymore.
evga 680i mobo
evga 8800gts 640mb
ocz reaper 9200 ddr2 2gb
Stephen
August 19th, 2007 at 11:14 am
43Ok. What’s the deal here? I see…like…30 posts here of people with the same problem and NO TECHNICAL SUPPORT yet that can fix it??!
This really bites. Same error when running WOW on my NEW XPS M1210 laptop from Dell. Running Windows Vista and the 945GM intel chipset…igfx, etc. Sometimes when running in-game, as long as the graphics don’t get too complex, it seems the error subsides slightly. When the scenery changes to something more dramatic (like looking around quickly while running) I get the black 3-5 second screen, then pops back on. When I exit the game, there is an error repeated for each blackout that occurred, stating igfx display driver has stopped responding and has recovered. I do notice ALOT of heat coming from the side vent and it happens also when I run second life.
Hey, Dell! Microsoft! Intel!! HELP!!!!
Stephen
August 19th, 2007 at 11:20 am
44Here’s a thought: changing out components that may generate less btu’s may lead you to believe that the new install was the problem when it actually might be the FAN. Bummer that some people paid hundreds of dollars more for a less patient solution. I’m merely speculating. I was hoping the geniuses in the Silicon Valley might have offered some cognative relief by now.
Pat
August 26th, 2007 at 2:30 pm
45I have the same symptoms Cory, new comp with Intel display driver and troubles with WOW. Any fix?
Dennis van der Pool
August 27th, 2007 at 12:24 pm
46I installed the latest beta driver from Nvidia, problem is finally solved!!!
I used 3 different drivers before, but this one solved the problem.
The one i currently use:
NVIDIA ForceWare Release v163.44 for Windows Vista 64-bit (BETA) (August 20, 2007)
ken
September 2nd, 2007 at 1:04 am
47same issue, new laptop, intel video card. it wont play any 3d intensive game without doing it. turning on software mode made it go away, but not every game has that anymore
Bizkitfoot
September 2nd, 2007 at 7:53 am
48I don’t know if this is still an active forum, but….
http://support.microsoft.com/kb/938194
windows already released a hotfix.
gMsCoTT
September 2nd, 2007 at 11:18 pm
49Finally some kind of solution. But anything that will work with Vista 32-Bit?
Bite
September 27th, 2007 at 8:27 am
50Hey got the same problem. Crashes when playing a game.
I tryyed the update. no go.. It told me update not needed..
Hmm it didn’t say anything about
system 32. just 64.
So, this is new to my system. I did just add 2 more gigs. Making it a total of 4gig. Hahah.. and Vita says i have 3.25gig.
But, in BIO it says i got 4gigys in there.. I trust the bios for sure.
I have a single 8800 ultra. and when i run 3Mark06. In the results i get a 320Mhz and it should be 630Mhz.
It says to update the driver….. I have a few times..
http://www.nvidia.com/object/winvista_x86_163.69.html
Who to beleve….. Quite the pulzz with these computers….
Maybe i should try Bios update…
AMD25000 asusmobo 4gig 8800ultra Vista
Michael
September 30th, 2007 at 11:53 pm
51I’ve had same problem with ASU 7900GT TOP and now MSI 8800GTS 640MB OC.
The video card is faulty. take it back.
wander
October 3rd, 2007 at 1:09 am
52I now know why I had this problem.I didn’t have have a sufficient power supply.The confusing thing was the driver only failed if I was playing a game that needed the disc.Seems my old power supply couldn’t run my new graphics card and the rom drive at once.
i.nconspicuo.us
October 11th, 2007 at 10:11 am
53I just installed some updates for Windows Vista yesterday and the problem came back. My computer had been operating perfectly or the past 4 or 5 months… no problems at all. The latest set of windows updates caused absolute chaos. My machine wouldn’t even boot… it’d get to the logon screen with all sorts of rainbow noise on the screen, then it would blue screen and restart.
So once again, I’m at a loss as to what to do… any suggestions? I downloaded the latest NVIDIA graphics drivers, but haven’t yet had a chance to install them.
Dennis van der Pool
October 11th, 2007 at 11:58 am
54I still use the NVIDIA ForceWare Release v163.44 for Windows Vista 64-bit (BETA) (August 20, 2007) driver, works for me, sometimes i get the error message, but not that much that i’m going to try updating the display driver…
Dennis van der Pool
October 11th, 2007 at 1:44 pm
55I just installed “NVIDIA ForceWare Release v163.69 for Windows Vista 64-bit (WHQL) (September 18, 2007)” to give it a try, i’ll let you know when i have my first crash
No news = good news…
tom
October 15th, 2007 at 6:57 am
56I have the same problem, however i do not think it is anythik to do with your graphics cards because i have the latest NVIDIA 8800GS with the latest driver software and i still get the same error message. i think its a problem with VISTA!
i.nconspicuo.us
October 16th, 2007 at 9:31 am
57Could the problem be the power supply? For the most part, this error has subsided for me, however, occasionally, I’ll get the nvlddmkm error after installing Windows updates – any ideas on that?
Noirriver
October 21st, 2007 at 12:29 pm
58Hi guys,
Basically after not being able to run Planet Extreme for more than a few minutes or World in conflict…Now I’ve been playing so far for 3 days with no issues (fingers cross)
I read everything from driver, DX10, temperature and voltage related, etc…and for me nothing was working
But after tinkering with this for a few days …(I think) the issue appears to be related (at least for me) with the Nvidia driver setting for “Textures” and “Adjust image setting with preview”.
Running with 163.69, without even reinstalling drivers etc…
so I haven’t gone for the ‘fine tuning’ yet …
I have:
“Adjust image setting with preview” : Let 3D application decide (yes, for me some times even just asking the driver to show the preview would make it crash!!!)
“Manage 3D settings” (Global settings): main thing here is around “Texture” management.
- Texture filtering (TxF) – Anisotropic: Off
- TxF – Negative LOD Bias: Clamp
- TxF – Quality: Performance
- TxF – Trilinear optimization : Off
-
You could play with these setting more… I was just happy that I was able to play without crashing
But (at least for me) it appears to be “Texture” management related…
Bets of luck!
E6850, 4GB ram, Vista Ultimate, 8800 GTX XFX
Blackdaze
October 21st, 2007 at 2:55 pm
59The card is not faulty… Vista and nvidia’s driverset is faulty…
john
October 26th, 2007 at 12:49 pm
60Just purchased last week from best buy a Compaq Presario PC SR5250NX with Vista. I also purchased a new HD Monitor at the same time. Right out of the box I soon found the same exact problems. Also, when typing in my web search box, letters in my words are always missing. But this typing problem only happens on my AT&T Yahoo home page. No problem when using MSN or excite for a home page.
Omni^
November 10th, 2007 at 7:17 pm
61I just got my vista box up a few weeks ago, and I was planning on getting an 8800gt for it, but since I have a LAN coming up I decided to throw my old x850xt in it so I could take advantage of my e6750.
At the same time as I did this, I also put in my last stick of ram (4th one, I had three in before) which I had taken out to let a friend borrow for diagnosing his system.
When I tried to play some games, I got this problem. Also, I can’t even change the resolution in my copy of Company of Heroes without it giving me some crap about having an old version of DX9 (I have the most up-to-date one). I don’t know if they are related, but it’s very irritating.
I guess I’ll see if taking out the stick of ram I added helps… That would be a strange thing to have happened, but I guess I better try everything.
Noirriver
November 11th, 2007 at 3:30 am
62Hi guys, as mentioned on previous post sit has to do (at least for a few of us) between the CPU and RAM freq….just make sure they are 2:1 and the problem will go away.
I.e.:
- If your preocessor is running at 1333 then RAM should be at 667.
- If you have RAM running at 800 either underclock it to 667 or overclock your processor to 1600 to keep the ratio clean.
This definetly works for NVidia chipset MB.
The issue is not temperature nor voltage issue but rather a MB-Vista-BIOS-Driver combo…
Give it a go and see if it also works for you.
E6850 (running at 1600 not 1333)
4GB Ram (Running at default 800)
XFX 8800 GTX (no OC)
Asus P532-SLI
JAXX
November 19th, 2007 at 11:59 pm
63@ any ppl with issues..
but a new video board
@ i.nconspicuo.us
“Really? Do you think that everyone who is having this problem does not have enough cooling power on their video cards?”
no you dumb ****.. I was suggesting you to search for any hardware problems before you blame it on the software..
your sistem is obsolete so if you want vista buy any NEW video board that supports directx 10
and STFU
BenF
November 22nd, 2007 at 9:22 am
64Well…I read just about every post, but very few seam to relate directly with my problem…so here is my situation, and hopefully someone can help.
My specs:
Biostar TForce 6100-939 mobo
AMD Athlon 64 3500+ 2.2 ghz.
NVidia GeForce 7600 GT (256 mb onboard)
2 Gigs of RAM
250 Gig SATA HardDrive
My problem:
It is November…thanksgiving to be exact. I have been using Vista for probably 9 months now. I never…NEVER had a “Display Driver stopped working…” message before until I booted up my computer this morning. I have numerous cooling fans and the machine had been sitting since yesterday. It was not hot and had not been used. Now, not only did I get that message (which led me to do a search and thus I found this message board) but now when I type, letters keep missing or not showing up. I have to look at every letter on the screen in this comment box to make sure they are showing up. I never had to do that before. I do not have a wireless keyboard and my plug is snuggly connected. No new apps have been downloaded. The only thing that I did recenty was system updates that were prompted by Vista…but that was a couple of days ago. I have used the computer since then, before today, with no problem. I am going to try playing a game (Flight Sim X) to see if it has any problems doing that. I will check back here to see what suggestions I might get. Should I restore my system to where it was a couple of days ago, before the updates…or what should I do? Thanks!
BenF
November 24th, 2007 at 8:02 am
65I had this problem happen to me the other day…and that was the first time it has happened to me and I have been using Vista for over 9 months. My Windows Vista Experience Index score is 4.2, but that is only because of my relatively weak processor (2.2 ghz single core). My graphics is rated as a 5.9 and my gaming graphics as 5.5. My unit is well ventilated with numerous cooling fans. This message came up the other day right when I turned the computer on, when the computer was still cold.
Here are my specs:
AMD Athlon 64 3500+ 2.2 ghz. cpu
Biostar TForce 6100 939 mobo
2 gigs of RAM
XFX GeForce 7600 GT Vid. Card with 256 mb. onboard memory
250 gig SATA HD.
I have not added hardware to my system at all since I built it at the beginning of this year. I have not added software expect for the system updates that Vista prompted me to add. The most recent set of updates was done about 2 or 3 days before this message came up.
Can someone please tell me what might be causing this, aside from a cooling issue, which it is not with my computer?
Thanks!
Blackdaze
November 24th, 2007 at 8:27 pm
66I hate you Micro$oft… you have now cost me hundreds of dollars because of this crap…
So, I was getting the nvlddmkm error that all the rest of you are getting and thought it may be due to memory speed. So I contacted OCZ and asked them if they had any suggestions. Of course they said I should first update my motherboard firmware to the latest version before troubleshooting. I had FW 1.4, and I noticed that 1.5 came out last week, so I went to update it. In the middle of the FW flashing process in windows nvlddmkm stopped responding and the machine BSOD’d. Now my motherboard is now completely worthless. There goes $200 for a new motherboard, not to mention that I’ve already replaced the video card twice, and memory once… This has cost me over $600… So, I decided to go for the new intel G35 chipset in hopes that this nvlddmkm error will cease if I leave the nforce chipset behind… I’m not optimistic, however…
One word of advice… don’t flash your firmware in windows if you are getting the nvlddmkm errors… I hate you Microsoft…
Partechie
November 25th, 2007 at 1:28 pm
67Well, in MS defense..yYOU are the mildy stupid one for flashing BIO in WINDOWS..ALWAYS…ALWAYS do it from dos. Either from a bootable floppy or bootable CD
StrEagle
November 27th, 2007 at 3:50 pm
68Disable from BIOS the Intel (R) SpeedStep (TM) Tech. under Advanced -> Configure Advanced CPU Settings. Worked for me.
I couldn’t play Company of Heroes for more than 2-3h before the video driver stopped responding, now after the disable I just did 8h straight run..
Got P4 Quad, 4GB 800MHz Corsair DDR2, XFX GF8800 Ultra 768MB, ASIS 5PKC with Intel chipset, X-Fi Pro Gamer, Windows Vista Ultimate 32bit. All latest drivers, including forceware 169.12.
I Hate Errors
November 27th, 2007 at 5:26 pm
69I am having an error that keeps occuring, particularly when I am playing World in Conflict, and particularly when a game starts. The comp will freeze up, constantly replay the sound that was playing when the comp froze, and then the screen goes black for about 5-10 secconds. when the screen comes back to life, it says “Display driver nvlddmkm has stopped restonding and recovered”. I have an XPS system with a Nvidia video card. I have tried installing new drivers, and the Nvidia hot fix, but neither worked, although the hotfix seemed to fix the error the day I installed it.
OH MY GOD!!! PLEASE HELP, THIS ERROR IS THE MOST ANNOYING ERROR I HAVE EVER SEEN ON A COMPUTER!!!
FatalDelay
November 30th, 2007 at 8:25 am
70I’m getting the error on a Vista PC with a built-in Intel video card, so I doubt it’s related to Nvidia drivers. Rather, I think it’s a Vista issue that’s related to when the computer comes out of sleep mode. I’ve disabled sleep mode altogether and don’t seem to be getting the error anymore.
Dennis van der Pool
November 30th, 2007 at 1:57 pm
71Yeah, i had the same problem on my laptop (nvidia card though). I just disabled sleep mode. I seem to got rid of the problem on all of my machines…
CodeCrackerx9
December 3rd, 2007 at 9:59 pm
72This is a TDR issue (Timeout Detection and Recovery)
it is an issue with windows vista TDR system.
TDR is designed to detect when your display driver is or your video card is about to crash or freeze. It then resets the display driver and allows you to continue working without having to restart.
there is many reasons why your video card could be freezing, so power or a faulty card or issues with the dirvers (which there is still TDR issues with nvidia drivers and the next release will fix many of them!)
for more info, click here http://forums.nvidia.com/index.php?showtopic=31913
Things to do to help lessen the frequency of TDR related issues:
1) UPDATE YOUR CARD’S DRIVERS!
2) Update the game and/or vista
3) Disable desktop composition and visual themes for any game related issues
4) Turn off TDR in vista click here to see how. (not recommended if your card is freezing due to heat or power issues) http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
Hope this helps!
eddyz
December 12th, 2007 at 6:58 pm
73Ok – same nvlddmkm error occurs on my 3 week old Dell 1520:
Core 2 Duo T7250 (2.0 GHz)
2046 MB
GeForce 8600m GT w/ latest driver as of today.
Vista Home Premium 32 bit w/ latest updates as of today.
Stock Dell laptop.
I haven’t played any games on this system and I’m getting this error. I think it’s happened specifically when the system comes out of sleep mode. Kind of reminds me of the Windows98 system I had that would crash coming out of sleep mode. Disabling sleep mode solved that Win98 issue; has Dennis VdP pointed us in the right direction?
How does it work when M$ has a set of power mgmt instructions and the manufacturer installs a set of power mgmt instuctions also?
jay
December 13th, 2007 at 10:07 am
74The problem is with nothing but driver. Vista has been long having problems with proper driver signing, and if it installs 4 u the latest driver for your OWN graphics card, you not too far from getting fooled. Install the driver that came with ur system board (if ur using onboard VGA) or otherwise with the driver that came with your off board graphics card.
Blake
December 18th, 2007 at 7:22 am
75We’ve got a lot of points of failure here.
I’ve got a desktop running Vista Ultimate 64 whose Windows Experience Index whines that memory is too slow (3GB@ 2 x 1.5, dual-channel enabled). If I set the memory timings tightly to EXACTLY what the RAM manufacturer says is the most stable with MY SPECIFIC MOTHERBOARD, FOR VISTA, Vista won’t boot at all. I have to let it be “Auto” so Vista can tune the memory as it pleases. And whine about it being too slow.
This machine, by the way, has an ATI card. And crashes and does awful things in-game.
Vista does at least some graphics writes directly to graphics memory, bypassing the CPU; I have this from Microsoft people who demo’d the concept at the Vista Launch event. Whether non-Microsoft programmers know how to deal with a system that’s hitting graphics hardware from two places at once, or whether Microsoft writes their graphics calls in a way that doesn’t bump heads with other people’s software, is unknown by me.
I have a very high-end laptop that has 4GB of RAM. By coincidence, they only shipped me one video card (I ordered two), so I had a couple of weeks to game on a single card configuration and had no problems. Once the second card was in place and SLI enabled, I not only had to turn off Aero (or I’d only get a black screen), I’ve also had every single game crash on me regardless of how I tune the settings or what variation of SLI I try.
I suspect nVidia’s drivers for mobile SLi are unstable–I wonder why they’re typically only available directly from the manufacturer, and nVidia won’t even host them?
I suspect Vista’s cute little graphics tricks are a potential problem.
I can see that memory management is screwy–look at how many people can’t go over 3GB. Or how my “Memory speed” went up when I put in the second card–is Vista lumping mobo RAM with Graphics RAM? Does it then lump ReadyBoost RAM in the same bucket and ignore the fact that they exist at separate addresses? ‘Cause gods help us if it does.
Blake
December 18th, 2007 at 7:35 am
76We’ve got a lot of points of failure here.
I’ve got a desktop running Vista Ultimate 64 whose Windows Experience Index whines that memory is too slow (3GB@ 2 x 1.5, dual-channel enabled). If I set the memory timings tightly to EXACTLY what the RAM manufacturer says is the most stable with MY SPECIFIC MOTHERBOARD, FOR VISTA, Vista won’t boot at all. I have to let it be “Auto” so Vista can tune the memory as it pleases. And whine about it being too slow.
This machine, by the way, has an ATI card. And crashes and does awful things in-game.
Vista does at least some graphics writes directly to graphics memory, bypassing the CPU; I have this from Microsoft people who demo’d the concept at the Vista Launch event. Whether non-Microsoft programmers know how to deal with a system that’s hitting graphics hardware from two places at once, or whether Microsoft writes their graphics calls in a way that doesn’t bump heads with other people’s software, is unknown by me.
I have a very high-end laptop that has 4GB of RAM. By coincidence, they only shipped me one video card (I ordered two), so I had a couple of weeks to game on a single card configuration and had no problems. Once the second card was in place and SLI enabled, I not only had to turn off Aero (or I’d only get a black screen), I’ve also had every single game crash on me regardless of how I tune the settings or what variation of SLI I try.
I suspect nVidia’s drivers for mobile SLi are unstable–I wonder why they’re typically only available directly from the manufacturer, and nVidia won’t even host them?
I suspect Vista’s cute little graphics tricks are a potential problem.
I can see that memory management is screwy–look at how many people can’t go over 3GB. Or how my “Memory speed” went up in the WEI when I put in the second card–is Vista lumping mobo RAM with Graphics RAM? Does it then lump ReadyBoost RAM in the same bucket and ignore the fact that they exist at separate addresses? ‘Cause gods help us if it does.
CodeCrackerx9
December 18th, 2007 at 8:34 pm
77I have fixed all of my TDR and vista/nvidia driver issues with the new beta version of there forceware drivers. if you have a laptop, i highly suggest going here http://www.laptopvideo2go.com/forum/index.php?showtopic=16542 to download display nvidia display drivers to fix this issue. it worked for me.
Blake
December 20th, 2007 at 6:44 am
78I second that, CodeCracker, with the caveat that if you can’t find the mobile drivers directly from your specific manufacturer, for your specific model, this would make a good second bet. Sager/Clevo have fixed the problem for their units, and also gone the extra mile and applied Windows SLI hotfixes to the systems they ship. Thank goodness.
(P.S.: Sorry for the apparent double-post above–not intentional)
John Smith
December 20th, 2007 at 9:11 pm
79Any updates on this ? I was told by a DELL tech that their most recent XPS 720 series has ‘fixed’ this problem (don’t know how).
I was about to buy a new PC but this nvidia driver thing has been holding me off, and it doesn’t seem to end soon..
Appreciate your thoughs,
Blake
December 21st, 2007 at 11:53 am
80Dell’s support is harmful to your health, but they do have good tech forums. You might want to stop by, look up your model, and see what actual customers (and some Dell employees) have to say–I’m sure if they’re still experiencing the problem, they’ll be talking about it in the forums…
CodeCrackerx9
December 22nd, 2007 at 12:50 pm
81john smith
many issues relating to this post have been fixed with the new nvidia beta drivers. it is a specific fix listed in the release notes that deals with compatibility issues with new games and there hardware. so you should be able to buy with confidence from dell.
good luck!
Y
December 28th, 2007 at 1:16 pm
82I too have this problem, (Compaq Presario SR5210NX) and believe it must have something to do with Vista. I am currently searching for a solution. Yes, extremely frustrating!
lisa
December 29th, 2007 at 10:20 am
83okay guys just got new dell pc. don;t know anything about gaming but this happens when i’m play solitaire the pre installed version. This has to be a vista problem. Nothing has been loaded on my computer or downloaded it just did this straight out of the box.
Godfail
January 2nd, 2008 at 3:01 am
84ReadyBoost is a paging file stored on removeable media…so it’s not even possible to be in the same “bucket”.
You’ve got a lot of baseless suspicions there and it sounds like you’re not doing any research…
Godfail
January 2nd, 2008 at 3:03 am
85It’s a driver issue, and it’s happening to XP machines as well.
Krell
January 4th, 2008 at 9:06 pm
86The ATI forums are filled with angry customers with the same error whilst using Radeon cards. Nvidia is not at fault. Running the same cards under XP works flawlessly. The only consistent variable is Vista…
dois
January 9th, 2008 at 8:39 pm
87vista 32-bit
8800 GT in SLi
happens only when I’m playing Company of Heroes which I’ve just bought.
halp
Charles
January 14th, 2008 at 11:05 am
88On a Dell laptop, I started getting the error while switching to my monitor display. I changed the resolution to a higher (highest setting on a 19″) and the problem (“Display driver…”) went away.
Who is Jason Roberts?
Paul Trively
January 15th, 2008 at 5:59 am
89It’s amazing, the first instance of this that I can find appeared almost a year ago. It’s just frustrating when you spend $3000 on a machine and it doesn’t work as well as a $250 Wii.
Dell is being nice and sending me two new graphics cards (even though I doubt that’s the problem), but hey, who am I to complain.
It started very suddenly for me (I’m guessing it was on a patch Tuesday) and has progressively gotten worse. It’s now to the point that it’s even doing it while browsing. I thought it could be a heat related issue, but surely, all of these people couldn’t be overheating.
I’m running a Q6600, dual 8800GTX with Vista Premium.
~P~
Edie
January 17th, 2008 at 11:51 am
90I had this same problem with my new Dell laptop. After spending 3 days online with a dell rep who tried everything he could think of including downloading the newest driver version, he had the computer replaced for me. After I downloaded the newer driver the computer was ok for a few hours of use then the error message occured again and after that happened every few minutes.
jack0022
January 18th, 2008 at 7:19 am
91I have had my laptop for 4 months now with no problems. (Vista Home Premium, Nvidia, 2gb RAM).
I’ve never had this problem until yesterday after installing Dreamscene (similar to Deskscape).
I dont know if any of you have now installed this software, or use Deskscape, but I think thats what initialy caused my problem.
John
January 18th, 2008 at 12:19 pm
92Yeah I just had a HD corruption, so I replaced it and decided to clean install Vista Ultimate…. now the problem occurs for me after a period of time playing CoD4.
If this means my dual 8800GTX cards are f’d…. I’m gonna get a tad annoyed. No way I’m spending any more money on this computer – Vista has been a money sink so far.
ran
January 23rd, 2008 at 11:04 am
93what you are writing is not true, i have a lenovo think center with an intel graphic carda and i’m suffering from the same problem. it appears that nvidia is not the cause for the problem
Helper
January 23rd, 2008 at 1:20 pm
94UPDATE YOUR .NET FRAMEWORK
Fixed it for me
Shane H
January 26th, 2008 at 6:02 am
95I have been getting the driver error also. Only when playing F.E.A.R. It seems to happen randomly, and I cannot “generate” the error no matter how high the graphics are tuned and what im trying to make it do during game play. I ran the game in 1920 X 1200 getting an average of 46 fps on extreme settings.
I have a customized Dell Inspiron 1720
Windows Vista Home Premium
Bios: Phoenix ROM BIOS Version 1.10 A02
Processor: Intel Core 2 Duo T7700 (2.40 ghz)
Ram: 2046
Video Card: Nvidia geForce 8600M GT with updated drivers
I know the card can handle the graphics, along with the computer. But after reading the above messages im starting to think it has something to do with Vista. Or maybe DirectX 10, since Vista is the only system to use it.
If anyone can offer real help that FIXes the problem, please email me at shane@rogem.net
Kevin
January 30th, 2008 at 3:57 am
96It is a vista issue not a driver issue. It happens on both Ati and Nvidia cards. Here are some solutions http://www.repairyourpcnow.com/resources/atikmdag-has-stopped-responding.php?comm_page=2#
or at
http://nvlddmkm.allofyourquestionsanswered.com/
Godfail
January 30th, 2008 at 4:03 pm
97It’s been proven again and again that this happens in both Vista and XP and that it’s not a Vista issue. Even the links you provided show that a true fix still has not been found.
matt
January 30th, 2008 at 4:13 pm
98your discription is my exact problem what did he replace your computer with? i am having these problems with my new dell laptop inspiron with a geforce 8600M GT, 2 gigs ram. what changes were made on the new one, running windows XP?
Blake
January 30th, 2008 at 4:16 pm
99I wish I could offer better solutions for all of you. Mine was simply a matter of waiting. New drivers for my video cards (dual 8700Ms) finally fixed the problem last month.
When I’ve had trouble before, I go through three paths. First is to try an earlier version of the nVidia drivers (I keep my drivers up-to-date, but sometimes a new release is not really ready for my machine). Second, I’ll try drivers from the hardware manufacturer–for instance in my case the maker of the machine did a better job making compatible drivers than nVidia did.
Third is Omega Drivers. They’re third-party rebuilds, so they’ll either be super-great for you ’cause they don’t contain things you don’t need…or they’ll be super-unstable and you might have to be savvy enough about Safe Mode to back your way out of them.
Regardless, the people who write Microsoft DirectX, the folks at nVidia, and the hardware makers really need to pull together to figure this one out.
alekourse
February 1st, 2008 at 4:16 pm
100Same prob, igfx, no solution found, still looking
ken
February 9th, 2008 at 10:23 pm
101I have had same problem for bout 2 mo, did everything from replace video card to complete sys restore. Finally found the problem. Its due to a bad memory stick, I have two corsair dominators at 1 g a piece. pulled one out and when i tried to turn pc on i got nothing so I swapped them and pc was ok, then tryed the dual swap again in the other slot and same thing occured. leaving me to the conclusion that the stick that wouldnt allow my pc to boot up was bad so i replaced the bad stick and all is well. no more display driver failure, you can tell its memory issue due to the randomness of the driver error. not only does it happen when i tried to play games, it would also occur when pc was idle. This is a definate pointer to a memory issue. so i would suggest everyone with this problem to check your memory and the diag test from bios is not enough to tell, you actually have to do it manually. questions or concerns kendogii@yahoo.com
Blackdaze
February 13th, 2008 at 6:37 pm
102@ ken:
I’ve had this problem for 8 months now… tried replacing the memory… 3 times. This is NOT due to a bad stick. It happens whenever you try to use more then 1 DIMM module. Any single DIMM will work, whenever you attempt to run a pair (or more) of modules, you will get this error. It is an issue with Vista memory managment and TDR (windows recovery). Don’t look for MS to correct this any time soon, even though literally hundreds of thousands of end users are encountering this error. The easiest fix is to go back to windows XP…
PsychoTim
February 18th, 2008 at 7:55 pm
103This problem makes me mad. I got it first when i instaled vista x64, vista worked for a couple of days without this happening, then suddenly the computer starts crashing every 5 minute. I try to instal vista x86 again, and everything works fine for 2 days, then it starts happening again, for no reason, no new software or anything, it just starts happening. Before i instaled vista x64 i had vista x86 on the system for months, had some sli probs and stuff but this never happend. New computer and stuff to. Q6600 2,4ghz cpu, 8800GTX SLI, 4gig pc2-8500 ram, nforce 680i motherboard. I had XP installed for a month or so, but i never had any problems there, with anything. My conclusion is that VISTA SUX!
Blake
February 20th, 2008 at 8:42 am
104Godfail, since the message ‘the display driver has stopped responding and has recovered’ is a Vista message, I’d like to see you post links where this is an XP issue.
Because I’m explicitly referring to my own experiences, there is no “baseless” to it. This is what I’ve learned, I’m trying to identify where connections may or may not be, your mileage may vary.
Instead of news flashes like, ‘it’s a driver issue’, and ‘a true fix still has not been found’, why not try swapping armchair judgement of the people in this forum for helpful links and useful information?
Updated drivers fixed my problem. Some people here are still having the problem. I’ll only post from here forward if I have something worthwhile to contribute. And I hope for all of you that a fix is found soon.
Blackdaze
February 22nd, 2008 at 2:49 pm
105Just phoned in to MS support. What a horrible experience… I suppose if I spoke with a thick middle-eastern accent I may have actually understood half of what they were saying to me. Regardless, after an hour on the phone I was eventually transferred to a “technician”, which I had to hold for for an additional 40 minutes (they said it would be a 3 to 5 minute hold time), before giving up and having to call back in, this time I was slightly less polite. After another 45+ minutes of holding and transferring I was routed to a tech (again). I explained the situation to the tech (Sam) and he was fucking clueless. It took 5 minutes before he actually understood the problem, he kept trying to fix my internet connection (which is working fine)… Once I got Sam on the same page we sat there for 5 minutes or so taking noted and (I assume) trying to find a solution. He found nothing… he kept suggesting I return my parts. I explained to him that I have already replaced all the parts… 3 times, and that the problem persists, but does not exist when the machine boots into XP. I explained that this is definately a Vista specific problem, and he had no suggestions or offered any solutions. He was dumbfounded… I asked him to escalate this issue internally and he said he would have an advanced Vista tech call me back within 24 hours (I won’t hold my breath). I will post more information if and when I get my callback. System specs are below:
Gigabyte P35 DS4 Motherboard
Intel Core2Duo E6750
2x 2gb Corsair Dominator (at 800MHz)
750watt PSU (4x +18A 12v rails)
XFX Nvidia 8800GT
Antec Sonata Case
Windows Vista Ultimate (retail) x64
Blackdaze
February 25th, 2008 at 12:21 am
106Microsoft was no help so far. They called an hour late and said they would have to call me back in 30 minutes. As if I have nothing better to do then sit around and wait on them… I had to leave and we had to reschedule the call. They will phone in tomorrow, but I’ve been doing some research of my own.
Windows Vista has a great “feature” for crash detection and recovery. TDR (Timeout Detection & Recovery) is attempting to reset the video driver under heavy load because it (due to poor code) thinks that the video driver is about to crash due to the length of time it is taking to process something, so, trying to prevent a blue screen, it steps in and basically bitchslaps whatever your active video driver may be. This is why both ATI and Nvidia users are affected. Driver updates are not likely to solve anything because this is a windows issue… Only an update from Microsoft can fix this.
The following is a brief overview of the TDR process:
1.
Timeout detection: The Video Scheduler component of the Windows Vista graphics stack detects that the GPU is taking more than the permitted quantum time to execute the particular task and tries to preempt this particular task. The preempt operation has a “wait” timeout—the actual “TDR timeout.” This step is thus the “timeout detection” phase of the process. The default timeout period in Windows Vista is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout, then the GPU is diagnosed as hung. <– first problem… we need to set the TDR timeout higher… say to 4 or 5 seconds….
2.
Preparation for recovery: The operating system informs the WDDM driver that a timeout has been detected and it must reset the GPU. The driver is told to stop accessing memory and should not access hardware after this time. The operating system and the WDDM driver collect hardware and other state information that could be useful for post-mortem diagnosis. <– wonderful… where this post mortem diagnostic information is stored is anyone’s guess at this point.
3.
Desktop recovery: The operating system resets the appropriate state of the graphics stack. The Video Memory Manager component of the graphics stack purges all allocations from video memory. The WDDM driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As mentioned earlier, some older DirectX applications may now render just black, and the user may be required to restart these applications. Well-written DirectX 9Ex and DirectX 10 applications that handle “Device Remove” continue to work correctly. The application must release and then recreate its Microsoft Direct3D device and all of its objects. DirectX application programmers can find more information in the Windows SDK.
So, how do we fix this? The TDR-related registry keys are located under HKLM\System\CurrentControlSet\Control\GraphicsDrivers.
• TdrLevel: REG_DWORD. The initial level of recovery. The possible values are:
• TdrLevelOff (0). – Detection disabled.
• TdrLevelBugcheck (1) – Bug check on detected timeout, for example, no recovery.
• TdrLevelRecoverVGA (2) – Recover to VGA (not implemented).
• TdrLevelRecover(3) – Recover on timeout. This is the default value.
• TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold. The default value is 2.
• TdrDdiDelay: REG_DWORD. The number of seconds that the operating system allows threads to leave the driver. After a specified time, the operating system bug checks the system with the code VIDEO_TDR_FAILURE (0×116). The default value is 5.
• TdrTestMode: REG_DWORD: Internal test usage.
• TdrDebugMode: REG_DWORD: The debugging-related behavior of the TDR process.
• TDR_DEBUG_MODE_OFF (0) breaks to kernel debugger before the recovery to allow investigation of the timeout.
• TDR_DEBUG_MODE_IGNORE_TIMEOUT (1) ignores any timeout.
• TDR_DEBUG_MODE_RECOVER_NO_PROMPT (2) recovers without break into the debugger. This is the default value.
• TDR_DEBUG_MODE_RECOVER_UNCONDITIONAL (3) recovers even if some recovery conditions are not met (for example, recovers on consecutive timeouts).
I’m currently tweeking some values and will report more tomorrow.
CodeCrackerx9
February 25th, 2008 at 9:05 am
107I have posted a while back that this is a TDR problem, and i have tried to tweak the TDR registry settings to see if that did help the problem. For some situations it might, but mine did not, if I wa to turn off the TDR detection or just ignore the the timeout, my system would freeze when playing games. So it would appear that the TDR was actually doing its job, so beware anyone who changes these settings, they may or may not help you.
However what did help me was downloading the newest Nvidia beta drivers form http://www.laptopvideo2go.com Nvidia and ATI are aware of this issue and even though this is a Microsoft problem, this issue can be fixed or at least worked around by the GFX card companies. So if the TDR tweaks in the registry do not help your situation, try downloading beta drivers.
Good luck to all!
baude
February 25th, 2008 at 1:41 pm
108If i get these freezes both in vista and xp it would be more likely to be a hardware problem?
CodeCrackerx9
February 25th, 2008 at 7:37 pm
109-Baude
yes if you are getting these freezes both in xp and vista AND the latest display drivers have not seemed to help, then there is probably a hardware problem. investigate both your video card and your memory, as those are likely to be the sources of freezes while playing games.
Good Luck!
St
February 29th, 2008 at 7:36 pm
110I am using a brand new Dell Tablet with the same display problem.
MOB KING
March 1st, 2008 at 4:53 am
111See if this will help u out http://support.microsoft.com/kb/938194/en-us
adgie
March 1st, 2008 at 11:27 am
112hi guys i had this same problem and it took me about a week of looking at forums and i never got anywhere but i found a fix that might be worth trying i cleard all my movies and games on to dvds as i was going to reinstall and i downloaded nvidia driver 169.25 and gpu-z.0.1.7 and i deleated the new nvidia driver and installed 169.25 and installed gpu-z0.1.7 and tried the games that were crashing and i havent had that anoying thing on my screen since oh my specs are
q6600
8800gtx bfg oc
4gig xms2 corsair 6400
zalman resinator v2 watercooling
antec 900 gamer case
samsung 2232bw moniter
creative extreme gamer sound card
creative t9700 7.1 audio
logitech g15 keyboard
logitech presision mouse
i think its worth a try i know everyones problem isnt the same but give it a try it might just work for you as it did for me
CodecCackerx9
March 1st, 2008 at 9:47 pm
113i agree with adgie, ever since i upgraded to nvidia beta driver 169.28 (which is very similar to 169.25 in architecture) i have not had a problem on my vista laptop. i have also tried using the 173.xx series and those work just fine as well. anything above the 169.25 driver did the trick for me. you can find these drivers on nvidia’s website or at http://www.laptopvideo2go.com
good luck!
Sager NP2090 (compal ifl90)
Intel Core 2 Duo CPU T7500 @ 2.20GHz
2.00 GB RAM DDR2 667
NVIDIA GeForce 8600M GT
Intel Wireless N
Seagate Momentus 7200.2 160GB SATA 7200RPM Mobile Hard Drive
15.4 1680×1050 Display
Broadcom NetLink Gigabit Ethernet
Windows Vista Ultimate
Genukie
March 18th, 2008 at 11:35 am
114SOLVED!!!
Its not your drivers, its not ur graphics card that is defective
Simply drop your settings if ur playing stuff that doesnt require dx10 for ex. Anti-aliasing etc … or keep it set on “Use Application Settings” so if the game is compatible with the extra features it can still utilize it. I think the error comes from trying to force certain features on a platform which is not compatible.
My RIG:
Q6600
ASUS P5WDH-Deluxe
4GB Corsair Dominators 800Mhz
2 x 2900XT
Samsung 46 inch LCD 1920 x 1280
I had the same issues tried just about everything, until i sat down and thought for a bit. Let me know if this helps… I know how u all feel that is why i posted this hopefully it can help.
Please let me know how it goes via email: Genukie@hotmail.com
CodeCrackerx9
March 18th, 2008 at 12:30 pm
115Genukie -
Thank you for posting your findings, but your solution is just a workaround. most graphics card settings are set to application preference by default and unless you use a forced preference on a game or app, it will not make the game or app use those settings. plus, many people still have problems that do not have to do with any games or apps running that would take advantage of any graphics card settings. some just crash on the desktop while doing nothing. and it is a workaround because those settings should never render a computer incapable of operating unless force settings are used.
although your findings are good may help some people, but the solution you are describing should not do what you claim, but i suppose it is worth a shoot. did you do anything else that may have helped out your situation? if you did, please post that here too, for i am curious. thank you.
Genukie
March 18th, 2008 at 9:11 pm
116Yeah maybe, i also went into msconfig and ticked “Number of processors” and unticked “Maximum memory” I had issues with any apps i was running…
But maybe im posting in the wrong area, as many of my friends who play WoW and Ragnarok who ran Vista had the same issues and this had resolved their issues.
Hopefully this issue will be resolved soon, as it was such a pain for me.
I found when i setup my custom settings on my gfx then launch different games the display drivers crash, so i thought this may have been the issue.
Dan
March 21st, 2008 at 9:59 am
117umm… lots of coloured dots, etc mean corruption in the GPU ram, most often this is down to damage to the components, not the driver
ohdannyboy!!!
March 23rd, 2008 at 5:25 pm
118my system
:Manufacturer:
System manufacturer
asus striker extreme motherboard
Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz
Memory: 4094MB RAM
Hard Drive: 148 GB
Video Card: NVIDIA GeForce 8800 GTX
Monitor: SyncMaster 226BW(Digital)
Sound Card: Speakers (SoundMAX Integrated Digital HD Audio)
Speakers/Headphones:
Keyboard: USB Root Hub
Mouse: USB Root Hub
Mouse Surface:
Operating System: Windows Vista™ Business (6.0, Build
I have spent all day today trying to get company of heroes running on my machine with all the patches installed (inc directx10). The game itself would run fine for atleast the very first mission but at start of second mission it would crash to desktop saying something about nvlddmkm has recovered succesfully. This required my pc to be rebooted each time, as it became near impossible to open even a desktop folder without it crashing again. It has only been through persistant digging via google about everyone having problems of the same caliber and trying all there solutions such as update graphics drivers (which i did to 169.25), checking windows updates etc etc. howerver i must admit i did not try all the take some ram out, lower ram speeds, use driver cleaners, change bios settings malarky…. all abit to complicated for my liking.
What i did find was a chap talking about nvidia beta drivers such as 169.44 and how it fixed the same issues but with crisis. As crisis uses directx10 capabilities i sorta thought it would be worth a try seen as my company of heroes is now patched up and running it. Low and behold so far for me i can safely say that uptill this point it has seen me get up to mission 3 of the game without crashing once. For me this is a vast improvement considering sometimes it wouldn even let me do the first half of the first mission.
hope this helps someone else.
daniel.
Tommi
March 26th, 2008 at 5:36 am
119The problem just happens when my video card gets too hot. So this is definitely related to heat for me. It happened when I was overclocking my old radeon x1900xt as well as with my new 9600gt with passive cooling. I’ve now enabled my 120mm fan at the back of my pc case which keeps the card cooler. Didn’t have any problems since then….
bigbirtha
April 2nd, 2008 at 10:21 pm
120its your ram you putts trust me the nvidia rendering issue is cuased by your ram trust me get diffrent ram i struggled with it for 6 months trying everything you guys wrote and now i have come to the conclusion it was my ram the hole time it doesn’t matter how much you got just what you are running
amd 6400 black
asus crosshair
8 gigs of muskin xp2 6400
1 t galaxy
cosmos s case
liquid cooled
2x xfx 8800 gts 512 xxx
enough said
Grant Edelsten (Brisbane PC)
April 8th, 2008 at 2:14 am
121Possible Solution. I suffered this problem every 3 minutes when using sketchup and found what appears to be a solution. Firstly, I have a quad core intel and 2 gig ram. crappy 8600GT nvidia card with 512k onboard. I was using 169.35 version of the graphics drivers (the latest official version). To fix I loaded beta release version 172.74 (I think) which appears to have resolved the issue. Interestingly though, (and this didn’t happen before) when I open Sketchup the system displays a message advising that the colour scheme has been reduced to basic. I can only come to the conclusion that the more advanced colour scheme (i.e Aero) was something to do with the problem. No guarantees and I haven’t tested this on any games but I hope this helps to lead to a solution.
Blackdaze
April 9th, 2008 at 11:30 pm
122“The Display Driver has stopped responding and recovered” error is simply a preventive BSOD. The cause for the BSOD could be any number of things… a stick of bad memory, faulty video card, CPU, or failing hard drive. It could even be a software or driver issue in some cases. This is why some people have fixed it using various methods and some others who have swapped hardware have also had success where others have not. Each case is unique and this TDR (timeout detection and recovery) feature only kicks in to save you from a bluescreen and losing all your work. In that respect it is actually a cool feature.
So… how do we fix it. Well… there is no easy answer for this unfortunately. The best thing you could do it to disable TDR in the registry to allow the stop error (BSOD) to happen naturally. The idea of allowing the BSOD to run it’s course it so that you can note the information within the blue screen trap. You can post the information on hardware forums or try to get Microsoft support to help you. Try process of elimination first. Run one stick of memory at a time. Clock everything down to stock. Test something that you know will crash your system and try to reproduce the issue.
If all else fails, write down the model number of your memory, motherboard, and video card and keep a txt file saved with your system specs. Make a new post in the support forums for each hardware manufacturer. I have open tickets with XFX, Microsoft (managment escalation), Intel, and Corsair. I have swapped everything but my processor at this point and that is next.
Zwaf
April 13th, 2008 at 8:55 am
123“Nvidia responsible for over 30% of Microsoft Vista crashes”
Was in the news lately.