Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List


This is a discussion on BSOD - ntoskrnl.exe IRQL_NOT_LESS_OR_EQUAL within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. OS - Windows 7 Home Premium SP 1 x64 Built this system about 2.5 years ago. Reformatted approximately one year

Closed Thread
Thread Tools Search this Thread
Old 07-17-2013, 01:31 AM   #1
Registered Member
Join Date: Jul 2013
Posts: 3
OS: Win7 Home Premium Service Pack 1

OS - Windows 7 Home Premium SP 1 x64

Built this system about 2.5 years ago. Reformatted approximately one year ago. This makes the OS a retail version.

The hardware is all 2.5 years old except the GPU which is about 8 months old.

CPU - AMD Phenom X4 965 Black Edition

GPU - XFX Core Edition FX-787A-CNFC Radeon HD 7870 GHz Edition


PSU - ANTEC EarthWatts EA-650

RAM - 2 x 4GB G.SKILL Ripjaws DDR3 1333

These BSODs have been happening primarily while playing video games (League of Legends, CS:GO, XCOM). WhoCrashed says its a cause of ntoskrnl.exe and ntkrnlmp.exe. The BSOD will say IRQL_NOT_LESS_OR_EQUAL. I've tried updating a few drivers: Audio/MOBO, graphics, webcam, keyboard, USB 3.0, and PCI IDE Controllers. DriverMax only shows that I've updated the webcam out of all of those and says a total of 16 are out of date (don't know if its scanning wrong or if I'm just an idiot and downloading the wrong drivers). The BSODs started happening about 1 week ago frequently.

For the few months prior, my computer startup was becoming very slow. I attributed that to the computer getting kind of old. Sometimes if I jumped into launching programs too quickly I would BSOD (not very frequently) but I would usually wait 10-15 minutes after launching windows to do anything. However, after updating some of these drivers, the computer startup has gotten better (I can start programs immediately with no crashes). I don't know if this contributes to the new BSODs that seem to happen randomly while playing video games. Sometimes they'll happen 5 minutes into the game and sometimes they don't come at all.
Attached Files
File Type: zip Windows7_Vista_jcgriff2.zip (3.12 MB, 109 views)
idmajestic is offline  
Sponsored Links
Old 07-17-2013, 01:42 AM   #2
TSF Team, Emeritus
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64


First of all, don't use 3rd party driver applications to update your drivers as they are known to download / install buggy, incomplete, and outdated drivers. Always get your drivers if they are out of date from the manufacturers website of the piece of hardware in question.

All of the attached DMP files are of the IRQL_NOT_LESS_OR_EQUAL (a) bugcheck:

A kernel-mode driver or process attempted to access a protected memory location it does not have permission for, or a kernel interrupt request level (IRQL) attempted to access a memory address that is too high.

This bugcheck usually occurs when a driver uses an incorrect memory address. Other possible causes of this error include: bug in a device driver, system service, the BIOS, an old Anti-virus program or backup tool, or possibly memory issues.
1. Uninstall AVG and replace with Microsoft Security Essentials for troubleshooting purposes:

AVG removal - AVG | Download tools and utilities

MSE - Microsoft Security Essentials - Microsoft Windows

If after removing and replacing AVG you're still crashing, enable Driver Verifier:

Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:


Patrick is offline  
Old 07-17-2013, 07:14 PM   #3
Registered Member
Join Date: Jul 2013
Posts: 3
OS: Win7 Home Premium Service Pack 1

Thanks! I've gotten MSE installed and will see if the BSODs keep coming.
idmajestic is offline  
Sponsored Links
Old 07-17-2013, 07:21 PM   #4
TSF Team, Emeritus
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64

My pleasure, keep me updated.


Patrick is offline  
Old 07-18-2013, 12:02 AM   #5
Registered Member
Join Date: Jul 2013
Posts: 3
OS: Win7 Home Premium Service Pack 1

I just got another BSOD -- I wasn't doing anything at this point, I was away and when I came back my computer had restarted and said that I had blue screened. This time WhoCrashed states the fault at

NTFS_FILE_SYSTEM from ntfs.sys. I'm going to run the driver verifier in the morning and will post tomorrow. Thanks for the help.
idmajestic is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD issues - ntoskrnl.exe and fltmgr.sys ?
Hi TechSupport people, This my first post in this forum and I hope I'm doing things right. :smile: I'm getting BSOD usually occurring when I'm watching a gaming stream (twitch.tv) for some reason. Crashes have also been occuring when I'm playing a game (league of legends) however no BSOD...
JtoC BSOD, App Crashes And Hangs 16 05-05-2013 08:13 PM
[SOLVED] HELP: BSOD caused by ntoskrnl.exe
Windows 7 Home Premium SP1 64-bit Original installed OS - N/A OEM purchased from a retailer All hardware about 2,5 years Intel i5 760 @ 2.80GHz ATI HD Radeon 5700 series Asus P7P55D-E Ram 8 gig outline problem:
DapperD BSOD, App Crashes And Hangs 3 04-16-2013 09:22 AM
ntoskrnl.exe BSOD
I've been having lot's of BSOD when gaming and doesn't really occur when browsing the web. I used bluescreenviewer and opened the dump file and it said caused by driver: ntoskrnl.exe. This started happening when I reinstalled windows and I thought it might of messed up in the installation and I...
JicaFold BSOD, App Crashes And Hangs 1 03-07-2013 11:56 AM
BSOD ntoskrnl.exe
Hello! I'm following this forum for a while, and was seeking for solutions for my problem. Somehow, i've tryied verifier, and worked, but today i have experienced another BSODS Again! But it happens when i'm playing Guild Wars 2. Happened to me like 2 or 3 times when i was playing, and when the...
Aquash BSOD, App Crashes And Hangs 4 12-11-2012 06:49 AM
The well known Windows 7 Bsod caused by ntoskrnl.exe !
Hi guys, :pray: :pray: :pray: First I'm running on : ∑ OS -Windows 7 ∑ x64 ∑ OEM version but purchased from retailer (weird I know) ∑ Age of system : 1.5 year ∑ Age of OS installation 1.5 years ∑ CPU : Core Quad Q8400 2.66 GHz
polol119 BSOD, App Crashes And Hangs 4 01-04-2011 02:29 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Post a Question

» Site Navigation
 > FAQ
Powered by vBadvanced CMPS v3.2.3

All times are GMT -7. The time now is 02:00 PM.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts