Warning

 

Close
Confirm Action

Are you sure you wish to do this?

Cancel Confirm
AR15.COM
11/29/2009 7:59:36 AM EDT
Posting from my laptop.

 Was playing Modern Warfare 2 last night on my PC when the system crashed.  I restarted with no other problems.  This morning I turned on Fallout 3 and within five minutes had a huge crash, and finally witnessed the Blue Screen of Death for the first time with this system.  I've restarted in Safe Mode a couple of times but now I can't even do that.  I also ran a System Restore but it crashed again in the middle of that and now I can't run it again.

I see a technical message regarding NVLDDMKM.sys, but I don't know what to do to fix it.  Any ideas?
11/29/2009 8:08:52 AM EDT
[#1]
get the newest video drivers online- prolly from you pc manufacturer
11/29/2009 8:09:51 AM EDT
[#2]
Sounds like a hardware problem and you fried the GPU from letting it overheat while playing 3D-intensive games. Is it covered by warranty?
11/29/2009 8:10:39 AM EDT
[#3]
If you get a BSoD again, grab the error from it and give it a Google.  That will let you know what to look towards as to what caused your crash.
11/29/2009 8:10:50 AM EDT
[#4]
Could be a hardware problem.



Uninstall the driver and then reinstall to make sure it isn't a corrupt driver first.
11/29/2009 8:12:51 AM EDT
[#5]
Dude, the other day MW2 tried to divide by zero and crashed.  

I laughed my ass off when the error came up.  I shit you not, it said "application fail, integer divide by zero...."
11/29/2009 8:13:27 AM EDT
[#6]
Quoted:
Could be a hardware problem.

Uninstall the driver and then reinstall to make sure it isn't a corrupt driver first.



In my 10+ year experience in IT and support, I have RARELY encountered a BSOD that was caused by hardware.   Rarely.
11/29/2009 8:18:12 AM EDT
[#7]
this is a well known problem with vista and certain nvidia cards... a friend of mine had a similar problem with an 8000 series card...

from what i've read, it seems like the card has some built in power management features like CPU stepping and what not, one guy posted that disabling these features via nvidia driver and/or UAC in vista can help alleviate the problem... based on several threads i've read on it, from a techie standpoint, it sounds to me like part of the driver is running in user mode, when it wants to step up the CPU for high demand applications (directx 10 stuff like games) the vista UAC component is preventing it causing the driver or system to crash...

- update to latest NVIDIA drivers from NVIDIA
- turn off NVIDIA power/performance management
- if you are the only person who uses your computer and aren't a complete moron (open random email attachments, use Internet Explorer to surf porn, and other high risk for malware activities), TURN OFF UAC.
11/29/2009 8:18:39 AM EDT
[#8]



Quoted:



Quoted:

Could be a hardware problem.



Uninstall the driver and then reinstall to make sure it isn't a corrupt driver first.






In my 10+ year experience in IT and support, I have RARELY encountered a BSOD that was caused by hardware.   Rarely.
Have you ever overclocked a cpu or video card? Taking it too high will almost always result in a BSOD.



Not saying the OP is overclocking but his board could be overheating. Just something to check into.





 
11/29/2009 8:19:10 AM EDT
[#9]
Quoted:
Quoted:
Could be a hardware problem.

Uninstall the driver and then reinstall to make sure it isn't a corrupt driver first.



In my 10+ year experience in IT and support, I have RARELY encountered a BSOD that was caused by hardware.   Rarely.


i will agree with this, hardware breaks, kernel drivers give you errors (ie: BSOD)
11/29/2009 9:06:34 AM EDT
[#10]
Had issues with the drivers from July. Went back to the ones from March...no more issues.

Do a rollback on your drivers from system management, video adapter.
11/29/2009 9:11:42 AM EDT
[#11]
Guys, thanks for all the info but I can't even get into Safe Mode now.  I have a visible mouse cursor on a blank screen, and that's it.  Do I need to call a repair shop?  I want to avoid that at all costs.
11/29/2009 9:14:54 AM EDT
[#12]
I was having problems with the same name error, I updated the drivers and it seemed to fix it.
11/29/2009 9:16:59 AM EDT
[#13]
do you have an onboard video card? if so...plug into that...make changes as needed to the nvidia card and reboot.
11/29/2009 10:25:05 AM EDT
[#14]
Any other ideas?
11/29/2009 10:26:35 AM EDT
[#15]
try a system restore from a time before you did the driver
11/29/2009 10:28:10 AM EDT
[#16]
go buy a new card
11/29/2009 10:28:41 AM EDT
[#17]
http://guru3d.com/
Check the forums there. These guys test drivers a bunch and can probably tell you which driver would work best for your computer. Some drivers work better with certain games and there might be one that works particularly well with MW2.
11/29/2009 10:33:32 AM EDT
[#18]
Quoted:

Quoted:
Quoted:
Could be a hardware problem.

Uninstall the driver and then reinstall to make sure it isn't a corrupt driver first.



In my 10+ year experience in IT and support, I have RARELY encountered a BSOD that was caused by hardware.   Rarely.
Have you ever overclocked a cpu or video card? Taking it too high will almost always result in a BSOD.

Not saying the OP is overclocking but his board could be overheating. Just something to check into.

 



I run an overclocked AMD Opteron in my desktop at home.  It did take quite a bit of tweaking to get it stable.  I also did run into a problem where CoD4 (and later 5) would hang and the system would become unresponsive.  Happened every other or every third time I'd play the game.  After months of doing that (and troubleshooting - updated drivers, played with the overclocking...) it FINALLY gave me a BSOD.  Researched it and found that the ValueSmart RAM I had in the box was crap.  Replaced it with good RAM, and now the machine hums right along.   Now, if I weren't playing a game, the machine was rock solid.  It only fuxxored up when playing a game.  

So I do have experience with hardware causing problems, but more often than not, something is corrupted, or something otherwise software related isn't playing nice.  

11/29/2009 10:35:21 AM EDT
[#19]
The freezer, it's your only hope!



http://www.ar15.com/forums/topic.html?b=1&f=5&t=960703



11/29/2009 10:46:30 AM EDT
[#20]
Quoted:
Posting from my laptop.

 Was playing Modern Warfare 2 last night on my PC when the system crashed.  I restarted with no other problems.  This morning I turned on Fallout 3 and within five minutes had a huge crash, and finally witnessed the Blue Screen of Death for the first time with this system.  I've restarted in Safe Mode a couple of times but now I can't even do that.  I also ran a System Restore but it crashed again in the middle of that and now I can't run it again.

I see a technical message regarding NVLDDMKM.sys, but I don't know what to do to fix it.  Any ideas?


Yes. I had the same issue when I downloaded the new vid drivers from Nvidia. My pc kept blue screening when trying to play cod4. I put back the old drivers, and everything is ok again.
11/29/2009 12:36:08 PM EDT
[#21]
I had this problem non-stop when playing an old copy of Halo 2 on my Windows 7 box.  I downloaded the latest Nvidia drivers (dated 11/26/2009) and haven't had it happen once since.
12/3/2009 6:08:09 AM EDT
[#22]
I was able to get the OS working again by restarting with the original Vista disc in the drive, then doing a system restore to 11/28.  However, I still can't run any graphics-intensive programs because I'm getting a 'Code 43' error in Windows Device Manager for the Nvidia card.  It's an 8800 GTS.  Anyone know how to fix a Code 43?  I've already downloaded the latest drivers and that didn't do any good.  Thanks.
12/3/2009 6:16:38 AM EDT
[#23]
Quoted:
I was able to get the OS working again by restarting with the original Vista disc in the drive, then doing a system restore to 11/28.  However, I still can't run any graphics-intensive programs because I'm getting a 'Code 43' error in Windows Device Manager for the Nvidia card.  It's an 8800 GTS.  Anyone know how to fix a Code 43?  I've already downloaded the latest drivers and that didn't do any good.  Thanks.


Code 43
Windows has stopped this device because it has reported problems. (Code 43)
Recommended resolution

One of the drivers controlling the device notified the operating system that the device failed in some manner.

If you have already run the Troubleshooting Wizard, you might want to check the hardware documentation for more information about diagnosing the problem.


Guy on another forum reports:
"Install the driver -> you'll notice that one GPU installs. Now go to the device manager.

Manually removed the unknown device (un-install) in device manager, then hit the refresh button then the 2nd GPU is properly detected as 295, and after installing restart. This works on my end.

Worst case scenario is reinstalling a clean Vista. "
12/3/2009 6:19:31 AM EDT
[#24]
It's your Power supply. Can't keep up with power needs.