F5F Stay Refreshed Hardware Desktop You're experiencing unusual system failures with your computer.

You're experiencing unusual system failures with your computer.

You're experiencing unusual system failures with your computer.

Pages (2): 1 2 Next
A
Aragone
Member
224
07-19-2025, 06:18 AM
#1
Throughout the past eight months, I've experienced puzzling shutdowns. After installing new drivers, they disappeared temporarily before reappearing. Since then, I've refreshed my BIOS, consistently monitored for updates, and verified everything is functioning properly. However, this problem persists. My current assumptions are:

A) A gradual NVMe failure
B) Windows 11 deteriorating over time
C) My RAM not compatible with the motherboard (despite not being an issue before) – especially since AM5 is known for tricky RAM behavior)
D) A slow but steady motherboard malfunction.

I’m hoping this isn’t the case. PC specifications include a Ryzen 7 7700x, Asrock Taichi Carrara x670, 64 GB Corsair RAM (verified), 4 NVMe drives, 2 SSDs, a 2070 MSI Armored 8 GB Corsair 1000W PSU, and an Openhardware Monitor for detailed info. I replaced my Corsair AIO with a Noctura D15 G2 after it failed during one crash, which caused me to restart the PC repeatedly.

My typical usage is mostly browsing, listening to music, or playing Minecraft. During these sessions, I notice audio stuttering, loss of keyboard control, two SATA SSDs failing, and speakers turning off while switching to monitor output. Internet access also drops.

Restarting my PC often triggers a BIOS blue screen error, followed by Windows attempting to recover memory. After this, a system thread error appears briefly, then disappears after a week or a month. Previously, this happened frequently, but now it occurs less often—sometimes once a week or once a month.

I’ve tested extensively with tools like LatencyMon and 3DMark, but haven’t run memtest yet because I suspect RAM rather than hardware failure. I’m not sure why this keeps happening; my motherboard seems fine, and I don’t recall any other issues.

I’ve tried every diagnostic method I can think of—from latency checks to stress tests—and still can’t pinpoint the cause. I’ve even skipped a BIOS update just to rule out that possibility. My main concern is whether RAM might be failing, especially given my recent gaming habits.

I don’t have screenshots of error codes or detailed BSODs, as I didn’t expect such a long pattern. I’m not seeking advice from others because I already understand the signs. However, I’m open to suggestions if you think it helps.

Please note: I edited this on March 30, 2025, by Morality33.
A
Aragone
07-19-2025, 06:18 AM #1

Throughout the past eight months, I've experienced puzzling shutdowns. After installing new drivers, they disappeared temporarily before reappearing. Since then, I've refreshed my BIOS, consistently monitored for updates, and verified everything is functioning properly. However, this problem persists. My current assumptions are:

A) A gradual NVMe failure
B) Windows 11 deteriorating over time
C) My RAM not compatible with the motherboard (despite not being an issue before) – especially since AM5 is known for tricky RAM behavior)
D) A slow but steady motherboard malfunction.

I’m hoping this isn’t the case. PC specifications include a Ryzen 7 7700x, Asrock Taichi Carrara x670, 64 GB Corsair RAM (verified), 4 NVMe drives, 2 SSDs, a 2070 MSI Armored 8 GB Corsair 1000W PSU, and an Openhardware Monitor for detailed info. I replaced my Corsair AIO with a Noctura D15 G2 after it failed during one crash, which caused me to restart the PC repeatedly.

My typical usage is mostly browsing, listening to music, or playing Minecraft. During these sessions, I notice audio stuttering, loss of keyboard control, two SATA SSDs failing, and speakers turning off while switching to monitor output. Internet access also drops.

Restarting my PC often triggers a BIOS blue screen error, followed by Windows attempting to recover memory. After this, a system thread error appears briefly, then disappears after a week or a month. Previously, this happened frequently, but now it occurs less often—sometimes once a week or once a month.

I’ve tested extensively with tools like LatencyMon and 3DMark, but haven’t run memtest yet because I suspect RAM rather than hardware failure. I’m not sure why this keeps happening; my motherboard seems fine, and I don’t recall any other issues.

I’ve tried every diagnostic method I can think of—from latency checks to stress tests—and still can’t pinpoint the cause. I’ve even skipped a BIOS update just to rule out that possibility. My main concern is whether RAM might be failing, especially given my recent gaming habits.

I don’t have screenshots of error codes or detailed BSODs, as I didn’t expect such a long pattern. I’m not seeking advice from others because I already understand the signs. However, I’m open to suggestions if you think it helps.

Please note: I edited this on March 30, 2025, by Morality33.

X
XDMillie
Junior Member
33
07-19-2025, 06:18 AM
#2
I should also mention the audio BSOD people experienced about a month ago because of a failing drive, though it seems to have minimal impact. My PC also crashed unexpectedly when trying to play VR, which might be due to a dead or damaged USB cable or a faulty case.
X
XDMillie
07-19-2025, 06:18 AM #2

I should also mention the audio BSOD people experienced about a month ago because of a failing drive, though it seems to have minimal impact. My PC also crashed unexpectedly when trying to play VR, which might be due to a dead or damaged USB cable or a faulty case.

R
Reapar_Blade
Junior Member
17
07-19-2025, 06:18 AM
#3
What error code appears on your system? If multiple codes exist, list them. Generally, you should investigate the affected part. However, have you increased or decreased the voltage and frequency settings? Have you tested all components using standard BIOS configurations for a short period? Yes, you should also disable XMP settings and run the system with default RAM speeds and latency, keeping all voltages on auto for CPU, GPU, RAM, and motherboard. These parts typically don’t fail instantly unless they’re receiving excessive power. But if overclocking is too aggressive or undervolting too severe, it could push your hardware beyond safe operating limits. Another possibility is a failing drive; verify their condition. Also inspect cables and motherboard mounting points, including front I/O connections, which might cause shorts and trigger shutdowns. As noted, monitor temperatures closely. Pay attention to the PSU temperature as well—especially if it’s outdated, ensure its fans are functioning properly. Sometimes the issue lies with the power supply itself, even when it seems intact.
R
Reapar_Blade
07-19-2025, 06:18 AM #3

What error code appears on your system? If multiple codes exist, list them. Generally, you should investigate the affected part. However, have you increased or decreased the voltage and frequency settings? Have you tested all components using standard BIOS configurations for a short period? Yes, you should also disable XMP settings and run the system with default RAM speeds and latency, keeping all voltages on auto for CPU, GPU, RAM, and motherboard. These parts typically don’t fail instantly unless they’re receiving excessive power. But if overclocking is too aggressive or undervolting too severe, it could push your hardware beyond safe operating limits. Another possibility is a failing drive; verify their condition. Also inspect cables and motherboard mounting points, including front I/O connections, which might cause shorts and trigger shutdowns. As noted, monitor temperatures closely. Pay attention to the PSU temperature as well—especially if it’s outdated, ensure its fans are functioning properly. Sometimes the issue lies with the power supply itself, even when it seems intact.

H
hdoor20
Senior Member
477
07-19-2025, 06:18 AM
#4
I encounter the least frequent BSOD a BIOS ACPI error, yet post-reboot I often face a SYSTEM THREAD EXPECTION problem. It usually disappears temporarily and returns after roughly a week. I don’t adjust my PC’s clock speed, and everything in my system runs normally from the BIOS settings. My machine never shuts down by itself; I always need to restart it manually. I use monitoring tools, but nothing fails when it crashes. During the crash, some USB devices lose control, yet my mouse—still connected via USB—works fine even if the keyboard stops. I can’t power off Windows and lose both of my SATA SSDs. It’s hard to believe a power supply issue is the cause, though I’ll consider that next time. My PC stays on continuously, so it seems RAM-related rather than hardware problems, possibly due to compatibility issues with AM5 before my recent upgrade.
H
hdoor20
07-19-2025, 06:18 AM #4

I encounter the least frequent BSOD a BIOS ACPI error, yet post-reboot I often face a SYSTEM THREAD EXPECTION problem. It usually disappears temporarily and returns after roughly a week. I don’t adjust my PC’s clock speed, and everything in my system runs normally from the BIOS settings. My machine never shuts down by itself; I always need to restart it manually. I use monitoring tools, but nothing fails when it crashes. During the crash, some USB devices lose control, yet my mouse—still connected via USB—works fine even if the keyboard stops. I can’t power off Windows and lose both of my SATA SSDs. It’s hard to believe a power supply issue is the cause, though I’ll consider that next time. My PC stays on continuously, so it seems RAM-related rather than hardware problems, possibly due to compatibility issues with AM5 before my recent upgrade.

M
MagmaLeCool
Junior Member
49
07-19-2025, 06:18 AM
#5
These issues could actually indicate problems with the motherboard or power supply unit. I’d start by testing all USB devices and the USB ports themselves—try moving the mouse and keyboard connections to see if control returns. Since this might point to a hardware or driver conflict, especially on the motherboard, it’s worth checking RAM compatibility. If the system doesn’t boot properly or runs at significantly reduced speeds, it could be due to overclocking or conflicting drivers. In my experience, a RAM issue would only appear if it’s running at higher speeds than rated, with poor timing. If XMP is enabled, consider disabling it to see if performance improves.
M
MagmaLeCool
07-19-2025, 06:18 AM #5

These issues could actually indicate problems with the motherboard or power supply unit. I’d start by testing all USB devices and the USB ports themselves—try moving the mouse and keyboard connections to see if control returns. Since this might point to a hardware or driver conflict, especially on the motherboard, it’s worth checking RAM compatibility. If the system doesn’t boot properly or runs at significantly reduced speeds, it could be due to overclocking or conflicting drivers. In my experience, a RAM issue would only appear if it’s running at higher speeds than rated, with poor timing. If XMP is enabled, consider disabling it to see if performance improves.

N
Nird_Bird
Member
165
07-19-2025, 06:18 AM
#6
My mouse is connected to my keyboard, and I'm using a Razer Black widow Pro. It seems like the problem might be with the motherboard instead of the RAM, because the Asrock site doesn't mention compatibility. Previously, when the PSU had issues, either the system crashed or the power cord was faulty.
N
Nird_Bird
07-19-2025, 06:18 AM #6

My mouse is connected to my keyboard, and I'm using a Razer Black widow Pro. It seems like the problem might be with the motherboard instead of the RAM, because the Asrock site doesn't mention compatibility. Previously, when the PSU had issues, either the system crashed or the power cord was faulty.

L
Lubmo
Member
190
07-19-2025, 06:18 AM
#7
I recently experienced another SYSTEM THREAD BSOD that caused the PC to restart, entering an endless loading screen. After rebooting, the Event Viewer displayed only "Unable to connect remote server ISAgent errors."
L
Lubmo
07-19-2025, 06:18 AM #7

I recently experienced another SYSTEM THREAD BSOD that caused the PC to restart, entering an endless loading screen. After rebooting, the Event Viewer displayed only "Unable to connect remote server ISAgent errors."

O
omniclean
Member
192
07-19-2025, 06:18 AM
#8
Purchased a modest 2x RAM package available on the QVL. Issue resolved. It seems the main concern was compatibility with the RAM type.
O
omniclean
07-19-2025, 06:18 AM #8

Purchased a modest 2x RAM package available on the QVL. Issue resolved. It seems the main concern was compatibility with the RAM type.

F
Frankette44
Posting Freak
809
07-19-2025, 06:18 AM
#9
It seems like you're seeking a fresh perspective beyond your own thoughts. Would you like me to offer another viewpoint?
F
Frankette44
07-19-2025, 06:18 AM #9

It seems like you're seeking a fresh perspective beyond your own thoughts. Would you like me to offer another viewpoint?

H
HU3_M4N1N
Member
56
07-19-2025, 06:18 AM
#10
Here are some points to discuss. First, let's see if you have any dump files from the BSODs. Navigate to C:\Windows\Minidump and verify the presence of minidump files. If available, return to your Windows directory and transfer the Minidump folder to the Downloads folder (or use your desktop if OneDrive isn't syncing). Compress the folder and attach it to a message. Please adhere strictly to instructions since Windows doesn’t allow changes in this area.

Next, regarding SMART status for NVMe SSDs: it’s largely irrelevant. The general health indicator (Good) has been unreliable for over a decade across all drives, as manufacturers control when the status updates and most units are faulty. The percentage value offers little insight into actual drive condition—it mainly reflects remaining write capacity.

For NVMe drives, the critical warning parameter is the only meaningful metric left. In practice, very few faulty NVMe drives show any activity in this area. If you're unsure about a tool for checking NVMe SSDs, there aren’t many reliable options. Some users rely on HD Sentinel, but it depends heavily on SMART data and can miss electrical faults.

If you need to test an NVMe SSD, consider physically removing the drive and observing if the issue persists. The QVL (Quality Version List) isn’t a compatibility guide; it’s about real-world factory testing results. RAM not listed there usually functions properly. AM5 remains compatible with BIOS updates and dual sticks, though four sticks may cause problems.
H
HU3_M4N1N
07-19-2025, 06:18 AM #10

Here are some points to discuss. First, let's see if you have any dump files from the BSODs. Navigate to C:\Windows\Minidump and verify the presence of minidump files. If available, return to your Windows directory and transfer the Minidump folder to the Downloads folder (or use your desktop if OneDrive isn't syncing). Compress the folder and attach it to a message. Please adhere strictly to instructions since Windows doesn’t allow changes in this area.

Next, regarding SMART status for NVMe SSDs: it’s largely irrelevant. The general health indicator (Good) has been unreliable for over a decade across all drives, as manufacturers control when the status updates and most units are faulty. The percentage value offers little insight into actual drive condition—it mainly reflects remaining write capacity.

For NVMe drives, the critical warning parameter is the only meaningful metric left. In practice, very few faulty NVMe drives show any activity in this area. If you're unsure about a tool for checking NVMe SSDs, there aren’t many reliable options. Some users rely on HD Sentinel, but it depends heavily on SMART data and can miss electrical faults.

If you need to test an NVMe SSD, consider physically removing the drive and observing if the issue persists. The QVL (Quality Version List) isn’t a compatibility guide; it’s about real-world factory testing results. RAM not listed there usually functions properly. AM5 remains compatible with BIOS updates and dual sticks, though four sticks may cause problems.

Pages (2): 1 2 Next