Question Newly built PC fails to boot only at first startup of the day ?

[LabrieD]

So I recently rebuilt my PC with almost entirely new parts save for the storage (3 SSD's + 1 HDD) and OS and it's been failing to post only the first time of the day I start it up (VGA & BOOT lights). If I restart it, everything boots perfectly fine it runs everything excellent afterward even if I shut down and boot up again.

Specs:
CPU: AMD Ryzen 7 9800X3D 4.7 GHz 8-core
Cooler: Thermalright Phantom Spirit 120 SE
Mobo: ASRock B650 Steel Legend Wifi ATX AM
RAM: Corsair Vengeance 32 GB (2x16 GB) DDR5-6400 CL32
Storage: Western Digital Black SN850 1 TB M.2 (Hosting Windows 10 Home OS)
Samsung 970 EVO 1 TB
Samsung 860 EVO 500 GB
Seagate BarraCuda 4 TB Internal HDD 3.5 Inch
GPU: XFX RX-79GMERCB9 Radeon RX 7900 GRE 16GB
PSU: be quiet! Pure Power 12M 750W 80+ Gold Certified
Case: be quiet! Shadow Base 800 FX ATX Mid-Tower

I know the Mobo isn't natively compatible with the 9800X3D, so I did the bios update using the button on the IO panel via USB and confirmed it's properly running the latest Bios version now (3.16).
Regarding the VGA light I've tried re-seating the GPU twice now, power cables and all, and it's running the latest drivers, so I'm not sure what else to check. It runs like a champ even under high load (120-240 FPS in Helldivers 2, ZZZ & FFXIV on max settings) after the first restart following the initial failed post test.
As for the BOOT light, I've ensured all of the prior OS data & partitions were wiped from the older SSD's I'm using for storage now and reinstalled windows 10 on the main SSD. I've tried running the system file checker and it didn't find anything post-OS re-install.
I've discharged the CMOS battery, tried disabling fast boot in UEFI, changed out the monitor cables and recent did a full tear-down & re-installation minus the CPU & cooler. Still the same thing.

It's been super difficult to test because I can only replicate it by waiting until the next day so I'm a bit at a loss of what to look into next.

 

[DRagor]

Ugh, this kind of inconsistent symptoms are worst to diagnose. But if we assume your EVGA is fine this would imply your BeQuiet is not guilty either, so it shifts blame onto motherboard. Or some weird combination of problems.

 

[Darkbreeze]

What Windows version are you running?

 

[LabrieD]

What Windows version are you running?

Windows 10 22H2

 

[LabrieD]

Ugh, this kind of inconsistent symptoms are worst to diagnose. But if we assume your EVGA is fine this would imply your BeQuiet is not guilty either, so it shifts blame onto motherboard. Or some weird combination of problems.

Inconsistent is definitely the word for what I’m seeing. I had today off and tested the following. All tests were done leaving the surge protector & PSU on per everyone’s suggestions with the exception of when I changed back to the new PSU. Only shutdowns were done from the desktop start menu.

2/13
Surge protector outlet - Old EVGA PSU - Wait time 1HR: Successful boot

Wall outlet - EVGA PSU - Wait time 1HR: Successful boot

2/14
Wall outlet - EVGA PSU - Wait time 9HR: Successful boot
Restart to UEFI to check RGB settings caused VGA&BOOT failure

Wall outlet - EVGA PSU - Wait time 1HR: Successful boot
Restart to UEFI successful

Surge protector outlet - EVGA PSU - Wait time 3HR: Successful boot
Restart to UEFI successful

PSU swapped
Surge protector outlet - New BQ! PSU - Wait time 1HR: Successful boot
Restart to UEFI successful

Surge protector outlet - BQ! PSU - Wait time 3HR: Successful boot
Restart to UEFI caused VGA&BOOT failure

 

[LabrieD]

It seems 3 hours may be the sweet spot for testing. Changed nothing from the prior test 3 hours ago and it failed to post again. I honestly would have preferred something just exploded at this point so I would at least know what’s broken

 

[Darkbreeze]

Try this. Do this, exactly as outlined, then see if the problem happens going forward. The reason is, fast/hybrid startup and hibernation OFTEN cause problems because in reality the system doesn't always actually shut down. Then cutting power confuses the hell out of it and it has to reconfigure the boot configuration.

Hibernation

Disabling Hibernation is very easy.

You do not want to do this if you have a laptop as Hibernation is essential when a laptop's battery loses charge and the system needs to safely save it's state. If you have a laptop skip disabling Hibernation and instead disable Fast Startup and Hybrid Sleep if you are having issues.
To disable Hibernation:

1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt (Admin)" or right clicking "Command prompt" and selecting "Run as administrator".

2. Type in "powercfg.exe /h off" without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input

3. Now just exit out of command prompt


And for the record, I've encountered problems trying to get systems to "restart to UEFI/BIOS" on a number of different boards, so I would not count that towards your problem. Only if starting from a cold start does the same thing you've been having problems with. The restart to UEFI/BIOS is an entirely different problem.

 

[LabrieD]

Try this. Do this, exactly as outlined, then see if the problem happens going forward. The reason is, fast/hybrid startup and hibernation OFTEN cause problems because in reality the system doesn't always actually shut down. Then cutting power confuses the hell out of it and it has to reconfigure the boot configuration.

Hibernation

Disabling Hibernation is very easy.

You do not want to do this if you have a laptop as Hibernation is essential when a laptop's battery loses charge and the system needs to safely save it's state. If you have a laptop skip disabling Hibernation and instead disable Fast Startup and Hybrid Sleep if you are having issues.
To disable Hibernation:

1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt (Admin)" or right clicking "Command prompt" and selecting "Run as administrator".

2. Type in "powercfg.exe /h off" without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input

3. Now just exit out of command prompt


And for the record, I've encountered problems trying to get systems to "restart to UEFI/BIOS" on a number of different boards, so I would not count that towards your problem. Only if starting from a cold start does the same thing you've been having problems with. The restart to UEFI/BIOS is an entirely different problem.

Well, it booted up successfully this morning with the BQ! PSU in after sitting for about 12 hours. I entered the command line as admin without any issue and testing it again after 4 hours it failed to boot again. Touched nothing on the surge protector or PSU itself. I'll set the timer again and see if it does anything later in the day...

 

[LabrieD]

I've been looking at any other parts still connected that could be affecting this and found out there's apparently a firmware update for my monitors, the Samsung Odyssey G7's, that I was unaware of and some folks did mention a boot failure prior to it. Doubt its the cause but hey, what's to lose? Updated both of them to the final firmware update Samsung made so hopefully that'll help at least. I'll see you all in 4 hours with hopefully good news...

 

[LabrieD]

I've been looking at any other parts still connected that could be affecting this and found out there's apparently a firmware update for my monitors, the Samsung Odyssey G7's, that I was unaware of and some folks did mention a boot failure prior to it. Doubt its the cause but hey, what's to lose? Updated both of them to the final firmware update Samsung made so hopefully that'll help at least. I'll see you all in 4 hours with hopefully good news...

Yeah, no good. Another boot failure after 4 hours.

 

[Darkbreeze]

Now, I'd pull the CPU and make absolutely certain there are no bent pins on the motherboard, not even SLIGHTLY bent, and if there are you MIGHT try very carefully straightening it, otherwise I can't really see much of any way this could be anything other than the board.

 

[LabrieD]

Now, I'd pull the CPU and make absolutely certain there are no bent pins on the motherboard, not even SLIGHTLY bent, and if there are you MIGHT try very carefully straightening it, otherwise I can't really see much of any way this could be anything other than the board.

If there are I’m not seeing any. Hard to get my phone in there for a photo but I’ve been going over this with a magnifying glass and I got nothing.

 

[DaleH]

So I recently rebuilt my PC with almost entirely new parts save for the storage (3 SSD's + 1 HDD) and OS and it's been failing to post only the first time of the day I start it up (VGA & BOOT lights). If I restart it, everything boots perfectly fine it runs everything excellent afterward even if I shut down and boot up again.

Specs:
CPU: AMD Ryzen 7 9800X3D 4.7 GHz 8-core
Cooler: Thermalright Phantom Spirit 120 SE
Mobo: ASRock B650 Steel Legend Wifi ATX AM
RAM: Corsair Vengeance 32 GB (2x16 GB) DDR5-6400 CL32
Storage: Western Digital Black SN850 1 TB M.2 (Hosting Windows 10 Home OS)
Samsung 970 EVO 1 TB
Samsung 860 EVO 500 GB
Seagate BarraCuda 4 TB Internal HDD 3.5 Inch
GPU: XFX RX-79GMERCB9 Radeon RX 7900 GRE 16GB
PSU: be quiet! Pure Power 12M 750W 80+ Gold Certified
Case: be quiet! Shadow Base 800 FX ATX Mid-Tower

I know the Mobo isn't natively compatible with the 9800X3D, so I did the bios update using the button on the IO panel via USB and confirmed it's properly running the latest Bios version now (3.16).
Regarding the VGA light I've tried re-seating the GPU twice now, power cables and all, and it's running the latest drivers, so I'm not sure what else to check. It runs like a champ even under high load (120-240 FPS in Helldivers 2, ZZZ & FFXIV on max settings) after the first restart following the initial failed post test.
As for the BOOT light, I've ensured all of the prior OS data & partitions were wiped from the older SSD's I'm using for storage now and reinstalled windows 10 on the main SSD. I've tried running the system file checker and it didn't find anything post-OS re-install.
I've discharged the CMOS battery, tried disabling fast boot in UEFI, changed out the monitor cables and recent did a full tear-down & re-installation minus the CPU & cooler. Still the same thing.

It's been super difficult to test because I can only replicate it by waiting until the next day so I'm a bit at a loss of what to look into next.

The symptoms seem to indicate that the problem may only, or more frequently, occur when the PC has been off for a period of time. That would make me suspicious that some component(s) have become more sensitive to temperature. Perhaps you could better tell if this hypothesis is correct by blowing a heat gun (hair dryer) over your motherboard before startup. You might have to try this test multiple times before you could draw any conclusion. I would probably apply the heat to the PSU at the same time. I'm not thinking that you'd want to apply a lot of heat - maybe only enough to heat it a few degrees above ambient.

 

[LabrieD]

The symptoms seem to indicate that the problem may only, or more frequently, occur when the PC has been off for a period of time. That would make me suspicious that some component(s) have become more sensitive to temperature. Perhaps you could better tell if this hypothesis is correct by blowing a heat gun (hair dryer) over your motherboard before startup. You might have to try this test multiple times before you could draw any conclusion. I would probably apply the heat to the PSU at the same time. I'm not thinking that you'd want to apply a lot of heat - maybe only enough to heat it a few degrees above ambient.

The room this PC is in is pretty consistently controlled, between 65f-72f. Testing’s shown the issue still happens when started at both ends of that temperature range too.

 

[Ralston18]

Is there anything (error codes, warning, informational) at all in Reliability History/Monitor and/or Event Viewer with respect to the failed 1st start up boots?

Either at the time and date of known 1st startup boot OR at the time of the preceeding shutdown?

Look in Update History as well for any continuing pattern of failed and problem updates.

 

[LabrieD]

Is there anything (error codes, warning, informational) at all in Reliability History/Monitor and/or Event Viewer with respect to the failed 1st start up boots?

Either at the time and date of known 1st startup boot OR at the time of the preceeding shutdown?

Look in Update History as well for any continuing pattern of failed and problem updates.

The only one I'm seeing consistently in event viewer is event 41, "The system has rebooted without cleanly shutting down first", which matches the only consistent message in reliability history. Shows up every time I've had to force it to power down after it gets stuck in the boot failure, also matching the timestamp just now when I booted it up after checking the socket pins. Update history shows all updates performed successfully too.

 

[Darkbreeze]

If the problem is occurring from a cold boot, then there wouldn't be any relevant Windows events or history because the problem happens before it ever even tries to be in the Windows environment, unless I'm entirely off the mark and have misunderstood the entire problem. This is, to the best of my knowledge based on the information I've read, entirely NOT related to anything in Windows. Especially since he already disabled hibernation. This is a hardware level issue. Anytime something happens BEFORE the POST screen can complete or even appear, it is hardware level, not relevant to anything in Windows. Else I'm an idiot and have not the slightest idea how to work on a computer.

I'm calling foul, based on what you've tried and what has not borne fruit, on the motherboard. It's not the PSU. You've tried two different ones. It's not the graphics card. You've tried multiple cards AND the integrated graphics.

I guess the only thing we really haven't looked at are drives and memory, but I've never heard of either of them causing anything like this. I guess as a final shot in the dark before fully condemning the board, you could try disconnecting all the drives and see if you have the same problem on a cold boot.

And, since I don't think it's been suggested and I don't see that you mention having done it, maybe also run Memtest 86 for FOUR FULL PASSES. This will take a while so just let it run and come back to it later. Also, for the purpose of testing I would disable the XMP memory profile before running the test.

Memtest86​

Go to the Passmark software website and download the USB Memtest86 free version. You can do the optical disk version too if for some reason you cannot use a bootable USB flash drive.


Create bootable media using the downloaded Memtest86. Once you have done that, go into your BIOS and configure the system to boot to the USB drive that contains the Memtest86 USB media or the optical drive if using that option.


You CAN use Memtest86+, as they've recently updated the program after MANY years of no updates, but for the purpose of this guide I recommend using the Passmark version as this is a tried and true utility while I've not had the opportunity to investigate the reliability of the latest 86+ release as compared to Memtest86. Possibly, consider using Memtest86+ as simply a secondary test to Memtest86, much as Windows memory diagnostic utility and Prime95 Blend or custom modes can be used for a second opinion utility.

Click here to download Memtest86 USB package​

Create a bootable USB Flash drive:

1. Download the Windows MemTest86 USB image.

2. Right click on the downloaded file and select the "Extract to Here" option. This places the USB image and imaging tool into the current folder.

3. Run the included imageUSB tool, it should already have the image file selected and you just need to choose which connected USB drive to turn into a bootable drive. Note that this will erase all data on the drive.


No memory should ever fail to pass Memtest86 when it is at the default configuration that the system sets it at when you start out or do a clear CMOS by removing the CMOS battery for five minutes.

Best method for testing memory is to first run four passes of Memtest86, all 11 tests, WITH the memory at the default configuration. This should be done BEFORE setting the memory to the XMP profile settings. The paid version has 13 tests but the free version only has tests 1-10 and test 13. So run full passes of all 11 tests. Be sure to download the latest version of Memtest86. Memtest86+ has not been updated in MANY years. It is NO-WISE as good as regular Memtest86 from Passmark software.

If there are ANY errors, at all, then the memory configuration is not stable. Bumping the DRAM voltage up slightly may resolve that OR you may need to make adjustments to the primary timings. There are very few secondary or tertiary timings that should be altered. I can tell you about those if you are trying to tighten your memory timings.

If you cannot pass Memtest86 with the memory at the XMP configuration settings then I would recommend restoring the memory to the default JEDEC SPD of 1333/2133mhz (Depending on your platform and memory type) with everything left on the auto/default configuration and running Memtest86 over again. If it completes the four full passes without error you can try again with the XMP settings but first try bumping the DRAM voltage up once again by whatever small increment the motherboard will allow you to increase it by. If it passes, great, move on to the Prime95 testing.

If it still fails, try once again bumping the voltage if you are still within the maximum allowable voltage for your memory type and test again. If it still fails, you are likely going to need more advanced help with configuring your primary timings and should return the memory to the default configuration until you can sort it out.

If the memory will not pass Memtest86 for four passes when it IS at the stock default non-XMP configuration, even after a minor bump in voltage, then there is likely something physically wrong with one or more of the memory modules and I'd recommend running Memtest on each individual module, separately, to determine which module is causing the issue. If you find a single module that is faulty you should contact the seller or the memory manufacturer and have them replace the memory as a SET. Memory comes matched for a reason as I made clear earlier and if you let them replace only one module rather than the entire set you are back to using unmatched memory which is an open door for problems with incompatible memory.

Be aware that you SHOULD run Memtest86 to test the memory at the default, non-XMP, non-custom profile settings BEFORE ever making any changes to the memory configuration so that you will know if the problem is a setting or is a physical problem with the memory.

 

[Ralston18]

@LabrieD

Two questions;

Question 1): Have you seen or tried this?

https://www.asrock.com/support/QA/FlashbackSOP.pdf

Not something (full disclosure) that I have worked with but when all else has failed may be worth a try. Perhaps others have tried updating BIOS in that manner and can post accordingly.

However, I am leaning towards a hardware problem.

Found this Interesting:

" ' The system has rebooted without cleanly shutting down first', which matches the only consistent message in reliability history."

From Window's viewpoint: " I'm trying to shutdown here and being told to reboot" - or something to that effect. A bit mind-twisting.

And could explain why an error message is being captured at all in Reliability History. Windows is still running.

(Just thinking out loud a bit.)

The time patterns are not consistent but it may indeed be a matter of temperature and some component needing to warm up just a bit in order for the system to successfully boot the first time. Or wiggle a bit to make a connection or cause some needed connection to disconnect. However briefly.

The exact timestamps may be a clue: when were the error messages captured with respect to known startup and shutdown times? Date and time....

This motherboard?

https://download.asrock.com/Manual/B650E Steel Legend WiFi.pdf

[Be sure to verify that I found the applicable manual.]

Question 2): Have you taken a close look at the motherboard to case connections : Power, reset, etc.? Are all those connections fully and firmly in place? Reference physically numbered Page 38, (2.12) in the manual and the Panel 1 connections.

No cable twists, tangles, pinches, kinks, debris, and so forth that could be impacted by expansion/contraction, vibrations, movement (air flows) etc.?

Check the length of the cables for any signs of damage, melting, bare conductor showing.

Try unplugging and replugging the System Panel Header (Panel 1) connections on both ends (motherboard and case) a couple of times. Ensure that the connectors go on smoothly and firmly and that there is no looseness or wiggle.

If Panel1 proves problematic then the motherboard may need replacement.

Otherwise, one more potential culprit may be off the list.

 

[Darkbreeze]

@LabrieD

Two questions;

Question 1): Have you seen or tried this?

https://www.asrock.com/support/QA/FlashbackSOP.pdf

Not to offend, at all, but he indicated in the OP that he's already on the latest BIOS version so not sure really how this would help?

He's also stated that he's had the system apart several times, reconnecting everything, and has tried multiple power supplies and then gone back to the original power supply. So both those questions, I believe, have been answered and addressed previously. Never hurts to double or triple check something though, I agree, but I think at this point it's safe to say he's done that.

 

[Ralston18]

It is all fair game. No offense.

Simply trying to brainstorm or otherwise get some sense as to why Windows is capturing/reporting "The system has rebooted without cleanly shutting down first."

What sort of conditions - hardware, sofware, both would cause that to happen?

Why the reboot to begin with? Or even the shutdown? Chicken or egg question.

A lot has been done thus far.

Indeed likely going over past ground but something else, possibly missed at first, may turn up.

I have been delving a bit into Powershell and the Get-WinEvent cmdlet specifically. Looking for some relevant filter that can narrow down the results from the logs.

Get-WinEvent -ListLog * shows the logs and how many records are in each log. I would be especially curious about the provider logs.

On my system I see logs from Dell, PRTG, Intel (2). PRTG no longer installed - no records in the log.

Reference:

https://learn.microsoft.com/en-us/p....diagnostics/get-winevent?view=powershell-7.5

Actually this link is more direct about it all:

https://powershellfaqs.com/get-windows-event-logs-using-powershell/

From the link:

Get-EventLog -LogName System -EntryType Error, Warning -Newest 200

Easy copy and paste into Powershell.

(My system is showing mulitple Warning repeats involving DCOM and Event ID 10016. Also not happy about something involving Bluetooth. Hmmmm....?)

= = = =

Event Viewer has filters that can be used. If anything, maybe OP can create a filter to find some applicable Event ID and see what results. I just do not know what to filter for. TBD.

I believe that the date and time stamps are relevant.

Planning to ask what Event ID/ Error codes are showing up in Reliability History/Monitor and Event Viewer.
Cannot always rely on the codes but looking for clues at the moment. Maybe "Perfect Storm" scenerio.

 

[Darkbreeze]

Yeah, ok. That is outside the original set of problems. Parameters if you will. My understanding was that the problem only presents during cold boots. If it is doing things like rebooting or freezing or restarting WHILE the OS is running, then that is a different thing AND I must have missed that part because I don't recall that being part of the problem but if it IS, then obviously you have multiple scenario problem and this points even further towards motherboard especially since it's so intermittent AND changeable in regard to conditions.

 

[LabrieD]

If the problem is occurring from a cold boot, then there wouldn't be any relevant Windows events or history because the problem happens before it ever even tries to be in the Windows environment, unless I'm entirely off the mark and have misunderstood the entire problem. This is, to the best of my knowledge based on the information I've read, entirely NOT related to anything in Windows. Especially since he already disabled hibernation. This is a hardware level issue. Anytime something happens BEFORE the POST screen can complete or even appear, it is hardware level, not relevant to anything in Windows. Else I'm an idiot and have not the slightest idea how to work on a computer.

I'm calling foul, based on what you've tried and what has not borne fruit, on the motherboard. It's not the PSU. You've tried two different ones. It's not the graphics card. You've tried multiple cards AND the integrated graphics.

I guess the only thing we really haven't looked at are drives and memory, but I've never heard of either of them causing anything like this. I guess as a final shot in the dark before fully condemning the board, you could try disconnecting all the drives and see if you have the same problem on a cold boot.

And, since I don't think it's been suggested and I don't see that you mention having done it, maybe also run Memtest 86 for FOUR FULL PASSES. This will take a while so just let it run and come back to it later. Also, for the purpose of testing I would disable the XMP memory profile before running the test.

Memtest86​

Go to the Passmark software website and download the USB Memtest86 free version. You can do the optical disk version too if for some reason you cannot use a bootable USB flash drive.


Create bootable media using the downloaded Memtest86. Once you have done that, go into your BIOS and configure the system to boot to the USB drive that contains the Memtest86 USB media or the optical drive if using that option.


You CAN use Memtest86+, as they've recently updated the program after MANY years of no updates, but for the purpose of this guide I recommend using the Passmark version as this is a tried and true utility while I've not had the opportunity to investigate the reliability of the latest 86+ release as compared to Memtest86. Possibly, consider using Memtest86+ as simply a secondary test to Memtest86, much as Windows memory diagnostic utility and Prime95 Blend or custom modes can be used for a second opinion utility.

Click here to download Memtest86 USB package​

Create a bootable USB Flash drive:

1. Download the Windows MemTest86 USB image.

2. Right click on the downloaded file and select the "Extract to Here" option. This places the USB image and imaging tool into the current folder.

3. Run the included imageUSB tool, it should already have the image file selected and you just need to choose which connected USB drive to turn into a bootable drive. Note that this will erase all data on the drive.


No memory should ever fail to pass Memtest86 when it is at the default configuration that the system sets it at when you start out or do a clear CMOS by removing the CMOS battery for five minutes.

Best method for testing memory is to first run four passes of Memtest86, all 11 tests, WITH the memory at the default configuration. This should be done BEFORE setting the memory to the XMP profile settings. The paid version has 13 tests but the free version only has tests 1-10 and test 13. So run full passes of all 11 tests. Be sure to download the latest version of Memtest86. Memtest86+ has not been updated in MANY years. It is NO-WISE as good as regular Memtest86 from Passmark software.

If there are ANY errors, at all, then the memory configuration is not stable. Bumping the DRAM voltage up slightly may resolve that OR you may need to make adjustments to the primary timings. There are very few secondary or tertiary timings that should be altered. I can tell you about those if you are trying to tighten your memory timings.

If you cannot pass Memtest86 with the memory at the XMP configuration settings then I would recommend restoring the memory to the default JEDEC SPD of 1333/2133mhz (Depending on your platform and memory type) with everything left on the auto/default configuration and running Memtest86 over again. If it completes the four full passes without error you can try again with the XMP settings but first try bumping the DRAM voltage up once again by whatever small increment the motherboard will allow you to increase it by. If it passes, great, move on to the Prime95 testing.

If it still fails, try once again bumping the voltage if you are still within the maximum allowable voltage for your memory type and test again. If it still fails, you are likely going to need more advanced help with configuring your primary timings and should return the memory to the default configuration until you can sort it out.

If the memory will not pass Memtest86 for four passes when it IS at the stock default non-XMP configuration, even after a minor bump in voltage, then there is likely something physically wrong with one or more of the memory modules and I'd recommend running Memtest on each individual module, separately, to determine which module is causing the issue. If you find a single module that is faulty you should contact the seller or the memory manufacturer and have them replace the memory as a SET. Memory comes matched for a reason as I made clear earlier and if you let them replace only one module rather than the entire set you are back to using unmatched memory which is an open door for problems with incompatible memory.

Be aware that you SHOULD run Memtest86 to test the memory at the default, non-XMP, non-custom profile settings BEFORE ever making any changes to the memory configuration so that you will know if the problem is a setting or is a physical problem with the memory.

Ran Memtest86 via the link provided with both default configuration and the XMP1-6400 profile to match the DRAM's actual listed speed and both passed without any issue. Ran the Prime95 for about a half hour and temp didn't even exceed 85c/185f at peak load.

 

[LabrieD]

@LabrieD

Two questions;

Question 1): Have you seen or tried this?

https://www.asrock.com/support/QA/FlashbackSOP.pdf

Not something (full disclosure) that I have worked with but when all else has failed may be worth a try. Perhaps others have tried updating BIOS in that manner and can post accordingly.

However, I am leaning towards a hardware problem.

Found this Interesting:

" ' The system has rebooted without cleanly shutting down first', which matches the only consistent message in reliability history."

From Window's viewpoint: " I'm trying to shutdown here and being told to reboot" - or something to that effect. A bit mind-twisting.

And could explain why an error message is being captured at all in Reliability History. Windows is still running.

(Just thinking out loud a bit.)

The time patterns are not consistent but it may indeed be a matter of temperature and some component needing to warm up just a bit in order for the system to successfully boot the first time. Or wiggle a bit to make a connection or cause some needed connection to disconnect. However briefly.

The exact timestamps may be a clue: when were the error messages captured with respect to known startup and shutdown times? Date and time....

This motherboard?

https://download.asrock.com/Manual/B650E Steel Legend WiFi.pdf

[Be sure to verify that I found the applicable manual.]

Question 2): Have you taken a close look at the motherboard to case connections : Power, reset, etc.? Are all those connections fully and firmly in place? Reference physically numbered Page 38, (2.12) in the manual and the Panel 1 connections.

No cable twists, tangles, pinches, kinks, debris, and so forth that could be impacted by expansion/contraction, vibrations, movement (air flows) etc.?

Check the length of the cables for any signs of damage, melting, bare conductor showing.

Try unplugging and replugging the System Panel Header (Panel 1) connections on both ends (motherboard and case) a couple of times. Ensure that the connectors go on smoothly and firmly and that there is no looseness or wiggle.

If Panel1 proves problematic then the motherboard may need replacement.

Otherwise, one more potential culprit may be off the list.

The FlashbackSOP was actually the very first thing I did with the system and verified it's the most up-to-date one, before I even put the CPU in. I was seeing part compatibility checkers saying the out-of-box BIOS for the board wouldn't be able to support the 9800X3D without it so I figured that would be my first step.
I believe Darkbreeze does have the right of it though, I probably did not represent the information as clearly as I could have. I encountered the issue again this morning but the event viewer and reliability history lacks a log of an error within the last 24 hours from right now.

With the way I initially had my cables laid out I would have believed that could be a problem, since I routed as many as I could through the back panel gap, but when swapping to the old PSU and then back to the new one most of the cables were pretty slack so I could access all the parts easily. Every cable looked clean, I did a full tear-down to check the back of the board for damage and all plugs available inserted cleanly when put back together.

 

[Ralston18]

Helpful:

" I encountered the issue again this morning but the event viewer and reliability history lacks a log of an error within the last 24 hours from right now."

It may not be an error per se....

I have done a bit of Googling and Powershell testing.

Came with the following two cmdlets:


Get-WinEvent -FilterHashtable @{LogName='System' } | Where-Object -Property Message -Match 'reboot'

Get-WinEvent -FilterHashtable @{LogName='System' } | Where-Object -Property Message -Match 'shutdown'
What each cmdlet does is look in the System logs for entries where the message includes 'reboot' or 'shutdown'

Open Powershell, copy and past in the first cmdlet and run it.

The results should be similar to the following from my PC:

======

PS C:\Users\UserNameRedacted> Get-WinEvent -FilterHashtable @{LogName='System' } | Where-Object -Property Message -Match 'shutdown'


ProviderName: Microsoft-Windows-Dhcp-Client

TimeCreated Id LevelDisplayName Message
----------- -- ---------------- -------
2/16/2025 7:26:22 AM 50103 Information DHCPv4 client registered for shutdown notification


ProviderName: Microsoft-Windows-Kernel-Boot

TimeCreated Id LevelDisplayName Message
----------- -- ---------------- -------
2/16/2025 7:26:07 AM 20 Information The last shutdown's success status was true. The last boot's su...


ProviderName: Microsoft-Windows-Kernel-Power

TimeCreated Id LevelDisplayName Message
----------- -- ---------------- -------
2/15/2025 9:01:49 PM 109 Information The kernel power manager has initiated a shutdown transition....


ProviderName: Microsoft-Windows-Dhcp-Client

And more......

Note the TimeCreated field. Any entries of any sort matching the last time the issue occured?

= = = =

The target log (LogName) can be changed as can -Match value e.g., reboot or shutdown

The objective simply to narrow down log searches to log entries that correspond to some extent (hopefully) with the cited Windows messages. Then look at the other information: TimeCreated, IdLevel,,DisplayName, Message.