Constant BSOD crashes

DarthLordZuko · 27 Oct 2020

Insider -
Had some problems with earlier builds :S

Ztruker · 27 Oct 2020

His first V2 zip dumps were okau and I could look at them with no symbol problems. Just the dump fmrom the 26th has the problem. I wonder if there has been an update?

Run this batch file: getWindowsUpdateList.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Part Three

Capture output of batch file to Clipboard

Follow the directions in Part Two-OneB of the Index (first post at the top) to capture the output of the batch file displayed in notepad for posting in your BSOD thread at tenforums.com.

philc43 · 27 Oct 2020

Yes, you can see from the updates file in the logs that he had an update between the last two crash dumps. As this is an insider build the symbols won't be made publicly available straightaway.

Code:

HotFixID  Description     InstalledOn           
--------  -----------     -----------           
KB4561600 Security Update 8/8/2020 12:00:00 AM  
KB4570334 Security Update 8/8/2020 12:00:00 AM  
KB4577266 Security Update 9/18/2020 12:00:00 AM 
KB4576754 Update          9/20/2020 12:00:00 AM 
KB4562830 Update          9/28/2020 12:00:00 AM 
KB4578968 Update          10/14/2020 12:00:00 AM
KB4580325 Security Update 10/14/2020 12:00:00 AM
KB4580364 Update          10/23/2020 12:00:00 AM

Ztruker · 27 Oct 2020

So that's the cause and what makes the dumps mostly unusable.Thanks Phil.
@DarthLordZuko, no need to run the batch file.

DarthLordZuko · 28 Oct 2020

Gotcha - wont run it.
I'll update on the MemTest thats currently runinng and activate the driver verifier tomorrow :)

- - - Updated - - -

So MemTest came out clear, I ran 2 tests back to back (literally 2 seconds apart) and there were no errors (attaching images):

Attachment 303798

If anyone wants to see the .html logs they are here -
Link

zbook · 28 Oct 2020

Please continue with hardware testing:
OCCT > run for 2 hrs

DarthLordZuko · 29 Oct 2020

Consulting with you guys -
These past 3 days I got 3-4 BSODS, but all the dump files are corrupted due to the symbol problems...
this morning I got 2 BSODS and when the blue screen got to 100% it just got stuck and did not reset the system (I had to do it manually).
Now I can't even debug the BSODS... and I don't know if turning the driver verifier will even help...

What are my options?
should I format the system completely?
should I wait for a windows update?

Thanks for the help!

Just incase you need more info, uploading the log collector...
Link

philc43 · 29 Oct 2020

Are you running any virtual PCs (e.g. Hyper V) on this system and if so are they running when you get the crashes?

DarthLordZuko · 29 Oct 2020

I am using WSL, BUT these crashes are not happening when I'm using it...

philc43 · 29 Oct 2020

OK, I was seeing some logs relating to virtual drives and that would explain it. I think the crashes are related to virtual memory address corruption but with so much memory on your system I was trying to work out why you would run into situations using virtual memory. I think this is pointing towards virtual memory corruption which involves the disk system - please continue with the hardware testing of the drives.