Repeated BSOD 0x08E

[Jake1211]

I have this emachines T3958 desktop that had multiple viruses on it, and a reoccurring 0x08e BSOD. I used avast to remove all viruses and ccleaner to fix registry errors, but only in safe mode. It boots into safe mode but when it does a normal boot it seems ok at first but after a couple minutes (sometimes right away) the BSOD occurs and reboots the system in a constant loop. It points to a file named aswndis2.sys

I ran startup repair, tried to do sys restore but no points were set, replacing ram, putting hdd into another system, and windows recovery disk.

I copied the events from event viewer and ran DM Log collector as instructed.

Here are the logs from event viewer:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0x80000003, 0x87b0db03, 0x80d8ad7c, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 031116-66703-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0x80000003, 0x87af6b03, 0x80d8ad7c, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030916-66203-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0x80000003, 0x87af1b03, 0x80d8ad7c, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030916-65968-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0x80000003, 0x87aedb03, 0x80d8ad7c, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030916-66640-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0x80000003, 0x87f04b03, 0x8758ad7c, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030916-66062-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0x80000003, 0x87ae8b03, 0x80d8ad7c, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030916-65140-01.

DM Logs are attached



Thanks in advance

 

[BorisTheAnimal]

Hello Jake.

I've taken a quick peak at your zip and noticed that it seems the DM-log collector didn't run 100%, many files are missing.

Do you remember if there was any error message or something out of the ordinary when you ran it? Did you remember to select run as administrator?

Cheers, Boris

 

[axe0]

Please uninstall Avast and use Microsoft Security Essentials as alternative.
Also go to %systemroot%\minidump and delete all files that are not from 2016.
http://www.sevenforums.com/tutorials/343783-avast-uninstall-completely.html

kd> k
 # ChildEBP RetAddr  
WARNING: Stack unwind information not available. Following frames may be wrong.
00 80d8ae08 82868587 [COLOR="Red"]aswNdis2[/COLOR]+0x4b04
01 80d8ae4c 8286852b nt!KiProcessTimerDpcTable+0x50
02 80d8af38 828683e8 nt!KiProcessExpiredTimerList+0x101
03 80d8afac 8286679e nt!KiTimerExpiration+0x25c
04 80d8aff4 82865f6c nt!KiRetireDpcList+0xcb
05 80d8aff8 98aeae48 nt!KiDispatchInterrupt+0x2c
06 82865f6c 00000000 0x98aeae48

If any new crash occurs, run the DM Log Collector again and upload the new zip in your next reply :_

 

[Jake1211]

Boris, it didn't say anything about it not finishing the tests and everything seemed fine. Ran as Admin

Axe, I'll try your suggestions and will let you know how it turns out.

 

[Jake1211]

So, I can't install MSE because I have to be out of safe mode. Running on Safe Mode is the only way that I can do anything with the system. Booting Normally would cause the BSODs to happen again. Should I try to install MSE before it crashes or is that not a good idea, probably isnt. The computer isn't online so unless I have to use MSE for this I should be fine. Uninstalled Avast with Removal tool and ran cleanup.

 

[axe0]

Does the crash occur at startup or some time after startup?

 

[Jake1211]

Either. Sometimes 10 minutes after, sometimes 10 seconds

 

[BorisTheAnimal]

So I take it that you can't get to Safe Mode with Networking?

 

[Jake1211]

No I can, thats actually what i boot into

 

[Jake1211]

I got it to boot up normally and installed MSE. I reran the logger and it doesn't look like it added any more files than before. I did remove all old dmp files except the ones from 2016. When it finished it just told me the file was on my desktop, no errors. I'll attach it anyway. I am currently out of the house so I don't know if the system crashed yet or not.

 

[BorisTheAnimal]

The BSOD that happened on the 16th was caused by aswNdis2.sys which is a type of SYS file associated with avast!

 

[axe0]

Diagnostics Test

 Clean boot

Please try the following:

• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Go to the tab startup
  • Disable everything
• Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist.

If no problem occurs when everything is enabled, try driver verifier

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[Jake1211]

Axe0 I will run the tests when I am home.