New
#1
BSOD nvlddmkm.sys
Hey folks,
I've been getting a BSOD right before the Windows log on screen...
DRIVER_IRQL_NOT_LESS_OR EQUIL
STOP: 0x000000D1
nvlddmkm.sys
address FFFFF8800FFAC22E base at FFFFF8800FE2000
What have I done so far?
I looked up nvlddmkm.sys. Seems like this is a problematic file for lots of folks. My workaround up until recently has been to boot into safe mode, totaly uninstall all of my Nvidia drivers, boot back into normal mode, and reinstall the latest video drivers. After doing that everything works fine for a couple of days.
More recently I noticed that when my PC was totaly shut down my external hard drive's lights were alternating as if the drive was transfering data. This external is a Western Digital My Book Essential 1TB USB 2.0 hdd.
Puzzled as to why the hard drive would be on and seem to be active when the system is totaly shut down I powered on the system and I got the same BSOD before the Windows logon screen.
I shut it down with the power switch on the PSU, unplugged the USB cable for the external hdd, powered back on... everything booted normally.
So, now my workaround is to just remember to unplug the external hard drive before I power the system on. Granted, its a much shorter and easier workaround, but still a workaround nonetheless. I'd like to solve the issue totally.
The only conclusion I can draw from this is that the external hard drive or something to do with USB is screwing with the video drivers somehow.... I lean toward the hard drive and not USB in general because I have a USB gaming headset that stays plugged in. I also sometimes leave my iPhone and iPods connected during power cycles and reboots with no problems. It only seems to happen with this external WD hdd is hooked up.
I'm usually pretty good at troubleshooting this kind of thing but I am stumped on this one.
I tried finding the \Windows\minidump folder and I don't seem to have one even after enabling show hidden files files and system files.
Any ideas? :)
Thanks,
LF
Last edited by LiquidFlames; 16 Mar 2010 at 14:10. Reason: clarification