Crash with nvlddmkm.sys in Vista

dangfx · May 26, 2008

I have a pretty basic system setup.

My System
-Asus AN8-E version 2 motherboard, bios version 1013 (most recent)
-AMD Athlon X2 4400+
-2GB Corsair ValueSelect memory (2x 1GB modules, model VS1GB400C3)
-Creative E-MU 0404 PCI audio card
-Antec True 550 EPS12V server-class rated SSI PSU
-Netgear WN311B Wireless NIC
-Maxtor B200 200GB HDD (software and files)
-Western Digital WD800 80GB HDD (system/Windows)
-2x Western Digital Raptor 74GB in RAID0 (media) using onboard RAID controller
-BFG 7800 GTX, 169.25 WHQL drivers (tried several previous versions)
-Plextor CD-R (PX-W1610A) -firmware updated
-Plextor DVDR (PX-716AL) -firmware updated
-Logitech PC/2 (serial) mouse
-Wacom Intuos2 USB tablet
-Floppy drive
-Dual VGA monitors
-All temps and fans are running fine
-No overclocking in the BIOS (stock motherboard settings)
-No overclocking of the video card (stock BFG settings)
-Onboard sound is disabled in the BIOS.
-Onboard NIC is disabled in the BIOS.
-AMD Cool n Quiet is disabled in the BIOS.

My Software
-Windows Vista Ultimate x64 with SP1 (completely updated via Windows Update as of 5/26/2008)
(these were installed after a while of not being installed, and the crashes still happened)
-Brand new complete install of the OS on a freshly formatted HDD, not an upgrade, or an install over a previous install
-Adobe Acrobat Professional
-Flash Player (ActiveX plugin)
-Adobe Acrobat Reader
-America Online
-Azureus
-Canon IP90 drivers and software
-Deskscapes
-DivX
-Java
-Microsoft Office 2007
-Firefox
-Nero
-Objectdock
-Quicktime
-Rangemax (Netgear wireless) drivers and software
-RealPlayer
-WinAmp
-WinRAR
-Shareaza
-Sony Sound Forge
-E-MU Patchmix drivers and software
-Wacom Intuos2 tablet driver software (ver 6.05-7)
-Maya Unlimited 2008
-Photoshop CS3
-MagicISO
-Asus PC Probe

All third party software is updated and the latest version of that software. If I have not listed the software, it was never installed on the system. I have no games installed, and the error only occurs when playing video. It occurs regardless of the player (WMP, WinAMP, etc.), regardless of the file extension, (.mpg, .avi, .mpeg, etc.) and regardless of the codec used. This problem only exists under Windows Vista (both 32bit and 64bit). All other OSs I have tried (Windows XP, 2K, Linux) experience no problem like this.

I Have Tried:
-Running memtest/memtest86 (11 hours). I have gotten no errors, and there were no errors in other OSs (Windows XP, 2K, Linux).
-Running Prime95 I have gotten no errors, and there were no errors in other OSs (Windows XP, 2K, Linux).
-Disabling Aero (running old Windows 2000 theme), along with disabling Dreamscene/animated desktops.
-Disabling UAC.
-Uninstalling/reinstalling the video display drivers (fresh, from Safe Mode and regular Windows).
-Changing nvlddmkm.sys in windows/system32 to nvlddmkm.sys.old, then expand.exe via Command Prompt.
-Uninstalling and removing my Creative sound card completely (removing drivers in safemode and taking out the card).
-Trying to put my Creative sound card in a different PCI slot.

This Problem Exists Elsewhere
http://www.tweakforce.com/modules.php?name=Forums&file=viewtopic&t=738
http://hardforum.com/showthread.php?t=1247726&highlight=nvlddmkm
http://hardforum.com/showthread.php?t=1237285&highlight=nvlddmkm
http://hardforum.com/showthread.php?t=1227744&highlight=nvlddmkm
http://forums.nvidia.com/index.php?...in=posts&result_type=topics&highlite=nvlddmkm
http://www.nvnews.net/vbulletin/showthread.php?t=86550
http://i.nconspicuo.us/2007/03/28/nvidia-nvlddmkm-vista-driver-fix-here-is-the-solution/
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1532547&SiteID=17
http://forums.guru3d.com/showthread.php?t=219186

Exact Problem
Crash occurs as a blank/black screen. This happens when playing video files, and usually happens faster if I jump around the movie manually. The screen stays black for a few minutes. If I leave the computer sitting, a blue screen comes up. The BSOD reads:

Code:

STOP: 0x00000116 (0XFFFFFA8004c9F180, 0xFFFFF980040525F0, 0x0000000000000000, 0x0000000000000002)
nvlddmkm.sys address FFFFF980040525F0, base at FFFFF9800404A000, datestamp 475F455F

A small memory dump happens, then I restart. If I had Dreamscene running, upon restarting, it is disabled.

ANY help would be GREATLY appreciated.

xxEIEIOxx · May 26, 2008

Well, it looks like you have tried all of the things I would have. My only thought would be that if you are running the 169.25 WHQL drivers, get rid of them and try another. They were not a good set for me stability wise. I found the 163.75 WHQL to be the most stable set I have used. They gave the worst performance, but only about 2 or 3%, which is well worth a stable machine. I'm not doing too badly with the 175.16, but still not as stable as the 163.75. Both better than the 169.25.

dangfx · May 26, 2008

Sorry, I should have mentioned: I have tried using various graphics drivers since Vista x64 came out -- about 5+ versions previous to 169.25

xxEIEIOxx · May 26, 2008

dangfx said:
Sorry, I should have mentioned: I have tried using various graphics drivers since Vista x64 came out -- about 5+ versions previous to 169.25

Well, I am still betting it is a driver issue. Unfortunately you may not find any currently available that will work for you. I didn't see any security software in your list. Either I overlooked it or you don't have any. If you do try to exclude any nv services. I added all of the nv services to the exclusion list in Kaspersky and it eliminated 90% of my BSODs.

panhead · May 27, 2008

dangfx said:
Exact Problem
Crash occurs as a blank/black screen. This happens when playing video files, and usually happens faster if I jump around the movie manually. The screen stays black for a few minutes. If I leave the computer sitting, a blue screen comes up. The BSOD reads:

Code:

STOP: 0x00000116 (0XFFFFFA8004c9F180, 0xFFFFF980040525F0, 0x0000000000000000, 0x0000000000000002) nvlddmkm.sys address FFFFF980040525F0, base at FFFFF9800404A000, datestamp 475F455F

A small memory dump happens, then I restart. If I had Dreamscene running, upon restarting, it is disabled.

Hate to tell you , but it is a Vista problem. Occurs with NV and ATI drivers. Probably related to Vista's DRM. Try XP64.

LoStMaTt · May 27, 2008

I am not so sure panhead.

Have you tried a fresh install of Vista? Maybe try a fresh install of Vista x64 with SP1. Sometimes residue from buggy drivers gets left behind.

I would give that a shot.

dangfx · May 27, 2008

Hate to tell you , but it is a Vista problem. Occurs with NV and ATI drivers.

If that were true, all people with Vista and a NV or ATI card would experience this problem. There must be something else.

Have you tried a fresh install of Vista?

Yes. This install (and others before that) were fresh. Please see the OP.

xxEIEIOxx · May 27, 2008

panhead said:
Hate to tell you , but it is a Vista problem. Occurs with NV and ATI drivers. Probably related to Vista's DRM. Try XP64.

Where as I could agree it is a Vista problem, I believe it is an NV on Vista problem. The file crashing is an NV file, and it has been announced on several sites that NV is the single largest cause of Vista crashes. Though I have an NV card at the moment, I ran ATI for 10 years, and never had the crashing problems with them. With ATI, it was always little irritating issues, like settings not sticking, games not drawing properly, etc. The 8800 GTX has been flawless for me except for the occasional BSOD that comes from the drivers.

Unfortunately, I don't have anything to add to the problem at the moment. I have seen it discussed to death and nobody has a fix for it. I am hoping at some point they will release drivers that no longer do this.

Nasty_Savage · May 28, 2008

I believe it was a bad patch. I haven't had that error in awhile.

dangfx · May 28, 2008

Nasty_Savage,
Could you please be a bit more specific? I would love to remedy this error. Which "patch" was bad? For which component? Is there a good one available?

Nasty_Savage · May 28, 2008

I don't recall which patch it was. My best answer for you is to go into software and start removing patches or use the system restore option to a time where it wasn't a problem and start from there...

der_jackal · May 28, 2008

panhead said:
Hate to tell you , but it is a Vista problem. Occurs with NV and ATI drivers. Probably related to Vista's DRM. Try XP64.

Realllllllly now...

dangfx · May 28, 2008

Nasty_Savage said:
My best answer for you is to go into software and start removing patches or use the system restore option to a time where it wasn't a problem and start from there...

Nasty Savage--
I have always had this problem, since the very moment Vista was first installed.

der_jackal · May 28, 2008

dangfx said:
Nasty Savage--
I have always had this problem, since the very moment Vista was first installed.

Post a dump file, from the looks of the BSOD the hardware (namely your BFG 7800GTX) is not responding to a reset reqeust.

Was this system running any other OS before you did the clean install of Vista?

dangfx · May 28, 2008

Was this system running any other OS before you did the clean install of Vista?

der_jackal--
thank you for your response, but please read the whole original post before, where I indicated that, yes, I have run Windows 2000, XP, and Linux on the machine prior to installing Vista (both 32 and 64 bit versions).

Don't know what you will do with this, but you asked for it:

MEMORY.DMP:

Code:

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
No module list information.  Delay kernel load.
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Windows Server 2008 Kernel Version 6001 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff800`01e0edb0
Debug session time: Wed May 28 01:31:05.453 2008 (GMT-4)
System Uptime: 0 days 0:00:25.046
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
No module list information.  Delay kernel load.
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
No module list information.  Delay kernel load.
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004a76030, b2000000, 70f0f}

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
ReadControl failed - kernel symbols must be loaded first
ReadControl failed - kernel symbols must be loaded first
ReadControl failed - kernel symbols must be loaded first
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
ReadControl failed - kernel symbols must be loaded first
ReadControl failed - kernel symbols must be loaded first
ReadControl failed - kernel symbols must be loaded first
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

dangfx · May 28, 2008

MINI052608-01.DMP:

Code:

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini052608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`01c59000 PsLoadedModuleList = 0xfffff800`01e1edb0
Debug session time: Mon May 26 20:45:58.534 2008 (GMT-4)
System Uptime: 0 days 0:09:43.156
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004ea14e0, fffffa600260f5f0, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+85f0 )

Followup: MachineOwner
---------

ASIA911 · May 29, 2008

It's definitly a video driver problem. Try uninstalling the driver and use Drive Cleaner. Try Driver 169.44.

diablerie · May 29, 2008

One other unfortunate possibility is that there's a hardware problem with your video card.

Last summer, I was a experiencing the same issues as you, with the NVidia driver constantly crashing. I put up with it for a while, until I started seeing video artifacts while playing games. Fortunately, my 7900 GT was still under warranty.

dangfx · May 29, 2008

ASIA911--
I appreciate your response, but please read the original post carefully. As already stated, I have tried using other (previous) drivers before, including 169.44.

diablerie--
I appreciate your response, but please read the original post carefully. As already stated, It is not a hardware problem, because Vista is the only OS that experiences this phenomenon.

der_jackal · May 29, 2008

dangfx said:
der_jackal--
Don't know what you will do with this, but you asked for it:

I'd like to have the actual minidump file so I can poke at the TDR context message in a debugger and see if it sheds more light as to what the problem really is...

dangfx · May 29, 2008

Sure... i suppose i need your email -- can't figure out a way to attach a file on vBulletin 3.6.8 via PM or post.

der_jackal · May 29, 2008

PM sent.

dangfx · May 29, 2008

you have email.

Nasty_Savage · Jun 3, 2008

dangfx said:
Nasty Savage--
I have always had this problem, since the very moment Vista was first installed.

You had the problem pre-SP1 from the first install?

dangfx · Jun 3, 2008

Nasty_Savage said:
You had the problem pre-SP1 from the first install?

Yes.

der_jackal · Jun 4, 2008

dangfx said:
Yes.

If it makes you feel any better, I just hit this in my office on a machine w/ an Intel GPU.

Vashypooh · Jun 5, 2008

I had this issue until i used the most recent nvidia drivers. I even had the exact same problem in windows XP.

Crash with nvlddmkm.sys in Vista

Gawd

2[H]4U

Gawd

2[H]4U

Gawd

2[H]4U

Gawd

2[H]4U

Fully [H]

Gawd

Fully [H]

Limp Gawd

Gawd

Limp Gawd

Gawd

Gawd

[H]ard|Gawd

Weaksauce

Gawd

Limp Gawd

Gawd

Limp Gawd

Gawd

Fully [H]

Gawd

Limp Gawd

2[H]4U