Aug 31, 2022
7
0
10
Hello,

I've been going crazy the last few weeks trying to figure out the cause of random shutdowns in games (Black Desert Online, War Thunder) and while just booted to Windows 10 and doing nothing.

Initially, I had a situation where a power outage in my entire house caused my previous Ryzen 5 5600x to fail, and wouldn't be recognized by the motherboard. I've since replaced it with a new 5600x, new RAM, new motherboard, and new PSU. So far, since upgrading those parts I've had almost nothing but issues.

Here's my
Motherboard is an ASUS TUF Gaming x570-Plus (Wi-Fi)
RAM is Corsair Vengeance RGB Pro DDR4 2x16GB 3200MHz
CPU is Ryzen 5 5600x
GPU is GeForce RTX 3070
PSU is Corsair RM850x

Machine Id: {F1FE67CA-4EDE-43EE-8884-1332857ADA21}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 4403 (type: UEFI)
Processor: AMD Ryzen 5 5600X 6-Core Processor (12 CPUs), ~3.7GHz
Memory: 32768MB RAM
Available OS Memory: 32682MB RAM
Page File: 8406MB used, 29139MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.1741 64bit Unicode

and a link to my google drive with full event files, OCCT test info, and DxDiag
From the Event Viewer, I get mostly WHEA-Logger with Event ID 18 Task Category None, and Kernel Power with Event ID 41, Task Category (63). I'll include my Event Files here, though, with more specific info. Here's the last two errors from this morning:

[ Name]Microsoft-Windows-WHEA-Logger
[ Guid]{c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID18

Version0

Level2

Task0

Opcode0

Keywords0x8000000000000000

-TimeCreated
[ SystemTime]2022-08-31T12:23:20.7319219Z

EventRecordID31545

-Correlation
[ ActivityID]{ef32f06a-193a-4d9f-8cc7-edc3c9305e7c}

-Execution
[ ProcessID]4940
[ ThreadID]5856

ChannelSystem

ComputerDESKTOP-HHHR7P0

-Security
[ UserID]S-1-5-19

-EventData

ErrorSource3

ApicId4

MCABank5

MciStat0xbaa0000000040150

MciAddr0x0

MciMisc0xd01a0ffe00000000

ErrorType9

TransactionType0

Participation256

RequestType5

MemorIO256

MemHierarchyLvl0

Timeout256

OperationType256

Channel256

Length936

RawData435045521002FFFFFFFF03000100000002000000A803000007170C001F0816140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBC970B26B34BDD80102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010300000000120FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000400000000000000120FA20000080C040B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C01000000000000009F0014060000000000000000000000000000000000000000000000000000000000000000000000000200000002000000453F176D34BDD801040000000000000000000000000000000000000005000000500104000000A0BA000000000000000000000000FE0F1AD0000000000400000000000000B00005000800004D00000000F9010000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ Name]Microsoft-Windows-Kernel-Power
[ Guid]{331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID41

Version8

Level1

Task63

Opcode0

Keywords0x8000400000000002

-TimeCreated
[ SystemTime]2022-08-31T12:23:07.5029702Z

EventRecordID31505

Correlation

-Execution
[ ProcessID]4
[ ThreadID]8

ChannelSystem

ComputerDESKTOP-HHHR7P0

-Security
[ UserID]S-1-5-18

-EventData

BugcheckCode0

BugcheckParameter10x0

BugcheckParameter20x0

BugcheckParameter30x0

BugcheckParameter40x0

SleepInProgress0

PowerButtonTimestamp0

BootAppStatus0

Checkpoint0

ConnectedStandbyInProgressfalse

SystemSleepTransitionsToOn0

CsEntryScenarioInstanceId0

BugcheckInfoFromEFIfalse

CheckpointStatus0

CsEntryScenarioInstanceIdV20

LongPowerButtonPressDetectedfalse

From the Reliability Monitor, I see Hardware errors with the following info:
Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 124
Parameter 1: 0
Parameter 2: ffffe7859fc82a40
Parameter 3: baa00000
Parameter 4: 40150
OS version: 10_0_19044
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033

and

Problem signature
Problem Event Name: BlueScreen
Code: a
Parameter 1: ffffed88c5cb76d0
Parameter 2: 2
Parameter 3: 1
Parameter 4: fffff8017b052e68
OS version: 10_0_19044
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033

So far, I've tried testing out
  • various modes of over and underclocking with Ryzen Master and ASUS BIOS, and nothing's resolved the issue
  • Running memtest86 yielded no errors over 5 passes
  • OCCT consistently turns up error strings in CPU tests:
00:00:00 - Info - Test schedule started at 2022-08-29 15:02:02
00:00:00 - Info - CPU - Started (Duration : 01:00:00)
00:00:53 - Error - CPU - 2 error(s) found on physical core #4 (Virtual core #8)
00:00:53 - Error - CPU - 3 error(s) found on physical core #4 (Virtual core #9)
00:00:54 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:54 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:55 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:55 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:00:56 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:56 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:57 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:57 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:58 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:58 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:00:59 - Error - CPU - 4 error(s) found on physical core #4 (Virtual core #8)
00:00:59 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:01:00 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8) etc
  • With OCCT, if I run a CPU test with the load type as Variable, I'll get the above string of errors. If I run it with the mode Normal, it'll typically run until I stop it, but if I run it on "Extreme" it'll BSOD or power off before displaying any CPU Errors.
  • I've reseated RAM, CPU, GPU, and issues persist
  • Doesn't seem related to anything I'm actively doing, but I suspect it's something to do with rapidly increasing/decreasing loads on the CPU.
  • I've run DISM /Online /Cleanup-Image /CheckHealth , DISM /Online /Cleanup-Image /RestoreHealth , and all the associated windows validation/verification stuff - windows updated, clean boot, etc., and issues persist
  • I've installed a fresh copy of Windows 10 to another SSD and booted from it. OCCT gave same CPU errors on test both with and without drivers installed from manufacturer website
Please help me, tom's hardware forum. I'm losing my mind about these shutdowns.
 
Last edited:
Hello,

I've been going crazy the last few weeks trying to figure out the cause of random shutdowns in games (Black Desert Online, War Thunder) and while just booted to Windows 10 and doing nothing.

Initially, I had a situation where a power outage in my entire house caused my previous Ryzen 5 5600x to fail, and wouldn't be recognized by the motherboard. I've since replaced it with a new 5600x, new RAM, new motherboard, and new PSU. So far, since upgrading those parts I've had almost nothing but issues.

Here's my
Motherboard is an ASUS TUF Gaming x570-Plus (Wi-Fi)
RAM is Corsair Vengeance RGB Pro DDR4 2x16GB 3200MHz
CPU is Ryzen 5 5600x
GPU is GeForce RTX 3070
PSU is Corsair RM850x

Machine Id: {F1FE67CA-4EDE-43EE-8884-1332857ADA21}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 4403 (type: UEFI)
Processor: AMD Ryzen 5 5600X 6-Core Processor (12 CPUs), ~3.7GHz
Memory: 32768MB RAM
Available OS Memory: 32682MB RAM
Page File: 8406MB used, 29139MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.1741 64bit Unicode

and a link to my google drive with full event files, OCCT test info, and DxDiag
From the Event Viewer, I get mostly WHEA-Logger with Event ID 18 Task Category None, and Kernel Power with Event ID 41, Task Category (63). I'll include my Event Files here, though, with more specific info. Here's the last two errors from this morning:

[ Name]Microsoft-Windows-WHEA-Logger
[ Guid]{c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID18

Version0

Level2

Task0

Opcode0

Keywords0x8000000000000000

-TimeCreated
[ SystemTime]2022-08-31T12:23:20.7319219Z

EventRecordID31545

-Correlation
[ ActivityID]{ef32f06a-193a-4d9f-8cc7-edc3c9305e7c}

-Execution
[ ProcessID]4940
[ ThreadID]5856

ChannelSystem

ComputerDESKTOP-HHHR7P0

-Security
[ UserID]S-1-5-19

-EventData

ErrorSource3

ApicId4

MCABank5

MciStat0xbaa0000000040150

MciAddr0x0

MciMisc0xd01a0ffe00000000

ErrorType9

TransactionType0

Participation256

RequestType5

MemorIO256

MemHierarchyLvl0

Timeout256

OperationType256

Channel256

Length936

RawData435045521002FFFFFFFF03000100000002000000A803000007170C001F0816140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBC970B26B34BDD80102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010300000000120FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000400000000000000120FA20000080C040B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C01000000000000009F0014060000000000000000000000000000000000000000000000000000000000000000000000000200000002000000453F176D34BDD801040000000000000000000000000000000000000005000000500104000000A0BA000000000000000000000000FE0F1AD0000000000400000000000000B00005000800004D00000000F9010000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ Name]Microsoft-Windows-Kernel-Power
[ Guid]{331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID41

Version8

Level1

Task63

Opcode0

Keywords0x8000400000000002

-TimeCreated
[ SystemTime]2022-08-31T12:23:07.5029702Z

EventRecordID31505

Correlation

-Execution
[ ProcessID]4
[ ThreadID]8

ChannelSystem

ComputerDESKTOP-HHHR7P0

-Security
[ UserID]S-1-5-18

-EventData

BugcheckCode0

BugcheckParameter10x0

BugcheckParameter20x0

BugcheckParameter30x0

BugcheckParameter40x0

SleepInProgress0

PowerButtonTimestamp0

BootAppStatus0

Checkpoint0

ConnectedStandbyInProgressfalse

SystemSleepTransitionsToOn0

CsEntryScenarioInstanceId0

BugcheckInfoFromEFIfalse

CheckpointStatus0

CsEntryScenarioInstanceIdV20

LongPowerButtonPressDetectedfalse

From the Reliability Monitor, I see Hardware errors with the following info:
Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 124
Parameter 1: 0
Parameter 2: ffffe7859fc82a40
Parameter 3: baa00000
Parameter 4: 40150
OS version: 10_0_19044
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033

and

Problem signature
Problem Event Name: BlueScreen
Code: a
Parameter 1: ffffed88c5cb76d0
Parameter 2: 2
Parameter 3: 1
Parameter 4: fffff8017b052e68
OS version: 10_0_19044
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033

So far, I've tried testing out
  • various modes of over and underclocking with Ryzen Master and ASUS BIOS, and nothing's resolved the issue
  • Running memtest86 yielded no errors over 5 passes
  • OCCT consistently turns up error strings in CPU tests:
00:00:00 - Info - Test schedule started at 2022-08-29 15:02:02
00:00:00 - Info - CPU - Started (Duration : 01:00:00)
00:00:53 - Error - CPU - 2 error(s) found on physical core #4 (Virtual core #8)
00:00:53 - Error - CPU - 3 error(s) found on physical core #4 (Virtual core #9)
00:00:54 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:54 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:55 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:55 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:00:56 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:56 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:57 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:57 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:58 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:58 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:00:59 - Error - CPU - 4 error(s) found on physical core #4 (Virtual core #8)
00:00:59 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:01:00 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8) etc
  • With OCCT, if I run a CPU test with the load type as Variable, I'll get the above string of errors. If I run it with the mode Normal, it'll typically run until I stop it, but if I run it on "Extreme" it'll BSOD or power off before displaying any CPU Errors.
  • I've reseated RAM, CPU, GPU, and issues persist
  • Doesn't seem related to anything I'm actively doing, but I suspect it's something to do with rapidly increasing/decreasing loads on the CPU.
  • I've run DISM /Online /Cleanup-Image /CheckHealth , DISM /Online /Cleanup-Image /RestoreHealth , and all the associated windows validation/verification stuff - windows updated, clean boot, etc., and issues persist
  • I've installed a fresh copy of Windows 10 to another SSD and booted from it. OCCT gave same CPU errors on test both with and without drivers installed from manufacturer website
Please help me, tom's hardware forum. I'm losing my mind about these shutdowns.
When you built the system did you clear the cmos from any test info? Most of the time this issue stems for a test bench toake sure the system works before sale. So it has a old cpuid registered to it causing the Mobo to fight between to CPU profiles when there's only one CPU..
With the psu unplugged remove the litium battery from your mobo with both removed hold the power button to the system for 30s x2s then reseat the battery in Mobo then psu cable boot system and test
 
Aug 31, 2022
7
0
10
When you built the system did you clear the cmos from any test info? Most of the time this issue stems for a test bench toake sure the system works before sale. So it has a old cpuid registered to it causing the Mobo to fight between to CPU profiles when there's only one CPU..
With the psu unplugged remove the litium battery from your mobo with both removed hold the power button to the system for 30s x2s then reseat the battery in Mobo then psu cable boot system and test

I did clear the cmos when I built it after testing the old cpu, and after resetting CMOS i'm afraid the issues persist
 
Aug 31, 2022
7
0
10
You need to enable xmp In your bios and generally from what I can understand most of the time profile 2 is the most stable I don't know 100% on that part though I don't use Intel to much so I don't mess with xmp all to often
Well, I did what you said and enabled that in bios, and am definitely getting better performance, now! Still getting errors on core 4 in OCCT and restarts, though :\
 
Nov 11, 2022
1
0
10
Hello,

I've been going crazy the last few weeks trying to figure out the cause of random shutdowns in games (Black Desert Online, War Thunder) and while just booted to Windows 10 and doing nothing.

Initially, I had a situation where a power outage in my entire house caused my previous Ryzen 5 5600x to fail, and wouldn't be recognized by the motherboard. I've since replaced it with a new 5600x, new RAM, new motherboard, and new PSU. So far, since upgrading those parts I've had almost nothing but issues.

Here's my
Motherboard is an ASUS TUF Gaming x570-Plus (Wi-Fi)
RAM is Corsair Vengeance RGB Pro DDR4 2x16GB 3200MHz
CPU is Ryzen 5 5600x
GPU is GeForce RTX 3070
PSU is Corsair RM850x

Machine Id: {F1FE67CA-4EDE-43EE-8884-1332857ADA21}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 4403 (type: UEFI)
Processor: AMD Ryzen 5 5600X 6-Core Processor (12 CPUs), ~3.7GHz
Memory: 32768MB RAM
Available OS Memory: 32682MB RAM
Page File: 8406MB used, 29139MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.1741 64bit Unicode

and a link to my google drive with full event files, OCCT test info, and DxDiag
From the Event Viewer, I get mostly WHEA-Logger with Event ID 18 Task Category None, and Kernel Power with Event ID 41, Task Category (63). I'll include my Event Files here, though, with more specific info. Here's the last two errors from this morning:

[ Name]Microsoft-Windows-WHEA-Logger
[ Guid]{c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID18

Version0

Level2

Task0

Opcode0

Keywords0x8000000000000000

-TimeCreated
[ SystemTime]2022-08-31T12:23:20.7319219Z

EventRecordID31545

-Correlation
[ ActivityID]{ef32f06a-193a-4d9f-8cc7-edc3c9305e7c}

-Execution
[ ProcessID]4940
[ ThreadID]5856

ChannelSystem

ComputerDESKTOP-HHHR7P0

-Security
[ UserID]S-1-5-19

-EventData

ErrorSource3

ApicId4

MCABank5

MciStat0xbaa0000000040150

MciAddr0x0

MciMisc0xd01a0ffe00000000

ErrorType9

TransactionType0

Participation256

RequestType5

MemorIO256

MemHierarchyLvl0

Timeout256

OperationType256

Channel256

Length936

RawData435045521002FFFFFFFF03000100000002000000A803000007170C001F0816140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBC970B26B34BDD80102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010300000000120FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000400000000000000120FA20000080C040B32F87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C01000000000000009F0014060000000000000000000000000000000000000000000000000000000000000000000000000200000002000000453F176D34BDD801040000000000000000000000000000000000000005000000500104000000A0BA000000000000000000000000FE0F1AD0000000000400000000000000B00005000800004D00000000F9010000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ Name]Microsoft-Windows-Kernel-Power
[ Guid]{331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID41

Version8

Level1

Task63

Opcode0

Keywords0x8000400000000002

-TimeCreated
[ SystemTime]2022-08-31T12:23:07.5029702Z

EventRecordID31505

Correlation

-Execution
[ ProcessID]4
[ ThreadID]8

ChannelSystem

ComputerDESKTOP-HHHR7P0

-Security
[ UserID]S-1-5-18

-EventData

BugcheckCode0

BugcheckParameter10x0

BugcheckParameter20x0

BugcheckParameter30x0

BugcheckParameter40x0

SleepInProgress0

PowerButtonTimestamp0

BootAppStatus0

Checkpoint0

ConnectedStandbyInProgressfalse

SystemSleepTransitionsToOn0

CsEntryScenarioInstanceId0

BugcheckInfoFromEFIfalse

CheckpointStatus0

CsEntryScenarioInstanceIdV20

LongPowerButtonPressDetectedfalse

From the Reliability Monitor, I see Hardware errors with the following info:
Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 124
Parameter 1: 0
Parameter 2: ffffe7859fc82a40
Parameter 3: baa00000
Parameter 4: 40150
OS version: 10_0_19044
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033

and

Problem signature
Problem Event Name: BlueScreen
Code: a
Parameter 1: ffffed88c5cb76d0
Parameter 2: 2
Parameter 3: 1
Parameter 4: fffff8017b052e68
OS version: 10_0_19044
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19044.2.0.0.256.48
Locale ID: 1033

So far, I've tried testing out
  • various modes of over and underclocking with Ryzen Master and ASUS BIOS, and nothing's resolved the issue
  • Running memtest86 yielded no errors over 5 passes
  • OCCT consistently turns up error strings in CPU tests:
00:00:00 - Info - Test schedule started at 2022-08-29 15:02:02
00:00:00 - Info - CPU - Started (Duration : 01:00:00)
00:00:53 - Error - CPU - 2 error(s) found on physical core #4 (Virtual core #8)
00:00:53 - Error - CPU - 3 error(s) found on physical core #4 (Virtual core #9)
00:00:54 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:54 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:55 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:55 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:00:56 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:56 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:57 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:57 - Error - CPU - 6 error(s) found on physical core #4 (Virtual core #9)
00:00:58 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8)
00:00:58 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:00:59 - Error - CPU - 4 error(s) found on physical core #4 (Virtual core #8)
00:00:59 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #9)
00:01:00 - Error - CPU - 5 error(s) found on physical core #4 (Virtual core #8) etc
  • With OCCT, if I run a CPU test with the load type as Variable, I'll get the above string of errors. If I run it with the mode Normal, it'll typically run until I stop it, but if I run it on "Extreme" it'll BSOD or power off before displaying any CPU Errors.
  • I've reseated RAM, CPU, GPU, and issues persist
  • Doesn't seem related to anything I'm actively doing, but I suspect it's something to do with rapidly increasing/decreasing loads on the CPU.
  • I've run DISM /Online /Cleanup-Image /CheckHealth , DISM /Online /Cleanup-Image /RestoreHealth , and all the associated windows validation/verification stuff - windows updated, clean boot, etc., and issues persist
  • I've installed a fresh copy of Windows 10 to another SSD and booted from it. OCCT gave same CPU errors on test both with and without drivers installed from manufacturer website
Please help me, tom's hardware forum. I'm losing my mind about these shutdowns.

The Problem is same for me too, I've been using that Mobo Asus TUF X570 WiFi for 6 Month with Bios 4021 with no suddeny shutdown
Event Id 41 (The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.)
When using Bios 4021 my sytem cause fTPM issue causes random stuttering because Windows 11 BUT no problem Event ID 41

Example AMD fTPM Ramdom Stutering:
View: https://youtu.be/TYnRL-x6DVI


But the Problem is happen when using Bios 4403
I Already doing like :
  1. Using DDU Reinstall Driver and Reseat Graphics card I Though is my Graphics card the culprit but is Not or is it
  2. Reset CMOS EVERY DAMN TIMEE
  3. Unplug/ Replug DISPLAY PORT
I Saw JayTwoCent video :
View: https://youtu.be/LQG153s1NIM

when my pc messed up can't be power on because that Bios 4403 when eneble ReSizeBar is became troublesome like the pc black screen the power button can't be click just lights on
install NVIDIA_DisplayID_Firmware But that Temporary Fix Still the same suddenyly shutdown but the pc can be restart and click power on

My Possiblity is the BIOS 4403 cause of this and thats the problem :
  1. DOCP TURN ON / TURN OFF STILL THE SAME MY PC SUDDENLY SHUT DOWN EVENT ID 41
  2. ReSize Bar when Enable my pc became worse suddenly shutdown but when click Power On My PC can't be activated
  3. Suddenly Shut Down Event ID 43
4. just write down if Maybe Someone having other issue too ?


PC SPEC :
MOTHERBOARD: ASUS TUF GAMING X570-PLUS (WI-FI)
BIOS VERSION : 4403
CPU : AMD RYZEN 7 5800X
CPU COOLER : NOCTUA NH-U9S
GPU : GIGABYTE RTX 3060 EAGLE 12G
RAM : TEAMGROUP XTREEM ARGB DDR4 2X16GB 3600MHZ (CL18-22-22-42)
PSU : COOLER MASTER MWE 650W GOLD
STORAGE :
SSD : SAMSUNG 980 PRO 1TB NVME
SSD : SAMSUNG SSD 860 EVO 250 GB SATA
HDD : SEAGATE BARRACUDA 2TB X2
DVD-ROM : ASUS DRW-24D3ST
OS : WINDOWS 11 PRO 22H2

I Already Contact ASUS CS after long chit chat yeah the answer is wait for next Bios Update (Asus Solution)
Because iam using Windows 11 22H2 i don't know Windows 10 though
Or just Go back to Bios 4021 at cost fTPM Random Stutering Again (Solution From Me)

Anyone have figure out maybe encounter this isssue and fix this issue ?
 
Last edited: