Computer restarting for no apparent reason

Delirium Ghs

Reputable
Mar 22, 2015
27
0
4,530
Hello.

I recently changed my GPU from a Gigabyte R9 390X to an ASUS RoG STRIX GTX 1070 OC. I installed it on a clean machine (Windows was just installed, no drivers were there before).

I noticed that my computer restarted twice for no apparent reason. One time when it was idle in Power Saver mode (the default Windows power save mode) and once, during a 3DMark Firestrike test (with the GPU overclocked to a stable profile).

There is no overheating issue. This is 100% not the case here.

My build:

CPU: i7 4790K (stock clocks - turbo boost enabled)
Motherboard: Gigabyte Z97X Gaming 5
RAM: 2x Teamgroup Vulcan + 2x G.Skill Ripjaws
GPU: Asus RoG GTX 1070 Strix OC
PSU: Corsair CS 750W Gold+
CPU Cooler: NXT Kraken X61


Any ideas about what the issue could be? It's definitely not a temperature issue. All drivers I have installed are the latest.

If it helps, this is the Windows event crash logs:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 20/11/2016 5:08:07 πμ
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: BATTLESTATION
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2016-11-20T03:08:07.646776600Z" />
<EventRecordID>2151</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>BATTLESTATION</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">281</Data>
<Data Name="BugcheckParameter1">0x10</Data>
<Data Name="BugcheckParameter2">0xffff9689aad14000</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
</EventData>
</Event>
 
Probably the mixed RAM. Try it with only two stick of the same kind and if it is unstable try the other two. Or it could just be the combination of the 4 sticks. All RAM should always be the exact same make and model, preferably bought in a 4 stick "kit" if you are using 4.
 

Delirium Ghs

Reputable
Mar 22, 2015
27
0
4,530


I've been using this RAM combination for around 2 years. Never had issues with it. According to the BugcheckCode of the error event entry, the problem is this:

"A device object has been blocking an IRP for too long a time." I have no idea what it could mean.
 

Delirium Ghs

Reputable
Mar 22, 2015
27
0
4,530
dxgkrnl.sys dxgkrnl.sys+c2a4 fffff801`99dd0000 fffff801`99fee000 0x0021e000 0x5801a43e 15/10/2016 5:36:30 πμ Microsoft® Windows® Operating System DirectX Graphics Kernel 10.0.14393.351 (rs1_release_inmarket.161014-1755) Microsoft Corporation C:\WINDOWS\system32\drivers\dxgkrnl.sys

dxgmms2.sys dxgmms2.sys+1a5c0 fffff801`9a5b0000 fffff801`9a657000 0x000a7000 0x5801a824 15/10/2016 5:53:08 πμ Microsoft® Windows® Operating System DirectX Graphics MMS 10.0.14393.351 (rs1_release_inmarket.161014-1755) Microsoft Corporation C:\WINDOWS\system32\drivers\dxgmms2.sys

nvlddmkm.sys nvlddmkm.sys+9f398 fffff801`9c7e0000 fffff801`9d5b3000 0x00dd3000 0x582cf91c 17/11/2016 2:26:04 πμ

watchdog.sys watchdog.sys+34ae fffff801`99db0000 fffff801`99dc4000 0x00014000 0x57899b9b 16/7/2016 4:27:39 πμ Microsoft® Windows® Operating System Watchdog Driver 10.0.14393.0 (rs1_release.160715-1616) Microsoft Corporation C:\WINDOWS\system32\drivers\watchdog.sys


This is the call chain that causes the crash according to the minidump generated.