Blue Screen error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Anonymous
2011-02-19T04:59:53+00:00

original title: Another sad story of the dreaded BSOD... error: DRIVER_IRQL_NOT_LESS_OR_EQUAL ... Please advise as to best approach to remedy problem~

I guess it would be almost two weeks ago now that my wifes laptop first had the error (tech info line is as follows):

iaStor.sys - Address FFFFF8800110BF2B base at FFFFF880010C1000, DateStamp 4a287aa4.

The Laptop is a year old and has had no problems previously. I dont know all the specs but its an ASUS with an Intel Centrino and running Windows 7 OS.

Here's what I have done so far:

  1. I tried to boot system in all SAFE modes ... no joy... same error~
  2. I booted system with recovery CD and tried to to perform a restore from previous resore points (tried 3 previous dates so far) ... no joy ... same error~
  3. (after reading previous posts of others with simular problems) I booted system with recovery/driver cd and renamed existing iaStor.sys to iaStor1.sys and, then copied iaStor.sys file from recovery/driver cd ... no joy... same error~
  4. Submitting to my level of ignorance, I told my wife to take it Best Buy and have the Geek Squad Fix it... Knowing that she had purchased the extended warranty(costing $220), I thought it would certainly be covered! She reports them saying its not a harware problem, its a driver problem and it will cost $140 for them to fix it! She went on to tell me if we didnt have the warranty, the Geeks would chage $240, so we should feel better about that! lmao!!! we cant afford either ammount!  Well the Geek in question may well be very computer savy but he is and idiot in securing company software as he left his diagnostic disk in my laptop. Lucky for him, I am an honest man and I wont go and sell Geek Squad software on the black market!

*** Not wanting to loose any personal files existing, I have not completely reinstalled Windows 7... and I am really wanting to avoid that process (mostly, because figuring out how to copy everything without spending $$$ on an external is still baffling me!)  I hope that you'all can walk me through the fix on this because I cant afford any other process to getting our laptop back on-line~

Thx in advance for your help,

Ra

USN ret

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

42 answers

Sort by: Newest
  1. Anonymous
    2011-02-22T06:02:17+00:00

    Here's the link for directions:

    http://downloadmirror.intel.com/17882/eng/readme.txt

    I found this link just below the specific download for my OS (link below).

    http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3154&DwnldID=17882&keyword=%22matrix+storage+manager%22&lang=eng

    Im pretty sure i did it correctly and I did it after the time of the all the minidumps.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-02-22T04:17:29+00:00

    Hi,

    The issue damaged the MBR and that had to be rebuilt, not unexpected since the iastor.sys

    is a hard disk driver.

    No the same driver was in all the minidumps starting from that early one so it has not been updated.

    You might have installed the same one again which was reasonable if there were no updated ones

    available (no need now to re-install the same one).

    You need to get the methods to install that driver from ASUStek and/or Intel - there is information

    available at their sites and from their tech support. You need to know the procedure from them so

    I will not guess though it probably is very simple, most are these days. Any time you are installing

    BIOS or a low level driver (such as iastor.sys) a certain amount of care needs to be taken.

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-02-22T04:11:08+00:00

    roger ~ roger

    put a reminder on my desktop to do that weekend after next!  :-)

    As for the WiFi driver... if I remember correctly, I installed an updated driver just after that (when I installed a new Wifi router at home)... but, Ill check it with all the others~


    Im still a lil confused how doing a Complete Rebuild (...and nothing short of doing the Complete rebuild as posted above would work!) on the BCD fixed the iaStor.sys (I didnt run/install the the new IMSM program (installing a clean iaStor.sys driver) til' after I got the system up and running!

    anyway...Thx Rob~

    Ra

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-02-22T01:15:30+00:00

    Hi,

    Yes its a good link.

    Results verifies by WinDBG, DumpCHK, and BlueScreenView.

    If you run BlueScreenView it will show the CAUSE of all the Feb. BSOD's was iastor.sys. Confirmed

    by DumpCHK and WinDBG.

    WinDBG for a couple : (all were checked)

    BugCheck D1, {0, 2, 1, fffff8800112b6ff}

    Probably caused by : iaStor.sys ( iaStor+4a6ff )

    FAILURE_BUCKET_ID:  X64_0xD1_iaStor+4a6ff

    BugCheck 1E, {0, 0, 0, 0}

    Probably caused by : iaStor.sys ( iaStor+5288c )

    FAILURE_BUCKET_ID:  X64_0x1E_0_iaStor+5288c

    ================================

    The minidump back on 6/26/2010 was 0x000000C2 CAUSE ndis.sys which is a Windows component

    which means something else drove it into Fault. The root cause was NETw1v64.sys 7/20/2009 so

    look for updated to it - the Intel Wireless Driver (WiFi) - check with ASUStek if on-board and with

    the actual device maker if a separate device and of course Intel Downloads.

    Even though it was a long time ago I would update that driver.

    BugCheck C2, {7, 1097, 406000c, fffffa8004116530}

    Probably caused by : NETw1v64.sys ( NETw1v64+59e9 )

    FAILURE_BUCKET_ID:  X64_0xc2_7__U33_NETw1v64+59e9


    Wait a week or so to be sure the smoke has cleared then I would update the BIOS, low level chipset

    drivers, and other on-board device drivers you can. Then look for updates to the major device drivers

    for separate devices. See the troubleshooter link for information on how to manually update drivers.

    For BlueScreen troubleshooting methods using BlueScreenView and MyEventViewer see my replies

    if this thread - top 3 answers (+1 other).

    http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2011-02-22T00:36:13+00:00

    did i post that link right?

    Was this answer helpful?

    0 comments No comments