View Full Version : Display driver nvlddmkm stopped responding - GTX260
Ghosthunter
07-27-08, 11:11 PM
Ok i got this message tonight for the first time while playing Age of Conan twice
It happened really fast, when it happened it look like my screen was going to crash, everything froze and for a quick second i saw a tons of red dots all across the screen and then the screen went to normal.
I was like WTF.
I went to my desktop and temps seemed to be normal according to rivatuner hardware log
So I looked in event log and I saw this message twice right in a row but in between there was in a windows defender message that it found some problem with cpu-z. No idea if that was the cause
Is this a sign of a card going bad? I am using 177.41 drivers for Vista 64. Have not had any problems since I put the system together about 3 weeks ago and been playing AoC since
For now i totally disabled windows defender, i do not need that i have Nod32 anyway
Thanks
here are the exact messages in the event viewer
Event ID 4101
Display driver nvlddmkm stopped responding and has successfully recovered.
Lfctony
07-28-08, 01:01 AM
http://www.nvnews.net/vbulletin/showthread.php?t=86550
You can't troubleshoot specifically, just mess around and hope it's fixed...
Ghosthunter
07-28-08, 02:55 AM
great..so i guess it is not a bad card then..some weird driver vista issue
Badboy_12345
07-28-08, 04:59 AM
for me it has been heat related on my 8800gtx
The card and the standard cooler cant take the heat.
It was the same last summer
The only other thing you can do is buy an aftermarket cooler or downclock the card during the summer.
Lfctony
07-28-08, 05:31 AM
Sometimes it can be caused by the drivers as well. The worst thing about these errors is exactly that. The error is always the same, but the cause is always different. Others have had it from faulty cards, other from bad ram, others from system incompatibilities of a sort, others from unstable Nvidia drivers. The only way to make sure your system is not at fault is run a Windows XP installation side by side with Vista. If your system is rock solid in XP, then it's very likely that this error is because of drivers or a weird conflict.
For example, I have a WinXP x64 installation with my current system that is, until now, error free. My Vista installation is also, error-free. Yesterday, I installed the 177.73, which caused this error within a minute in Crysis. Rolled back to the 177.41s and ran the timedemo for 90 minutes without error...
Conclusion: The 177.73 are an unstable set of drivers for my system. For you, they might work perfectly...
Tony.
nekrosoft13
07-28-08, 08:43 AM
there are many factors that can cause this error.
temps
card
driver
game
software config
os issue
other hardware issues (memory, board)
sometimes can be quite hard to troubleshoot. lucky i only had this issue in early 07 with first set of 8800gtx drivers.
Ghosthunter
07-28-08, 11:33 AM
thanks for suggestions i ran memtest overnight and no erros showed up so that is a good sign that it is not memory
i am thinking it is Age of Conan i bet that game is buggy as hell
nekrosoft13
07-28-08, 11:37 AM
Age of Conan is buggy, very buggy. Does it happen in any other game?
Ghosthunter
07-28-08, 11:41 AM
i have not played any other game i been so addicted to AOC
I guess I should try maybe I will play Crysis or COD 4
that would be a really good test to at least know if it driver related or the card
nekrosoft13
07-28-08, 11:44 AM
for temp or card, load up furmark and let it run for about 2-3 minutes.
keep rivatuner or evga precision tool in the background to minitor the temps.
Ghosthunter
07-28-08, 01:45 PM
well i played about an hour of COD 4 no problems but will try that furmark
Ghosthunter
07-29-08, 12:05 PM
ok i ran furmark for 5 minutes it never went past 86C according to rivatuner and it never crashed
So i think the card is ok right?
so far I played Age of Conan all night last night and it only crashed once when i went to alt tab to check one thing, and boom it BSOD, i guess it does not like to go into window mode
other then that it seems to be running ok
I played COD4 again and it never crashed, so it must be just AoC
Thanks for all your help
nekrosoft13
07-29-08, 12:08 PM
also you can try the new driver 177.79 that was released today.
Maybe it will help with AoC, but most likelly AoC is just buggy.
It has been confirmed that AoC is a piece of ****. It's an 8 year old proprietary 'rebuilt' engine, what do you expect?
DreamWorld Engine
The DreamWorld graphics engine was developed by Funcom circa 2000. Other computer games powered by DreamWorld technology include Anarchy Online and its various expansion packs. When Funcom began developing Age of Conan: Hyborian Adventures, the company reviewed its existing technology base and decided to focus on the further evolution of their proprietary DreamWorld engine as opposed to licensing a third-party engine like many online RPG companies do. As such, Funcom began to retool their engine with the overall design, pipeline and implementation process was taken into account. In light of these changes, the DreamWorld engine has been rebuilt for Age of Conan: Hyborian Adventures with new features, special effects and optimizations.
LORD-eX-Bu
07-29-08, 07:53 PM
when I was having this problem with my 8800 gts I was told to RMA the card. Took care of the problem.
DarkOneX
07-31-08, 02:01 AM
when I was having this problem with my 8800 gts I was told to RMA the card. Took care of the problem.
Same here, had that problem so bad with my first 8800GTS that I couldn't even get into Winodws all the way without it happening so I RMA'd it and that one worked perfect and has for the 7 months I owned it.
------------------ATTENTION: IMPORTANT POST-----------------------------
I think I have the solution to your problem cuz I had similar problems with my new XFX GTX260 XXX. Try DISABLING the RIVA TUNER. Because I had no crashes or red dots since I stopped running the EVGA-Tool which also starts some kind of Riva Tuner Program when its running.
Hope that solution works for you too. Good luck ;)
Ghosthunter
08-11-08, 10:03 PM
actually updating my driver to 177.79 fixed this problem
I waited a while to update this beucase wanted to make sure
I am really impressed with this driver set, not only did it fix this problem, but gave me a nice FPS increase in AOC and fixed my downclocking problem in another thread as well
Thanks everyone for the help here, i love nvnews.net forums here rock great help here =)
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.