Bluescreen: IRQL Not Less Or Equal BSOD error

wybrem

Reputable
Apr 25, 2015
55
0
4,630
Hello,
I have this error since recently really, mostly when playing The Crew, not every time though for a while. Now I recently reinstalled Windows and got some new hardware, and made some changes in Windows.

PC specs :
Mobo: Asus Crosshair Formula-Z
CPU: 5.0GHz AMD FX9590
GPU1: MSI R9 390 8G *new (GTX 560 SC 1G before)
GPU2: MSI R9 390 8G *new (GTX 560 SC 1G before)
MEM: 32GDDR3 @ 2400Mhz *new (12GB @ 1333mhz before)
PSU: 1000W CoolerMaster Gold

Recent changes in Windows:
Reduced pagefile size: old size: 32GB, new size: 1024MB - 2048MB.

Dump files (3):
http://puu.sh/kTYSf/9e97b7931e.rar

Things I tried:
-Anti Virus Scan
-Anti Mallware Scan
-Anti Rootkit Scan
-Anti Exploit Scan
-Aggressive Multi Scan
-Registery Cleanup / Defrag

I really have no clue about these things, so any help would be much appreciated.
 
Solution
first bugcheck was in the video driver, the stack was corrupted.

you have 3 overclocking drivers installed remove all three:
AODDriver2.sys Tue Feb 11 03:06:52 2014
AODDriver2.sys Tue Oct 29 17:58:36 2013
RTCore64.sys Fri Apr 24 00:01:47 2015

generally the overclocking drivers would not cause this type of corruption but remove them and see if anything is improved.
if you still get a bugcheck, then I would run cmd.exe as an admin and
then run
verifier.exe /standard /all
if verifier detects a driver corrupting some others drivers data it will call a bugcheck and name the driver in the memory .dmp file.
note use verifier.exe /reset
to turn off verifier function when done testing.

wybrem

Reputable
Apr 25, 2015
55
0
4,630


I've done that now, but it's still happening, during the game it is 65C, i will try the page file size now.
 
first bugcheck was in the video driver, the stack was corrupted.

you have 3 overclocking drivers installed remove all three:
AODDriver2.sys Tue Feb 11 03:06:52 2014
AODDriver2.sys Tue Oct 29 17:58:36 2013
RTCore64.sys Fri Apr 24 00:01:47 2015

generally the overclocking drivers would not cause this type of corruption but remove them and see if anything is improved.
if you still get a bugcheck, then I would run cmd.exe as an admin and
then run
verifier.exe /standard /all
if verifier detects a driver corrupting some others drivers data it will call a bugcheck and name the driver in the memory .dmp file.
note use verifier.exe /reset
to turn off verifier function when done testing.
 
Solution

wybrem

Reputable
Apr 25, 2015
55
0
4,630


Thanks, i will try to remove them, i'm not sure how to remove them thoughh