Solved BSOD happens randomly after no computer use for one month

[jbro212]

So I came back from a one month vacation trip, and my computer BSODs at random times. Sometimes when I'm using chrome, sometimes when I'm playing a game, sometimes when I'm using skype. Starting a download, taking a coffee break, and coming back to a BSOD is pretty typical. Finally decided that I need some help.

Attached files has a few BSODs that were caused by driver verifier. The most recent BSOD was caused by driver verifier for sure, the others I don't remember.

Also, I turned on the BSOD dump file option on after this problem got bad, so there isn't any before those.

 

[Arc]

Various different bugcheck codes are there which may indicate many a things (plus a good lot of craps and bloatwares and installed there) but first of all you need to test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

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

Let us know the result.

 

[Layback Bear]

This could also be causing a problem. Their is a very good chance the computer is infected.

From jbro212 System Specs.

Antivirus None
Browser Google Chrome

I will go back to watching.

 

[jbro212]

Currently running memtest, 2 passes no errors so far. Will update if any errors occur or after 8 passes. Also, what do I have that's bloatware? I don't know what's considered bloatware. And is chrome not a good browser anymore?

 

[jbro212]

Finished running memtest, 8 passes no errors.

 

[Arc]

I hope you used Memtest 86+, not any other program.

Now 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.

 

[jbro212]

Crashed, dump file attached.

 

[Arc]

BugCheck 19, {3, fffffa800c7a6490, fffffa800c7a6490, 7ffffa800c7a6490}

[COLOR=Red]*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys[/COLOR]
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1528 )

Followup: Pool_corruption
---------

Disable Driver Verifier now.

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.

Let us know the result.

 

[jbro212]

Uninstalled both Daemon Tools and SPTD, uninstall button was grayed out. Still got a blue screen after that. Attached the BSOD dump file that occurred after. Also computer freezes sometimes as well.

 

[Arc]

BugCheck 3B, {c0000005, fffff9600010f2fd, fffff8800746fa60, 0}

Probably caused by : win32k.sys ( win32k!StoreQMessageExtended+15 )

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

Another clueless Stop 0x3B.

Memtest86+ reported clean.

Make it sure that windows is up-to-date. And run driver verifier for one more time.

 

[jbro212]

Turns out my windows updates were outdated by one and a half years. Took awhile to update them all because I had a connection problem.

After finishing updates, ran driver verifier, and the computer was on for about 12 hours before it became unresponsive and I was forced to power down and reboot. Afterwards, the computer would BSOD shortly after logging into my account. Tried rebooting again, but forgot to turn on safe mode so same thing happened. Both BSODs had the message "a device driver attempting to corrupt the system has been caught." Both was caused by aswsp.sys, which is apparently an avast! file. It's kinda wierd because I didn't get the BSODs until after the second restart with driver verifier.

Anyways, I have attached the dump files.

 

[Layback Bear]

I wonder how you are getting a Avast problem when you specs show you have no Anti Virus program.

 

[jbro212]

I installed it after the BSODs because of your post.

 

[Arc]

Yes, it is Avast.

BugCheck C4, {e3, fffff88003e2854f, 2050010, 0}

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

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.

Let us know how it is running.

 

[jbro212]

Still getting blue screens. Going to run driver verifier again over night. Looked up some of the error messages from the BSODs, such as win32k.sys and dxgmms1.sys, and it seems to be driver related. Will post again once I have something new.

 

[jbro212]

BSODs during driver verifier, anyone help with dump files?

 

[Arc]

Disable driver verifier now. Let the computer run normally. Inform us for any further issue.

 

[jbro212]

Two more dump files from yesterday and today.

 

[Arc]

Can you disable indexing as a test?

Index - Enable or Disable
​

Let us know how it is running.
____________________________________________

BugCheck 34, {50853, fffff88009d78488, fffff88009d77ce0, fffff800032d1a16}

Probably caused by : ntkrnlmp.exe ( nt!IoSynchronousPageWrite+5a )

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

 

[jbro212]

Disabled indexing, still got BSOD. Attached dump file.