F5F Stay Refreshed Hardware Desktop Critical process stopped, drives are malfunctioning

Critical process stopped, drives are malfunctioning

Critical process stopped, drives are malfunctioning

A
Aeolo_
Junior Member
2
01-23-2022, 07:44 AM
#1
I've faced some technical problems since November 2024: unexpected freezing and crashes while using UE5 or Helldivers 2. The BSOD appeared quickly, and the PC restarted right away. I turned off autorestart to analyze the BSOD details. The code was CRITICAL_PROCESS_DIED, Windows didn<|pad|> to not save a .DMP file, and Event Viewer showed an error from volmgr about failing to create a dump file. BugCheckProgress was 0x00060049.

My troubleshooting steps: I used Clean Boot, reinstalled Windows (10 and 11), and tried Fedora and Mint to exclude OS issues. Still, crashes persisted. I updated BIOS, drivers, reset CMOS, tested with single RAM sticks without XMP and one NVMe drive, but nothing worked. I ran a full memory test with MEMTEST86 and confirmed stability on another system. I swapped the motherboard for an identical model, yet crashes continued with the same BSOD.

I have four NVMe drives with specific setups:
- Socket 1: Gen 4 PCIe, used for Linux boot (still crashes)
- Socket 2: Gen 4 PCIe, used for Linux (NTFS)
- Socket 3: Gen 3 PCIe, used for Windows Boot (CSmile
- Socket 4: Gen 3 PCIe, used for Linux (still crashes)

If I remove drives from Sockets 1 and 4, the system runs smoothly with UE5 and games. On Linux, when booting from Socket 1, the kernel sometimes fails or crashes mid-session. Drives in Sockets 2 and 3 work temporarily but become unstable. On Windows, BSOD CRITICAL_PROCESS_DIED appears even without data read. Event Viewer logs a warning about disk errors during paging, with a driver error on port 0.

I've checked two identical drives and got the same issues. The failing drives function on another machine. My hardware specs: CPU Ryzen 9 5950X, 128GB DDR4 RAM, GTX 3090 Ti, 1000W PSU, storage including a failing WD SN850 and a failing WD SN750.
A
Aeolo_
01-23-2022, 07:44 AM #1

I've faced some technical problems since November 2024: unexpected freezing and crashes while using UE5 or Helldivers 2. The BSOD appeared quickly, and the PC restarted right away. I turned off autorestart to analyze the BSOD details. The code was CRITICAL_PROCESS_DIED, Windows didn<|pad|> to not save a .DMP file, and Event Viewer showed an error from volmgr about failing to create a dump file. BugCheckProgress was 0x00060049.

My troubleshooting steps: I used Clean Boot, reinstalled Windows (10 and 11), and tried Fedora and Mint to exclude OS issues. Still, crashes persisted. I updated BIOS, drivers, reset CMOS, tested with single RAM sticks without XMP and one NVMe drive, but nothing worked. I ran a full memory test with MEMTEST86 and confirmed stability on another system. I swapped the motherboard for an identical model, yet crashes continued with the same BSOD.

I have four NVMe drives with specific setups:
- Socket 1: Gen 4 PCIe, used for Linux boot (still crashes)
- Socket 2: Gen 4 PCIe, used for Linux (NTFS)
- Socket 3: Gen 3 PCIe, used for Windows Boot (CSmile
- Socket 4: Gen 3 PCIe, used for Linux (still crashes)

If I remove drives from Sockets 1 and 4, the system runs smoothly with UE5 and games. On Linux, when booting from Socket 1, the kernel sometimes fails or crashes mid-session. Drives in Sockets 2 and 3 work temporarily but become unstable. On Windows, BSOD CRITICAL_PROCESS_DIED appears even without data read. Event Viewer logs a warning about disk errors during paging, with a driver error on port 0.

I've checked two identical drives and got the same issues. The failing drives function on another machine. My hardware specs: CPU Ryzen 9 5950X, 128GB DDR4 RAM, GTX 3090 Ti, 1000W PSU, storage including a failing WD SN850 and a failing WD SN750.

Z
zBrennoMelo
Junior Member
37
01-24-2022, 01:32 AM
#2
Hard Disk Sentinel provides insights on the drives. Have you checked the CMOS battery voltage?
Z
zBrennoMelo
01-24-2022, 01:32 AM #2

Hard Disk Sentinel provides insights on the drives. Have you checked the CMOS battery voltage?

G
gamer2hokv
Member
198
01-26-2022, 05:25 PM
#3
I haven't used Hard Disk Sentinel, but I did perform a complete scan with Disk Genius and both WD and Samsung utilities—no bad sectors detected. I installed the drives on another PC to verify; they mount, clean, and format without issues. This made me uncertain if the issue lay with the drives themselves, as they seemed to function properly before. Having two drives from different brands fail simultaneously was unusual. The mounting slots are M2A_CPU and M2D_SB. I haven't checked the CMOS battery voltage and will look for a method to test it.
G
gamer2hokv
01-26-2022, 05:25 PM #3

I haven't used Hard Disk Sentinel, but I did perform a complete scan with Disk Genius and both WD and Samsung utilities—no bad sectors detected. I installed the drives on another PC to verify; they mount, clean, and format without issues. This made me uncertain if the issue lay with the drives themselves, as they seemed to function properly before. Having two drives from different brands fail simultaneously was unusual. The mounting slots are M2A_CPU and M2D_SB. I haven't checked the CMOS battery voltage and will look for a method to test it.

M
MineCraftHuub
Member
92
02-02-2022, 11:19 AM
#4
Hello Lord D, I share the same symptoms since around November 2024. The situation is still unclear. I’ve thoroughly explained everything in your original message. Currently, my operating system becomes less stable over time. I’ll discuss this later. Whether coincidental or not, our setup has some similarities that could be helpful: CPU i9-12900K, memory Asus Strix Z690-A, GPU RTX 2080 Ti, power supply Corsair RM750x. Storage includes NVMe 2TB and two failed drives (Samsung 970 Evo Plus and Samsung 980 SATA). I’m running Windows 11 Pro 10.0.26100.

In my case, different connectors don’t seem to impact stability. The two failed drives can be accessed on another machine, but they aren’t recognized here. Initially, I used Windows 11 on the Corsair drive; after several blue screens (CRITICAL_PROCESS_DIED), my PC entered startup recovery and stopped being detected by BIOS. The data was still readable elsewhere.

Later, I upgraded to Windows 22H2, 23H2, and 24H2 on the 970 Evo Plus (including the Corsair drive). The issues persisted. I repeated the process on the 980, but now the gap between crashes widened (5–10 minutes vs. 1–2 minutes after boot), and the frequency increased as my system aged.

During testing, I ran a GPU check with another card (1070 Ti), flashed the GPU with the latest BIOS, tried CPU diagnostics, and used various tools. The CPU ran into a BAD_POOL_CALLER error after one run, and I had to reset the system. I disabled auto-restart from BSOD and encountered a kernel data page error (KERNEL_DATA_INPAGE_ERROR).

I performed additional checks: stress tests on all components, no link to BSOD. Temperatures stayed normal, with only slight CPU throttling. All drives showed expected speeds in CrystalDiskMark and no issues in CrystalDiskInfo.
M
MineCraftHuub
02-02-2022, 11:19 AM #4

Hello Lord D, I share the same symptoms since around November 2024. The situation is still unclear. I’ve thoroughly explained everything in your original message. Currently, my operating system becomes less stable over time. I’ll discuss this later. Whether coincidental or not, our setup has some similarities that could be helpful: CPU i9-12900K, memory Asus Strix Z690-A, GPU RTX 2080 Ti, power supply Corsair RM750x. Storage includes NVMe 2TB and two failed drives (Samsung 970 Evo Plus and Samsung 980 SATA). I’m running Windows 11 Pro 10.0.26100.

In my case, different connectors don’t seem to impact stability. The two failed drives can be accessed on another machine, but they aren’t recognized here. Initially, I used Windows 11 on the Corsair drive; after several blue screens (CRITICAL_PROCESS_DIED), my PC entered startup recovery and stopped being detected by BIOS. The data was still readable elsewhere.

Later, I upgraded to Windows 22H2, 23H2, and 24H2 on the 970 Evo Plus (including the Corsair drive). The issues persisted. I repeated the process on the 980, but now the gap between crashes widened (5–10 minutes vs. 1–2 minutes after boot), and the frequency increased as my system aged.

During testing, I ran a GPU check with another card (1070 Ti), flashed the GPU with the latest BIOS, tried CPU diagnostics, and used various tools. The CPU ran into a BAD_POOL_CALLER error after one run, and I had to reset the system. I disabled auto-restart from BSOD and encountered a kernel data page error (KERNEL_DATA_INPAGE_ERROR).

I performed additional checks: stress tests on all components, no link to BSOD. Temperatures stayed normal, with only slight CPU throttling. All drives showed expected speeds in CrystalDiskMark and no issues in CrystalDiskInfo.

D
ddgrey
Junior Member
42
02-10-2022, 12:51 AM
#5
Did you modify the firmware of the SN750? The WD and Sandisk products (same owner) experienced problems with Win11 24H2 because of changes in the default RAM cache size (HMB). The Sandisk update only covered 2TB drives, but it’s important to verify. This situation indicates the page file has become corrupted, which is a serious warning about storage health. Have you verified which drive contains the page file? It typically resides on C:, though it can span multiple drives. If uncertain, run the following PowerShell command: Get-CimInstance -ClassName Win32_PageFileUsage -Property * This will show the exact location. If it lists C:\pagefile.sys, that drive is likely the culprit.
D
ddgrey
02-10-2022, 12:51 AM #5

Did you modify the firmware of the SN750? The WD and Sandisk products (same owner) experienced problems with Win11 24H2 because of changes in the default RAM cache size (HMB). The Sandisk update only covered 2TB drives, but it’s important to verify. This situation indicates the page file has become corrupted, which is a serious warning about storage health. Have you verified which drive contains the page file? It typically resides on C:, though it can span multiple drives. If uncertain, run the following PowerShell command: Get-CimInstance -ClassName Win32_PageFileUsage -Property * This will show the exact location. If it lists C:\pagefile.sys, that drive is likely the culprit.

S
SoloDroid
Member
180
02-10-2022, 08:03 AM
#6
I noticed some parallels with your system's situation. Recently I came across discussions about problems with WD Sandisk and Windows 11 24H2. It seemed logical. I began observing problems and BSODs around October, probably after the 24H2 update, though I hadn't realized it until now. All drives and WD as well as Samsung firmware were updated, but the issue persisted. I also reinstalled the latest 23H2 build, currently running 10.0.22631 Build 22631, with NVME updated yet still facing challenges. Other efforts: MB: Swapped drives with the same motherboard, Gigabyte Aero G X570. I downgraded to BIOS F4 2022-12-27 (the one included in the second MB). CPU: I replaced the 5950X with a new 5600X, but the same issues continue. Patterns on the drives seem to cause failures. My WD SN850X 2TB is used for project storage and has never stopped before. Recently, after installing it in the top M.2 slot, it appears inaccessible to Windows. In Disk Manager it loses the label name and a small 2MB unallocated space appears. When I attempt to check and repair, it fails with "The disk check could not be performed because Windows can't access the disk." The fact that every drive in the top slot shows some disconnect prompted me to try a different CPU. Further testing reveals: Scenario 1: Programs run smoothly for hours, no issues in UE5 or Helldivers 2 (my main programs). This is the only stable situation. Bay 1: C: Bay 2: Empty Bay 3: Empty Bay 4: Empty Scenario 2: Bay 1 empty Bay 2 C: Bay 3 H: DATA Bay 4 I: DATA (this drive will fail Scenario 3: Bay 1 DATA(this drive will fail) Bay 2 C: Bay 3 H: DATA Bay 4 I: DATA (this drive will fail) Scenario 4: This one is unusual, it failed repeatedly, to the point where BIOS didn't recognize any boot options, after many resets it started showing the Boot drive. After reverting to BIOS version, it would boot every time, but when running UE5 or Helldivers 2 the problems continued.) I’m wondering if this second Aero G MB is also problematic. What might be causing these issues? My motherboard has functioned well for three years until October 2024.
S
SoloDroid
02-10-2022, 08:03 AM #6

I noticed some parallels with your system's situation. Recently I came across discussions about problems with WD Sandisk and Windows 11 24H2. It seemed logical. I began observing problems and BSODs around October, probably after the 24H2 update, though I hadn't realized it until now. All drives and WD as well as Samsung firmware were updated, but the issue persisted. I also reinstalled the latest 23H2 build, currently running 10.0.22631 Build 22631, with NVME updated yet still facing challenges. Other efforts: MB: Swapped drives with the same motherboard, Gigabyte Aero G X570. I downgraded to BIOS F4 2022-12-27 (the one included in the second MB). CPU: I replaced the 5950X with a new 5600X, but the same issues continue. Patterns on the drives seem to cause failures. My WD SN850X 2TB is used for project storage and has never stopped before. Recently, after installing it in the top M.2 slot, it appears inaccessible to Windows. In Disk Manager it loses the label name and a small 2MB unallocated space appears. When I attempt to check and repair, it fails with "The disk check could not be performed because Windows can't access the disk." The fact that every drive in the top slot shows some disconnect prompted me to try a different CPU. Further testing reveals: Scenario 1: Programs run smoothly for hours, no issues in UE5 or Helldivers 2 (my main programs). This is the only stable situation. Bay 1: C: Bay 2: Empty Bay 3: Empty Bay 4: Empty Scenario 2: Bay 1 empty Bay 2 C: Bay 3 H: DATA Bay 4 I: DATA (this drive will fail Scenario 3: Bay 1 DATA(this drive will fail) Bay 2 C: Bay 3 H: DATA Bay 4 I: DATA (this drive will fail) Scenario 4: This one is unusual, it failed repeatedly, to the point where BIOS didn't recognize any boot options, after many resets it started showing the Boot drive. After reverting to BIOS version, it would boot every time, but when running UE5 or Helldivers 2 the problems continued.) I’m wondering if this second Aero G MB is also problematic. What might be causing these issues? My motherboard has functioned well for three years until October 2024.

D
Dandalilly
Junior Member
10
02-12-2022, 12:35 PM
#7
I overlooked adding that I’ve started experiencing unexpected black screens on my primary screen, and my secondary display occasionally fails to show video.
D
Dandalilly
02-12-2022, 12:35 PM #7

I overlooked adding that I’ve started experiencing unexpected black screens on my primary screen, and my secondary display occasionally fails to show video.

K
KizuPvP
Member
137
02-13-2022, 10:55 AM
#8
Hi, I'm just dropping by to update you on my situation. I have managed to sort out the stability issues. I only now face the occasional GPU driver crash whenever working with high GPU workloads, but I have zero blue screens so far. I don't know what was the cause and what solved it, so I'll list the changes I have made since the last post. Changed the SATA cable to my Gigabyte SSD because the end was fraying. Updated my Ethernet drivers because Windows does not do it automatically. Changed to a new power supply (RM750x Shift). Ran DDU and installed drivers via NVIDIA App (versus NVCleanstall and Geforce Experience). I feel that my blue screens have stopped after updating my Ethernet drivers. I have paused my Windows updates, so I am still on Windows 11 Pro Version 10.0.26100. I am running the GeForce Game Ready Driver Version 572.83.
K
KizuPvP
02-13-2022, 10:55 AM #8

Hi, I'm just dropping by to update you on my situation. I have managed to sort out the stability issues. I only now face the occasional GPU driver crash whenever working with high GPU workloads, but I have zero blue screens so far. I don't know what was the cause and what solved it, so I'll list the changes I have made since the last post. Changed the SATA cable to my Gigabyte SSD because the end was fraying. Updated my Ethernet drivers because Windows does not do it automatically. Changed to a new power supply (RM750x Shift). Ran DDU and installed drivers via NVIDIA App (versus NVCleanstall and Geforce Experience). I feel that my blue screens have stopped after updating my Ethernet drivers. I have paused my Windows updates, so I am still on Windows 11 Pro Version 10.0.26100. I am running the GeForce Game Ready Driver Version 572.83.