F5F Stay Refreshed Hardware Desktop Multiple BSOD occurrences and failed NVMe SSDs reported.

Multiple BSOD occurrences and failed NVMe SSDs reported.

Multiple BSOD occurrences and failed NVMe SSDs reported.

R
RemoteGunner
Junior Member
5
04-11-2020, 01:52 PM
#1
Initial components needed:
- Windows 10 Education Edition 64-bit
- Aorus X570 Elite Mobo
- AMD Ryzen 5 5600X processor
- Cooler Master MASTERLIQUID ML240L RGB V2 AIO
- Corsair Vengeance LPX 2x8GB DDR4-3600 CL18 RAM
- Sabrent Rocket 4.0 500GB M.2 NVMe SSD (used as boot drive)
- Kingston SSDNow V300 120GB SATA SSD
- Seagate Barracuda 1TB SATA HDD
- EVGA GeForce GTX 1060 6GB Gaming (temporary)
- Corsair RM850 (2019) power supply unit
- Lian Li Lancool II Mesh Case
- Focusrite Scarlett 2i2 2nd Gen audio interface
- TP-Link AX3000 Wi-Fi adapter

During the past two years, the system experienced several instability events. Most often, a BSOD appeared with codes such as WHEA_UNCORRECTABLE_ERROR, MEMORY_MANAGEMENT, and CRITICAL_PROCESS_DIED. We checked BIOS, drivers, and Windows regularly, and even reformatted drives multiple times.

We sent details about the problems: frequent crashes under stress, occasional SSD failures, and a recurring WHEA_UNCORRECTABLE_ERROR. After replacing components, we ruled out the motherboard, GPU, and RAM as primary causes. We kept software up to date and performed stress tests.

Issues persisted until April 2023 with a critical process failure followed by SSD disappearance. We suspected the motherboard was involved and ordered an ASUS TUF Gaming X570 PLUS Wi-Fi. After installation and BIOS updates, another BSOD occurred with the same error. We considered replacing the CPU and PSU but decided against it due to risk.

Ongoing tests show continued instability around BSODs, especially when under load. Support is needed for further troubleshooting.
R
RemoteGunner
04-11-2020, 01:52 PM #1

Initial components needed:
- Windows 10 Education Edition 64-bit
- Aorus X570 Elite Mobo
- AMD Ryzen 5 5600X processor
- Cooler Master MASTERLIQUID ML240L RGB V2 AIO
- Corsair Vengeance LPX 2x8GB DDR4-3600 CL18 RAM
- Sabrent Rocket 4.0 500GB M.2 NVMe SSD (used as boot drive)
- Kingston SSDNow V300 120GB SATA SSD
- Seagate Barracuda 1TB SATA HDD
- EVGA GeForce GTX 1060 6GB Gaming (temporary)
- Corsair RM850 (2019) power supply unit
- Lian Li Lancool II Mesh Case
- Focusrite Scarlett 2i2 2nd Gen audio interface
- TP-Link AX3000 Wi-Fi adapter

During the past two years, the system experienced several instability events. Most often, a BSOD appeared with codes such as WHEA_UNCORRECTABLE_ERROR, MEMORY_MANAGEMENT, and CRITICAL_PROCESS_DIED. We checked BIOS, drivers, and Windows regularly, and even reformatted drives multiple times.

We sent details about the problems: frequent crashes under stress, occasional SSD failures, and a recurring WHEA_UNCORRECTABLE_ERROR. After replacing components, we ruled out the motherboard, GPU, and RAM as primary causes. We kept software up to date and performed stress tests.

Issues persisted until April 2023 with a critical process failure followed by SSD disappearance. We suspected the motherboard was involved and ordered an ASUS TUF Gaming X570 PLUS Wi-Fi. After installation and BIOS updates, another BSOD occurred with the same error. We considered replacing the CPU and PSU but decided against it due to risk.

Ongoing tests show continued instability around BSODs, especially when under load. Support is needed for further troubleshooting.

T
Timaan
Junior Member
3
04-11-2020, 07:19 PM
#2
The dump files are attached as requested. Please refer to the pinned thread for further details.
T
Timaan
04-11-2020, 07:19 PM #2

The dump files are attached as requested. Please refer to the pinned thread for further details.

D
Default_Matix
Member
138
04-11-2020, 07:39 PM
#3
We don't have any of the dump files since they're on the dead SSDs.
D
Default_Matix
04-11-2020, 07:39 PM #3

We don't have any of the dump files since they're on the dead SSDs.

C
CoolFox111
Junior Member
11
04-11-2020, 09:49 PM
#4
Hello, CRITICAL_PROCESS_DIED Key reasons behind this error include recent changes on your system. Typically, the most common issue is an unexpected update, followed by file damage that stops essential executables like svchost.exe. Possible factors to explore are: sponsored links, software updates, and system corruption. If you own a mouse, this game may disrupt your sleep. No installation needed—just play for free. Combat Siege Rogue update refers to a recent Windows patch such as Cumulative or security updates that may trigger problems. When you see the update in Microsoft’s release notes, look for guidance on KB5003173. You can search online using terms like “site:Microsoft.com KB5003173” to find relevant advice. Third-party resources might also offer solutions not yet approved by Microsoft. To check recent installations, open the old Windows control panel, go to Programs and Features, and click “View installed updates.” Uninstall any problematic entries by right-clicking and selecting “uninstall.” If that fails, use the Windows Recovery environment and run DISM to remove an offline image. This process can be complex but is covered in Shawn Brink’s TenForums guide on uninstalling Windows updates. It appears you may have corrupted Windows across different versions. If the problem persists despite updates, consider a clean Windows installation using a verified ISO, as some code issues could be present.
C
CoolFox111
04-11-2020, 09:49 PM #4

Hello, CRITICAL_PROCESS_DIED Key reasons behind this error include recent changes on your system. Typically, the most common issue is an unexpected update, followed by file damage that stops essential executables like svchost.exe. Possible factors to explore are: sponsored links, software updates, and system corruption. If you own a mouse, this game may disrupt your sleep. No installation needed—just play for free. Combat Siege Rogue update refers to a recent Windows patch such as Cumulative or security updates that may trigger problems. When you see the update in Microsoft’s release notes, look for guidance on KB5003173. You can search online using terms like “site:Microsoft.com KB5003173” to find relevant advice. Third-party resources might also offer solutions not yet approved by Microsoft. To check recent installations, open the old Windows control panel, go to Programs and Features, and click “View installed updates.” Uninstall any problematic entries by right-clicking and selecting “uninstall.” If that fails, use the Windows Recovery environment and run DISM to remove an offline image. This process can be complex but is covered in Shawn Brink’s TenForums guide on uninstalling Windows updates. It appears you may have corrupted Windows across different versions. If the problem persists despite updates, consider a clean Windows installation using a verified ISO, as some code issues could be present.

_
_SIRENDER_
Member
146
04-16-2020, 02:15 PM
#5
The drives are nonfunctional. Verified dead on another computer. This isn't a software problem.
_
_SIRENDER_
04-16-2020, 02:15 PM #5

The drives are nonfunctional. Verified dead on another computer. This isn't a software problem.

N
NL_Powerrr
Junior Member
27
04-21-2020, 07:34 AM
#6
The failures seem linked to the M.2 port or NVMe storage device. Having two faulty SSDs in a row is unusual, but it’s likely the area next to RAM where they’re installed. I don’t see this as a good fix, though it feels more probable than the motherboard failing gradually. WHEA depends on the CPU’s error logs and the CPU keeps track of PCIe devices. NVMe drives connect via PCIe.
N
NL_Powerrr
04-21-2020, 07:34 AM #6

The failures seem linked to the M.2 port or NVMe storage device. Having two faulty SSDs in a row is unusual, but it’s likely the area next to RAM where they’re installed. I don’t see this as a good fix, though it feels more probable than the motherboard failing gradually. WHEA depends on the CPU’s error logs and the CPU keeps track of PCIe devices. NVMe drives connect via PCIe.

K
kaire2015
Member
232
05-03-2020, 09:35 PM
#7
You're confusing the issues with the motherboards. It seems the Rocket drive didn't work in the Aorus Elite, and the Corsair drive didn't work in the Asus TUF. It's possible both had faulty M.2 slots.
K
kaire2015
05-03-2020, 09:35 PM #7

You're confusing the issues with the motherboards. It seems the Rocket drive didn't work in the Aorus Elite, and the Corsair drive didn't work in the Asus TUF. It's possible both had faulty M.2 slots.

C
CrimsonNacho
Member
208
05-04-2020, 03:42 PM
#8
I thought it was more probable you had two faulty drives.
C
CrimsonNacho
05-04-2020, 03:42 PM #8

I thought it was more probable you had two faulty drives.