booted up to BSOD after computer logo

[townsbg]

There haven't been any further issues? Then I'd say wait it out and see if it happens again.

 

[axe0]

I changed my settings AFTER the BSOD... (including turning on exploit - which they said not to because it would CAUSE a crash but since I only turned it on for the first time ever AFTER the crash it's obviously not that). The suggestions they made were how I had it set since day 1 so all I did was put everything back to how it was in the first place. I also made no software changes so it can't be that.. so the only thing I can think of is hard drive is dying.. but all tests say it's OK but apparently that could be false by checking while using windows...

You're just proving the point, crashes stopped after reapplying the settings. It does not matter that they're the same, it's like reinstalling the same driver which overwrites any files and can solve crashes when a file got corrupted.

You don't need to look further into your hard drive, it's not dying or you would've already seen indications. I checked your event logs which in other situations have indication of hard drive problems, but none of them were with your logs. Any other test also came back negative on issues with your drive, there's no performance issues and your crash dumps were also consistent from what I saw leading me to say reapplying the Malwarebytes settings was sufficient. Doing more than that and continuing to focus on your drive would be a waste of time, and money if you intend on replacing it

 

[meesh]

It was just odd because it happened over and over for no reason during two days.. I haven't had issues (but I think that was before I reactivated Malwarebytes).. On Malwarebytes they initially said my logs didn't show any issue with the program so I went back to thinking it was the hard drive.. Either way, thank you so much for all the help - I really appreciate it.. hopefully it won't happen again.

 

[axe0]

They mentioned they looked at the stack, I typically look into the raw stack which showed traces of autochk.exe, a Windows file used for scheduling a chkdsk at boot in case you want to do a chkdsk on your Windows partition. Only in the raw stack I saw traces of a Malwarebytes driver, that however only indicates Malwarebytes was involved in the process. From what it looks like in the raw stack, cleanup was happening (roughly put) and since settings were changed in Malwarebytes there was a conflict with Malwarebytes during the process.