F5F Stay Refreshed Hardware Desktop Question Random "Kernel Power 41 (63)" issues remain even following a new Windows setup?

Question Random "Kernel Power 41 (63)" issues remain even following a new Windows setup?

Question Random "Kernel Power 41 (63)" issues remain even following a new Windows setup?

D
DRGNdragsYT
Senior Member
723
08-30-2024, 06:33 PM
#1
I frequently reinstalled Windows 10/11, and sometimes I encountered a kernel power error right after five minutes in a clean system. Other times it didn’t happen at all, or it occurred during high load or gaming. I’m not sure what’s going on; it was fine before the reinstall and now it happens unexpectedly without any reason. This randomness is really confusing.

PC specifications:
CPU: i5-11400F
Motherboard: MSI MAG B560 TORPEDO
GPU: Asrock Radeon RX 6950 XT Phantom Gaming 16GB OC
RAM: DDR4 GOODRAM 32GB (2x16GB) 3600MHz CL18 IRDM PRO
SSD: Silicon Power 1TB M.2 PCIe NVMe XD80
Soundcard: Asus Xonar DGX
Power Supply: SilentiumPC Supremo FM2 Gold 650W
BIOS was recently updated.

CPU and GPU were tested using OCCT and Furmark/3DMark Time Spy benchmarks, RAM with memtest, and the M.2 drive checked by Crystaldisk. All tests passed without issues. I tried various Windows ISO images, different versions, and different USB drives. No BSOD logs were found; instead, I noticed brief lag, freezing, followed by a kernel power BSOD after restarting. The PC would enter BIOS because it couldn’t detect the hard drive. After a full shutdown and reboot, the disk was detected normally and the system booted as expected. This model uses a MSI MOMO shield with a 1TB SSD, maintaining temperatures around 30-35°C in different slots. The only exception was the RAM, which showed an XMP profile but remained unchanged without it. I also tested without the Asus soundcard.

Now the system is generally stable (no BSOD under light load), but it crashes after playing games like Palia for extended periods. The unusual part is that it worked fine before the reinstall.

I performed a power supply test using OCCT, but when the CPU reached 95°C I stopped it for two minutes. Then, after stress testing, it crashed again—right after entering Windows and another crash occurred immediately. It’s puzzling, please help.
D
DRGNdragsYT
08-30-2024, 06:33 PM #1

I frequently reinstalled Windows 10/11, and sometimes I encountered a kernel power error right after five minutes in a clean system. Other times it didn’t happen at all, or it occurred during high load or gaming. I’m not sure what’s going on; it was fine before the reinstall and now it happens unexpectedly without any reason. This randomness is really confusing.

PC specifications:
CPU: i5-11400F
Motherboard: MSI MAG B560 TORPEDO
GPU: Asrock Radeon RX 6950 XT Phantom Gaming 16GB OC
RAM: DDR4 GOODRAM 32GB (2x16GB) 3600MHz CL18 IRDM PRO
SSD: Silicon Power 1TB M.2 PCIe NVMe XD80
Soundcard: Asus Xonar DGX
Power Supply: SilentiumPC Supremo FM2 Gold 650W
BIOS was recently updated.

CPU and GPU were tested using OCCT and Furmark/3DMark Time Spy benchmarks, RAM with memtest, and the M.2 drive checked by Crystaldisk. All tests passed without issues. I tried various Windows ISO images, different versions, and different USB drives. No BSOD logs were found; instead, I noticed brief lag, freezing, followed by a kernel power BSOD after restarting. The PC would enter BIOS because it couldn’t detect the hard drive. After a full shutdown and reboot, the disk was detected normally and the system booted as expected. This model uses a MSI MOMO shield with a 1TB SSD, maintaining temperatures around 30-35°C in different slots. The only exception was the RAM, which showed an XMP profile but remained unchanged without it. I also tested without the Asus soundcard.

Now the system is generally stable (no BSOD under light load), but it crashes after playing games like Palia for extended periods. The unusual part is that it worked fine before the reinstall.

I performed a power supply test using OCCT, but when the CPU reached 95°C I stopped it for two minutes. Then, after stress testing, it crashed again—right after entering Windows and another crash occurred immediately. It’s puzzling, please help.

K
ko94
Member
222
08-30-2024, 06:33 PM
#2
I changed my Windows 10/11 multiple times. Where did you get the installer for your operating systems?
SilentiumPC Supremo FM2 Gold 650W
The PSU in your build is the most recent model.
The latest BIOS has been flashed.
Please state the BIOS version. Also, confirm whether you reset the CMOS after ensuring the BIOS update was applied successfully.
K
ko94
08-30-2024, 06:33 PM #2

I changed my Windows 10/11 multiple times. Where did you get the installer for your operating systems?
SilentiumPC Supremo FM2 Gold 650W
The PSU in your build is the most recent model.
The latest BIOS has been flashed.
Please state the BIOS version. Also, confirm whether you reset the CMOS after ensuring the BIOS update was applied successfully.

E
EdenMarie
Member
190
08-30-2024, 06:33 PM
#3
Is the specified RAM model listed in the motherboard's QVL? If not, it could affect stability. You might need to purchase new RAM, ideally available on the QVL. Avoid using XMP profiles during Windows installation on an unstable system, particularly at 3600MHz. If overclocked RAM leads to file corruption during installation, recovery won't be possible.

Turn off XMP and revert to the JEDEC default speed of either 2,133 or 2,400MT/s. Start the computer via USB and run MemTest86+ multiple times to verify memory integrity at JEDEC speed.

Clear the drive and reinstall Windows without XMP. Test for stability. Only then should you consider enabling XMP. If it remains unstable at 3600MHz, try a lower speed like 3000MHz and gradually increase until the system becomes unresponsive. Adjust the XMP speed or adjust the CL (CAS) setting by increasing one or two clock cycles, making the CL value larger. Re-test for stability.
E
EdenMarie
08-30-2024, 06:33 PM #3

Is the specified RAM model listed in the motherboard's QVL? If not, it could affect stability. You might need to purchase new RAM, ideally available on the QVL. Avoid using XMP profiles during Windows installation on an unstable system, particularly at 3600MHz. If overclocked RAM leads to file corruption during installation, recovery won't be possible.

Turn off XMP and revert to the JEDEC default speed of either 2,133 or 2,400MT/s. Start the computer via USB and run MemTest86+ multiple times to verify memory integrity at JEDEC speed.

Clear the drive and reinstall Windows without XMP. Test for stability. Only then should you consider enabling XMP. If it remains unstable at 3600MHz, try a lower speed like 3000MHz and gradually increase until the system becomes unresponsive. Adjust the XMP speed or adjust the CL (CAS) setting by increasing one or two clock cycles, making the CL value larger. Re-test for stability.

S
StaTICGamERXD
Member
51
08-30-2024, 06:33 PM
#4
Official Windows ISO from Microsoft site is available. The BIOS version is E7D15IMS.A90 (7D15v29 MSI site). CMOS wasn't cleared. No GOODRAM sticks appear in the MSI-supported memory list. It worked fine after changing it, but issues began after a Windows reinstall. I plan to test memory without XMP and will reinstall Windows on the old SSD drive, removing the M.2 slot from the PC.
S
StaTICGamERXD
08-30-2024, 06:33 PM #4

Official Windows ISO from Microsoft site is available. The BIOS version is E7D15IMS.A90 (7D15v29 MSI site). CMOS wasn't cleared. No GOODRAM sticks appear in the MSI-supported memory list. It worked fine after changing it, but issues began after a Windows reinstall. I plan to test memory without XMP and will reinstall Windows on the old SSD drive, removing the M.2 slot from the PC.

B
beichner
Senior Member
447
08-30-2024, 06:33 PM
#5
RAM tested on XMP and without on 2133, 0 errors.
When i changed hard drive to the old SSD it was all good
untill full powerdown and couple restarts,
mobo stopped at RAM yellow led.
That may suggest this can be a memory problem so i used OCCT to stress the memory 80% load.
3200/3600 crashing the test quite fast, 2133 gets 30 minutes cycle without problem.
Anyway system failed soon after with BSOD displaying
UNEXPECTED STORE EXCEPTION.
Now im just using default 2133 speed and waiting for crashes...
Any idea after those clues? Is it really memory or just coincidence to crash like that, or what about that new BSOD content.
B
beichner
08-30-2024, 06:33 PM #5

RAM tested on XMP and without on 2133, 0 errors.
When i changed hard drive to the old SSD it was all good
untill full powerdown and couple restarts,
mobo stopped at RAM yellow led.
That may suggest this can be a memory problem so i used OCCT to stress the memory 80% load.
3200/3600 crashing the test quite fast, 2133 gets 30 minutes cycle without problem.
Anyway system failed soon after with BSOD displaying
UNEXPECTED STORE EXCEPTION.
Now im just using default 2133 speed and waiting for crashes...
Any idea after those clues? Is it really memory or just coincidence to crash like that, or what about that new BSOD content.

R
roydemooij9
Member
54
08-30-2024, 06:33 PM
#6
After hours of gaming, the system crashed again. Default RAM settings were used. It's hard to figure out what's wrong since it behaves similarly even when checking RAM details.
R
roydemooij9
08-30-2024, 06:33 PM #6

After hours of gaming, the system crashed again. Default RAM settings were used. It's hard to figure out what's wrong since it behaves similarly even when checking RAM details.