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.