Windows 10: PC freezing and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M bsod

Hello,

As the title says my pc will randomly freeze and give me the [COLOR=rgba30, 30, 30, 1]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M blue screen of death. I've uploaded the dump files created by the last BSOD. I have had previous crashes but these files have been deleted somehow. [/COLOR]


[COLOR=rgba30, 30, 30, 1]I am also having issues updating to Windows 10, version 20H2 - Error 0x8007001f if this has anything to do with it.[/COLOR]



https://drive.google.com/drive/folders/13q7AgJlV6WvDhO-GFWHxv2yitZBh8nzq?usp=sharing

:)

 

BSOD and freezing

Yesterday I started up my laptop from hibernating and it freezes, after restarting several times I get a BSOD which freezed on the BSOD one time.
After restarting again the laptop freezed at the Welcome screen.
I have had the freezing before, it was gone for about 2 months.
I did not install any new hardware.
Now it seems to run fine again.

But what is causing the freezing and the BSOD?
I bought this laptop last January.

 

BSOD Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

I have been having several BSOD recently and have reinstalled windows a few times but have been getting the Error:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

I have a crash report of:

On Mon 8/7/2017 4:31:47 PM your computer crashed

crash dump file: C:\Windows\Minidump\080717-7781-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800A9B5B5D8, 0xFFFFBC8125F8AA28, 0xFFFFBC8125F8A270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 8/7/2017 4:31:47 PM your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800A9B5B5D8, 0xFFFFBC8125F8AA28, 0xFFFFBC8125F8A270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 8/7/2017 1:23:30 PM your computer crashed

crash dump file: C:\Windows\Minidump\080717-7906-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018394B5D8, 0xFFFFA500C6488A28, 0xFFFFA500C6488270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 8/3/2017 3:33:48 PM your computer crashed

crash dump file: C:\Windows\Minidump\080317-9781-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0xCB5D8)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8012635B5D8, 0xFFFFCB0149BF5A28, 0xFFFFCB0149BF5270)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Can anyone help me figure this out?

Thank you

 

New Homebuild freezing and BSOD

So you are saying a PSU can never cause a computer to Freeze/BSOD...???