Windows 10 Randomly Restarting w/out BSOD

Discopickle975

Reputable
May 15, 2016
39
2
4,545
Recently for the past month or so, my computer has been, as the title suggests, randomly restarting. When the computer restarts, it does so without a blue screen and thus no error code to look into. I have tried un-checking the auto restart box in the advanced system settings tab as well. Upon the computer restarting automatically roughly 10 minutes ago, I went into the dump cache and found the following:

Microsoft (R) Windows Debugger Version 10.0.17074.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\052018-33468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`ee296000 PsLoadedModuleList = 0xfffff802`ee5fc030
Debug session time: Sun May 20 10:54:01.227 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:10.940
Loading Kernel Symbols
...............................................................
...
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffca8354ef3038, 0, 0}

Probably caused by : AuthenticAMD

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

nt!WheapCreateLiveTriageDump+0x7b:
fffff802`ee9f3b63 48895c2438 mov qword ptr [rsp+38h],rbx ss:0018:ffff800e`9df565e8=ffffca8300000a50


For the past 2 restarts, this AuthenticAMD figure seems to have been the problem. I have looked at my temperatures, and upon gaming or just idling in general the temperatures have not been high enough to cause an auto restart. Any help in solving this issue would be appreciated, as it is very annoying to be playing a competitive match of CS:GO or Siege and to get a temp ban because I got booted from the game. I have heard that this issue might be from a faulty PSU and that there was a way to look at the voltages in the BIOS, but if I were to do that, I am not sure what exactly I'd be looking for to find faults.
 

Discopickle975

Reputable
May 15, 2016
39
2
4,545


This is the critical log as far as restarts go.

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 5/20/2018 10:54:07 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: CybertronPC
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>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2018-05-20T14:54:07.137241000Z" />
<EventRecordID>12398</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>CybertronPC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</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>
<Data Name="BugcheckInfoFromEFI">true</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

And another from yesterday:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 5/19/2018 8:12:39 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: CybertronPC
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>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2018-05-20T00:12:39.942315000Z" />
<EventRecordID>12284</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>CybertronPC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</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">3</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">true</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>
 

Discopickle975

Reputable
May 15, 2016
39
2
4,545


I went to the website and went to the bottom solution, since the bugcheckercode is 0. I have so far tried all of the recommendations (disable overclocking which wasn't enabled in the first place, check to make sure PSU can handle the wattage, check for overheating, reset to defaults) except for the memory checker one. That one I am going to do at a later date when I have more time. I will update you when I check the memory with the standard windows memory diagnostic tool.