Windows 10 random reboot, screen hangs, sometimes BSOD

So this week, I've been getting a lot of reboots on my laptop. Sometimes my screen just freezes and I would need to hit the power button to restart. I also get BSODs with the stop code WHEA UNCORRECTABLE ERROR. Tried everything I could but I can't seen to find the cause of the problem




Update:
I used FurMark, Prime95, MemTest86+ and didn't get any errors. I've also used CrystalDiskInfo to check the health of my SSD/HDD and they're both at a 100% health (although SSD says 98% at HDsentinel). I've also tested their read/write and nothing's out of the ordinary. I've requested Sager for a BIOS update but they've never contacted me back

 

Download Who Crashed and see what the logs say. Then Google the results.

 

Still hasn't crashed and all the mini dumps were deleted for some reason but here's a mini dump for when I posted it from else where https://files.fm/u/k6j6xa69

I don't know how to read it tho

Update:
I used FurMark, Prime95, MemTest86+ and didn't get any errors. I've also used CrystalDiskInfo to check the health of my SSD/HDD and they're both at a 100% health (although SSD says 98% at HDsentinel). I've also tested their read/write and nothing's out of the ordinary. I've requested Sager for a BIOS update but they've never contacted me back

 

That's not going to help. What is your Windows version and what hardware are you running on?

 

I'm on Windows 10 1803 (I just tried 1809 a few hours ago and the problem still persists).

I have a P650RE laptop w/ GTX 970M, 16GB ram, 6th Generation Skylake Intel Core i7-6700HQ

Edit: I got 3 BSODs and here's what WhoCrashed says

On Mon 10/29/2018 2:40:23 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102918-5515-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3F520)
Bugcheck code: 0x124 (0x0, 0xFFFFDF0C71103028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 10/29/2018 2:40:23 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xD0)
Bugcheck code: 0x124 (0x0, 0xFFFFDF0C71103028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 10/29/2018 3:43:31 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102818-3265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x197650)
Bugcheck code: 0x139 (0x3, 0xFFFFF00405457340, 0xFFFFF00405457298, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

More likely HDD bad sectors and filesystem integrity issue.
Try chkdsk /f /x C: in elavted powershell/cmd prompt.

 

I got this result https://pastebin.com/CKJFsdUU

Can't copy paste it here for some reason

 

Ok looks like there were few filesystem errors and did you really get that Internal Info with some numbers and inverted question tags?
Try the same cmd for other partition/volumes.
Also, open crystaldisk info and see SMART status, if its green its okay. Additionally check or upload the screenshot of the fields such as, Current pending sector, relocated sector, error rates, uncorrectable errors.

 

actually Vasudev running chkdsk like that is not enough to fix bad sectors.
OP needs to run CHKDSK with the /R switch to actually fix bad sectors, although it will take much longer when using the /R switch.

so on the CMD prompt, run "chkdsk c: /r /x"

also try to listen for out of the ordinary sounds from the laptop; a laptop making strange humming/buzzing/clicking/tapping sounds when turning it on may indicate a failing HDD

 

I know that. I suggested the simple filesystem check to see if it passes w/o errors. If HDD is faulty then checking for bad sector might kill possibility of recovering data completely w/o any harm or damage.

 

So my laptop caught too much heat (idk where exactly) and local technician said it crisp the MOSFET and IC. Is there a chance to repair that?

 

I don't think so. If you have a picture of burned MOSFET and ICs I think only @Khenglish can help you in patching up your Sager.