DRIVER_IRQL_NOT_LESS_OR_EQUAL & IRQL_NOT_LESS_OR_EQUAL Blue Screen of Death

ddjovcic · Apr 24, 2015

Please help me,
I have a problem. Every time I start a game I get a blue screen saying IRQL_NOT_LESS_OR_EQUAL or DRIVER_IRQL_NOT_LESS_OR_EQUAL. I downloaded BlueScreenView and saw that the cause was once tcpip.sys then in another BSOD ntoskrnl.exe then in another atikmdag.sys etc etc.. I really need help guys, my PC worked fantastic on its first OS install but when I did a clean re-install of Windows 8.1, after 2 months of using it, the problems started.

My AMD Driver is Omega 14.12 Link to minidump

My PC Specs:
Motherboard: ASUS Republic of Gamers Hero VII
CPU - Intel i7-4790K
GPU - MSI Gaming R9-290X
RAM - Kingston HyperX Fury Red 1866MHz
SSD - Intel 520SSD 120GB
HDD - Seagate Barracuda 3TB

johnbl · Apr 27, 2015

I could not get to your minidump
generally any bugcheck in tcpip will be caused by bugs in a wired or wireless ethernet driver.
(at lease as a direct cause, indirect causes would be any driver corrupting the network drivers data)

ddjovcic · Apr 29, 2015

johnbl :

Thanks for the feedback, i am resending the minidump file: https://www.dropbox.com/s/mkp48918mw4hymu/BlueScreenView.txt?dl=0

johnbl · Apr 29, 2015

I actually need the memory dump binary. You provided a text file that just shows that something was wrong with your graphics subsystem. With that info all I can say is update your graphics driver. Not to useful because it is often the first thing people do.

ddjovcic :

ddjovcic · Apr 29, 2015

johnbl :

I actually need the memory dump binary. You provided a text file that just shows that something was wrong with your graphics subsystem. With that info all I can say is update your graphics driver. Not to useful because it is often the first thing people do.

ddjovcic :

Oh sorry, I am a noob.. :/ Here are the actual dump files https://www.dropbox.com/s/j5epbjhpylzomaq/minidmp.rar?dl=0

johnbl · Apr 29, 2015

bugcheck was called because CCC.exe Catalyst Control Centre
made a system call but the data passed to the system got garbled.
I would reset the BIOS to defaults and make sure nothing is overclocked.

if there is any chance that your various binaries for your graphics card might be of mixed builds I would uninstall them reboot and reinstall. Pay particular attention to the Graphics cards audio support driver. often, people don't update that binary when they update the graphics card drivers. That driver can conflict with the motherboard audio driver.
and if it becomes too out of date with the graphic driver you can get errors like you have.

\SystemRoot\system32\drivers\AtihdWB6.sys Sat Jun 21 19:32:00 2014 <----- different date of this file
\SystemRoot\system32\DRIVERS\atikmdag.sys Thu Nov 20 18:30:27 2014
\SystemRoot\system32\DRIVERS\atikmpag.sys Thu Nov 20 18:08:54 2014

you may just want to go to amd and get the current driver version and make sure you also include the graphic drivers high definition audio driver (even if you don't use it) if you don't use it, disable it in winodws control panel device manager. when you are done, to to the bios and reset it to defaults, it will force the BIOS to rescan and assign interrupts and DMA channels again and make a database of settings to be passed to windows.

--------------
remove WinDivert network packet capture and (re)injection driver
windivert.sys
and see if you can get the bugcheck without the hacking software installed.
-----------
I would also reset the BIOS to defaults, the current speed is a unusual number.
and may indicates some BIOS overclocking or incorrect settings.

make sure your BIOS is not overclocking the PCI/e bus
-----
BIOS Version 2601
BIOS Starting Address Segment f000
BIOS Release Date 03/26/2015
Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VII HERO
Version Rev 1.xx
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4013MHz

ddjovcic :

ddjovcic · Apr 29, 2015

johnbl :

bugcheck was called because CCC.exe Catalyst Control Centre
made a system call but the data passed to the system got garbled.
I would reset the BIOS to defaults and make sure nothing is overclocked.

if there is any chance that your various binaries for your graphics card might be of mixed builds I would uninstall them reboot and reinstall. Pay particular attention to the Graphics cards audio support driver. often, people don't update that binary when they update the graphics card drivers. That driver can conflict with the motherboard audio driver.
and if it becomes too out of date with the graphic driver you can get errors like you have.

\SystemRoot\system32\drivers\AtihdWB6.sys Sat Jun 21 19:32:00 2014 <----- different date of this file
\SystemRoot\system32\DRIVERS\atikmdag.sys Thu Nov 20 18:30:27 2014
\SystemRoot\system32\DRIVERS\atikmpag.sys Thu Nov 20 18:08:54 2014

you may just want to go to amd and get the current driver version and make sure you also include the graphic drivers high definition audio driver (even if you don't use it) if you don't use it, disable it in winodws control panel device manager. when you are done, to to the bios and reset it to defaults, it will force the BIOS to rescan and assign interrupts and DMA channels again and make a database of settings to be passed to windows.

--------------
remove WinDivert network packet capture and (re)injection driver
windivert.sys
and see if you can get the bugcheck without the hacking software installed.
-----------
I would also reset the BIOS to defaults, the current speed is a unusual number.
and may indicates some BIOS overclocking or incorrect settings.

make sure your BIOS is not overclocking the PCI/e bus
-----
BIOS Version 2601
BIOS Starting Address Segment f000
BIOS Release Date 03/26/2015
Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VII HERO
Version Rev 1.xx
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4013MHz

ddjovcic :

Thank you so much for the quick answer! I will try to do the things you stated and will report back asap

Also I forgot to tell you this, I was running memtest86 and an error popped up. Before I even managed to read what the error said, a BlueScreen popped up.

ddjovcic · Apr 30, 2015

johnbl :

bugcheck was called because CCC.exe Catalyst Control Centre
made a system call but the data passed to the system got garbled.
I would reset the BIOS to defaults and make sure nothing is overclocked.

if there is any chance that your various binaries for your graphics card might be of mixed builds I would uninstall them reboot and reinstall. Pay particular attention to the Graphics cards audio support driver. often, people don't update that binary when they update the graphics card drivers. That driver can conflict with the motherboard audio driver.
and if it becomes too out of date with the graphic driver you can get errors like you have.

\SystemRoot\system32\drivers\AtihdWB6.sys Sat Jun 21 19:32:00 2014 <----- different date of this file
\SystemRoot\system32\DRIVERS\atikmdag.sys Thu Nov 20 18:30:27 2014
\SystemRoot\system32\DRIVERS\atikmpag.sys Thu Nov 20 18:08:54 2014

you may just want to go to amd and get the current driver version and make sure you also include the graphic drivers high definition audio driver (even if you don't use it) if you don't use it, disable it in winodws control panel device manager. when you are done, to to the bios and reset it to defaults, it will force the BIOS to rescan and assign interrupts and DMA channels again and make a database of settings to be passed to windows.

--------------
remove WinDivert network packet capture and (re)injection driver
windivert.sys
and see if you can get the bugcheck without the hacking software installed.
-----------
I would also reset the BIOS to defaults, the current speed is a unusual number.
and may indicates some BIOS overclocking or incorrect settings.

make sure your BIOS is not overclocking the PCI/e bus
-----
BIOS Version 2601
BIOS Starting Address Segment f000
BIOS Release Date 03/26/2015
Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VII HERO
Version Rev 1.xx
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4013MHz

ddjovcic :

Unfortunately, this hasn't helped

I have the latest AMD Driver with the Audio Driver installed and I still get the BSOD 5 minutes into playing a game. This time it's memory management. Here's the dump file: https://www.dropbox.com/s/j5epbjhpylzomaq/minidmp.rar?dl=0 I've deleted windivert.sys and reset the bios too.

Tradesman1 · Apr 30, 2015

Have you downloaded the latest WIN drivers for you mobo and installed them?

ddjovcic · Apr 30, 2015

Tradesman1 :

Yes, I have the latest motherboard drivers installed and still, the bluescreens stay.

Tradesman1 · Apr 30, 2015

What PSU? and how old is it?

ddjovcic · May 1, 2015

Tradesman1 :

I have this PSU (730W): http://www.thermaltake.com/products-model.aspx?id=C_00001966
The whole PC is 6 months old so aging capacitors can't be the problem.

ddjovcic · May 1, 2015

Well, turns out it was faulty ram. I pulled out both RAM's. When I put just one DIMM in, everything worked like a charm. Then, I replaced this DIMM with the other one from the kit, after 2 mins a BSOD popped up. I have a kit of 2 8GB Kingston HyperX Fury Red 1866MHz DIMM's and one of them failed.. Big thumbs down for Kingston.. :/ Anyways, thanks for the help guys, appreciate it!

Tradesman1 · May 1, 2015

No worries, they have a lifetime warranty so should be relatively easy to get replaced

johnbl · May 2, 2015

first bugcheck, caused by memory corruption, you still have a hacking program running.
remove your hacking program and reproduce the problem without it running.
system is also slightly overclocked. reset the BIOS to defaults.

second bugcheck also caused by a bad instruction pointer

you can not debug these problems with a mini memory dump you need a kernel memory dump
and you need to run cmd.exe as an admin then run
verifier.exe /standard /all
this will bugcheck the system if a driver is doing bad calls or corrupting memory. it will save a memory dump and name the bad driver.

suspect driver:
DAEMON Tools Virtual SCSI Bus Driver (remove)
\SystemRoot\system32\DRIVERS\dtscsibus.sys Mon Oct 29 02:28:48 2012

also windivert hacking program is installed and it could cause this type of error.

ddjovcic · May 5, 2015

johnbl :

first bugcheck, caused by memory corruption, you still have a hacking program running.
remove your hacking program and reproduce the problem without it running.
system is also slightly overclocked. reset the BIOS to defaults.

second bugcheck also caused by a bad instruction pointer

you can not debug these problems with a mini memory dump you need a kernel memory dump
and you need to run cmd.exe as an admin then run
verifier.exe /standard /all
this will bugcheck the system if a driver is doing bad calls or corrupting memory. it will save a memory dump and name the bad driver.

suspect driver:
DAEMON Tools Virtual SCSI Bus Driver (remove)
\SystemRoot\system32\DRIVERS\dtscsibus.sys Mon Oct 29 02:28:48 2012

also windivert hacking program is installed and it could cause this type of error.

Thanks but I already solved the problem, it was 1 faulty RAM stick.

Search

DRIVER_IRQL_NOT_LESS_OR_EQUAL & IRQL_NOT_LESS_OR_EQUAL Blue Screen of Death

ddjovcic

Reputable

johnbl

Polypheme

ddjovcic

Reputable

johnbl

Polypheme

ddjovcic

Reputable

johnbl

Polypheme

ddjovcic

Reputable

ddjovcic

Reputable

Tradesman1

Legenda in Aeternum

ddjovcic

Reputable

Tradesman1

Legenda in Aeternum

ddjovcic

Reputable

ddjovcic

Reputable

Tradesman1

Legenda in Aeternum

johnbl

Polypheme

ddjovcic

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page