PC automatically reboots

[tilvio]

Hello,
My PC is being automatically rebooted and i don't know why!

I am attaching the .dmp file:WD-20100131-1557.dmp

This is what the event log shows:

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100131-1557.dmp
C:\Windows\Temp\WER-22427546-0.sysdata.xml
C:\Windows\Temp\WER4DC8.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_121e4dc8

Analysis symbol:
Rechecking for solution: 0
Report Id: 7c6f191b-0e9a-11df-9dba-002185595b09
Report Status: 0

Please help! I don't know what to do.

Thanks in advance,
Silvio.

 

[richc46]

I will get an expert to look at your file. The ususal cause of reboot is overheating. I would go easy with the computer until the file is analzyed.

 

[zigzag3143]

Hello,
My PC is being automatically rebooted and i don't know why!

I am attaching the .dmp file:WD-20100131-1557.dmp

This is what the event log shows:

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100131-1557.dmp
C:\Windows\Temp\WER-22427546-0.sysdata.xml
C:\Windows\Temp\WER4DC8.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_121e4dc8

Analysis symbol:
Rechecking for solution: 0
Report Id: 7c6f191b-0e9a-11df-9dba-002185595b09
Report Status: 0

Please help! I don't know what to do.

Thanks in advance,
Silvio.

Silvio

This crash was caused by y our video driver nvlddmkm.sys. You need to un-install all the remnants of this driver and install a fresh copy. I believe nvidia actually has an un-install tool.

You may also want to run a system file check
to do so type cmd in search>right click and run as admin>sfc /scannow (not the space between sfc and "/")

Let us know the results


Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\WD-20100131-1557.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c86e50
Debug session time: Sun Jan 31 14:57:31.846 2010 (GMT-4)
System Uptime: 0 days 6:13:46.407
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image 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 117, {fffffa80038954e0, fffff880049db220, 0, 0}

Unable to load image 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+e7220 )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80038954e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880049db220, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+e7220
fffff880`049db220 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02e8e5f0 fffff880`0485b4ef : fffffa80`038954e0 fffff880`048a7c80 fffffa80`038954e0 fffff880`04829843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`02e8eb10 fffffa80`038954e0 : fffff880`048a7c80 fffffa80`038954e0 fffff880`04829843 00000000`00000000 : dxgkrnl+0x5b4ef
fffff880`02e8eb18 fffff880`048a7c80 : fffffa80`038954e0 fffff880`04829843 00000000`00000000 00000000`00000000 : 0xfffffa80`038954e0
fffff880`02e8eb20 fffffa80`038954e0 : fffff880`04829843 00000000`00000000 00000000`00000000 fffffa80`01be4440 : dxgkrnl+0xa7c80
fffff880`02e8eb28 fffff880`04829843 : 00000000`00000000 00000000`00000000 fffffa80`01be4440 fffff8a0`0ce81948 : 0xfffffa80`038954e0
fffff880`02e8eb30 00000000`00000000 : 00000000`00000000 fffffa80`01be4440 fffff8a0`0ce81948 fffffa80`0408a010 : dxgkrnl+0x29843


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+e7220
fffff880`049db220 ??              ???

SYMBOL_NAME:  nvlddmkm+e7220

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4abfff56

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

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

 

[tilvio]

Thank you, Ken! I'll give it a shot.
Regards,
Silvio.