Windows 10: BSOD occurring every time my computer idles

Hello,

While searching online for a solution to my BSODs, I came across Windows 10 Forums and thought I'd ask you guys! I recently built my first computer to use for when I work remotely. Everything was great to start, but after a short time (a few days to a week or two), my computer started to BSOD every single time it idled. I have wiped everything and installed Windows 10 Pro at least 3 times only to get the same issue after about a week. I then tried Windows 10 Enterprise and my computer has started BSODing again after the same amount of time passed. For the first few days after each Windows installation everything works great. Here are all the components I used to build my computer:

GIGABYTE GA-H170M-D3H (rev. 1.0) LGA 1151 Intel H170 HDMI SATA 6Gb/s USB 3.0 Micro ATX Intel Motherboard
Intel Core i5-6600K 6M Skylake Quad-Core 3.5 GHz LGA 1151 91W BX80662I56600K Desktop Processor Intel HD Graphics 530
SAMSUNG 850 EVO 2.5" 500GB SATA III 3-D Vertical Internal Solid State Drive (SSD) MZ-75E500B/AM
CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000) Desktop Memory Model CMK16GX4M2A2133C13
I ran the dm_log_collector.exe from this site and attached the .zip it generated (13 .dmp files since 12/1/16!). Please let me know if there is any other information I can provide that will help in the troubleshooting process.

:)

 

BSOD: CRITICAL PROCESS DIED

Before BSOD occur, my disk usage is 100% then suddenly it occur. It is not the case that every time when my disk usage is 100%, BSOD occurs.

 

BSOD error message system thread exception not handled

Hi,

My computer recently has been shutting down on its own several times a day. Typically when computer is idle.

I get the BSOD with error message system thread exception not handled. I dont have time to write down the whole thing as its so randam that im usually not by my computer. Is there a way I can print the BSOD or find out what errors are really occurring
after the event?

Can anyone help with what I should do

I have windows 10 home, version 10.0.14393

hp computer h8 1210t

Thank you in advance

 

In similar threads user axe0 has suggested running sfc/scannow in the cmd. I got this:
Attachment 112471
Would this file be helpful? It exceeds 2.0 MB so I will need to use another service to upload it.

 

Diagnostic Test

RAM TEST
*Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

Hi axe0,I was reading other BSOD threads and decided to run MemTest86+ before I got your response. I hope that running this first is not a big deal as it took 15.5 hours! Here is a picture of the .html report generated from MemTest86+ as well as the HDTune screen clippings requested: Attachment 112585



Attachment 112586
Attachment 112587
Attachment 112588



















































































































I attached the chkdsk results as well. Please let me know if there is anything else you would like me to do!

 

Run chkdsk, same command, once more please. The file system has/had quite some corruption.

Run MemTest86+ v5.01 as requested.

 

Attached is the chkdsk log from running it again this morning. You want me to run MemTest86+ for a second time? If so, I won't be able to run it until late Wednesday night as I need the computer for work.

Another tidbit that may or may not be beneficial is that my Hyper-V VM (same OS) is also BSODing with the same behavior as my host computer:

Attachment 112643

 

The previous memory test wasn't memtest86+, but mentest86.

 

Jesus, my bad. Ok I'll run MemTest86+ Wednesday night. BSOD update: FAULTY_HARDWARE_CORRUPTED_PAGE just now on my VM, and KERNAL_SECURITY_CHECK_FAILURE on my host machine yesterday. It keeps getting better!

 

Just found Gigabyte came out with a recent BIOS updatae: GIGABYTE - Motherboard - Socket 1151 - GA-H170M-D3H (rev. 1.0)


I just Q-Flashed to the newest F20 version.

 

Don't forget to run MemTest86+ *Smile
If the memory appears faulty in the test, the BIOS update won't help much.