Thanks, I've used the DDU tool quite a bit lately due to my own suspicions that the GPU could be the culprit, obviously didn't resolve it but I'm willing to do it again just to completely rule it out. Wagnardsoft doesn't seem to recommend GeForce Experience to update drivers apparently since it can cause issues according to them.
Windows 10 BSOD, event 41 & bugcheckcode 292
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.
58 answers
Sort by: Most helpful
-
Anonymous
2023-04-12T18:58:20+00:00 -
David-M 126.2K Reputation points Independent Advisor2023-04-12T18:17:59+00:00 Your computer does not have recent minidump files because the creation of the dump files is failing.
In the last crashes, I did not identify any specific error that can be pointed out as a probable cause for the issue. However, a few days ago, there are some errors involving the Nvidia driver.
As the crash occurs when you are using Prepar3D and at a specific time, perhaps the Nvidia driver could be related to the crash.
Do a clean install of the Nvidia driver and see if the system will work stable.
Download the latest driver for your graphics card from the Nvidia website. Then use the free DDU tool to remove the current driver. Then install the latest driver using the installer you downloaded.
DDU: https://www.guru3d.com/files-details/display-dr...
Nvidia driver download: https://www.nvidia.com/Download/driverResults.a...
________________________________________________________
Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
-
Anonymous
2023-04-12T17:54:27+00:00 These are the two files I saved to the Desktop.
https://www.dropbox.com/s/a6589d1whctnefe/logs.evtx?dl=0 https://www.dropbox.com/s/uhqr098o4hi52aw/logs_1033.MTA?dl=0
-
David-M 126.2K Reputation points Independent Advisor2023-04-12T17:41:00+00:00 Thanks for the clarifications.
It's hard to determine the cause of BSOD without being able to analyze dump files.
Let's see if there is any useful information in the logs.
Export and send the log for analysis:
- Press "Windows + X" and select "Event Viewer";
- Expand "Windows Logs" and select "System";
- In the "Actions" panel on the right, select "Filter Current Log";
- In "Event level", check the boxes "Critical", "Warning", and "Error" and click on "Ok";
- Again, in the "Actions" panel, select "Save Filtered Log File As" and save in an easily accessible place.
Then upload the file to the cloud, choose to share it, and get the link.
Post the link to the file here so I can have a look.
-
Anonymous
2023-04-12T17:28:34+00:00 Yes that was the thing I forgot to tell - it's the only file and it's from March 30th. Nothing to do with the BSODs I've had. Yes I've had multiple since - March 30th is when I reinstalled Windows 10.
There is a MEMORY.DMP file in C:\Windows, but that one is also from March 30th.