Share via

Need help understanding certain error in blue screen logs please - critical event id 41, bug code 257

Anonymous
2024-09-25T20:30:08+00:00

This is the fourth "critical event id 41" blue screens I've had recently since I got this new pc that I built, so I was pretty concerned when they kept happening. For some context, I was playing valorant while on a discord call on my pc, and there was nothing out of the ordinary running (as far as I know or remember), when my whole computer froze, waited a few seconds, then blue screened. I'm often doing the same exact thing playing valorant same apps open and I'm completely fine so I don't expect it to be something application related but I would really appreciate learning what the bugcheckcode says or if it can help

I was unable to get my windows debugger open and working so I was wondering if someone could help me understand what this blue screen crash report was:

Critical event id 41 - Microsoft Windows Kernel Power


BugcheckCode 257
BugcheckParameter1 0x10
BugcheckParameter2 0x0
BugcheckParameter3 0xffff86019d8d1180
BugcheckParameter4 0x4
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Igor Leyko 110.6K Reputation points Independent Advisor
    2024-09-25T21:50:53+00:00

    Hi,

    My name is Igor, it's a pleasure for me to help others and I'll try to help you.

    Did you turn off your PC forcible by holding power button pressed? If not, Kernel-Power 41 (63) error mostly means the problem with power supplying. Can you replace power supply unit for checking? It may mean problems with power management in BIOS or motherboard too.

    And you may try to turn off all CPU power saving modes in BIOS (different C states) to check if the problem is in motherboard.

    See some details at https://docs.microsoft.com/en-us/windows/client...

    As for 257, typically, this bug check occurs when the processor is nonresponsive or is deadlocked. This may be result of power fault.

    0 comments No comments