BSOD happens randomly after no computer use for one month

jbro212 · 30 Aug 2014

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 · 30 Aug 2014

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

jbro212 · 30 Aug 2014

I installed it after the BSODs because of your post.

Arc · 31 Aug 2014

Yes, it is Avast.

Code:

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
Probably caused by : aswSP.sys ( 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 · 01 Sep 2014

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 · 03 Sep 2014

BSODs during driver verifier, anyone help with dump files?

Arc · 03 Sep 2014

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

jbro212 · 04 Sep 2014

Two more dump files from yesterday and today.

Arc · 04 Sep 2014

Can you disable indexing as a test?

Index - Enable or Disable

Let us know how it is running.
____________________________________________

Code:

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

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

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

jbro212 · 05 Sep 2014

Disabled indexing, still got BSOD. Attached dump file.