BSOD 0x0000000A

Hi leumas0097.

Code:

fffff880`106192b8  fffff880`0743023fUnable to load image \??\C:\Windows\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0x723f

Description here: Driver Reference Table - aswSnx.SYS

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.

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.

Let us know the results.

leumas0097 said:

Browsing the web, this error pops up. MEMORY_MANAGEMENT, I think it also said. I also have random programs crashing at seemingly random intervals,the most common culprit being a program I use for monitoring my CPU temp, RAM usage, and CPU clock (PCMeter V0.2), though other programs have as well. I've read this can mean I either have a bad slot or bad memory, but I want to make sure. Any thoughts?

Quoted from new topic I made without properly reading rules. Uninstalled daemon, didn't touch Avast because I've had it running for two years without this sort of issue. Did uninstall and reinstall it, though. Updated files including 4/12 0x0000001A BSOD added.

[EDIT] Ran Memtest86, one stick of RAM immediately gets errors, other does not. So, definately seems that bad RAM is the cause.

leumas0097 said:

didn't touch Avast because I've had it running for two years without this sort of issue.

Two or twenty, does not matter.

leumas0097 said:

[EDIT] Ran Memtest86, one stick of RAM immediately gets errors, other does not. So, definately seems that bad RAM is the cause.

Change the RAM in that case.

And, dont create more threads on the same issue, specially ignoring the previous ones.