F5F Stay Refreshed Hardware Desktop PC experiences unexpected blue screen - kernel power issue detected.

PC experiences unexpected blue screen - kernel power issue detected.

PC experiences unexpected blue screen - kernel power issue detected.

O
Ozzywrath
Junior Member
6
12-08-2023, 03:30 PM
#1
Hello everyone, I recently installed a new PC and it frequently experiences random bluescreens. They appear during gaming, when launching programs, sometimes while idle, and even when booting or restarting after a crash. I've already tried several fixes: reinserting the RAM, updating drivers, and updating the BIOS. My power supply came with an 8-pin PCIe cable and a 2x8-pin version. I also experimented using both cables to ensure full power delivery. I attempted to monitor power usage and temperatures with HWInfo, but it didn't trigger a crash yet. System details: Windows 11 Pro 64-bit, Ryzen 5 7500F, Radeon 7800XT, Qick 319 from GIGABYTE. My RAM model is F5-6400J3239G16 GA2 -TZ5RK. I've uploaded the dump files and perfmon data for anyone familiar with WinDbg to review. Please check if I missed anything important or made a mistake. Thanks, Simon – this is my first post, so let me know if I need clarification.
O
Ozzywrath
12-08-2023, 03:30 PM #1

Hello everyone, I recently installed a new PC and it frequently experiences random bluescreens. They appear during gaming, when launching programs, sometimes while idle, and even when booting or restarting after a crash. I've already tried several fixes: reinserting the RAM, updating drivers, and updating the BIOS. My power supply came with an 8-pin PCIe cable and a 2x8-pin version. I also experimented using both cables to ensure full power delivery. I attempted to monitor power usage and temperatures with HWInfo, but it didn't trigger a crash yet. System details: Windows 11 Pro 64-bit, Ryzen 5 7500F, Radeon 7800XT, Qick 319 from GIGABYTE. My RAM model is F5-6400J3239G16 GA2 -TZ5RK. I've uploaded the dump files and perfmon data for anyone familiar with WinDbg to review. Please check if I missed anything important or made a mistake. Thanks, Simon – this is my first post, so let me know if I need clarification.

S
SrKaner
Member
222
12-15-2023, 03:01 AM
#2
You can use an external hard drive to store your data and attempt to reinstall Windows.
S
SrKaner
12-15-2023, 03:01 AM #2

You can use an external hard drive to store your data and attempt to reinstall Windows.

V
ViktorVirre
Member
52
12-19-2023, 07:04 PM
#3
Thank you for the update. After reinstalling Windows, the issue persisted. I managed to play Rainbow Six Siege briefly without issues, but closing R6 and launching GTA V triggered another crash.
V
ViktorVirre
12-19-2023, 07:04 PM #3

Thank you for the update. After reinstalling Windows, the issue persisted. I managed to play Rainbow Six Siege briefly without issues, but closing R6 and launching GTA V triggered another crash.

T
TheTivekas
Member
194
12-20-2023, 03:46 PM
#4
It seems to refer to remnants from the dump files. Usually people think of RAM, but it’s common for Windows to store low-priority data in the page file and retrieve it when needed, making storage appear like memory. The memory controller is built into the CPU, and if it fails, it can mimic memory behavior. When about half of the dumps point to storage or its drivers, that’s typical. Some entries involved storage drivers, but I’m open to other causes. If there are any overclocking or undervolting issues, consider removing them. You’re likely using a newer BIOS (unless you’ve updated since uploading), so an update might help—but the version here is quite recent, making that less likely. To verify RAM health, run tests normally with one stick at a time. If only one stick causes crashes, it’s probably a faulty stick. If crashes occur with both sticks and storage issues are excluded, the CPU might be the culprit. Memory testers often miss defective RAM, especially DDR4 and newer types.
T
TheTivekas
12-20-2023, 03:46 PM #4

It seems to refer to remnants from the dump files. Usually people think of RAM, but it’s common for Windows to store low-priority data in the page file and retrieve it when needed, making storage appear like memory. The memory controller is built into the CPU, and if it fails, it can mimic memory behavior. When about half of the dumps point to storage or its drivers, that’s typical. Some entries involved storage drivers, but I’m open to other causes. If there are any overclocking or undervolting issues, consider removing them. You’re likely using a newer BIOS (unless you’ve updated since uploading), so an update might help—but the version here is quite recent, making that less likely. To verify RAM health, run tests normally with one stick at a time. If only one stick causes crashes, it’s probably a faulty stick. If crashes occur with both sticks and storage issues are excluded, the CPU might be the culprit. Memory testers often miss defective RAM, especially DDR4 and newer types.

L
lars0100
Member
70
12-27-2023, 09:11 AM
#5
From the file names it seems these were older versions, which is unusual given how often they crashed. I've updated the BIOS since and it's now reset; I never overclocked anything and it still failed. One stick stopped right away, the other delayed but possibly by chance. I reviewed my dump files but found none, even though there were 10 crashes in the last week. There are no dumps left because I reinstalled Windows a few weeks ago. Thanks for your assistance—I'll reach out to the store where I bought the CPU and RAM (same place) to find out what to do next.
L
lars0100
12-27-2023, 09:11 AM #5

From the file names it seems these were older versions, which is unusual given how often they crashed. I've updated the BIOS since and it's now reset; I never overclocked anything and it still failed. One stick stopped right away, the other delayed but possibly by chance. I reviewed my dump files but found none, even though there were 10 crashes in the last week. There are no dumps left because I reinstalled Windows a few weeks ago. Thanks for your assistance—I'll reach out to the store where I bought the CPU and RAM (same place) to find out what to do next.

C
CrazyBessyCat
Posting Freak
912
12-29-2023, 05:35 AM
#6
There are various configurations and conditions that might stop the creation of dump files. Storage issues also raise suspicion here. Verify if any settings or factors could block their formation. Encrypted drives, such as those protected by BitLocker, prevent access. The dump operation runs separately from Windows, limiting its ability to reach encrypted media. Insufficient space on the drive for the page file is another concern. The initial dump may contain all data in RAM, requiring at least your RAM plus 3-4GB of free space. If you've adjusted the page file size manually, ensure it's large enough—ideally matching the example size, but let the system handle it better. I'll provide a guide on adjusting the page file location so you can identify its position and move it if needed. It's typically stored on C:, though placing it on an internal drive is usually safe. External drives may trigger crashes.
C
CrazyBessyCat
12-29-2023, 05:35 AM #6

There are various configurations and conditions that might stop the creation of dump files. Storage issues also raise suspicion here. Verify if any settings or factors could block their formation. Encrypted drives, such as those protected by BitLocker, prevent access. The dump operation runs separately from Windows, limiting its ability to reach encrypted media. Insufficient space on the drive for the page file is another concern. The initial dump may contain all data in RAM, requiring at least your RAM plus 3-4GB of free space. If you've adjusted the page file size manually, ensure it's large enough—ideally matching the example size, but let the system handle it better. I'll provide a guide on adjusting the page file location so you can identify its position and move it if needed. It's typically stored on C:, though placing it on an internal drive is usually safe. External drives may trigger crashes.

E
EPIC_GT
Member
219
01-01-2024, 12:05 AM
#7
Sorry to hear that your situation isn’t working out. It sounds like you’re dealing with limited storage and a possible hardware issue. You’ve already tried mirroring the drive, which is a good step. If you want to try using this SSD as your boot drive, just keep an eye on performance and stability while testing.
E
EPIC_GT
01-01-2024, 12:05 AM #7

Sorry to hear that your situation isn’t working out. It sounds like you’re dealing with limited storage and a possible hardware issue. You’ve already tried mirroring the drive, which is a good step. If you want to try using this SSD as your boot drive, just keep an eye on performance and stability while testing.

H
HellNether
Senior Member
731
01-01-2024, 06:56 AM
#8
Update: I did switch to using the different drive (SATA SSD) to which I mirrored my files before reinstalling windows a while after posting this and it is running great. I had 1 random restart while downloading an 80GB game over night (thanks to my very fast german internet), realised the PC had restarted in the morning and that's it, no more bluescreens. With that I am pretty sure it is indeed a defect M.2 SSD and I will contact the vendor and ask for a replacement.
H
HellNether
01-01-2024, 06:56 AM #8

Update: I did switch to using the different drive (SATA SSD) to which I mirrored my files before reinstalling windows a while after posting this and it is running great. I had 1 random restart while downloading an 80GB game over night (thanks to my very fast german internet), realised the PC had restarted in the morning and that's it, no more bluescreens. With that I am pretty sure it is indeed a defect M.2 SSD and I will contact the vendor and ask for a replacement.