Random BSOD in Windows 7. Windbg: Probably cause NETIO.SYS

Hi digualada.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

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 then restart.

Avast is failing here, contributing to your BSODs.

Code:

fffff880`090bc2d8  fffff880`0699b5ceUnable to load image \??\C:\Windows\system32\drivers\aswStm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswStm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
 aswStm+0x55ce

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; for a safety reason.

And Fortinet FortiCliant.

Code:

BugCheck D1, {8, 2, 0, fffff88001658a1d}

*** WARNING: Unable to verify timestamp for FortiWF2.sys
*** ERROR: Module load completed but symbols could not be loaded for FortiWF2.sys
Probably caused by : NETIO.SYS ( NETIO!CalloutStreamDataInit+1d )

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

I would suggest to uninstall it, at least as a test.

Let us know the results.