[SOLVED] Windows 10 PC Crash reboot when stressing ressources

Apr 11, 2020
3
0
10
Hi,

Since 2 days from now, I've got some strange reboot on the computer when I'm playing game (no matter if their hungry or not in ressources eg. Wow, DBZ Kakarot, VR Games, Spellcaster University ... )
The computer is about 6 months old and is fairly recent regarding hardware.
Just in case I allready did a full windows reinstall.
Here's the spec :

CPU :
AMD Ryzen 7 3700X (3.7 GHz)
Socket AM4 - Octo Core - Cache 36 Mo - Matisse
MotherBoard :
Gigabyte X470 AORUS ULTRA GAMING
ATX - Socket AM4 - Chipset AMD X470 - USB 3.1 - SATA 6 Gb/s - M.
Ram :
DDR4 Corsair Vengeance LPX, Black, 16 Go (2 x 8 Go), 3000 MHz, CAS 15
Kit Dual Channel - PC-24000
CPU Fan :
Cryorig H5 Ultimate
GPU :
Gigabyte GeForce RTX 2070 GAMING OC, 8 Go
M.2 :
Gigabyte Aorus RGB SSD, 256 Go, M.2 (Type 2280)
SSD :
2 x 1to SSD (not remembering the brand)

HDD :
Seagate BarraCuda, 2 To
PSU :
Cooler Master MWE Gold 650 FM, 650W

As for crash rebort here what I got in event log :

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="2020-04-11T22:45:28.601145500Z" />
  <EventRecordID>772</EventRecordID>
  <Correlation />
  <Execution ProcessID="4" ThreadID="8" />
  <Channel>System</Channel>
  <Computer>DESKTOP-F139KGP</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">false</Data>
  <Data Name="CheckpointStatus">0</Data>
  </EventData>
  </Event>

And here's HWInfo on idle and when running 3DMark to force a crash (which happen in about 1 minute or 2)

Idle : https://ibb.co/Cs8SR5N

3D Mark : https://ibb.co/SBBhtyW

I'm no expert but I suspect PSU faillure but I wanted to be sure before getting a new one if you have any clue it would be more than welcome.
 
Last edited:
Solution
Ok sorry, took me some time I struggled with memtest (and still do though I've got some logs) for some reason I can't seem to get past the part where it run "Testing multiprocessor support" and don't have any splash screen with configuration available.

Still, I did DDU reinstall of nvidia driver and ran a 3dMark test, still rebooted computer after about 2 minutes of test running.
The windows event is a generic critical error for an unexpected shutdown as far as I can tell. This can be caused by a variety of issues so it is diagnostically idiopathic. Now The memtest; I have personally not ever looked at a memtest log and for whatever reason, I cannot download it anyway. I would try to run the Windows Memory Diagnostic which is...
Apr 11, 2020
3
0
10
Reinstall graphics drivers with DDU and run memtest if you still have issues. If you still have issues come back to post about them.

Ok sorry, took me some time I struggled with memtest (and still do though I've got some logs) for some reason I can't seem to get past the part where it run "Testing multiprocessor support" and don't have any splash screen with configuration available.

Still, I did DDU reinstall of nvidia driver and ran a 3dMark test, still rebooted computer after about 2 minutes of test running.

Here's the Event Log on Windows :

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="2020-04-12T00:30:51.690286100Z" />
  <EventRecordID>1796</EventRecordID>
  <Correlation />
  <Execution ProcessID="4" ThreadID="8" />
  <Channel>System</Channel>
  <Computer>DESKTOP-F139KGP</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">6</Data>
  <Data Name="PowerButtonTimestamp">0</Data>
  <Data Name="BootAppStatus">3221225684</Data>
  <Data Name="Checkpoint">16</Data>
  <Data Name="ConnectedStandbyInProgress">false</Data>
  <Data Name="SystemSleepTransitionsToOn">1</Data>
  <Data Name="CsEntryScenarioInstanceId">0</Data>
  <Data Name="BugcheckInfoFromEFI">false</Data>
  <Data Name="CheckpointStatus">0</Data>
  </EventData>
  </Event>

As for the memtest Log here's what I got :

(adding download link to prevent to long text)

memtestlog
 
Ok sorry, took me some time I struggled with memtest (and still do though I've got some logs) for some reason I can't seem to get past the part where it run "Testing multiprocessor support" and don't have any splash screen with configuration available.

Still, I did DDU reinstall of nvidia driver and ran a 3dMark test, still rebooted computer after about 2 minutes of test running.
The windows event is a generic critical error for an unexpected shutdown as far as I can tell. This can be caused by a variety of issues so it is diagnostically idiopathic. Now The memtest; I have personally not ever looked at a memtest log and for whatever reason, I cannot download it anyway. I would try to run the Windows Memory Diagnostic which is included with win10. Run it for at least 4 passes (this will take hours). I would not worry about the memtest error as it seems to be unrelated to your issue. I would also check to see if there are any BIOS updates for your motherboard and do that if there are.
 
Solution