Question Inconsistently recurring - Critical Errors (Kernel Power 41-(63))

Jun 7, 2021
Hi all,

I built a new PC about 6 months ago, and it was running fine for long periods but then started with random BSOD (every time with a different text, but always the same event ID in Event Viewer - Kernel-Power 41 (63).

I recently did a full format and clean Win 10 install, which fixed the problem for a week, but now its back.

I cannot correlate it to any specific activity as it seems to happen at random (sometimes 3 times in an hour, sometimes not for a week).

I have run MemTests, CPU checks etc. but everything seems to be fine.

I am going crazy and am really desperate for help. I have uploaded my latest files in case it is helpful:
MEMORY.DMP (as txt)

Let me know if there are any questions or any more information I need to add (sorry my first time posting here)

MANY thanks in advance.


Update your post to include full system hardware specs.

Include PSU: make, model, wattage, age, condition.

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all connectors, cards, RAM, and jumpers are fully and firmly in place.


Win 10 Master
if it survives a clean install its unlikely to be windows

but always the same event ID in Event Viewer - Kernel-Power 41 (63).
this is a reaction to the restart, not the cause of one. Windows runs a report at every startup and if it finds the previous shutdown was unexpected, it creates that event to say, hey that restart, it wasn't planned.

I will ask someone to look at dumps, see if they show anything


Win 10 Master
that is an odd error, windows was stuck in a loop


actions are in 1st in last out order, so bottom items were 1st

ffff950d94ef5d20 fffff8060d08775f : fffff8060cecf24c fffff80600000000 0000007ffffffff8 fffff8060cecf24c : nt!RtlpxVirtualUnwind+0x56
ffff950d94ef5da0 fffff8060d08747e : ffff950d94ef6360 0000000000000000 ffff950d94ef6570 fffff8060d0863c7 : nt!RtlVirtualUnwind+0x5f
ffff950d94ef5e20 fffff8060d086136 : ffff950d94ef6d38 ffff950d94ef6a70 ffff950d94ef6d38 0000000000fe0000 : nt!RtlDispatchException+0x1ce
ffff950d94ef6540 fffff8060d208dac : 0000000000001000 ffff950d94ef6de0 ffff800000000000 0000000000000000 : nt!KiDispatchException+0x186
ffff950d94ef6c00 fffff8060d204f43 : ffffd6055a4b5010 fffff8060d51fae2 ffffd6055a4b5170 ffffe60d819c8180 : nt!KiExceptionDispatch+0x12c
ffff950d94ef6de0 fffff8060d0863c7 : ffff950d94ef7958 ffff950d94ef7958 ffff950d94ef6fa0 0000000000fe0000 : nt!KiPageFault+0x443
it repeated those steps 5 times before it requested another page fault location and crashed

page faults are normal action of windows 10, badly named. Any time the CPU finds it doesn't have immediate access to the info it needs, on its caches on chip, it will issue a page fault and request info from ram. Since you have run memtest, it could be a driver error

try updating these
May 24 2019rt640x64.sysRealtek NICDRV 8169 PCIe GBE Family Controller driver
Download Win10 Auto Installation Program (SId:1152921505693508652) from
try running and let it check drivers
Newer Nvidia drivers too.