View Full Version : Nvlddmkm stopped responding is getting VERY OLD...
I think it's a bit better with SP1, at least for me. I was testing a "soon to be released" game and i can say that i can play for 20-30 minutes before it crashes to desktop. PRE-SP1 was crashing after 10 minutes.
I think there is no "better".....
Better=problem solved
Same=problem persist.....no matter 10-20-30minutes...
$n][pErMan
03-22-08, 04:23 PM
I think there is no "better".....
Better=problem solved
Same=problem persist.....no matter 10-20-30minutes...
Agreed. I might get an ATi card... im tired of waiting on nVidia.
slaWter
03-22-08, 06:23 PM
[pErMan']Agreed. I might get an ATi card... im tired of waiting on nVidia.
True, this error is annoying as hell but DX10 isn't really needed. Most games offer similar visuals and performance in DX9. The X2 is nice but the GX2 is simply put faster, I really like the GX2 even with this driver bug, just like the GTX.
Well how about that. I've installed SP1, AND 174.70, and I had a nice 6 hour session and a 5 hour session on Company of Heroes, no crashes. I had also installed the latest game patch 2.300. However, it only started to gel together once I installed 174.70.
Sweeeet.
slaWter
03-25-08, 06:51 PM
That's great news yummy! I hope it stays that way.
$n][pErMan
03-25-08, 07:32 PM
That's great news yummy! I hope it stays that way.
Downloading now :)
http://www.dailytech.com/NVIDIA+Drivers+Caused+Lions+Share+of+Early+Vista+C rashes/article11261.htm
:thumbdwn:
Microsoft data shows NVIDIA caused bulk of Vista crashes
When Windows Vista first hit market, some driver issues were to be expected as hardware manufacturers moved existing components to the new OS from Windows XP. As is natural for new items, the enthusiast community was among the first to embrace the new operating system.
The incompatibilities were part due to Vista incorporating Microsoft’s DirectX 10 promising better graphics and physics in PC games. At the time, the high-end G80 graphics cards were some of the most popular graphics cards on the market including the NVIDIA 8800 GTS, GTX, and Ultra.
NVIDIA had driver problems with of Vista and DirectX 10 from the get go and delayed their first driver from a December 2006 release to a January 2007 release. Even once the driver hit market, there were wide spread reports of crashes because of NVIDIA drivers.
The problem with reports of buggy drivers is that no one can really tell if the drivers are actually at fault, or if the computer experiencing the driver crash has some other underlying problem contributing to the crash.
As part of the ongoing Vista Capable class action lawsuit, Microsoft released data on exactly what drivers caused the bulk of logged Windows Vista crashes. The number one culprit of Vista crashes related to driver failure was NVIDIA at 28.8%. Microsoft only broke logged crashes out for a few companies including NVIDIA, Intel (8.8%) and ATI (9.3%). Microsoft’s data shows that it was responsible for 17.9% of logged crashes.
The main early adopters of Vista were PC enthusiasts; the hardware of choice for PC enthusiasts at the time was NVIDIA G80 GPUs so it would be natural that more crashes would be logged as caused by a NVIDIA driver. Ars Technica also points out that the Microsoft data doesn’t specify if the crashes logged are from multiple machines or a group of particularly error prone computers experiencing multiple crashes.
[EOCF] Tim
03-29-08, 08:35 AM
Got somebody else from another forum with something that fixed it for him.
I got it fix finally, after several weeks of frustration.
All I did was took out the memory, switch their position: A1 to A2, A2 to A1
Played Crysis 90mins long, 3DMark06 2HRS long, The error gone for good now.
Thinking about it, I never had the problem, but from day one I've put my ram sticks in order, highest overclocking stick in the furthest away slot (nr4) and slowest one in the nearest to the CPU slot (nr1). It's got to do with PCB trace length apparantly. This allowed me to get higher overclocks, and might be the key to solving this?
That's great news yummy! I hope it stays that way.
Thanks, I hope it stays that way as well :)
Another 5 hour and 3 hour sesh, crash free.
Mussels
03-30-08, 06:46 AM
one of the common causes (But not for everyone, so dont start flaming me) is a faulty OC or unstable system.
Just because the NV driver gave the error doesnt mean its the CAUSE of the error - dreamscene caused me crashes for ages, and an update to dreamscene fixed that. Some other people i know had constant issues and blamed Nvidia, but it was all to do with his systems ram having a bad stick in the end.
so a lot of these results would be people with unstsable systems sending 5-10 reports a week evert time it crashes out a game, without the drivers being the actual CASE.
kenshin159
04-05-08, 09:18 PM
Get this in Crysis and in 3DMark06
Did not do it before on my 8800GT.
Asus P5b-E
nVidia 9800GTX
174.74 drivers
x-fi xtreme music
2 raptors in raid 0
3GB DDR2 800 G.Skill
any help?
kenshin159
04-06-08, 11:05 PM
Get this in Crysis and in 3DMark06
Did not do it before on my 8800GT.
Asus P5b-E
nVidia 9800GTX
174.74 drivers
x-fi xtreme music
2 raptors in raid 0
3GB DDR2 800 G.Skill
any help?
Solved it by going back and exchanging the unit for a brand new 9800GTX. I guess I got a bad card!
malachi1313
04-09-08, 02:20 AM
I dont know if this has been posted here or not because this thread is huge, but apparrently if your video card hangs for more than a couple of seconds it will reset. Well if you change this setting to 0 it wont do the recovery /reset of your graphics card causing the crash. Actually saw this over at rage3d. Here is the microsoft article:http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx gonna try it and see what happens..
edit: running vista ultimate 64bit and those keys aren't there. Im kinda affraid to add them too!
malachi1313
04-09-08, 02:26 AM
Ah heck I made a new reg word and added it....:captnkill: :captnkill:
slaWter
04-09-08, 11:50 AM
Did it help? What happens now if the card hangs for a few seconds?
ragingWS6
05-01-08, 02:18 PM
Did it help? What happens now if the card hangs for a few seconds?
Yeah, I got it for the first time on Vista x64 today while playing COD4. Went to a BSOD on it too.
$n][pErMan
05-01-08, 09:49 PM
I dont know if this has been posted here or not because this thread is huge, but apparrently if your video card hangs for more than a couple of seconds it will reset. Well if you change this setting to 0 it wont do the recovery /reset of your graphics card causing the crash. Actually saw this over at rage3d. Here is the microsoft article:http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx gonna try it and see what happens..
edit: running vista ultimate 64bit and those keys aren't there. Im kinda affraid to add them too!
Did anyone try this and did it work?
Roliath
05-02-08, 12:16 AM
Quick update, now using SP1 and with a 9800GX2 this issue is still apparent for me.
"edit, actually just put my rig up for sale on craigslist going to try a local sale and off to ebay it goes. i'm that sick of pc gaming"
ragingWS6
05-02-08, 01:33 AM
Ok...I got mine resolved...for now.
I am running 2 Evga 8800GTX Superclocked cards (621/1000). I had to DOWNCLOCK them to 575/900 in COD4 for it to stay stable. All other games (Crysis, Bioshock, Gears of War) I can run the cards at 640/1045 and it will play all day long.
Kind of strange, isn't it?????
Roliath
05-02-08, 01:35 AM
Ok...I got mine resolved...for now.
I am running 2 Evga 8800GTX Superclocked cards (621/1000). I had to DOWNCLOCK them to 575/900 in COD4 for it to stay stable. All other games (Crysis, Bioshock, Gears of War) I can run the cards at 640/1045 and it will play all day long.
Kind of strange, isn't it?????
Are you on dfwstangs.net?
Your S/N looks familiar, well i'm happy for you that you got them to work!
:-)
ragingWS6
05-02-08, 01:37 AM
Are you on dfwstangs.net?
Your S/N looks familiar, well i'm happy for you that you got them to work!
:-)
No, just part of a local Mustang board (stlmustangs.com). I get on there to razz them a bit since I have a WS6 and we go back and forth. Good times!
Let's just HOPE it keeps up...I bet tomorrow, they come back.
I get this error sometimes in AC ..
slaWter
05-02-08, 10:15 AM
I don't get this problem that often anymore, the GX2 and newer drives really improved the situation. Especially in FSX DX10, 174.93 was the first stable driver in a very long time. I'm currently using the 175.12 set but I didn't have time to test FSX yet. I hope it's just as good as the 174.93!
:thumbdwn: Its back. That crappy error, again!!!
I was playing Turok a while, like 5-10 mins into the game. Then i met a bad guy who was gonna shot at me, when a friendly shot him.
When the badguy falls to the ground in a movie sequence, the game stops with the error. No matter what setting i use in graphics. Always when he falls.
Guess the driver cant keep up with rapid changes in that close of view.
Using currently the beta 175.12 driver. Had this problem with all drivers. What shall i do??
Anyone with this problem solved it somehow???
Im using a driver cleaner, and going into safemode to clean more and install. Same problem what ever i do...
Help!! I wanna play Turok past that falling scene without errors!!!
ragingWS6
05-03-08, 06:18 PM
Yep, they just came back. When trying to select weapons after a map loads in COD4, screen starts flashing and then I see the damn balloon at the bottom of the screen....
Going to run driver cleaner and see if I can install the 174.93s (I skipped that driver) and see how those do...
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.