F5F Stay Refreshed Hardware Desktop Troubles with your homemade gaming setup Have some odd problems popping up lately?

Troubles with your homemade gaming setup Have some odd problems popping up lately?

Troubles with your homemade gaming setup Have some odd problems popping up lately?

A
Angoldir
Member
Find
83
10-18-2016, 03:24 AM
#1
I assembled a custom gaming setup and fitted a WD blue Sa510 SSD. It would vanish unexpectedly, so I searched for a necessary firmware fix via WD’s online portal. After downloading, the system rebooted smoothly, but shortly afterward it entered a persistent blue screen with multiple errors—bad pool call, attempts to write to read-only space, and IRQL not acceptable. Windows attempted an automatic repair from an older version, yet the PC would abruptly power down. Once restored, I turned on the fans, which initially spun up, then stopped and restarted again.

I took the SSD out, tried another machine where it functioned, but WD’s dashboard still reported the firmware was current. Logging in with Windows and opening Chrome twice triggered dozens of instances—possibly a coincidence since it only happened after the first boot. I reset CMOS, removed the graphics card, connected the monitor via MOBO, and even tried deleting all four RAM sticks before installing two, then one. It beeped when I pressed the power button, then spun up normally.

After reinstalling the RAM, the system booted into Windows with all sticks detected. The event monitor showed an error: event 41 kernel power issue at crash time. My uncertainty lingered—was it a corrupted firmware, faulty RAM, or power instability? At that moment, I had WSL installed, suggesting the SSD firmware might have been incompatible. I installed WSL Ubuntu briefly to test, but it didn’t resolve the problem.

I removed the original power supply, still couldn’t get a boot. I swapped all four RAM modules, tried two then one, and each time it beeped before fans accelerated as usual. Eventually, I reinstalled everything and managed to boot Windows correctly.

During troubleshooting, I checked the Event Monitor and saw the same kernel power error at the crash. I also reviewed CPU-Z screenshots. My PC specs were: HP EliteDesk 800G1 chassis with a motherboard (details in CPU-Z). Intel I5-4590 processor, stock HP cooler, WD Blue HDD (S/N WCC2E4ADB82HJ), four 2GB Samsung 2Rx8 sticks, and an EVGA SC GAMING ACX 2.0 1050TI graphics card (powered via a 300W ATX PSU, model FH-XD301MYR).

I had WSL installed, which might have caused the SSD firmware to reject it, though I wasn’t certain. The monitor was connected via MOBO, and after several attempts, everything finally worked.
Reply
Reply
A
Angoldir
10-18-2016, 03:24 AM #1

I assembled a custom gaming setup and fitted a WD blue Sa510 SSD. It would vanish unexpectedly, so I searched for a necessary firmware fix via WD’s online portal. After downloading, the system rebooted smoothly, but shortly afterward it entered a persistent blue screen with multiple errors—bad pool call, attempts to write to read-only space, and IRQL not acceptable. Windows attempted an automatic repair from an older version, yet the PC would abruptly power down. Once restored, I turned on the fans, which initially spun up, then stopped and restarted again.

I took the SSD out, tried another machine where it functioned, but WD’s dashboard still reported the firmware was current. Logging in with Windows and opening Chrome twice triggered dozens of instances—possibly a coincidence since it only happened after the first boot. I reset CMOS, removed the graphics card, connected the monitor via MOBO, and even tried deleting all four RAM sticks before installing two, then one. It beeped when I pressed the power button, then spun up normally.

After reinstalling the RAM, the system booted into Windows with all sticks detected. The event monitor showed an error: event 41 kernel power issue at crash time. My uncertainty lingered—was it a corrupted firmware, faulty RAM, or power instability? At that moment, I had WSL installed, suggesting the SSD firmware might have been incompatible. I installed WSL Ubuntu briefly to test, but it didn’t resolve the problem.

I removed the original power supply, still couldn’t get a boot. I swapped all four RAM modules, tried two then one, and each time it beeped before fans accelerated as usual. Eventually, I reinstalled everything and managed to boot Windows correctly.

During troubleshooting, I checked the Event Monitor and saw the same kernel power error at the crash. I also reviewed CPU-Z screenshots. My PC specs were: HP EliteDesk 800G1 chassis with a motherboard (details in CPU-Z). Intel I5-4590 processor, stock HP cooler, WD Blue HDD (S/N WCC2E4ADB82HJ), four 2GB Samsung 2Rx8 sticks, and an EVGA SC GAMING ACX 2.0 1050TI graphics card (powered via a 300W ATX PSU, model FH-XD301MYR).

I had WSL installed, which might have caused the SSD firmware to reject it, though I wasn’t certain. The monitor was connected via MOBO, and after several attempts, everything finally worked.

Reply
Reply
L
lola102004
Junior Member
Find
23
10-18-2016, 10:54 PM
#2
It seems the firmware update may have damaged some data, leading to Windows malfunctions and UEFI problems. Physical damage during disassembly—like a loose power cable or RAM sticks—could have triggered these issues. Windows recovery resolved the data corruption, CMOS reset fixed the UEFI quirks, and re-seating the hardware corrected the bad connection. This is just speculation; I’ve never encountered the idea of an “SSD not liking WSL.” Logic remains solid. WSL operates as a Linux virtual machine in Hyper-V, so unless there’s a virtualization issue on your system, linking it to these problems isn’t clear.
Reply
Reply
L
lola102004
10-18-2016, 10:54 PM #2

It seems the firmware update may have damaged some data, leading to Windows malfunctions and UEFI problems. Physical damage during disassembly—like a loose power cable or RAM sticks—could have triggered these issues. Windows recovery resolved the data corruption, CMOS reset fixed the UEFI quirks, and re-seating the hardware corrected the bad connection. This is just speculation; I’ve never encountered the idea of an “SSD not liking WSL.” Logic remains solid. WSL operates as a Linux virtual machine in Hyper-V, so unless there’s a virtualization issue on your system, linking it to these problems isn’t clear.

Reply
Reply