nvlddmkm.sys - BSOD - Page 2

BeepBeep2 · 30 April 09, 02:03

I've had a 120mm sleeve bearing fan in the back for 2 years, chugging away at 1800 RPM for 7-10 hours per day (about as much as my PC is on a day...)

It seems to be turning about 60 in human years. It's giving up and I'm broke, lol. I'll get a ball bearing fan and stick it in there backwards.

Open up the attachment lol
My case is internally a mess.

Butch Nackley · 3 May 09, 04:11

Well, it happened again today

Quazar · 3 May 09, 07:35

I was having problems with my gmotor based games crashing, I upgraded my HD and graphics card and well decided it was time to re-install vista x64.

I install vista x64 with SP1, things went swimmingly. I was able to plat gtr-evo with out any crashes

I then installed the available security and os updates, now gtr is back to its usual self crashing after a few lap or on the car select screen. This has lead me to believe that one of the updates is the cause of the problem and not the nvidia drivers.

I upgraded my GPU from 7800gtx SLI to 9800GT 1gb.

My Specs:
AMD 4400 x2, 4gb DDR, 3x 200gb HD, 500gb HD, 2x Pioneer DVR-109, 1gb 9800GT
550W Antec TruePower PSU.

Now I haven't determined which update it is causing me these problems for this particular games and I really not sure if I can be bothered going thru the hassle of tracking it down, however the update would have been released between the 169.xx and 180.xx nvidia drivers. The 169.05 were the last drivers that worked for me, however a roll back to these drivers didn't resolve the issues when I had the 7800Gtx cards installed.

If anyone has any suggestions feel free to post, at this stage only gmotor based games are affected. Looks like I'll be installing and playing GP legends for the forseeable future

Butch Nackley · 3 May 09, 08:16

Hi and thanks for input.
Here is the last few updates from MS. However, if it is a update that causes it, it would have to of been the ones before April 16, because the first time this happened to me was April 15th during a online race.

Anyway, if you want to compare updates, here are some of mine.

~~AndrewJ~~ · 3 May 09, 10:43

I tested 9800GTX+ SLi in my tower yesterday with XP-SP2
I uninstalled 182.50 rebooted cancelled found driver removed my card
put in SLi cards installed 182.50 driver again, thats it ran all day all sims, not
a whimper

I never install updates none ever improved performance while most say they cant hurt I dont agree.
I never used CPU or dualcore optimizer with x2 nor for my 940. ( Yes I relise it apparently helps some shooters but I run all sims without either 101% )

Likewise I see people talking about netframe 3.5 update in stutter threads, if you look at W7 ATi info it still uses Netframe2 ergo its pointless updating it
to try to solve 3d/performance problems, lol ... oh thats right the old it wont hurt.

Butch Nackley · 3 May 09, 21:24

Hi again

Andrew, I'm sure you are only trying to help, but in all honesty, you are not. This is a Vista/Win7 issue. While I have read where it has happened to some under XP, it is very rare for that OS (in fact, I have only heard like two people say they had it happen under XP). So just telling us over and over how you don't have this problem running XP is really not helping anyone here. We already know that, or at least anyone that has spent a bit of time reading about this problem already knows this.

I don't know anything about a problem .net 3.5 might have. I know I don't have any stuttering, so it hasn't done anything there, that I can tell. I installed 3.5 because Spotter Plugin needs it. If you believe it is linked to the nvlddmkm.sys errors, then by all means post a link showing how and why. Just saying Win7 still uses 2.0 in no way leads me to think 3.5 is why I am getting the stop errors. Show me proof and I will then decide what to do.
I posted a full shot of my Windows updates at nVidia. Nothing wrong was the report I received from a user there.

Okay, I am down to my last trials. I have removed 4GB of ram, as per a suggestion.
While I was at that, I also hooked up my monitor to the other DVI link (my card has two). I had been using the one closest to my monitor. If looking at the back of the gfx card, that would be the one on the right. I now have it hooked up to the one on the left. That one is closest to the motherboard when the card is installed. I doubt that will have any affect on it, but I figured it couldn't hurt to try it.

I have a race tonight, so this will be a good chance to see if anything I did has helped.
If it happens again, I am going to put on XP Pro 32bit for dual boot and run rFactor under XP.

BeepBeep2 · 3 May 09, 21:39

If you can, get a camera and take a picture of the BSOD screen for me to see.

The

0xAAxxxxx xxxxxxx xxxxxxxxx

Is what I'm interested in, it is important.

Butch Nackley · 3 May 09, 22:39

I like your faith. A true believer in 'this will happen again', lol

I don't have a camera to take a shot, but I will write down the error code for you.
Hopefully I won't see it again, but like you, I'm a believer too. I feel sure I will get that info for you before too long.

Butch Nackley · 4 May 09, 01:55

Well, you won't get the info, yet.
I did one last thing, before entering the session tonight. I reinstalled the gfx driver. However, I just ran the installer, no removal first, same version. Somewhere I read it will help to reduce the chances, but the error will most likely reappear after a few days to a couple weeks or so

Anyway, tonight it was fine

I'll be doing some offline practice and have another race Wed. So, I should be ruinning the game quite a bit over the next few days.

I remembered something.
As hopeful as I would like to be, I don't know if this could cause it.
When I first built this pc, I hooked up my gfx cable to the DVI link it is now reattached to. The one on the left, closest to the motherboard.
Sometime, but I really don't know how long ago it was, I tidying up all my cables and that's when I switched DVI links.

Could that have the reason I all of a sudden, after nearly 3 months of excellent stability, get this error? I have no idea, but I am certain I did switch out the links. Probably hasn't a thing to with it, but I remember Performance Information saying it needed to refresh becasue of new hardware.
It says it now, but I don't know if it is because I removed the ram, or if because I changed the link. Everything in device manager shows fine.

Quazar · 4 May 09, 03:32

Hi butch,

I've installed all updates post SP1 in vista so I have all in your list installed. BSOD's have been extremely rare for me however gtr-evo will not work without CTD. From the clean install without updates and all latest drivers it work flawlessly, once I install the updates it wasn't so rosey.

Now eventually I may go and uninstall the updates and apply them 1 at a time in an effort to identify the update causing these problems. It may very well be a combination of updates only time will tell. I won't be able to investigate further until friday this week, stupid work and wanting me to turn up

Come the end of the week I may have an answer.

exilledweegie · 4 May 09, 13:47

i got this error and ctd last night for the first time,im on vistax64 with all updates,im pretty sure it was the track that caused it(monaco) i was getting some lag when going down the pit straight,other parts of the track were fine,after about 15 laps i turned onto the pit straight and BANG!! ctd with the nvidia error thats mentioned here,it said my display driver had to recover,this doesnt happen for me usually,ive never had this error before so it could well be the custom track that the driver doesnt like in my case.

~~AndrewJ~~ · 8 May 09, 22:46

Only BSOD I get is trying to run benches at 3.8GHz

BeepBeep2 · 9 May 09, 02:34

Trying to be constructive, helpful, remember.

~~AndrewJ~~ · 9 May 09, 02:48

Now I will say I run XP and Vista and W7 32/64 and ubuntu to boot and never have a nvlddmkm.sys - BSOD

My point being in last post I just dont get this bug so its no use blaming Vista

edit: Okay I be more constructive I going to run a fresh Vista 32Bit onto a 80GB and set it up the same way I do for other people that have it.

Straight sP1 install no updates, latest whql driver
I delete Netframe anything else from program features
I delete the 2 startups for nvidia leaving only the control panel one
I turn off sytem restore and bit manager whatever

I add DX May

Cant think of much else all i know is I build many Vista towers of all those I had a few come
cant say I ever remember this error in Vista on cards ranging from 6150/6600GT to 9800gtx

So I google and many have this problem leads me to think maybe it is something I do not do.

BeepBeep2 · 9 May 09, 03:58

Maybe there are dud cards out there. (It wouldn't suprise me.)

nvidia has posted Q1'09 a loss, I'm suprised. (Not really, the red team is sweeping them up).

Anyway, I also got this bug when I took an overclock just a little too far on my 8800GTS.
Stock was like, what 500/1598? I had it up at 605/1900 for a while, but it was factory overclocked to 540/1680 anyway. No wonder it didn't last very long...screen corruption/failure meant bad memory!

But every ten minutes or so this happened back in early 2008, nvidia does not really know how to make a good driver without spending two years on it.

~~AndrewJ~~ · 10 May 09, 01:20

Yes I heard underclocking card a bit solves for some

Tried 32Bit all night nothing yet to report but off course thats a 9800GTX+

I fair dinkum had stutters in 3Dmark'06 I mean a glaring ones, but never seen that with +4200 to +6400 with the identical card in XP or W7 yet for that matter.
( thats is apart from the well known 3dmark2001carchase stutter with a few varying drivers) but 3dmark only stutters for me you test a low power PC has no right even using 2006.

Very wierd with 940BE 100% okay in XP and W7
Vista lag noticeable in a few things. ( even game/sim loaders )
Even movies starts instant in XP and W7 start black screen in vista and slower.

Same whql driver but I noticed these problems oinks ago with much earlier drivers. Maybe Intel runs Vista better ?

I am actually surprised how well AMD quad runs in XP.

9 May 09, 02:48	#64
~~AndrewJ~~ Banned Join Date: Jan 2009	Now I will say I run XP and Vista and W7 32/64 and ubuntu to boot and never have a nvlddmkm.sys - BSOD My point being in last post I just dont get this bug so its no use blaming Vista edit: Okay I be more constructive I going to run a fresh Vista 32Bit onto a 80GB and set it up the same way I do for other people that have it. Straight sP1 install no updates, latest whql driver I delete Netframe anything else from program features I delete the 2 startups for nvidia leaving only the control panel one I turn off sytem restore and bit manager whatever I add DX May Cant think of much else all i know is I build many Vista towers of all those I had a few come cant say I ever remember this error in Vista on cards ranging from 6150/6600GT to 9800gtx So I google and many have this problem leads me to think maybe it is something I do not do. Last edited by AndrewJ; 9 May 09 at 03:29.

3 May 09, 04:11	#52
Butch Nackley Join Date: Aug 2008 Location: Clearwater, Florida Age: 51	Well, it happened again today

3 May 09, 07:35	#53
Quazar Join Date: Feb 2007 Location: Tasmania Age: 40	I was having problems with my gmotor based games crashing, I upgraded my HD and graphics card and well decided it was time to re-install vista x64. I install vista x64 with SP1, things went swimmingly. I was able to plat gtr-evo with out any crashes I then installed the available security and os updates, now gtr is back to its usual self crashing after a few lap or on the car select screen. This has lead me to believe that one of the updates is the cause of the problem and not the nvidia drivers. I upgraded my GPU from 7800gtx SLI to 9800GT 1gb. My Specs: AMD 4400 x2, 4gb DDR, 3x 200gb HD, 500gb HD, 2x Pioneer DVR-109, 1gb 9800GT 550W Antec TruePower PSU. Now I haven't determined which update it is causing me these problems for this particular games and I really not sure if I can be bothered going thru the hassle of tracking it down, however the update would have been released between the 169.xx and 180.xx nvidia drivers. The 169.05 were the last drivers that worked for me, however a roll back to these drivers didn't resolve the issues when I had the 7800Gtx cards installed. If anyone has any suggestions feel free to post, at this stage only gmotor based games are affected. Looks like I'll be installing and playing GP legends for the forseeable future

3 May 09, 10:43	#55
~~AndrewJ~~ Banned Join Date: Jan 2009	I tested 9800GTX+ SLi in my tower yesterday with XP-SP2 I uninstalled 182.50 rebooted cancelled found driver removed my card put in SLi cards installed 182.50 driver again, thats it ran all day all sims, not a whimper I never install updates none ever improved performance while most say they cant hurt I dont agree. I never used CPU or dualcore optimizer with x2 nor for my 940. ( Yes I relise it apparently helps some shooters but I run all sims without either 101% ) Likewise I see people talking about netframe 3.5 update in stutter threads, if you look at W7 ATi info it still uses Netframe2 ergo its pointless updating it to try to solve 3d/performance problems, lol ... oh thats right the old it wont hurt.

3 May 09, 21:24	#56
Butch Nackley Join Date: Aug 2008 Location: Clearwater, Florida Age: 51	Hi again Andrew, I'm sure you are only trying to help, but in all honesty, you are not. This is a Vista/Win7 issue. While I have read where it has happened to some under XP, it is very rare for that OS (in fact, I have only heard like two people say they had it happen under XP). So just telling us over and over how you don't have this problem running XP is really not helping anyone here. We already know that, or at least anyone that has spent a bit of time reading about this problem already knows this. I don't know anything about a problem .net 3.5 might have. I know I don't have any stuttering, so it hasn't done anything there, that I can tell. I installed 3.5 because Spotter Plugin needs it. If you believe it is linked to the nvlddmkm.sys errors, then by all means post a link showing how and why. Just saying Win7 still uses 2.0 in no way leads me to think 3.5 is why I am getting the stop errors. Show me proof and I will then decide what to do. I posted a full shot of my Windows updates at nVidia. Nothing wrong was the report I received from a user there. Okay, I am down to my last trials. I have removed 4GB of ram, as per a suggestion. While I was at that, I also hooked up my monitor to the other DVI link (my card has two). I had been using the one closest to my monitor. If looking at the back of the gfx card, that would be the one on the right. I now have it hooked up to the one on the left. That one is closest to the motherboard when the card is installed. I doubt that will have any affect on it, but I figured it couldn't hurt to try it. I have a race tonight, so this will be a good chance to see if anything I did has helped. If it happens again, I am going to put on XP Pro 32bit for dual boot and run rFactor under XP.

3 May 09, 21:39	#57
BeepBeep2 Join Date: Sep 2007 Location: Ohio, USA Age: 17	If you can, get a camera and take a picture of the BSOD screen for me to see. The 0xAAxxxxx xxxxxxx xxxxxxxxx Is what I'm interested in, it is important.

3 May 09, 22:39	#58
Butch Nackley Join Date: Aug 2008 Location: Clearwater, Florida Age: 51	I like your faith. A true believer in 'this will happen again', lol I don't have a camera to take a shot, but I will write down the error code for you. Hopefully I won't see it again, but like you, I'm a believer too. I feel sure I will get that info for you before too long.

4 May 09, 01:55	#59
Butch Nackley Join Date: Aug 2008 Location: Clearwater, Florida Age: 51	Well, you won't get the info, yet. I did one last thing, before entering the session tonight. I reinstalled the gfx driver. However, I just ran the installer, no removal first, same version. Somewhere I read it will help to reduce the chances, but the error will most likely reappear after a few days to a couple weeks or so Anyway, tonight it was fine I'll be doing some offline practice and have another race Wed. So, I should be ruinning the game quite a bit over the next few days. I remembered something. As hopeful as I would like to be, I don't know if this could cause it. When I first built this pc, I hooked up my gfx cable to the DVI link it is now reattached to. The one on the left, closest to the motherboard. Sometime, but I really don't know how long ago it was, I tidying up all my cables and that's when I switched DVI links. Could that have the reason I all of a sudden, after nearly 3 months of excellent stability, get this error? I have no idea, but I am certain I did switch out the links. Probably hasn't a thing to with it, but I remember Performance Information saying it needed to refresh becasue of new hardware. It says it now, but I don't know if it is because I removed the ram, or if because I changed the link. Everything in device manager shows fine.

4 May 09, 03:32	#60
Quazar Join Date: Feb 2007 Location: Tasmania Age: 40	Hi butch, I've installed all updates post SP1 in vista so I have all in your list installed. BSOD's have been extremely rare for me however gtr-evo will not work without CTD. From the clean install without updates and all latest drivers it work flawlessly, once I install the updates it wasn't so rosey. Now eventually I may go and uninstall the updates and apply them 1 at a time in an effort to identify the update causing these problems. It may very well be a combination of updates only time will tell. I won't be able to investigate further until friday this week, stupid work and wanting me to turn up Come the end of the week I may have an answer.

4 May 09, 13:47	#61
exilledweegie Join Date: Sep 2008 Location: Fife,Scotland Age: 35	i got this error and ctd last night for the first time,im on vistax64 with all updates,im pretty sure it was the track that caused it(monaco) i was getting some lag when going down the pit straight,other parts of the track were fine,after about 15 laps i turned onto the pit straight and BANG!! ctd with the nvidia error thats mentioned here,it said my display driver had to recover,this doesnt happen for me usually,ive never had this error before so it could well be the custom track that the driver doesnt like in my case.

9 May 09, 02:34	#63
BeepBeep2 Join Date: Sep 2007 Location: Ohio, USA Age: 17	Trying to be constructive, helpful, remember.

9 May 09, 03:58	#65
BeepBeep2 Join Date: Sep 2007 Location: Ohio, USA Age: 17	Maybe there are dud cards out there. (It wouldn't suprise me.) nvidia has posted Q1'09 a loss, I'm suprised. (Not really, the red team is sweeping them up). Anyway, I also got this bug when I took an overclock just a little too far on my 8800GTS. Stock was like, what 500/1598? I had it up at 605/1900 for a while, but it was factory overclocked to 540/1680 anyway. No wonder it didn't last very long...screen corruption/failure meant bad memory! But every ten minutes or so this happened back in early 2008, nvidia does not really know how to make a good driver without spending two years on it.

10 May 09, 01:20	#66
~~AndrewJ~~ Banned Join Date: Jan 2009	Yes I heard underclocking card a bit solves for some Tried 32Bit all night nothing yet to report but off course thats a 9800GTX+ I fair dinkum had stutters in 3Dmark'06 I mean a glaring ones, but never seen that with +4200 to +6400 with the identical card in XP or W7 yet for that matter. ( thats is apart from the well known 3dmark2001carchase stutter with a few varying drivers) but 3dmark only stutters for me you test a low power PC has no right even using 2006. Very wierd with 940BE 100% okay in XP and W7 Vista lag noticeable in a few things. ( even game/sim loaders ) Even movies starts instant in XP and W7 start black screen in vista and slower. Same whql driver but I noticed these problems oinks ago with much earlier drivers. Maybe Intel runs Vista better ? I am actually surprised how well AMD quad runs in XP.