BSOD when idle, new system build

sambisu · 01 Sep 2015

I just built a new system (specs below) and have been experiencing a number of issues. I was getting BSODs right off the bat and was able to find a bad RAM stick with memtest. I removed it and then the system seemed to be running fine. I was able to run prime95, furmark and 3dmark without any crashes. I have also been playing Crysis 3 at max settings and no issues there either. Also had the system OCed to 4.3GHz, but I have since taken it back to stock speed.

The problem seems to be whenever the system sits idle. It crashes overnight and while I am at work (approx every 12 hours). Dump files are pointing to hal.dll and ntoskrnl.exe. I ran the Windows Memory Diagnostics and found no issues.

Then I enabled the driver verifier and got BSOD before windows finished booting. The dump file pointed to ntoskrnl.exe. I have uploaded a zip with the dump files.

By systematically going through the various drivers in verifier, I seem to have narrowed at least part of the problem to grdrv.sys. I renamed grdrv.sys to disable it. Still BSODed over night after disabling that. 3 times between 11:56PM and 12:41AM.

I left memcheck running today while I'm at work to see if there are any additional errors, but it wasn't finding anything on the first 5-6 passes. After finding and removing the bad RAM module, I did not do a fresh install of everything. Should I? Could the bad RAM have corrupted something during Windows or driver installation?

Drivers are all up to date.

Intel Core i7-5820K 3.3GHz 6-Core Processor
Corsair H100i GTX 70.7 CFM Liquid CPU Cooler
Gigabyte GA-X99-SLI ATX LGA2011-3 Motherboard
G.Skill Ripjaws Series 32GB (4 x 8GB) DDR4-2400 Memory
Samsung 850 EVO-Series 250GB 2.5" Solid State Drive
Asus GeForce GTX 980 4GB STRIX Video Card
EVGA 750W 80+ Gold Certified Fully-Modular ATX Power Supply

Thanks in advance for any help!

**Pauly** · 01 Sep 2015

Blue Screen of Death (BSOD) Posting Instructions

Can you please run the tool and upload all the files as this assists us in finding the root cause

I personally would do a clean install if I had unknowingly installed with bad ram, at the very minimum you need to run an sfc scan to see if any errors are present
SFC /SCANNOW Command - System File Checker

**Pauly** · 01 Sep 2015

Before we proceed I should say that we are currently experiencing problems with microsofts symbol server (we think) which is causing multiple problems processing dump files ATM but we can give it a go

Had a look at the dumps you posted and the first three are 0x124 errors which point towards a hardware related issue, in your case the are looking like CPU issues but there are many errors when loading the dump file so that info is not massively reliable

The last two dumps are 0xD5 errors blaming ghflt.sys which I believe comes from your gigabyte motherboard software
I would try removing all of this software if only temporary to see if it helps the situation

sambisu · 01 Sep 2015

Is it odd that the system wouldn't crash on CPU stress tests though if the CPU was the problem?

Seems crazy that I got bad RAM and a bad CPU. What are the odds? I ran memtest on the 2 modules still installed and there were no errors.

sambisu · 01 Sep 2015

Here are dump files again, but with that program

sambisu · 02 Sep 2015

Uninstalled all of the Gigabyte software yesterday and replaced the RAM with the new kit I ordered. Defective RAM is on its way back to newegg. I am continuing my "confidence run" today and if there are no more crashes then hopefully I can finally move on to getting everything else I need installed.

**Pauly** · 02 Sep 2015

Hi, sorry I didn't explain myself clearly earlier I was not implying the cpu was faulty only that the 0x124 errors were referencing the cpu, bear in my mind most (nearly all I think) modern motherboards send PCI & RAM traffic through the cpu so it is not necessarily implying the cpu is faulty just that the reported error was in some way related to the cpu. Sometimes these errors are resolved with bios updates and/or chipset updates but as I said earlier the dump files were not running properly and these could well be erroneous reports, my money would be on the gigabyte software being related to the problem so lets wait and see how you get on :)