BSOD: System exception not handled and kernel mode heap corruption

Win 10 Build 19041.685

Hi there, I've been having frequent BSOD's recently. Not changed anything that I'm aware of, other than windows updates but been doing some more demanding tasks and these crashes have started occurring regularly.

Main errors are:

System exception not handled
Kernel mode heap corruption

I've tried updating graphics card drivers and ran MemTest, sfc/scannow and DISM which reported no errors.

Any suggestions would be great as I use this PC for work and it's becoming a real pain.

Thanks!

(Event logs attached.)

Update BIOS - MSI Polska
Update AMD chipset driver - https://www.amd.com/en/support/chips...ocket-am4/b450

Could you explain why this is relevant to my system and the problem I'm having? Thanks.

1) Run:

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


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


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


2) After completing the above steps:


Open administrative command prompt (ACP) and type or copy and paste:
powercfg -h off



3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

4) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive


5) Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Thank you, here are the results.

Tuneup.bat:

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow


chkdsk /scan


wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType


wmic pagefile list /format:list
wmic Computersystem where name="JAMIEDESKTOP" get AutomaticManagedPagefile
wmic Computersystem where name="JAMIEDESKTOP" set AutomaticManagedPagefile=True
wmic Computersystem where name="JAMIEDESKTOP" get AutomaticManagedPagefile


bcdedit /enum {badmemory}




C:\WINDOWS\system32>sfc /scannow


Beginning system scan. This process will take some time.


Beginning verification phase of system scan.
Verification 100% complete.


Windows Resource Protection did not find any integrity violations.


C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth


Deployment Image Servicing and Management tool
Version: 10.0.19041.572


Image Version: 10.0.19041.685


[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.


C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 10.0.19041.572


Image Version: 10.0.19041.685


[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


C:\WINDOWS\system32>sfc /scannow


Beginning system scan. This process will take some time.


Beginning verification phase of system scan.
Verification 100% complete.


Windows Resource Protection did not find any integrity violations.


C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is OS.


Stage 1: Examining basic file system structure ...
793088 file records processed.
File verification completed.
Phase duration (File record verification): 7.67 seconds.
9176 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.85 milliseconds.


Stage 2: Examining file name linkage ...
452 reparse records processed.
1056454 index entries processed.
Index verification completed.
Phase duration (Index verification): 21.41 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.81 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.08 milliseconds.
452 reparse records processed.
Phase duration (Reparse point and Object ID verification): 4.88 milliseconds.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 29.25 milliseconds.
131684 data files processed.
Phase duration (Data attribute verification): 0.37 milliseconds.
CHKDSK is verifying Usn Journal...
40390392 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 150.79 milliseconds.


Windows has scanned the file system and found no problems.
No further action is required.


976101375 KB total disk space.
574237536 KB in 621072 files.
377180 KB in 131685 indexes.
0 KB in bad sectors.
933987 KB in use by the system.
65536 KB occupied by the log file.
400552672 KB available on disk.


4096 bytes in each allocation unit.
244025343 total allocation units on disk.
100138168 allocation units available on disk.
Total duration: 32.10 seconds (32105 ms).


C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
TRUE




C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\JAMIEDESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.


C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE




C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7




C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\JAMIEDESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7




C:\WINDOWS\system32>wmic pagefile list /format:list




AllocatedBaseSize=13312
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20200318151045.541491+000
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE








C:\WINDOWS\system32>wmic Computersystem where name="JAMIEDESKTOP" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE




C:\WINDOWS\system32>wmic Computersystem where name="JAMIEDESKTOP" set AutomaticManagedPagefile=True
Updating property(s) of '\\JAMIEDESKTOP\ROOT\CIMV2:Win32_ComputerSystem.Name="JAMIEDESKTOP"'
Property(s) update successful.


C:\WINDOWS\system32>wmic Computersystem where name="JAMIEDESKTOP" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE




C:\WINDOWS\system32>bcdedit /enum {badmemory}


RAM Defects
-----------
identifier {badmemory}
Press any key to continue . . .

Logs.bat zip file can be downloaded from this Google Drive link.


Powercfg.bat zip file attached.
Attachment 310206


Startup & recovery settings:

Attachment 310204


Virtual memory settings:

Attachment 310205


Not had another BSOD yet but will run the log collector when I do. They are happening randomly every 10-15 minutes or so.

For share links please use: one drive, drop box, or google drive.

See posting instructions for tuneup.bat

Sorry, I have updated the previous post now.

Please rerun LOGS and post new results.

Indicate the progress with:
a) upgrading the BIOS
b) upgrading chipset drivers
c) powercfg -h off
d) reading the links on Windows driver verifier

Updated LOGS.BAT results.

a) BIOS is from 08/2019, I'm unable to upgrade today but can try in the near future.
b) Chipset drivers are up to date.
c) 'powercfg -h off' has been run.
d) I have read the link about driver verifier.

Create System Restore Point in Windows 10


Read these links on Windows driver verifier:

Learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified