BSOD IRQL_NOT_LESS_OR_EQUAL on new rig

[Gabriel Figueroa]

Hello everyone

I recently built a new rig with
Gigabyte z97-hd3 mobo
Intel Core i5 4590
8GB (4gbx2) Kingston Hyper X fury ram
120GB Kingston SSD as boot drive
1TB WD Blue for storage
LG BDROM
EVGA GTX 960 SSC
Ultra 650w PSU
Cooler Master Evo

Normally when I leave the house I put the compute to sleep so I can resume quickly when I get back. Every now and then when resuming the computer I am greeted by a windows has crashed message indicating a BSOD

I downloaded whocrashed me and this came up
------------------------------------------------------------------
On Sat 3/7/2015 1:30:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-6084-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0xFFFFFA8406DAF360, 0x2, 0x1, 0xFFFFF800030DC03E)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
---------------------------------------------------------------------

Links to dumpfiles
https://www.dropbox.com/s/9p0nltaerp5qlx1/022815-7846-01.dmp?dl=0
https://www.dropbox.com/s/uj0tvzmxbbv15b2/030715-6084-01.dmp?dl=0

SO far I verified and BIOS is updated, GPU is updated, ran memtest x86 for 4 passes and no errors came up.

Any ideas what could be causing this? I'm not good when it comes to diagnosing BSODs
if any more information is needed I can post right away

 

[Unolocogringo]

The only thing obvious is the Ultra power supply.
Haswell cpus have a lot lower power draw state than older processors when in sleep modes. Some power supplies are not compatable with Haswell cpus. They are not able to supply stable power at such low load levels.
Ultra have always been tier 4 or 5 power supplies. Tier 5 being the worst you can buy.

 

[Gabriel Figueroa]

The only thing obvious is the Ultra power supply.
Haswell cpus have a lot lower power draw state than older processors when in sleep modes. Some power supplies are not compatable with Haswell cpus. They are not able to supply stable power at such low load levels.
Ultra have always been tier 4 or 5 power supplies. Tier 5 being the worst you can buy.

Thanks for the input, I was thinking it could be the PSU, I got it on sale at tiger with them ram. I will try and see if there is anything else causing this issue, any suggestions on a good unit for my rig? (amazon preferred)

 

[Werkrat]

Tier 1 or 2 from this list are good http://www.tomshardware.com/forum/id-2547993/psu-tier-list.html

I got my seasonic x series off amazon, been perfect so far.

 

[Gabriel Figueroa]

Thank you for the PSU suggestions!

Okay I did some quick google-ing and found out that putting a non haswell PSU rig to sleep will cause problems. What I found as a solution was to go into the BIOS and disable c6/c7, my MOBO was set on auto so something has to give if this is the issue.

I did this and will monitor the rig for the next few days but my question remains,

Looking at that error is there any other possible thing that could be causing it? Just want to cover all of my bases while I check if the rig BSODs again after disableing c6/c7

 

[Unolocogringo]

A lot of times that error is related to memory or drivers.
It can also be caused by bad power to the memory or cpu.
But you stated that it happens when the computer is put into sleep mode.

 

[Gabriel Figueroa]

A lot of times that error is related to memory or drivers.
It can also be caused by bad power to the memory or cpu.
But you stated that it happens when the computer is put into sleep mode.

Besides testing the RAM is there anything else I may have overlooked? I'm planning on putting the rig to sleep tonight and waking it tomorrow to see if it was the c6/c7 setting but I'm still not holding my breath.

 

[Karadjgne]

Only thing I can suggest is in bios disable c-states, or if bios allows set c-states for maximum of c3. This will allow 'sleep' but kill hibernation, which many don't use anyways as it takes up a bunch of room on the SSD.