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).
Im pretty sure i did it correctly and I did it after the time of the all the minidumps.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
*** 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
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.
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).
Im pretty sure i did it correctly and I did it after the time of the all the minidumps.
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.
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
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).
Hope this helps.
Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
did i post that link right?