Weird problem with video card driver


I have this weird issue where my computer either freezes up completely or freezes up and restarts shortly after logging into Windows. When it does restart I get the nvldmkm.sys error that seems to be quite common with Windows 7.

However, after about 2 or 3 times of freezing, it will stop completely and my system will be stable. This only happens when my PC has been off for a while and I turn it back on. It's not a backbreaking issue but it is annoying and may be symptomatic of a more serious problem that could bite me in the butt later, so I want to get this figured out.

When I get the freeze and restart, the system is able to create a dump file for me. Here is the contents of that dump file:

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80088664e0, fffff880104f5d00, ffffffffc000009a, 4}

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
Probably caused by : nvlddmkm.sys ( nvlddmkm+6eed00 )

Followup: MachineOwner

And this only happens on the desktop! After 5-10 minutes, when my system is stable, I can run games and do whatever just fine.

I ran checkdsk on my system drive and ran 2 passes of memory check, all was fine.

Below are my specs:

MSI H55M-P31 motherboard
4GB G-skill DDR3-1333 PC10600
EVGA Nvidia GTX 470
i7 875k @ 2.93 ghz
PC Power Supply and cooling 610 watt PSU
WD 150GB 10000RPM drive
Hitachi 1TB 7200RPM drive

Thanks in advance for any help you can give me on this matter!
3 answers Last reply
More about weird problem video card driver
  1. Also, I have reinstalled the drivers multiple times (and driver sweep).
  2. I used analyze-v and found more dump data:

    Attempt to reset the display driver and recover from timeout failed.
    Arg1: fffffa80088664e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880104f5d00, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.

    Debugging Details:

    fffff880`104f5d00 4883ec28 sub rsp,28h



    BUGCHECK_STR: 0x116

    PROCESS_NAME: System


    fffff880`03fadb88 fffff880`10ad3ef8 : 00000000`00000116 fffffa80`088664e0 fffff880`104f5d00 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`03fadb90 fffff880`10aa7867 : fffff880`104f5d00 fffffa80`07753000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`03fadbd0 fffff880`10ad3d07 : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`088664e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`03fadc80 fffff880`10ba2ec1 : fffffa80`0781c010 00000000`00000080 00000000`00000000 fffffa80`0774f010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`03fadd00 fffff800`0316ea86 : 00000000`027f5dca fffffa80`0776c060 fffffa80`03c719e0 fffffa80`0776c060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`03fadd40 fffff800`02ea7b06 : fffff800`03043e80 fffffa80`0776c060 fffff800`03051c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03fadd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND: .bugcheck ; kb

    fffff880`104f5d00 4883ec28 sub rsp,28h

    SYMBOL_NAME: nvlddmkm+6eed00

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys


    FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

    BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

    Followup: MachineOwner

    IS this a TDR issue? Should I increase the timeout value? Where in the registry is this?

  3. Anyone have any ideas? It still takes 2-3 tries of booting after being off for through the night before it becomes stable.

    I also didn't see any TDR fields in the graphicdrivers key.
Ask a new question

Read More

Drivers Graphics Cards Windows 7