Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD driver irql not less or equal error


  • Please log in to reply

#1
Crownflame

Crownflame

    Member

  • Member
  • PipPip
  • 28 posts
Hi!

I've recently been recuperating my computer from a recent crash and factory restore, reinstalling all my old programs and whatnot. For a week or so I hadn't had any issues, but for the past three days I've been getting seemingly random BSODs (there doesn't seem to be any specific trigger) and I'm not really sure what to do about it. I attempted a system restore but the issue persisted, and now it looks like I have only one error to dump here. I've kind of searched around here and other places on the internet, but I'm still pretty baffled as to what to do about this.

Any help would be appreciated! Thanks!

I keep trying to attach the .DMP file, but it won't let me for some reason. This is copypasta from BlueScreenView. Let me know if there's anything else I need to get you.



Mini011112-01.dmp 1/11/2012 8:52:10 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa80`0969c000 00000000`00000002 00000000`00000000 fffffa60`00e601f2 dump_msahci.sys dump_msahci.sys+56b1000 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini011112-01.dmp 2 15 6002 270,752
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello Crownflame.... Welcome to
GeeksToGo, :thumbsup:
:ph34r: :yes:

I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
  • Please understand we are all volunteers and we are not here all the time.
  • Sometimes it may be a extended amount of time to get back to you. If it has been
    more then 3 days please shoot me a PM and I will try to get back to you quickly
    then.
  • Please do the following and supply the requested information as needed. If you
    don't understand my instructions please ask and I will try to explain them
    clearer for you.
  • Do not attempt any steps unless instructed or ask before to
    make sure they will not cause any further issues.
  • If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.


Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?
  • If a name brand system then what brand, make and model is the system?
  • If custom built then what brand, make and model is the motherboard
  • Total memory installed
  • Total hard drive capacity and free space
  • What steps have you taken so far to resolve the issue

Below is a explanation of the bug check code you posted.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.



First step is to check the memory for any issue.

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#3
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
Thanks so much for the response!

Just so that you don't think I was completely ignoring you, I'll give you an update here:

I actually put off running the memtest for a while, since I didn't happen to have any blank media on me to burn the program onto. I have not had any issues with bluescreen since that error, though. If it starts up again, I'll be sure to try the memtest, but seeing as the computer's now gone a week without any issue, I think I'll wait for now (and acquire some blank media just in case. XD)

Seems odd that it would mysteriously go from an error every few hours or so to no errors at all, since I don't really recall doing any action on this side of the system restore I ran that would fix it. But hey, it's working for now.

Thanks so much for your help-- I'll be sure to be back with an update if I have further issues.
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I suggest running the memtest just to check the system.
  • 0

#5
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
All right, I had two BSOD crashes within about an hour of each other last night (it was the first time I'd turned on the computer for a week- I just went on a trip)

Op, and I just had another one while compiling this post, so clearly it's deciding to be an issue again. XD

Mini013112-02.dmp 1/31/2012 12:45:50 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa80`08eb4000 00000000`00000002 00000000`00000000 fffffa60`00e581f2 tcpip.sys tcpip.sys+521f2 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini013112-02.dmp 2 15 6002 273,120

Mini013112-01.dmp 1/31/2012 12:20:15 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa80`09a5e000 00000000`00000002 00000000`00000000 fffffa60`00e601f2 tcpip.sys tcpip.sys+521f2 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini013112-01.dmp 2 15 6002 273,120

Mini013112-03.dmp 1/31/2012 11:57:39 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa80`09274000 00000000`00000002 00000000`00000000 fffffa60`00e5d1f2 tcpip.sys tcpip.sys+521f2 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini013112-03.dmp 2 15 6002 273,120

Here's computer info:
computerinfo.jpg

I'll be acquiring media and performing the memtest in a few hours here, once I get out of my next class and have time to do so.
  • 0

#6
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
I just ran the memtest, and it came up with 0 errors.

I've since had this BSOD as well:

Mini013112-04.dmp 1/31/2012 2:06:46 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa80`0923c000 00000000`00000002 00000000`00000000 fffffa60`00e591f2 tcpip.sys tcpip.sys+521f2 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini013112-04.dmp 2 15 6002 273,120


These recent ones all seem to be originating the same place.
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.
  • 0

#8
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
All right, ran it four or five times, and it's still getting hung up on something. Here's the section of the report with the issue:

2012-02-01 14:56:50, Info CSI 000002fc [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-02-01 14:56:51, Info CSI 000002fe [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-02-01 14:56:51, Info CSI 000002ff [SR] This component was referenced by [l:164{82}]"Package_30_for_KB936330~31bf3856ad364e35~amd64~~6.0.1.18000.936330-185_neutral_GDR"
2012-02-01 14:56:51, Info CSI 00000302 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2012-02-01 14:56:51, Info CSI 00000304 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\PolicyDefinitions"\[l:24{12}]"inetres.admx" from store
2012-02-01 14:56:51, Info CSI 00000307 [SR] Repairing corrupted file [ml:520{260},l:76{38}]"\??\C:\Windows\PolicyDefinitions\en-US"\[l:24{12}]"InetRes.adml" from store
2012-02-01 14:56:51, Info CSI 0000030a [SR] Repair complete
2012-02-01 14:56:51, Info CSI 0000030b [SR] Committing transaction
2012-02-01 14:56:51, Info CSI 0000030f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired


Is there a way I can manually fix this? I, unfortunately, don't have my original OS disk, so that could be problematic, unless downloads are available elsewhere.

The article also recommends system restore, which I could try. I'm just worried that it's going to be a recurring problem, since I system restored the last time I had BSOD, and though it's originating from a new file pretty consistently now, it's still undeniably BSOD.
  • 0

#9
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
We can try a system restore back a couple of days before the issue originally started. Then if it returns we need to look at a update as being the issue.
  • 0

#10
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
I ran a system restore, and not long after resumed getting BSOD even as I was testing for it.

Here are the screen dumps- they look a bit different:

Mini020112-01.dmp 2/1/2012 7:50:58 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa80`0983c000 00000000`00000002 00000000`00000000 fffffa60`00e5a1f2 dump_msahci.sys dump_msahci.sys+55a4000 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini020112-01.dmp 2 15 6002 273,120
Mini011112-01.dmp 1/11/2012 8:52:10 AM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 fffffa80`0969c000 00000000`00000002 00000000`00000000 fffffa60`00e601f2 dump_msahci.sys dump_msahci.sys+56b1000 x64 ntoskrnl.exe+5a490 C:\Windows\Minidump\Mini011112-01.dmp 2 15 6002 270,752

and here's what the log said:

2012-02-01 20:52:00, Info CSI 000002f6 [SR] Beginning Verify and Repair transaction
2012-02-01 20:52:02, Info CSI 000002f8 [SR] Verify complete
2012-02-01 20:52:02, Info CSI 000002f9 [SR] Repairing 3 components
2012-02-01 20:52:02, Info CSI 000002fa [SR] Beginning Verify and Repair transaction
2012-02-01 20:52:02, Info CSI 000002fc [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-02-01 20:52:02, Info CSI 000002fe [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-02-01 20:52:02, Info CSI 000002ff [SR] This component was referenced by [l:164{82}]"Package_30_for_KB936330~31bf3856ad364e35~amd64~~6.0.1.18000.936330-185_neutral_GDR"
2012-02-01 20:52:02, Info CSI 00000302 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2012-02-01 20:52:02, Info CSI 00000304 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\PolicyDefinitions"\[l:24{12}]"inetres.admx" from store
2012-02-01 20:52:02, Info CSI 00000307 [SR] Repairing corrupted file [ml:520{260},l:76{38}]"\??\C:\Windows\PolicyDefinitions\en-US"\[l:24{12}]"InetRes.adml" from store
2012-02-01 20:52:02, Info CSI 0000030a [SR] Repair complete
2012-02-01 20:52:02, Info CSI 0000030b [SR] Committing transaction
2012-02-01 20:52:02, Info CSI 0000030f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

What's the next step?
  • 0

Advertisements


#11
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#12
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
Ah! I was wondering how everyone made it all tidy like that.

These are the two BSODs since the restore (i.e., everything there):

==================================================
Dump File : Mini020112-01.dmp
Crash Time : 2/1/2012 7:50:58 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`0983c000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa60`00e5a1f2
Caused By Driver : dump_msahci.sys
Caused By Address : dump_msahci.sys+55a4000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini020112-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 273,120
==================================================

==================================================
Dump File : Mini011112-01.dmp
Crash Time : 1/11/2012 8:52:10 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`0969c000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa60`00e601f2
Caused By Driver : dump_msahci.sys
Caused By Address : dump_msahci.sys+56b1000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini011112-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 270,752
==================================================
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK that i the Microsoft AHCI driver. Please do the following so I can verify something.

Please Go to

1: START and the click on RUN
2: Type in devmgmt.msc
3: Click Enter


To do a screenshot please have click on your Print Screen on your keyboard. It is normally the key above your number pad between the F12 key and the Scroll Lock key
Now go to Start and then to All Programs
Scroll to Accessories and then click on Paint
In the Empty White Area click and hold the CTRL key and then click the V
Go to the File option at the top and click on Save as
Save as file type JPEG and save it to your Desktop


Attach it to your next reply
  • 0

#14
Crownflame

Crownflame

    Member

  • Topic Starter
  • Member
  • PipPip
  • 28 posts
There you are: screenshot.jpg
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK the last BSOD's point toward a Microsoft driver issue so I would like to see if we can resolve that issue. Please do the below instructions but don't upgrade anything till I can see the results page please. Get a screenshot of the results page for what drivers need upgrading and I will follow up what to get first.

Download DriverMax and have it scan your system. It will open their website with all the out of date drivers you can update. With the free version you can update only 2 drivers per day so if you have a lot of them it will take a few days to get everything updated. I have been using it for about 4 months now and like it better then any other utility out there for keeping my drivers up to date.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP