Event ID 41 PC Crash

[Atriox]

My PC keeps randomly crashing using an error code of Event ID 41 without a BSOD.

The issue started happening after I had a windows update.

What happens is the PC will freeze, I can hear sounds for a few seconds and then the PC completely crashes.

I don't know how to fix it, I have tried to use SFC and DISM to repair it, and I have updated my graphics card driver but the issue is still going on.

It's worth noting that I have a 13900KF, so this might be causing the issues? Should I get an RMA?

I don't even know how to troubleshoot what could be causing these issues because windows does not give much information.

[smokerob79]

this is one of the problem CPU's from intel.....so good odds its a bad chip.....

[Atriox]

smokerob79님이 먼저 게시:

this is one of the problem CPU's from intel.....so good odds its a bad chip.....

Is it a known issue with those processors? I tried googling it but saw nothing

[YoSoyJosh]

Atriox님이 먼저 게시:

smokerob79님이 먼저 게시:

this is one of the problem CPU's from intel.....so good odds its a bad chip.....

Is it a known issue with those processors? I tried googling it but saw nothing

It's hard to believe after googling Intel instability you found nothing about 13/14 gen when that's been all the talk for months, but regardless, download the Intel Processor Diag tool

[Atriox]

NØNE님이 먼저 게시:

Atriox님이 먼저 게시:

Is it a known issue with those processors? I tried googling it but saw nothing

It's hard to believe after googling Intel instability you found nothing about 13/14 gen when that's been all the talk for months, but regardless, download the Intel Processor Diag tool

That's not what I said, I said that I have seen nothing regarding event ID 41

[DonMcK]

Have you looked in the Event Logs to see if there were any errors or warnings just before the crash?

[smokerob79]

code 41 is a general code that shows nothing but power loss......power stability is the biggest problem with these chips......

[Atriox]

smokerob79님이 먼저 게시:

code 41 is a general code that shows nothing but power loss......power stability is the biggest problem with these chips......

I disabled asus core enhancement and it seems to be ok for now, should I still RMA or wait until it acts up again?

[Illusion of Progress]

Event ID 41 isn't a crash itself. It's a symptom. It's simply the system logging for itself that "hey, the previous Windows session shutdown but it wasn't an expected or proper shutdown".

Event ID 41 is totally useless to you if you're already aware of the disruption. It's logged precisely to let you know it happened in case you're not aware of the disruption (such as if you weren't at the PC when it occurred).

When you see Event ID 41, the first thing you need to do is look at what else is logged. Windows usually logs other things.

Here's the rough troubleshooting process with this one.

If there's literally, and actually, nothing besides Event ID 41, you're dealing with a sudden power loss. If it's this one, the PC will almost always turn off and stay off (as opposed to restart).

If it's restarting, you likely have a different issue and will likely find some form of logs. You mentioned no BSODs, but there's a couple other places to check.

One place to look is in event viewer where you're presumably already looking if you're finding Event ID 41. Everyone simply focuses on Event ID 41 since it's logged under "critical" and the actual pertinent thing is probably logged under "error". You need to look at the time Event ID 41 was logged, which occurs after the next Windows startup (not when the crash actually happened), and then look backwards in time to find the time of the shutdown. You'd be looking for any errors in that time frame. Even ID 18/19 are such examples (usually 19 won't bring the PC down though).

The other place to look is in the "Windows hardware error architecture" directories, which is the following two directories...

Windows/LiveKernelReports/WHEA
Window/LiveKernelReports/WATCHDOG

If there are logs here, check the dates/times of them. You can use an application called WinDbg to open and analyze these logs, which may provide clues.

Atriox님이 먼저 게시:

It's worth noting that I have a 13900KF, so this might be causing the issues?

Definite maybe.

The types of issues caused by that one are usually a bit more particular than this one though (certain types of crashes, or more random crashes) as opposed to what sounds to me like a machine check exception panic and resulting restart.

That's not saying it isn't (or is) the cause of your issue. You simply have more checking to do as a result of having a CPU with known issues though, so do your homework on that side and ensure the BIOS is updated, the CPU is running to whatever limits it's needs to, etc.

As a rule, you should be setting the system to stock (XMP off and maybe limit the CPU p-core ratio to something like 52), which would help rule out the CPU or other overclocking things.

[Set-115689]

Update your bios and the intel management engine driver (don't update just one need both) and chose intel recommend settings. Even doing that some settings are still not what they should be just an fyi. Might also be new chip set drivers but that's just something extra to do vs the potential issue.

Each mainboard is slightly different and calls stuff different stuff.

Asus core enhancement should be set to intel settings. The core enhancement setting uses the old bad settings. Check your PL1 and PL2, cpu current limit, intel c states enabled, etc.... By choosing the other setting you are going more out of intel specs and disabling some safety measures. Basically running the processor beoyond it's limits in certain situations.

https://www.pcgamer.com/hardware/processors/intel-clarifies-what-bios-settings-13th14th-gen-cpus-should-be-used-for-power-and-current/

Kernel power 41 is just a generic crash code. Could be a variety of things.

[Atriox]

Set-115689님이 먼저 게시:

Update your bios and the intel management engine driver (don't update just one need both) and chose intel recommend settings. Even doing that some settings are still not what they should be just an fyi. Might also be new chip set drivers but that's just something extra to do vs the potential issue.

Each mainboard is slightly different and calls stuff different stuff.

Asus core enhancement should be set to intel settings. The core enhancement setting uses the old bad settings. Check your PL1 and PL2, cpu current limit, intel c states enabled, etc.... By choosing the other setting you are going more out of intel specs and disabling some safety measures. Basically running the processor beoyond it's limits in certain situations.

https://www.pcgamer.com/hardware/processors/intel-clarifies-what-bios-settings-13th14th-gen-cpus-should-be-used-for-power-and-current/

Kernel power 41 is just a generic crash code. Could be a variety of things.

I went into the BIOS last night and manually disabled ASUS Multi-core enhancement, and I didn’t have any more crashes after that, so hopefully that’s fixed it for now.

I am still going to look further into it as per the advice on the previous comment to yours just to check that it isn’t something else which could be causing the issue.

I think either way I need to RMA the CPU because I have been getting a lot of random crashes in lots of games for a while now so I think the CPU definitely needs to be replaced.

It’s probably just confirmation bias but I think the CPU is the biggest culprit because I have already been having issues with the PC thanks to it.

Do you know how I might access where the Windows/LiveKernelReports/WHEA
Window/LiveKernelReports/WATCHDOG
locations are? I tried looking online but I couldn’t find where to look just to determine what could be causing the crashes.

[DonMcK]

Atriox님이 먼저 게시:

Set-115689님이 먼저 게시:

Update your bios and the intel management engine driver (don't update just one need both) and chose intel recommend settings. Even doing that some settings are still not what they should be just an fyi. Might also be new chip set drivers but that's just something extra to do vs the potential issue.

Each mainboard is slightly different and calls stuff different stuff.

Asus core enhancement should be set to intel settings. The core enhancement setting uses the old bad settings. Check your PL1 and PL2, cpu current limit, intel c states enabled, etc.... By choosing the other setting you are going more out of intel specs and disabling some safety measures. Basically running the processor beoyond it's limits in certain situations.

https://www.pcgamer.com/hardware/processors/intel-clarifies-what-bios-settings-13th14th-gen-cpus-should-be-used-for-power-and-current/

Kernel power 41 is just a generic crash code. Could be a variety of things.

I went into the BIOS last night and manually disabled ASUS Multi-core enhancement, and I didn’t have any more crashes after that, so hopefully that’s fixed it for now.

I am still going to look further into it as per the advice on the previous comment to yours just to check that it isn’t something else which could be causing the issue.

I think either way I need to RMA the CPU because I have been getting a lot of random crashes in lots of games for a while now so I think the CPU definitely needs to be replaced.

It’s probably just confirmation bias but I think the CPU is the biggest culprit because I have already been having issues with the PC thanks to it.

Do you know how I might access where the Windows/LiveKernelReports/WHEA
Window/LiveKernelReports/WATCHDOG
locations are? I tried looking online but I couldn’t find where to look just to determine what could be causing the crashes.

Could try the 'Home Edition' of whocrashed

https://www.resplendence.com/whocrashed

[Atriox]

DonMcK님이 먼저 게시:

Atriox님이 먼저 게시:

I went into the BIOS last night and manually disabled ASUS Multi-core enhancement, and I didn’t have any more crashes after that, so hopefully that’s fixed it for now.

I am still going to look further into it as per the advice on the previous comment to yours just to check that it isn’t something else which could be causing the issue.

I think either way I need to RMA the CPU because I have been getting a lot of random crashes in lots of games for a while now so I think the CPU definitely needs to be replaced.

It’s probably just confirmation bias but I think the CPU is the biggest culprit because I have already been having issues with the PC thanks to it.

Do you know how I might access where the Windows/LiveKernelReports/WHEA
Window/LiveKernelReports/WATCHDOG
locations are? I tried looking online but I couldn’t find where to look just to determine what could be causing the crashes.

Could try the 'Home Edition' of whocrashed

https://www.resplendence.com/whocrashed

Cool thanks, that sounds like a good tool to use

[Illusion of Progress]

Atriox님이 먼저 게시:

Do you know how I might access where the Windows/LiveKernelReports/WHEA
Window/LiveKernelReports/WATCHDOG
locations are? I tried looking online but I couldn’t find where to look just to determine what could be causing the crashes.

Those are the directories. They will be on your system drive (usually the C drive). You access them them simply by navigating to them.

[Atriox]

Illusion of Progress님이 먼저 게시:

Atriox님이 먼저 게시:

Do you know how I might access where the Windows/LiveKernelReports/WHEA
Window/LiveKernelReports/WATCHDOG
locations are? I tried looking online but I couldn’t find where to look just to determine what could be causing the crashes.

Those are the directories. They will be on your system drive (usually the C drive). You access them them simply by navigating to them.

Cool thank you

[Atriox]

I just looked under Application under Event Viewer and I have been getting this error:

A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.