BSOD how do I find error

[mark38090]

My system shut down and says something about trying to reset the display driver? I don't know how to find the error. I can only run in safe mode.

Emachines EL1352G
Processor AMD Sempron 145 / 2.8 GHz
Memory 2.0 GB
Hard Drive 500.0 GB - 7200.0 rpm
Operating System Microsoft Windows 7 Home Premium 64-bit Edition
Optical Drive DVD±RW (±R DL) / DVD-RAM
Graphics Processor NVIDIA GeForce 6150 SE
Graphics Controller Integrated

 

[Arc]

Hi mark38090.

It is a display/graphics related issue.

As it is an old branded desktop, some things are to be checked at first.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of your PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

About the display unit, it seems to be onboard nvidia graphics?

NVIDIA GeForce 6150SE nForce 430

Run the SF Diag tool again and upload the dxdiag.txt file.
______________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80049b0010, fffff8800f1882b0, 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+14c2b0 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+14c2b0
fffff880`0f1882b0 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`02e679c8 fffff880`03d3f054 : 00000000`00000116 fffffa80`049b0010 fffff880`0f1882b0 00000000`00000000 : nt!KeBugCheckEx
fffff880`02e679d0 fffff880`03d3ed5e : fffff880`0f1882b0 fffffa80`049b0010 fffffa80`038154b0 fffffa80`034d7010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02e67a10 fffff880`03c0ff13 : fffffa80`049b0010 00000000`00000000 fffffa80`038154b0 fffffa80`034d7010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02e67a40 fffff880`03c39cf1 : 00000000`ffffffff 00000000`000006e8 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02e67b20 fffff880`03c38437 : 00000000`00000102 00000000`00000000 00000000`000006e8 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02e67b50 fffff880`03c0b2d2 : ffffffff`ff676980 fffffa80`034d7010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02e67bf0 fffff880`03c37ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`02c11168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02e67d00 fffff800`03377bae : 00000000`045ca0c2 fffffa80`0156db50 fffffa80`01546840 fffffa80`0156db50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02e67d40 fffff800`030ca8c6 : fffff880`009e6180 fffffa80`0156db50 fffff880`009f0f40 fffff880`02fc7050 : nt!PspSystemThreadStartup+0x5a
fffff880`02e67d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+14c2b0
fffff880`0f1882b0 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+14c2b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  510a2100

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f03c000 fffff880`0fd46000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Jan 31 13:15:04 2013 (510A2100)
    CheckSum:         00CEDB22
    ImageSize:        00D0A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4