Windows 10 BSOD, event 41 & bugcheckcode 292

Anonymous
2023-04-12T13:33:39+00:00

Hello,

Lately, when running an application called Prepar3D, my system has had BSODs. It's a flightsim application, which relies a lot on GPU, CPU and RAM. Lately, when flying over a certain part of the world with a lot of mountains, my pc bsods, so I suspect it has to do with all the terrain rendering that is necessary. My system used to be stable and never had BSODs whatsoever, but lately that has changed. Whether it's GPU or CPU related, I don't know, but essential to know. I've tried to reinstall Windows 10 and Prepar3D, also reapplied thermal paste to both the GPU and CPU, updated BIOS and enabled Hyperthreading, but none of that has really changed anything. My GPU's temperature decreased a bit (10-15 degrees) but can still go up as far as 80 degrees. I also monitored temps and VRAM usage prior to the crash, none of them being near the limits. Nothing is overclocked. As for the BSOD, it's always event 41 and bugcheckcode 292:

  • <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>8</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime="2023-04-12T03:49:16.0007809Z" /><EventRecordID>3680</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="8" /><Channel>System</Channel><Computer>DESKTOP-209P4JF</Computer><Security UserID="S-1-5-18" /></System>
  • <EventData> <Data Name="BugcheckCode">292</Data><Data Name="BugcheckParameter1">0x10</Data><Data Name="BugcheckParameter2">0x0</Data><Data Name="BugcheckParameter3">0x0</Data><Data Name="BugcheckParameter4">0x0</Data><Data Name="SleepInProgress">0</Data><Data Name="PowerButtonTimestamp">0</Data><Data Name="BootAppStatus">0</Data><Data Name="Checkpoint">0</Data><Data Name="ConnectedStandbyInProgress">false</Data><Data Name="SystemSleepTransitionsToOn">0</Data><Data Name="CsEntryScenarioInstanceId">0</Data><Data Name="BugcheckInfoFromEFI">true</Data><Data Name="CheckpointStatus">0</Data><Data Name="CsEntryScenarioInstanceIdV2">0</Data><Data Name="LongPowerButtonPressDetected">false</Data></EventData> </Event>

I think my minidump files are corrupted, which is why I consult the forum, because I have searched on Google already, but I'm not able to go ahead and debug myself.

Specs:
RTX 2080 SUPER, driver version 531.41
i9-9900k
32 GB RAM
4TB SSD
850W PSU
Windows 10
2x AOC 24" monitors

Windows for home | Windows 10 | 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

58 answers

Sort by: Oldest
  1. Anonymous
    2023-04-13T16:25:11+00:00

    Yeah I created a thread in their forum as well.

    Was this answer helpful?

    0 comments No comments
  2. David-M 126.2K Reputation points Independent Advisor
    2023-04-13T16:29:04+00:00

    Ok. It might be a good idea to provide the minidumps and see if the application didn't also create dump files. It should speed things up.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-04-13T17:33:21+00:00

    Just tried to deinstall an addon that I had installed into Prepar3D and then run a new session, and the session has run for about 25 mins so far without issues, so the issue might potentially have been resolved, but I'll report back if something happens again.

    Was this answer helpful?

    0 comments No comments
  4. David-M 126.2K Reputation points Independent Advisor
    2023-04-13T17:38:55+00:00

    Have you tried to reproduce the error by doing the same procedure that previously caused the BSOD?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-04-13T17:47:22+00:00

    No, but I'll do that to verify if that indeed was the issue. Meaning that I'll reinstall the addon and then do a new test session.

    Was this answer helpful?

    0 comments No comments