The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Desktop is restarting randomly. How do I find out why?
Sir Headless VII
Registered User regular
Registered User regular
A few days ago my desktop started having troubles booting up where it would not finish booting up properly and just restart. It would always eventually work but that cant be good. Now, after not really doing anything, it seems to boot properly most of the time but it seems to randomly crash completely and shut down. Normally I am pretty good at hunting down the source of these types of things but this one has me stumped as to where to start. I didn't change any of the hardware or software and it isn't throwing up any errors when it crashes. Start-up repair doesn't seem to do anything and I just formatted and reinstalled windows and it is still happening. I don't really know where to go from here does anyone have any ideas?
0
Posts
And if you right click my computer (in the start menu or desktop) and go to properties, then click on advanced system settings (win 7 at least), on the advanced tab there is a button that should be something close to "startup and recovery".
If you click on that you can see if your system automatically reboots on an error and if it's writing it to the system log.
While just trying to figure it out, I'd suggest unchecking automatically restart and seeing if you get a big ugly message on your screen when it crashes next, or if it still just randomly restarts.
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Inaccessible path: '"'
Symbol search path is: "srv*c:\cache*http://msdl.microsoft.com/download/symbols;";srv*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Tue Sep 30 16:04:54.521 2014 (UTC - 4:00)
System Uptime: 0 days 0:12:26.630
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80084974e0, fffff880107df7a0, ffffffffc000009a, 4}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -
Probably caused by : nvlddmkm.sys ( nvlddmkm!nvDumpConfig+2abda0 )
Followup: MachineOwner
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80084974e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880107df7a0, 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:
FAULTING_IP:
nvlddmkm!nvDumpConfig+2abda0
fffff880`107df7a0 48ff25f94eedff jmp qword ptr [nvlddmkm!nvDumpConfig+0x180ca0 (fffff880`106b46a0)]
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`023d6b88 fffff880`10b24cbc : 00000000`00000116 fffffa80`084974e0 fffff880`107df7a0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`023d6b90 fffff880`10af8867 : fffff880`107df7a0 fffffa80`07e9c000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023d6bd0 fffff880`10b24acb : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`084974e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`023d6c80 fffff880`03cd0ec1 : fffffa80`052e2010 00000000`00000080 00000000`00000000 fffffa80`04f50410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`023d6d00 fffff800`02f2cbc6 : 00000000`020e2677 fffffa80`07b87b60 fffffa80`04ec99e0 fffffa80`07b87b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`023d6d40 fffff800`02c67bc6 : fffff800`02e03e80 fffffa80`07b87b60 fffff800`02e11c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`023d6d80 00000000`00000000 : fffff880`023d7000 fffff880`023d1000 fffff880`023d65a0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm!nvDumpConfig+2abda0
fffff880`107df7a0 48ff25f94eedff jmp qword ptr [nvlddmkm!nvDumpConfig+0x180ca0 (fffff880`106b46a0)]
SYMBOL_NAME: nvlddmkm!nvDumpConfig+2abda0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53b4446a
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
7: kd> lmvm nvlddmkm
start end module name
fffff880`0fe3a000 fffff880`10ac8000 nvlddmkm (export symbols) nvlddmkm.sys
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Wed Jul 02 13:42:02 2014 (53B4446A)
CheckSum: 00C4C7C9
ImageSize: 00C8E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
What I get from that is it might be a problem with my graphics card, but if anyone else is better at reading them your insight would be appreciated.
Looks like there might have been a new driver released around when the problems started happening. I'll try that thanks.