IRQL_NOT_LESS_OR_EQUAL Error in Windows 7

DillonD

Reputable
May 2, 2014
5
0
4,510
Hello, every one out there. I was playing a game, nothing that was intense, and twice so far I received a IRQL_NOT_LESS_OR_EQUAL blue screen of death. I can use the computer normally without any BSoD, i.e. using internet, and microsoft word. I looked around on the forums and online, but couldn't find anything to really help me out. I was able to play the game fine for more than a week, but the past 2 days I have been getting this error screen randomly. I have a WhoCrashed log. The other times the laptop has crashed the message is the same. Thank you for any advice you may have. S

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 5/2/2014 10:53:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050214-35833-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C7CE52)
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.



On Fri 5/2/2014 10:53:24 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9BBF)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002C7CE52)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
You need to renew both NTOSKRNL and dxgmm1 from the installation DVD following the instructions in the web article. I got this problem on a new installation of Windows XP which rebooted frequently and this fixed it. Multiple Google searches indicate drivers, corrupted ntoskrnl.exe, games, hardware issues, but not many deffinite conclusions or solutions, but renewing the said file helped me solve it. BTW the ntoskrnl.exe file was not missing but maybe it got corrupted some way, because renewing it helped.

How to Replace NTOSKRNL.EXE (and dxgmms1.sys)
http://www.ehow.com/how_5085175_replace-ntoskrnlexe.html
 

DillonD

Reputable
May 2, 2014
5
0
4,510


The link you posted said to use a recovery cd/dvd. Would a flash drive work instead?
 

DillonD

Reputable
May 2, 2014
5
0
4,510


The problem is on a laptop, I do not think I am that familiar with hardware to be taking everything out and trying to fit it back together.
 

DillonD

Reputable
May 2, 2014
5
0
4,510


Just reread to article I do not have a windows recovery CD/DVD or a flash drive, I thought the website was saying to install NTOSKRNL onto a CD and boot it from that. Any other ideas on how to solve this problem?