[SOLVED] Fresh Install - IRQL_NOT_LESS_OR_EQUAL BSOD after waking up from Sleep mode

[cloudropis_1]

My machine used to suffer from quite frequent BSODs, especially of the type in the title. It was a bit of a mess, so a couple of days ago I decided to wipe the SSD clean and start completely fresh. Just a few minutes ago the PC went into sleep mode by itself because I forgot to disable the "go into sleep mode after 30 minutes of going unused" setting, I started it back up, and 40 seconds later I got a BSOD - just like old times. Even the "collecting errors before restarting" process was unusually long, taking 30 seconds. This is a completely fresh installation, what gives?

This isn't the first time I brought this issue in these forums, and the most likely culprits were fingered as being some faulty/bad drivers (especially the infamous Scarlet Production drivers for Dualshock 3 compatibility), and bad RAM (which indeed turned out to be after a catastrophic memtest with an 83% score, which made me replace it). However, this is a fresh install with no drivers outside the bare minimum, and this new RAM is barely 8-9 months old. I don't know what else could be going wrong outside of the RAM once again going bad, which is so unlucky it's borderline unlikable.

Here's the minidump: https://1drv.ms/u/s!AszPI4pVTqe0hBdBNTqUAwZkyPR8

 

[Colif]

i have sent dump to a friend.

So no scarlet crush this time? Windows will get drivers even if you don't install them, so could be it grabbed an old driver.
What are specs of the PC?

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pursiergharial.htmlpasta.com/

File information:	031220-8015-01.dmp (Mar 11 2020 - 19:11:55)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: igfxEM.exe)
Uptime:	0 Day(s), 3 Hour(s), 40 Min(s), and 31 Sec(s)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/GA-Z97-HD3-rev-10
There are multiple revisions of your motherboard and I can't be sure which one you have, so the page above may be incorrect. There is likely a BIOS update available for your system. You are using version F5. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Intel Graphics Executable Main Module - why do you have Intel graphics installed if you have a AMD GPU as well? Do you have a monitor attached to motherboard as well?

newest VGA drivers on any of the motherboard revisions are older than what is installed.

Given I have same CPU, I can tell its not overclocked... Here are newer drivers for the Intel graphics on that CPU - https://downloadcenter.intel.com/product/81496/Intel-HD-Graphics-4600

 

[cloudropis_1]

@Colif I'm not following sorry, isn't it normal to have drivers and other stuff related to the integrated GPU even when not in use? So far I haven't installed any drivers by myself (outside of the GPU obviously), so everything you see is what Windows Update installed itself after first boot.

"newest VGA drivers on any of the motherboard revisions are older than what is installed.", am I brainfarting or does that mean that my automatically installed by Windows Update drivers are actually more recent than the ones provided by the manufacturer? I have the newest versions of the latter in a folder ready to be installed, I haven't come around to it because I had other priorities, so I've been relying to the automatic ones the past few days (although I'd get these BSODs on my old installation, with updated manufacterer provided drivers, too).

Thanks to gardenmen too, I'll come around to updating my BIOS either today or tomorrow. Mobo is Rev 1.0.

 

[Colif]

Is your monitor attached to GPU?
wonder if IGPU enabled in BIOS (not sure if it could be reason or what default setting in bios would be)

I don't have the intel graphics drivers on my PC so I don't think its normal. I have a Z97 board as well so would think the basic install would be the same.

The Intel Graphics drivers on PC are newer than what shows on the Gigabyte website, they may have come from windows update as it will try to match hardware drivers to what you have. The intel link I gave at end is even newer.

I don't know why you have the drivers but it is them that caused BSOD and its reason I offered new versions.

 

[cloudropis_1]

Is your monitor attached to GPU?
wonder if IGPU enabled in BIOS (not sure if it could be reason or what default setting in bios would be)

I don't have the intel graphics drivers on my PC so I don't think its normal. I have a Z97 board as well so would think the basic install would be the same.

The Intel Graphics drivers on PC are newer than what shows on the Gigabyte website, they may have come from windows update as it will try to match hardware drivers to what you have. The intel link I gave at end is even newer.

I don't know why you have the drivers but it is them that caused BSOD and its reason I offered new versions.

Yes, monitor is attached to the GPU, and nothing is to the mobo. I think the IGPU is enabled because, a year ago or so, I changed GPU and I had a brainfart that made me connect the HDMI to the motherboard rather than the new GPU, which made me operate the computer on integrated for a few minutes before realizing - and the IGPU was definitely on and functioning (granted, I reinstalled Windows last week but I've never fiddled with IGPU settings with either installations)
Those drivers are the cause then? Guess updating them is worth the try. I was busy the last few days, I'll finish updating the other drivers and the bios and see how it goes.

 

[Calvin7]

Memory errors are often linked to what memory you bought or the memory itself is defective. I suggest listing it by part number and/or link. You can test for defective memory with MemTest86.

 

[Colif]

IRQ errors can be ram, as well as drivers. Since it showed which driver was to blame and the crash seemed to happen after sleep, I would be more inclined to think its the old drivers not waking up right even if they aren't in use.

If op keeps getting BSOD and they more random and start blaming unlikely drivers, then ram starts to be questioned.