BSOD Kernal Mode Heap Corruption

Windows 10 Pro Version 20190
Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics, 3500 Mhz, 4 Core(s), 4 Logical Processor(s)
Installed Physical Memory (RAM) 16.0 GB


GSOD Kernal Mode Heap Corruption when opening "ONLY" Teamviewer" and an email link to a Discover card payment.

When I copied link and opened it IE, it didn't BSOD yet does it every time with Edge or Chrome

Other than that, the PC functions with no problems.
Uploaded V2 Collector file.

In the Event Viewer, there are many instances of a Fatal Error:
"A fatal error occurred while creating a TLS client credential. The internal error state is 10013. The SSPI client process is svchost (PID: 9540)."
These appear always when the BSOD happens but also when the PC is not being used. There will be 5 or 6 instances in early morning when I'm not using the PC.

All updates done
All drivers have been updated,
All DISM commands run,
Malwarebytes and Adware cleaner run
Device Manager has no unknown devices
Cleaned or deleted all misc. programs that I'm not using

My main concern is the Teamviewer Free which I use as a volunteer for my senior citizens PC club.

(Just edited this. Forgot I posted problem with a different title 2 days ago. I think I'm losing it A fatal error occurred while creating a TLS client credential Checked for updates as requested)
Any help appreciated
Pete

Update BIOS - PRIME X370-A Driver & Tools | Płyty głowne | ASUS Polska
Install AMD chipset driver - https://www.amd.com/en/support/chips...ocket-am4/x370

The Ryzen with Vega display is current. Verified with AMD software.
Still BSOD'

Your Ego phrase fits me perfectly.
I can create the BSOD(Its green) any time by accessing TeamViewer or opening the link.

I just did it and created the BSOD screen.
HOWEVER, and this has been happening every time since this started. the screen hangs up and stays at 0% gathering information.
I then force shut down and restart.
Your comment about not seeing a dump file made me realize that this BSOD doesn't create one. I recall a number of times walking away and coming back hours later with the screen still there. And I'm sure it said 0% gathering.

I just ran the V2 again and this time watched it.
As it starts, it says "No crash dumps to copy" and then continues.
I should have noticed this days ago when it started

OK Rich
Ran most of these before but just ran batch file to make sure. Here's the results:

############################################################ The following commands will be run in sequence. ## The first 4 will take quite a while to run, be patient. ############################################################sfc /scannowdism /online /cleanup-image /scanhealthdism /online /cleanup-image /restorehealthsfc /scannowchkdsk /scanwmic recoveros get autorebootwmic recoveros set autoreboot = falsewmic recoveros get autorebootwmic recoveros get DebugInfoTypewmic recoveros set DebugInfoType = 7wmic recoveros get DebugInfoTypeC:\Users\petec\Desktop>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repaired them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.The system file repair changes will take effect after the next reboot.C:\Users\petec\Desktop>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.20190.1000Image Version: 10.0.20190.1000[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\Users\petec\Desktop>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.20190.1000Image Version: 10.0.20190.1000[===========================84.9%================= ][==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Users\petec\Desktop>sfc /scannowBeginning system scan. This process will take some time.There is a system repair pending which requires reboot to complete. RestartWindows and run sfc again.C:\Users\petec\Desktop>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 1057536 file records processed.File verification completed. Phase duration (File record verification): 18.69 seconds. 8549 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.79 milliseconds.Stage 2: Examining file name linkage ... 22017 reparse records processed. 1317332 index entries processed.Index verification completed. Phase duration (Index verification): 26.50 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 8.76 seconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.43 milliseconds. 22017 reparse records processed. Phase duration (Reparse point and Object ID verification): 96.23 milliseconds.Stage 3: Examining security descriptors ...Security descriptor verification completed. Phase duration (Security descriptor verification): 1.02 seconds. 129899 data files processed. Phase duration (Data attribute verification): 0.38 milliseconds.CHKDSK is verifying Usn Journal... 40698544 USN bytes processed.Usn Journal verification completed. Phase duration (USN journal verification): 230.47 milliseconds.Windows has scanned the file system and found no problems.No further action is required. 233310885 KB total disk space. 183305216 KB in 734876 files. 432772 KB in 129900 indexes. 0 KB in bad sectors. 1259541 KB in use by the system. 65536 KB occupied by the log file. 48313356 KB available on disk. 4096 bytes in each allocation unit. 58327721 total allocation units on disk. 12078339 allocation units available on disk.Total duration: 55.33 seconds (55336 ms).C:\Users\petec\Desktop>wmic recoveros get autorebootAutoRebootFALSEC:\Users\petec\Desktop>wmic recoveros set autoreboot = falseUpdating property(s) of '\\DESKTOP-5JNAOFF\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro Insider Preview|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'Property(s) update successful.C:\Users\petec\Desktop>wmic recoveros get autorebootAutoRebootFALSEC:\Users\petec\Desktop>wmic recoveros get DebugInfoTypeDebugInfoType7C:\Users\petec\Desktop>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\DESKTOP-5JNAOFF\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro Insider Preview|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'Property(s) update successful.C:\Users\petec\Desktop>wmic recoveros get DebugInfoTypeDebugInfoType7C:\Users\petec\Desktop>bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}########################################################################## Now copy the results in this window to the Clipboard so you can paste ## it into a post in your tenforums BSOD thread. ## See here for directions: #Batch files for use in BSOD debugging any key to continue . . .

- - - Updated - - -

Saved to a doc file. Here's an easier read.

The first scannow displayed:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Code:

The system file repair changes will take effect after the next reboot.

The second scannow displayed:

Code:

There is a system repair pending which requires reboot to complete. RestartWindows and run sfc again.

Please reboot > open administrative command prompt > run sfc /scannow > post results into the thread

Rebooted and made sure latest up in.
Here's latest V2 log (Not a BSOD expert but am basic W-10 IT) and it looks almost the same.
Since I still need the PC, found that by using Internet Explorer for all the BSOD sites, I have NO failures.
Before I consider a Reset or clean install, does this IE news change any thinking?
Pete