BSOD every 2 days or so - fresh windows install

[di11on]

Hi folks,

I posted this over on the Windows 10 Forums, but haven't had a response yet. If this is against the rules, please let me know.

Since upgrading to windows 10 I've been getting a BSOD every 2 days or so. It rarely happens when I'm using the computer but when I log in in the morning I see that it crashed at some point since I was last using it. Thinking it was the upgrade, I did a clean install of windows 10 and am getting the same error, even after all windows updates and latest drivers.

My system specs are as follows:

Intel i7 4790K (not overclocked - default settings)
OS SSD: Samsung Evo 850 250MB
Data HDD: HGST Deskstar Idk 3tb Nas Emea
Graphics: MSI GeForce GTX 960 Gaming 2G, 2GB GDDR5
RAM: 2x8 GB-Kit Kingston 1866MHz DDR3 CL10 DIMM XMP Beast Series
Motherboard: Gigabyte GA-Z97X-UD5H, Socket 1150, ATX
Sound card: Creative XFi Gamer (old card!)

Everything is default in BIOS - no over clocking - default memory settings. BIOS is updated to the latest version.

Temps checked with Core Temp and they are excellent 20-25 degrees when idle and max 61 degrees under load.

I thought it might be memory, so I ran the windows memory diagnostics and it crashed with a bluescreen straight away. Thinking then that it was ram, I took one stick out and ran the windows memory diagnostics - no error. Ran it with the other stick - no errors. Then I ran Memtest86 on each stick for 3 hours and no errors.

I'm totally stumped as to what it could be. It's very difficult to diagnose because there doesn't seem to me to be a single event causing it. Here are the details of the last 3 errors from bluescreenview:

==================================================
Dump File : 010717-6906-01.dmp
Crash Time : 07/01/2017 02:01:41
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000034
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff803`388dfd89
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a6f0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.576 (rs1_release_inmarket.161208-2252)
Processor : x64
Crash Address : ntoskrnl.exe+14a6f0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010717-6906-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 497,884
Dump File Time : 07/01/2017 02:02:20
==================================================

==================================================
Dump File : 010517-7187-01.dmp
Crash Time : 05/01/2017 21:20:31
Bug Check String : RESOURCE_NOT_OWNED
Bug Check Code : 0x000000e3
Parameter 1 : ffffe006`1111f050
Parameter 2 : ffffe006`153f2800
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000002
Caused By Driver : NTFS.sys
Caused By Address : NTFS.sys+789a0
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.0 (rs1_release.160715-1616)
Processor : x64
Crash Address : ntoskrnl.exe+14a6f0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010517-7187-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 543,604
Dump File Time : 05/01/2017 21:21:04
==================================================

==================================================
Dump File : 010417-7031-01.dmp
Crash Time : 04/01/2017 21:49:43
Bug Check String :
Bug Check Code : 0x00000133
Parameter 1 : 00000000`00000001
Parameter 2 : 00000000`00001e00
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a6f0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.576 (rs1_release_inmarket.161208-2252)
Processor : x64
Crash Address : ntoskrnl.exe+14a6f0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010417-7031-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 543,652
Dump File Time : 04/01/2017 21:50:14
==================================================

Anyone any thoughts?

 

[Ne0Wolf7]

DId you test motherboard DIMM slots? This error probably isn't any software if you clean installed, and is not the RAM sinsce you tested them both. To test RAM slots, test one of the sticks in each slot. If one (wost case more) of the slots start causing the error, just don't use that slot anymore.

 

[Dunlop0078]

So it crashes immediately when you run the memory diagnostic tool with both sticks installed? If so its likely something to do with your ram, the fact that they run fine separately does not rule out the ram if they don't work well together. Have you enabled the XMP profile for your memory in the bios? If you haven't I would enable XMP, if you have I would disable it and let the motherboard set the ram to whatever speeds it wants and see if it still crashes.

Possibilities besides ram are drivers. The IRQL_NOT_LESS_OR_EQUAL error can be caused by a bad driver among many other things. I would open up device manager and look for any devices with a yellow exclamation mark or question mark.

 

[englandr753]

Another option is to remove all hardware that isnt needed to boot, 2nd mechanical storage drive, old sound card and any additional peripherals you dont need that may be connected to your pc such as a USB device or headset. Run your system and see if the crashes persist and if it doesnt, add one component at a time until you see the bsod reappear.

I had a customer once that had a 7 usb port device connected to her system that was faulty and was causing her system to crash.

 

[di11on]

So it crashes immediately when you run the memory diagnostic tool with both sticks installed? If so its likely something to do with your ram, the fact that they run fine separately does not rule out the ram if they don't work well together. Have you enabled the XMP profile for your memory in the bios? If you haven't I would enable XMP, if you have I would disable it and let the motherboard set the ram to whatever speeds it wants and see if it still crashes.

Possibilities besides ram are drivers. The IRQL_NOT_LESS_OR_EQUAL error can be caused by a bad driver among many other things. I would open up device manager and look for any devices with a yellow exclamation mark or question mark.

It crashed immediately when I did it - I don't know that it would always do this - next thing on my list to test.

 

[di11on]

To rule out hardware - does it work to disable it in device manager, rather than having to physically remove it from the system?

 

[englandr753]

It would be best to remove physically. If you're like me with 8 hard drives, just unplug the sata and power cables and plug back in one at a time until the issue reappears.

 

[johnbl]

just looking at the first bugcheck you have a driver that is attempting to read from memory address 30. this is not a valid kernel address is more likely a pool header data structure. This mean a driver is accessing data that most likely has been corrupted by another driver.

you have to run verifier.exe to find the bad driver.
or put the memory dump on a server, share the files for public access and post a link.
often it is pretty easy to see which driver is the likely cause.

to run verifier you start cmd.exe as an admin then run
verifier.exe /all /standard
and reboot and wait for the next bugcheck, then the next memory dump should name the bad driver.

note: be sure to know how to get into safe mode so you can turn verifier off if it bugchecks during boot up.
when done testing run verifier.exe /reset or your machine will run slowly until you do