System Thread Exception Not Handled - can't find causes

1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create standard settings"
3. Select "Select driver names from a list"
4. Tick all 3rd party drivers
5. Accept changes and reboot computer

It looks to me as if one of the memory modules is faulty. Please try removing one of them and seeing if it makes a difference.

Repeat with the other one if necessary. There are various memory tests you can run but they are not always reliable. Report back on your findings.

The logs are in a foreign language and cannot be scanned.

Please change the default language to English and upload each V2 and DM into this thread:


https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

Sorry for that. Here are minidump and V2 files

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com


13) Make sure that there is no over clocking while troubleshooting

14) 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

Alright. Here are command prompt contents:

Microsoft Windows [Version 10.0.18362.836]
(c) 2019 Microsoft Corporation. All rights reserved.

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.18362.1

Image Version: 10.0.18362.836

[==========================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.18362.1

Image Version: 10.0.18362.836

[==========================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 Windows.

Stage 1: Examining basic file system structure ...
824064 file records processed.
File verification completed.
11156 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
4570 reparse records processed.
1076612 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
4570 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
126275 data files processed.
CHKDSK is verifying Usn Journal...
40032008 USN bytes processed.
Usn Journal verification completed.

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

248629505 KB total disk space.
212300632 KB in 611502 files.
334436 KB in 126276 indexes.
0 KB in bad sectors.
944593 KB in use by the system.
65536 KB occupied by the log file.
35049844 KB available on disk.

4096 bytes in each allocation unit.
62157376 total allocation units on disk.
8762461 allocation units available on disk.

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

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-J6N1FJH\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
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>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

And here are both requested images:
Attachment 281854
Attachment 281856

For virtual memory:
a) Move the dot from Custom size to System managed size
b) Check the box to Automatically manage paging file size for all drives
c) Reboot to maintain settings

Done.
Do you think this should do it?