three BSOD's with different error codes

marcelvertenten · 18 Mar 2014

Hi all,

Had three BSOD's the last week.

The first two happend on the same day and seemed to be related to harddisk drivers. I have recently installed a Seagate Central NAS, and Seagate Dashboard, the software for that, was upgraded a few days before the first BSOD.

I have not ran the software after the two BSOD and seemsed fine till today when a third one happened, which seems to be related to avast antivirus. I have updated avast, i was apparently running an old version.

I'm not sure if the three are related? Maybe there is another reason why these happened? Any ideas? tips? My logfiles are in attachement.

regards,
mv

Arc · 18 Mar 2014

Code:

BugCheck 1000008E, {c0000005, 84894415, 9e677bf4, 0}

*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswSP.SYS ( aswSP+20526 )

Followup: MachineOwner
---------

Code:

BugCheck D1, {ffffffe3, 2, 0, 8ce5d1e4}

Unable to load image \SystemRoot\system32\DRIVERS\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
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
Probably caused by : iaStor.sys ( iaStor+3d1e4 )

Followup: MachineOwner
---------

Code:

BugCheck D1, {4, 2, 1, 8ce57362}

Unable to load image \SystemRoot\system32\DRIVERS\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
Probably caused by : iaStor.sys ( iaStor+3d362 )

Followup: MachineOwner
---------

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one.

HP Mobile Data Protection is also a bad stuff. I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

But about Intel Rapid Storage, We cannot suggest the suitable steps without seeing the required data that is not included in the zip. Upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

marcelvertenten · 18 Mar 2014

Thanks Arc! I will try the suggestions. In meantime i have attached the MSINFO32.

Arc · 19 Mar 2014

IRST is uses as the AHCI controller here. Good for you.
Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

Right click on "my computer" icon and click "manage" on the context menu.
It will open the "computer management" window.
Select "Device Manager" in the left pane, It will list all the existing devices up.
Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
Select one Intel device item under it, right click, uninstall.
Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Also uninstall MagicISO, as the SCSI adapter installed by it may cause all those storage related issues by itself.