Code:
BugCheck 101, {31, 0, fffff880031d5180, 3}
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Code:
Usual causes: Device driver, BIOS bug, hardware defect
Since you experiencing a Stop 0x101, to thoroughly analyze the BSOD, you will need to configure a Kernel Memory dump and then upload the file in a zipped folder to a file sharing service such as Skydrive or Dropbox. Make sure you upload the file to the Public folder of your account and then post the URL in your next post.
Code:
0: kd> lmvm aswSnx
start end module name
fffff880`01aed000 fffff880`01bed000 aswSnx T (no symbols)
Loaded symbol image file: aswSnx.SYS
Image path: \SystemRoot\System32\Drivers\aswSnx.SYS
Image name: aswSnx.SYS
Timestamp: Thu Jun 27 16:37:25 2013 (51CC5C35)
CheckSum: 0010585C
ImageSize: 00100000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
avast! seems to be causing problems, please remove the program completely with the avast! Removal Tool, and then install and run full scans with these free and proven alternatives which work best with the operating system due to their compatibility and lightweight nature on system resources.
Install and perform full scans with:
Information
Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system
You can also view this thread for a complete free and lightweight security protection combination:
Remove:
Code:
Start Menu\Programs\DAEMON Tools Lite
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.
Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.
Remove:
Code:
Start Menu\Programs\IObit Malware Fighter
IOBit is another known cause for BSODs, and running two real time protection programs can cause serious problems and crashes with your system.
Remove:
Code:
Start Menu\Programs\Advanced SystemCare 6
Windows 7 doesn't require any programs which make changes to the operating system and registry, these programs tend to cause problems by modifying and deleting files.
Windows is a closed source system. Developers of registry cleaners do not have the core code of Windows 7 and are not working on definitive information, but rather they are going on past knowledge and experience. Automatic cleaners will usually have to do some guesswork.
Modifying registry keys incorrectly can cause Windows instability, or make Windows unbootable. No registry cleaner is completely safe and the potential is ever present to cause more problems than they claim to fix.
Registry cleaners cannot distinguish between good and bad. If you run a registry cleaner, it will delete all those keys which are obsolete and sitting idle; but in reality, those keys may well be needed by some programs or windows at a later time.
Windows 7 is much more efficient at managing the registry than previous Windows versions. If you run any other registry cleaner and do not know precisely what you are doing, you will have problems down the road. There are no gains to be had from using a registry cleaner and the risk is great.
Quote