PC random shutdowns and then reboots (system log included)

[Hemanse]

Specs: 3700X, MS B450 Tomahawk MAX, Crusial Ballstix elite memory / TridentZ Neo memory (not installed at the same time), MSI RTX 2070S and a Corsair RM750X

 

I have been dealing with problems where my PC will randomly shutdown and immediately restart. It seems to mostly happen within 10-15 mins of the PC booting up, but it also happend 2 times today while running a dskchk on startup.

 

The problem is that i happens quite randomly. It happend a few times yesterday, but once it sort of stopped, i ran a AIDA64 stress test with everything enabled for 7 hours while out and it runs just fine with no overheating or crashes.

 

This is what i have tried so far:

 

Memory in different slots and changing out the memory kit for a different one

Updated BIOS, chipset and GPU drivers to the latest

SFC scan and repair
CHKDSK scan and repair

Making sure all cables in the PC are seated firmly again

And so on

 

I have noticed one thing while looking at the system log. I see a pages of "spam" with this error that seems to coincide with the crashes and reboots, but looking it up, i cant really find any info on it, especially since mine just says Unknown error source and no error

 

 

I am kinda stuck on what to do, maybe a clean Windows install or trying out a different PSU would be the next step?

 

Any help is appreciated as i am kinda stuck

[TatamiMatt]

18 minutes ago, Hemanse said:

Specs: 3700X, MS B450 Tomahawk MAX, Crusial Ballstix elite memory / TridentZ Neo memory (not installed at the same time), MSI RTX 2070S and a Corsair RM750X

 

I have been dealing with problems where my PC will randomly shutdown and immediately restart. It seems to mostly happen within 10-15 mins of the PC booting up, but it also happend 2 times today while running a dskchk on startup.

 

The problem is that i happens quite randomly. It happend a few times yesterday, but once it sort of stopped, i ran a AIDA64 stress test with everything enabled for 7 hours while out and it runs just fine with no overheating or crashes.

 

This is what i have tried so far:

 

Memory in different slots and changing out the memory kit for a different one

Updated BIOS, chipset and GPU drivers to the latest

SFC scan and repair
CHKDSK scan and repair

Making sure all cables in the PC are seated firmly again

And so on

 

I have noticed one thing while looking at the system log. I see a pages of "spam" with this error that seems to coincide with the crashes and reboots, but looking it up, i cant really find any info on it, especially since mine just says Unknown error source and no error

 

 

I am kinda stuck on what to do, maybe a clean Windows install or trying out a different PSU would be the next step?

 

Any help is appreciated as i am kinda stuck

What is in the detailed section of the crash report?

[Hemanse]

19 minutes ago, TatamiMatt said:

What is in the detailed section of the crash report?

Do you mean the the details in the reports i posted or in the crash log? I can only see a critical error that just shows the system did not shut down properly, but that just seems like a generic error

 

This is from the WHEA error:

 

Quote

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />

  <EventID>19</EventID>

  <Version>0</Version>

  <Level>3</Level>

  <Task>0</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000000000000000</Keywords>

  <TimeCreated SystemTime="2024-01-05T07:14:25.0764504Z" />

  <EventRecordID>101665</EventRecordID>

  <Correlation ActivityID="{5de9b997-b4e8-4d23-add6-ba9953f0d5f0}" />

  <Execution ProcessID="4088" ThreadID="4636" />

  <Channel>System</Channel>

  <Computer>DESKTOP-P8LS44R</Computer>

  <Security UserID="S-1-5-19" />

  </System>

- <EventData>

  <Data Name="ErrorSource">0</Data>

  <Data Name="ApicId">0</Data>

  <Data Name="MCABank">25</Data>

  <Data Name="MciStat">0x98004000003e0000</Data>

  <Data Name="MciAddr">0x0</Data>

  <Data Name="MciMisc">0xd01a0ffe00000000</Data>

  <Data Name="ErrorType">0</Data>

  <Data Name="TransactionType">256</Data>

  <Data Name="Participation">256</Data>

  <Data Name="RequestType">256</Data>

  <Data Name="MemorIO">256</Data>

  <Data Name="MemHierarchyLvl">256</Data>

  <Data Name="Timeout">256</Data>

  <Data Name="OperationType">256</Data>

  <Data Name="Channel">256</Data>

  <Data Name="Length">872</Data>

  <Data Name="RawData">435045521002FFFFFFFF0300020000000200000068030000180E0700050118140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A3DB4CFAB9A63FDA0100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002000000000000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000100F8700000810000B32F87EFFFB8B17000000000000000000000000000000000000000000000000000000000000000002000000020000008229D5CFA63FDA0100000000000000000000000000000000000000001900000000003E0000400098000000000000000000000000FE0F1AD0000000000000000000048303FF000100000000000000000079000000230000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>

  </EventData>

  </Event>

It is also a shutdown and reboot with no BSOD, so the system does not generete a dmp file to help find out whats going on

 

I have now tried flashing back to the BIOS the board shipped to me with, which i can with for many years. I think i only updated the BIOS when i installed a new kit of TridentZ Neo memory. I have now reverted back to the old BIOS and reinstalled the Crucial Ballistix Elite kit i build the PC with and ran for many years. Just to cross off the Neo and BIOS being a culprit

[Bjoolz]

34 minutes ago, Hemanse said:

Do you mean the the details in the reports i posted or in the crash log? I can only see a critical error that just shows the system did not shut down properly, but that just seems like a generic error

 

This is from the WHEA error:

 

It is also a shutdown and reboot with no BSOD, so the system does not generete a dmp file to help find out whats going on

 

I have now tried flashing back to the BIOS the board shipped to me with, which i can with for many years. I think i only updated the BIOS when i installed a new kit of TridentZ Neo memory. I have now reverted back to the old BIOS and reinstalled the Crucial Ballistix Elite kit i build the PC with and ran for many years. Just to cross off the Neo and BIOS being a culprit

Because this is a corrected event, there isn't much info in it. When decoding the raw data you get this: 

Quote

 

Signature:     52455043 -- VALID
Revision:      0210     -- VALID
Signature End: FFFFFFFF -- VALID
 -- RECORD IS VALID --
 -- END SIGNATURE --

 -- HEADER --
Section Count:    0003
Severity:         Fatal
Valid Bits:       00000002
                   - Platform ID Invalid
                   - Timestamp Valid
                   - Partition ID Invalid

Data Length:      00000368 -- VALID
Timestamp:        5 Jan 2024 @ 07:14:24 -- PRECISE: False
Platform ID:      00000000-0000-0000-0000-000000000000
Partition ID:     00000000-0000-0000-0000-000000000000
Creator ID:       cf07c4bd-b789-4e18-b3c4-1f732cb57131 - WHEA_RECORD_CREATOR_GUID
Notify Type:      919448b2-3739-4b7f-a8f1-e0062805c2a3 - CMCI_NOTIFY_TYPE_GUID
Record ID:        01da3fa6b9fa4cdb
Flags:            00000000

Persistence Info: 0000000000000000
Reserved:         000000000000000000000000
 -- END HEADER --

 -- DESCRIPTOR --
Section Offset:   00000158
Section Length:   000000C0
Revision:         0300
Valid Bits:       00
                   - FRU ID Invalid
                   - FRU Text Invalid

Reserved:         00
Flags:            00000001
                   - Primary Section

Section Type:     9876ccad-47b4-4bdb-b65e-16f193c4f3db - PROCESSOR_GENERIC_ERROR_SECTION_GUID
FRU ID:           00000000-0000-0000-0000-000000000000
Section Severity: Fatal 00000002
FRU Text:         0000000000000000000000000000000000000000
 -- END DESCRIPTOR --

 -- PACKET 1 --
57010000000000000002000000000000 -- 0x10
100F8700000000000000000000000000 -- 0x20
00000000000000000000000000000000 -- 0x30
00000000000000000000000000000000 -- 0x40
00000000000000000000000000000000 -- 0x50
00000000000000000000000000000000 -- 0x60
00000000000000000000000000000000 -- 0x70
00000000000000000000000000000000 -- 0x80
00000000000000000000000000000000 -- 0x90
00000000000000000000000000000000 -- 0xa0
00000000000000000000000000000000 -- 0xb0
00000000000000000000000000000000 -- 0xc0
 -- END PACKET --

 -- DESCRIPTOR --
Section Offset:   00000218
Section Length:   00000040
Revision:         0300
Valid Bits:       00
                   - FRU ID Invalid
                   - FRU Text Invalid

Reserved:         00
Flags:            00000000

Section Type:     dc3ea0b0-a144-4797-b95b-53fa242b6e1d - XPF_PROCESSOR_ERROR_SECTION_GUID
FRU ID:           00000000-0000-0000-0000-000000000000
Section Severity: Fatal 00000002
FRU Text:         0000000000000000000000000000000000000000
 -- END DESCRIPTOR --

 -- PACKET 2 --
03000000000000000000000000000000 -- 0x10
100F8700000810000B32F87EFFFB8B17 -- 0x20
00000000000000000000000000000000 -- 0x30
00000000000000000000000000000000 -- 0x40
 -- END PACKET --

 -- DESCRIPTOR --
Section Offset:   00000258
Section Length:   00000110
Revision:         0300
Valid Bits:       00
                   - FRU ID Invalid
                   - FRU Text Invalid

Reserved:         00
Flags:            00000000

Section Type:     8a1e1d01-42f9-4557-9c33-565e5cc3f7e8 - !! INVALID GUID !!
FRU ID:           00000000-0000-0000-0000-000000000000
Section Severity: Fatal 00000002
FRU Text:         0000000000000000000000000000000000000000
 -- END DESCRIPTOR --

 -- PACKET 3 --
02000000020000008229D5CFA63FDA01 -- 0x10
00000000000000000000000000000000 -- 0x20
000000001900000000003E0000400098 -- 0x30
000000000000000000000000FE0F1AD0 -- 0x40
000000000000000000048303FF000100 -- 0x50
00000000000000007900000023000000 -- 0x60
00000000000000000000000000000000 -- 0x70
00000000000010000000000000001000 -- 0x80
00000000000010000000000000001000 -- 0x90
1B000000000000000000000000000000 -- 0xa0
00000000000000000000000000000000 -- 0xb0
00000000000000000000000000000000 -- 0xc0
00000000000000000000000000000000 -- 0xd0
00000000000000000000000000000000 -- 0xe0
00000000000000000000000000000000 -- 0xf0
00000000000000000000000000000000 -- 0x100
00000000000000000000000000000000 -- 0x110
 -- END PACKET --

 

It's basically just the CPU creating a record of an error being  corrected. And that doesn't mean that the error was with the CPU, it's just the CPU's job to do this with WHEA stuff. It can be, just no indication of it. 

 

When you have BSODs and no dump files, the immediate suspect is the storage. As you are getting WHEA events, are you getting WHEA BSODs as well? Please notify me if you are getting WHEA BSODs as we can add a registry setting to have the BSOD screen display more info. There are some other things that can prevent dump file creation.

 

• Storage is encrypted (E.g. using Bitlocker). The dump process happens outside of Windows so it can't access encrypted drives.
• Storage is too full. When it BSODs, it dumps everything in memory and other useful data into the page file and it turns that into a dump file on the next boot. Because of this, it can need as much extra space on the drive as your amount of RAM + 3-5GB. 
• Page file too small. If your drive has room and the page file is on System Managed Size then it shouldn't be an issue. This is just if you have manually set a size for the page file. 
• Faulty storage. The page file can be on any drive or even multiple drives so check which drive(s) has a page file. In Disk Management, look in the bottom half where the partitions are visualized. Below the size of a partition, you should see "page file" on the partitions with a page file.

If you have the page file on something weird like an external drive or if it's on multiple drives, move it. 

[Hemanse]

22 minutes ago, Bjoolz said:

Because this is a corrected event, there isn't much info in it. When decoding the raw data you get this: 

It's basically just the CPU creating a record of an error being  corrected. And that doesn't mean that the error was with the CPU, it's just the CPU's job to do this with WHEA stuff. It can be, just no indication of it. 

 

When you have BSODs and no dump files, the immediate suspect is the storage. As you are getting WHEA events, are you getting WHEA BSODs as well? Please notify me if you are getting WHEA BSODs as we can add a registry setting to have the BSOD screen display more info. There are some other things that can prevent dump file creation.

 

• Storage is encrypted (E.g. using Bitlocker). The dump process happens outside of Windows so it can't access encrypted drives.
• Storage is too full. When it BSODs, it dumps everything in memory and other useful data into the page file and it turns that into a dump file on the next boot. Because of this, it can need as much extra space on the drive as your amount of RAM + 3-5GB. 
• Page file too small. If your drive has room and the page file is on System Managed Size then it shouldn't be an issue. This is just if you have manually set a size for the page file. 
• Faulty storage. The page file can be on any drive or even multiple drives so check which drive(s) has a page file. In Disk Management, look in the bottom half where the partitions are visualized. Below the size of a partition, you should see "page file" on the partitions with a page file.

If you have the page file on something weird like an external drive or if it's on multiple drives, move it. 

I am not getting a BSOD tho. The PC basically just cuts power and restarts with no warning or blue screen. I guess it could be storage, tho i have i ran some benchmarks and tools, which all show that the Corsair MP510 that i have as boot drive is fine

 

No encryption, storage is 50% full and i have never touched the pagefile to my knowledge

 

I have reverted back to the BIOS the motherboard came with and installed the Ballistix memory i build the system with, instead of the 32GB kit of TridentZ Neo i upgraded to. I remember i updated the BIOS when i installed the new ram, so could maybe be either. 

[TatamiMatt]

1 minute ago, Hemanse said:

I am not getting a BSOD tho. The PC basically just cuts power and restarts with no warning or blue screen. I guess it could be storage, tho i have i ran some benchmarks and tools, which all show that the Corsair MP510 that i have as boot drive is fine

 

No encryption, storage is 50% full and i have never touched the pagefile to my knowledge

 

I have reverted back to the BIOS the motherboard came with and installed the Ballistix memory i build the system with, instead of the 32GB kit of TridentZ Neo i upgraded to. I remember i updated the BIOS when i installed the new ram, so could maybe be either. 

How much of a page file do you have dedicated?

[hrbruun]

hej prøv måske at tekke om din strømkabel i dit motherbort er ondlig i og så vis den er så måske flas din bios og wipe din pc og geninstler windos igen 

[Bjoolz]

3 hours ago, Hemanse said:

I am not getting a BSOD tho.

Sorry, I thought you were. My bad. 

[Hemanse]

6 hours ago, TatamiMatt said:

How much of a page file do you have dedicated?

I can see that it is set to 2432mb

 

4 hours ago, hrbruun said:

hej prøv måske at tekke om din strømkabel i dit motherbort er ondlig i og så vis den er så måske flas din bios og wipe din pc og geninstler windos igen 

I checked all cables this morning and all is snug and fine. I downgraded my BIOS to one i used for many years before i started updating when a new one comes out. I guess if none of that works, i will probably try out another PSU and a fresh OS install

 

2 hours ago, Bjoolz said:

Sorry, I thought you were. My bad. 

No problem. I guess it could still be the disk, but the weird thing is that the PC have now been running with a stress test since i went out and just got home. So Cinebench + GPU test on a loop can run for hours with no problem. The PC just shutting off and restarting seems very random, which i guess could also point to a PSU issue, which will probably be the next thing i try out. I will just switch the PSU with my media PC

[Hemanse]

I have downgraded to the BIOS the board came with (7C02v30) and will see if that works, if not, i will give another PSU a try

 

There we improvements to clock speed and boot times with the newer BIOS versions, but if it crashes my PC, its not really useful