Random BSODs in new Windows installation

[cmdr001]

Hello,

A pair of months back I got myself a Samsung EVO 840 SSD and given how my previous Windows 7 installation had been on for quite a while so I decided it might be a good time to do a fresh install rather than migrating, however a little while after reinstalling now and then the system has a BSoD. The only hardware changes I made was switching the graphics card even though it was for an equal model and adding the SSD. Driver wise only the graphics card might have gotten an update, and I did not install Intel RST.

The BSoDs happen somewhat at random, ocasionally being within a few minutes, but other times it can stay days without crashing.

Files requested are attached.

Thank you in advance, if there's something wrong let me know.

 

[Arc]

Hi cmdr001.

From your event logs:

Event[12499]:
Log Name: System
Source: Service Control Manager
Date: 2013-12-18T10:26:57.920
Event ID: 7026
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Mazinger
Description:
The following boot-start or system-start driver(s) failed to load:
AsIO
AsUpIO
aswRvrt
aswSnx
aswSP
aswTdi
aswVmm
discache
spldr
Wanarpv6

ASUS hardware monitoring, and Avast.

From the crash dump, it is Avast, too:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {a6e1c000, 0, 831fc84a, 0}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
[COLOR=Red]Probably caused by : aswSnx.sys[/COLOR] ( aswSnx+253b1 )

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.

Also uninstall ASUS hardware monitoring software like ASUS ShellProcess and if anything else is there. Uninstall CCC, too.

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.

 

[cmdr001]

Hello again.

Thanks for the reply before anything else.

I did most as suggested, uninstalled Asus stuff, Avast, Daemon Tools (SPTD removed), and a few items from the start up leaving only the things I'd run manually anyway.

Still, problem manifested a while later about in the same manner, so I'm submitting a new collection of files in hope that you can tell me if anything else now seems the culprit of it.

Thank you.

 

[Arc]

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP [/COLOR](4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16399.x86fre.win7_gdr.090722-1835

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest86+ reports no error, 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.
____________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {b4c26000, 0, 831f484a, 0}

Probably caused by : memory_corruption ( nt!MiCompressRelocations+3d )

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

 

[cmdr001]

Had done the memory test previously since I imagined that could too be cause of the issue, but Memtest returned no error.

Upon activating the Driver Verifier however (both before and after SP1 now) I get a BSOD at boot time "irql_not_less_or_equal", code 0x0000000a, but didn't show any other useful information. If this means anything or is there any other information that I can take from this bit please let me know.

Otherwise booted the machine, now with SP1, and waiting to see if there is a new blue screen.

 

[Arc]

If you get BSOD with DV enabled before getting the desktop, disable DV in safe mode. Then first 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.

Then enable DV again. Make it sure that you are not selecting any driver provided by "microsoft", "macrovision" and "brother" in the list.



Hopefully this time you will get to the desktop before it BSODs, and we will get the required crash dump.

 

[cmdr001]

Proceeded as instructed; disabled everything from the Startup tab, set DV according to instructions and not selecting Microsoft, Macrovision or Brother drivers, but end result is still a BSoD on boot up. I did tried to reboot a trio of times and I got once the 0x0000000a error and 0x000000c9 twice. Neither of them had any additional description or file name if such was expected.

 

[Arc]

Let us have a quick look? Run the SF diag tool and upload the output?

 

[cmdr001]

Here's the new SF files collection.

 

[Arc]

Here's the new SF files collection.

now with SP1, and waiting to see if there is a new blue screen.

There is only one crash dump of today, a stop 0x50; with SP1 not installed, and such a crash is somehow expected with non-SP1 systems.

After you installed SP1, we should wait and see how it goes.