Random Reboots

[elbeasto]

My PC has taken to randomly rebooting lately.
Either that or the monitor goes off and I have to manually reboot with the button on the case.

Event viewer reports this every time it happens:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa80113ba110, 0xfffff88005068a08, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\Windows\Minidump\060815-18252-01.dmp. Report Id: 060815-18252-01.

but I don't know what that means.

The .dmp file:
View attachment 361907

This build is only 4 months old.
Any help with this would be greatly appreciated.

 

[Arc]

:ar: Blue Screen of Death (BSOD) Posting Instructions

 

[elbeasto]

My bad...

I've attached the generated zip file to my original post.

 

[Arc]

The BSOD is blaming the nvidia display driver, whereas the driver is a good one, apparently.

Break the SLI. Stress test both the Graphics Cards using Furmark, one by one.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
____________________________________________

BugCheck 116, {fffffa80113ba110, fffff88005068a08, ffffffffc000009a, 4}

*** 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+7aca08 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80113ba110, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005068a08, 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+7aca08
fffff880`05068a08 48ff258126edff  jmp     qword ptr [nvlddmkm+0x67f090 (fffff880`04f3b090)]

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`037eaa48 fffff880`05351134 : 00000000`00000116 fffffa80`113ba110 fffff880`05068a08 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`037eaa50 fffff880`05324867 : fffff880`05068a08 fffffa80`0f6ea000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`037eaa90 fffff880`05350f43 : 00000000`ffffd846 fffff880`03340140 fffffa80`113ba110 fffff880`04837f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`037eab40 fffff880`0483803d : fffffa80`10edc010 00000000`00000080 00000000`00000000 fffffa80`0f6e0410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`037eabc0 fffff800`03367456 : 00000000`0272c9f2 fffffa80`0f72c200 fffffa80`0d37a9c0 fffffa80`0f72c200 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`037eac00 fffff800`030bf2c6 : fffff880`0333b180 fffffa80`0f72c200 fffff880`033461c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037eac40 00000000`00000000 : fffff880`037eb000 fffff880`037e5000 fffff880`037e9340 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7aca08
fffff880`05068a08 48ff258126edff  jmp     qword ptr [nvlddmkm+0x67f090 (fffff880`04f3b090)]

SYMBOL_NAME:  nvlddmkm+7aca08

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55259065

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
---------

11: kd> lmvm nvlddmkm
start             end                 module name
fffff880`048bc000 fffff880`052f4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Apr 09 02:02:37 2015 (55259065)
    CheckSum:         009F7AE7
    ImageSize:        00A38000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[elbeasto]

Thanks Arc, will do. I've already tried stressing both GPU's in SLI but couldn't reproduce the problem.

Could it be a bad GPU or PSU not supplying it well enough, or is it most probably a driver problem?

 

[Layback Bear]

A bad power supply could be the problem but I doubt that a
Seasonic 1250W is causing the problem. They have a very good reputation.

I will go back to watching.

 

[elbeasto]

A bad power supply could be the problem but I doubt that a
Seasonic 1250W is causing the problem. They have a very good reputation.

I will go back to watching.

Yeah I consider it a good unit but it's a few years old now, it's a carry over from my last build.

Also, how long should I run furmark for and are there any particular settings I shold use like native res, AA etc.

Thanks, really appreciate the help with this.

 

[Arc]

Also, how long should I run furmark for and are there any particular settings I shold use like native res, AA etc.

Run the preset stress test (not the benchmark) for your screen resolution for 15 minutes, unless you see that teh system is overheating beyond tolerance.

 

[elbeasto]

Also, how long should I run furmark for and are there any particular settings I shold use like native res, AA etc.

Run the preset stress test (not the benchmark) for your screen resolution for 15 minutes, unless you see that teh system is overheating beyond tolerance.

It hasn't happened for a a couple of days but prior to running the stress test today I had another reboot while watching a video in VLC.

Running the stress test on each card (15min each) produced no crashes, errors or high temps.
The 2nd card did however make a high pitched noise.

 

[Arc]

It hasn't happened for a a couple of days but prior to running the stress test today I had another reboot while watching a video in VLC.

Running the stress test on each card (15min each) produced no crashes, errors or high temps.
The 2nd card did however make a high pitched noise.

Just another reboot, or another BSOD?

 

[elbeasto]

It hasn't happened for a a couple of days but prior to running the stress test today I had another reboot while watching a video in VLC.

Running the stress test on each card (15min each) produced no crashes, errors or high temps.
The 2nd card did however make a high pitched noise.

Just another reboot, or another BSOD?

I can't say for sure the monitor goes off...

 

[Arc]

Can you apply any other power supply as a test?

 

[elbeasto]

Can you apply any other power supply as a test?

Not at the moment, I'm looking into buying a new one.
Do you think that may be the problem?

I also forgot to mention that I've gone back to driver version 347.88

 

[Arc]

Can you apply any other power supply as a test?

Not at the moment, I'm looking into buying a new one.
Do you think that may be the problem?

I also forgot to mention that I've gone back to driver version 347.88

This might be.

A random shutdown mostly indicates to a power outage, and if the PSU is anyhow failing then it may happen. Also check the power cables too.

 

[elbeasto]

Can you apply any other power supply as a test?

Not at the moment, I'm looking into buying a new one.
Do you think that may be the problem?

I also forgot to mention that I've gone back to driver version 347.88

This might be.

A random shutdown mostly indicates to a power outage, and if the PSU is anyhow failing then it may happen. Also check the power cables too.

Okay thanks Arc.
It's rebooting randomly, it doesn't actually shut down and stay off.

I heard some coil whine while browsing earlier but it has now stopped. The odd thing was that the Windows theme actually changed from Aero to the solid one for about a minute then changed back without me doing anything.

I'm leaning toward the 2nd GPU as the cause, although I can't prove it by reproducing the fault unfortunately.

 

[Layback Bear]

From post #9

Running the stress test on each card (15min each) produced no crashes, errors or high temps.
The 2nd card did however make a high pitched noise.

I would suggest leaving the noise card out of the computer for quite some time and see if things change. Normally a video card will not cause the high pitch noise on it's own but could cause a power supply to make the noise because of the extra load.

I'm back to lurking.

 

[Pauly]

I would try running with one card for a few days and then the other to see if you can isolate the problem, a whining gfx card cant be a good sign.
When you stressed the cards individually did they both reach the same temp or is the 2nd one getting hotter ?

 

[elbeasto]

From post #9

Running the stress test on each card (15min each) produced no crashes, errors or high temps.
The 2nd card did however make a high pitched noise.

I would suggest leaving the noise card out of the computer for quite some time and see if things change. Normally a video card will not cause the high pitch noise on it's own but could cause a power supply to make the noise because of the extra load.

I'm back to lurking.

Pretty sure the sound is coming from the video card.

I would try running with one card for a few days and then the other to see if you can isolate the problem, a whining gfx card cant be a good sign.
When you stressed the cards individually did they both reach the same temp or is the 2nd one getting hotter ?

Yeah might be a good idea to run without the 2nd card for a bit.

About the same, around 73c.

It's really weird that I can play Far Cry 4 all day without problems then go watch a movie in VLC and boom. :/

Honestly, this 2011-3 build is the most problematic I've ever had, it's just one problem after another.

 

[Pauly]

Honestly, this 2011-3 build is the most problematic I've ever had, it's just one problem after another.

The joys of new technology :devil: