F5F Stay Refreshed Hardware Desktop This processor and graphics card are stuck in an endless startup cycle.

This processor and graphics card are stuck in an endless startup cycle.

This processor and graphics card are stuck in an endless startup cycle.

N
NaRuToDeI
Member
53
02-17-2019, 01:24 PM
#1
Hello, I've set up my system since January 2020 with a Ryzen 5 3600 and an MSI x470 Gaming Plus Mobo. It runs a dual-boot of Windows 10 and Linux. Everything was fine until recently when the machine started rebooting unexpectedly in both environments. The issue has intensified over time, often shutting down before any login appears. I've changed the power supply, memory, GPU, and even booted from a Linux Live USB, but the problem persists. I can access BIOS normally and reset settings, yet when trying to launch Linux I see occasional error codes. [0.550017] mce: Hardware Error: CPU 0 Machine Check: 0 Bank 11: fea020000004010b [0.550019] mce: Hardware Error: TSC 0 ADDR 3f9e18600 MISC d012000600000000 SYMD 1bc971d47060a IPID 700b020750000 [0.550021] mce: Hardware Error: PROCESSOR 2:870f10 TIME 1590603861 SOCKET 0 APIC 0 microcode 8701013 It seems the CPU might be faulty, but it's puzzling that this happened suddenly after months of stable operation. Any advice or assistance would be invaluable!
N
NaRuToDeI
02-17-2019, 01:24 PM #1

Hello, I've set up my system since January 2020 with a Ryzen 5 3600 and an MSI x470 Gaming Plus Mobo. It runs a dual-boot of Windows 10 and Linux. Everything was fine until recently when the machine started rebooting unexpectedly in both environments. The issue has intensified over time, often shutting down before any login appears. I've changed the power supply, memory, GPU, and even booted from a Linux Live USB, but the problem persists. I can access BIOS normally and reset settings, yet when trying to launch Linux I see occasional error codes. [0.550017] mce: Hardware Error: CPU 0 Machine Check: 0 Bank 11: fea020000004010b [0.550019] mce: Hardware Error: TSC 0 ADDR 3f9e18600 MISC d012000600000000 SYMD 1bc971d47060a IPID 700b020750000 [0.550021] mce: Hardware Error: PROCESSOR 2:870f10 TIME 1590603861 SOCKET 0 APIC 0 microcode 8701013 It seems the CPU might be faulty, but it's puzzling that this happened suddenly after months of stable operation. Any advice or assistance would be invaluable!

T
Tyclonek
Member
81
02-17-2019, 09:56 PM
#2
The software passes the machine check yet fails the BIOS test. Fast boot is set to enable by default—consider turning it off temporarily to let the BIOS complete its self-check.
T
Tyclonek
02-17-2019, 09:56 PM #2

The software passes the machine check yet fails the BIOS test. Fast boot is set to enable by default—consider turning it off temporarily to let the BIOS complete its self-check.

M
Ms1990
Member
50
03-06-2019, 09:52 PM
#3
Thanks for the advice. It didn't work as expected. I was able to restart into Windows by changing the CPU ratio from Auto (36) to 30 manually. Going above that causes a boot loop. I'm sticking with the Auto setting and the voltage is set to "Auto." Noticing a big difference when adjusting the ratio—1.1v at 30, 1.45v at 36. I recall it was on Auto at 1.45v before it worked well. Temperature seems fine. Edit: Even at 3Ghz the system remains unstable in Windows. I had a hard reset after launching a Steam game and another when opening Task Manager. The CPU blinking Mobo Debug LED happens during these events.
M
Ms1990
03-06-2019, 09:52 PM #3

Thanks for the advice. It didn't work as expected. I was able to restart into Windows by changing the CPU ratio from Auto (36) to 30 manually. Going above that causes a boot loop. I'm sticking with the Auto setting and the voltage is set to "Auto." Noticing a big difference when adjusting the ratio—1.1v at 30, 1.45v at 36. I recall it was on Auto at 1.45v before it worked well. Temperature seems fine. Edit: Even at 3Ghz the system remains unstable in Windows. I had a hard reset after launching a Steam game and another when opening Task Manager. The CPU blinking Mobo Debug LED happens during these events.

S
ShinyKirby
Member
145
03-07-2019, 01:09 AM
#4
Are the operating systems installed on separate partitions using different drives? Perhaps switch to another drive and disconnect all currently connected ones to isolate them. Since you haven’t encountered many BIOS or BIOS-related problems, the board isn’t showing any known issues yet. Just want to rule out other hardware problems before considering a repair return.
S
ShinyKirby
03-07-2019, 01:09 AM #4

Are the operating systems installed on separate partitions using different drives? Perhaps switch to another drive and disconnect all currently connected ones to isolate them. Since you haven’t encountered many BIOS or BIOS-related problems, the board isn’t showing any known issues yet. Just want to rule out other hardware problems before considering a repair return.

M
mccoop03
Posting Freak
910
03-07-2019, 01:21 AM
#5
Here are some alternative approaches you could try:
- Consider different storage interfaces like PCIe or M.2 directly.
- Check if your system supports a more stable OS version.
- Test with a minimal boot environment to isolate the issue.
- Verify hardware compatibility and driver support.
M
mccoop03
03-07-2019, 01:21 AM #5

Here are some alternative approaches you could try:
- Consider different storage interfaces like PCIe or M.2 directly.
- Check if your system supports a more stable OS version.
- Test with a minimal boot environment to isolate the issue.
- Verify hardware compatibility and driver support.

T
TugaCarlos
Member
165
03-08-2019, 06:25 AM
#6
After disconnecting the CPU, proceed with the return merchandise authorization. Because the system is offline, also return the motherboard along with the order.
T
TugaCarlos
03-08-2019, 06:25 AM #6

After disconnecting the CPU, proceed with the return merchandise authorization. Because the system is offline, also return the motherboard along with the order.

B
Broflash
Senior Member
740
03-08-2019, 07:08 AM
#7
Great! You're welcome!
B
Broflash
03-08-2019, 07:08 AM #7

Great! You're welcome!