Random BSOD running various applications

Hello Dv8tor.

It is caused by Intel Storage drivers.

Code:

fffff880`09d3d848  fffff880`012885bfUnable to load image iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
 iaStor+0x2e5bf

Which is old enough.

Code:

1: kd> lmvm iastor
start             end                 module name
fffff880`0125a000 fffff880`01464000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Tue Jun 08 23:03:03 2010 (4C0E7ECF)
    CheckSum:         00090F4D
    ImageSize:        0020A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download and install it from http://downloadcenter.intel.com/Deta...ST%29&lang=eng.

From another crash dump,

Code:

BugCheck D1, {ea3b030, 2, 0, fffff88004545e8c}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Download intel graphics driver from Intel Download Center. Also test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Atheros network adapter driver is also in fault.

Code:

fffff880`09ffa938  fffff880`0947cf6cUnable to load image athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 athrx+0x3df6c

Update it from ATHEROS drivers for Microsoft Windows (Atheros?????)

Free up the startup. You have a lot of startup entries.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Let us know the results.

Dv8tor said:

May I also ask, is it common to encounter such BSODs for laptops if certain drivers are not updated regularly?

Yes, it is very common; better we can say it is the most common cause of a BSOD; for both of a desktop and a laptop..

Dv8tor said:

If so, is there any way to be notified when it's time to update or some way of automatically updating these drivers? It seems rather strange to me that the only way to know that I have to update drivers is to get BSODs.

Apparently there is no way. What you should do is to update all your installed programs and all the device drivers at a regular interval. There are some auto driver search programs, but I am not very sure how efficiently they work.

Dv8tor said:

Hello Arc,

Thank you for the helpful tips!

Since my last post I've ran memtest and nothing was reported, so I assumed everything is fine. This morning I was working on my laptop when it BSOD again. The funny thing is that there was no crash dump file written (I used bluescreenview to check first). However I did manage to see that it was caused by igdkmd64.sys. Some research indicated that it is due to the Intel Graphics Driver, but I am sure that I've already got the latest version.

How do I go about troubleshooting this? I will appreciate your help greatly. If you need certain files/logs please let me know and I will upload them.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.