Windows 10: Regular BSODs around 20-30 mins of running a game... Have run WinDbg !analyze -v but don't...

Hi - I am constantly getting a BSOD with what appear to be different causes within around 20-30 mins of playing a game called Manor Lords. I have checked all my drivers are up to date. I have run scannow and associated commands all seems fine. I have run the windows memory test and all seems fine. I have run Checkdisk and all seems fine...Below are the WinDbg - !analyze -v logs of the last 5 crashes if anyone would be kind enough to look at them and give me some pointers please?********************************************************************************

:)

 

"No export analyze found"-- WinDbg !analyze -v error

And here's a suggestion for users who don't like the sound of entering the command manually each time WinDbg starts:

In WinDbg, click File > Settings > Debugging settings > under Startup, paste the command AND CLICK 'OK'. Closing after entering the command won't save the settings.

After doing these steps, close the current session and open a dump file, you'll see that the command will automatically run, which will now allow you to run !analyze -v like you used to run before the bug started.

 

WinDbg "No export analyze found"

Hello,

While WinDbg has been working perfectly fine for years, this morning I came into work to find that running "!analyze -v" always just results in "No export analyze found".

This is true for minidumps that I have successfully analyzed in the past. I have both rebooted and reinstalled WinDbg from the Microsoft Store. Changing the symbol path also did not resolve the issue.

Any help would be much appreciated!

 

"No export analyze found"-- WinDbg !analyze -v error

Hi,

Recently I've been experiencing issues with WinDbg Preview. Whenever I run the analyze command, I get the error 'No export analyze found'. I decided to search online for fixes. In Microsoft Tech Community, one of them was to manually enter the source path, which I had already done. Another one was to roll back to Windows 10 v1903 which I will never do.

I checked if it's showing the same for older dumps which I had analyzed earlier, and as expected, it showed the same error. I also opened the minidumps on WinDbg as administrator, still the same.

Any help would be appreciated.

TIA,