Variety of BSODs - Log/Event Files included RAM TESTED

Theres quite a mix of stuff going on, which make it difficult to diagnose the problem.

Start with this:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {22, 0, 0, 0}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by : aswSnx.sys ( aswSnx+61104 )

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

Replace Avast with MSE, to test the BSOD.

Run the DOS version of the SHORT and LONG test of SeaTools:
SeaTools for DOS and Windows - How to Use

Put a jpeg image on your desktop, it will not show the .jpg extension name. Put a MS word file there, it will not show the .doc or .docx extension names there. It is the same for .img. Extension name will not be visible.

Bu for .ima, it will be visible.

WHY? The reason is there, in your folder options.

Attachment 346352

.ima is not considered as a known file type. So the extension name was visible there.

Removing .ima and adding .img as the extension, Seatools.ima will look as "seatools" only. Look at my desktop ....

Attachment 346353

Which means, you have added the extension name twice. So discimager failed to recognize it.

Do just as said. Everything will work perfectly.

Edit: See the screenshot of Option Two, Step 4 .... the extension name is not visible there, too.

timPM said:

...anything else in the dump files having to do with drivers etc that I can delete/fix?

If you have uninstalled Avast already, then apparently you have nothing more to do right now but wait and see how it goes.

Let us know for any further issue. Also let us know the result of the long generic test as Golden suggested.

Thats not a good sign. Back up any user data from that disk immediately, then look to replace it.

Yes, a failing HDD can always cause BSODs.