Question
4688 views

League of Legends on Windows 8.1: ERROR: DRIVER_IRQL_NOT_LESS_OR_EQUAL

ef2013 asked on

HP Pavilion g6-2291ea Notebook PC
Windows 8.1 64-bit
Intel (R) Core (TM) i3-3110M
Intel (R) HD Graphics 4000

My laptop came with Windows 8 and I have updated to windows 8.1. A few minutes into a game (League of Legends), I get a blue screen that says ERROR: DRIVER_IRQL_NOT_LESS_OR_EQUAL then my PC restarts. After the first 2 occurences, I had done some things which fixed the problem but after a few days, It happened again and again. This only happens when I play League of Legends and not with any other applications. Also, this happens when I HAVE ALREADY STARTED A GAME.

I tried downloading this but it tells me that my laptop already has a more recent version than the one I am attempting to download! http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-124655-1&cc=uk&dlc=en&lc=en&os=4158&product=5393772&sw_lang=

I have read so many threads about this problem but they tend to be specific as those that reply ask for minidump files etc which I know nothing about. I don't want to do anything as it may just make my problem worse! 
15 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Thanks!

All of the attached DMP files are of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bug check.

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+63287 )


^^ Intel Graphics Driver.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers (which you noted you are), uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

---- You can also try from Intel directly - http://www.intel.com/p/en_US/support/detect

--------------------------------------------

Do note that other things can be causing corruption as well, Norton for example is very likely.

Remove and replace Norton with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

Norton removal tool - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

--------------------------------------------

If you're still crashing after all of the above, please enable Driver Verifier:


Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 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 if it detects a violation.

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"
Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

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 & 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 [B]NOT[/B] 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 24 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 %systemroot%\Minidump

Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617

Regards,

Patrick
Debugger/Reverse Engineer.
2 people found this helpful

Abuse history


progress