Critical Kernel Power: Issue 41(63) Bug Code 209?
Critical Kernel Power: Issue 41(63) Bug Code 209?
Here is the rewritten version of your text:
I'm attempting to assist a friend with troubleshooting his PC, but we're facing difficulties. When trying to launch CS2 or Payday 3, the games either:
A) Crash immediately during shader compilation or startup.
B) Function for a short time before failing.
C) Trigger a BSOD displaying a specific error in the title, with a full crash report available here:
Loggnamn: System Källa: Microsoft-Windows-Kernel-Power
Datum: 2024-04-18 10:54:20 Händelse-ID: 41 Aktivitetskategori
🙁
63) Nivå: Kritisk Nyckelord: (70368744177664),(2) Användare: SYSTEM Dator: Daniel
Beskrivning: Datorn har startats om utan att ha stängts av ordentligt först. Detta kan inträffa om systemet slutar svara, om det kraschar eller om strömförsörjningen oväntat bryts. Händelsens XML-data: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID> <Version>9</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2024-04-18T08:54:20.8834852Z" />
<EventRecordID>3744</EventRecordID>
<Correlation /> <Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Daniel</Computer>
<Security UserID="S-1-5-18" />
</System>
📌 Note: Några mönster var inte mer än normalt, och det är tillgänglig för att säga systemet om att sluta, om det kraschar eller om de funktionarade. Händelsens XML-data: <BugcheckCode>209</BugcheckCode>
I was taken aback that your PC is functioning properly.
According to the Intel Spec sheet, the highest memory speed your CPU can handle is 5600mhz. Try disabling XMP to determine if that resolves your issue.
If it does, you've likely identified the problem.
Hey, I noticed he didn't mention using 6600 mhz, the XMP is off and they're set to around 4000 something.
Hey thanks for your response. We managed to fix it setting the cpu to x53 instead of 57 (no idea what it even means) but that fixed it for him lol.