Jump to content

CommonCurt

Members
  • Content Count

    26
  • Joined

  • Last visited

About CommonCurt

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey, Not sure if you saw my last post above due to the holidays, but I managed to find the first BSOD (when all this started), and it looks like the very first one might say something a little different.
  2. I haven't tried doing a clean boot on either system because of how long it takes for the BSODs to show up (this system around 5 days, and on the other system 7-10 days). It never happens right after a restart. After I try uninstalling somethings if that doesn't flush out what's causing it I might consider trying clean boot, but it would take a long time with how long in between the BSODs are. I also will look into the other forum that you mentioned. Then, as a last resort, I might go back and start installing the Monthly roll up Updates starting with the Month when my problem started. Just for the sake of it I attached the first two BSODs I received on this system when all of this started. Maybe one of them can give some information that we haven't gotten from the current ones. 071317-7956-01.zip 071317-8782-01.zip
  3. Yeah, when I get some time in the next day or two I will uninstall it and see what happens.
  4. Hi, this is the second system (my main Desktop PC) with what seems to be an identical issue, at least from what I can gather from "Who Crashed". It has Malwarebytes 3.2.2.2018 and Microsoft Security Essentials running at the same time, and I've attempted to add the exclusions after I started getting the BSOD's. It seems to have started around the time that I upgraded to Malwarebytes 3.0, but I was never really sure because it was around that time that I did a Security Only windows update. Who Crashed is telling me it's the IRST driver iastora.sys (iaStorA+0x877B8). I have upgraded to all the available IRST drivers for my chipset, and still the BSOD's continued. So I eventually went back to the original IRST drivers that had been fine for years. I have the most current MoBo BIOS installed. SFC scans come up clean. Every few days I get some Event ID 2001 "Microsoft Antimalware has encountered an error trying to update signatures". The system restarts randomly every few days. It almost always happens in the morning between 7:00am - 8:00am, which is around when Malwarebytes is doing it's automatic scan. Please, any help will be much appreciated. I built, and have maintained this systems since the end of 2013 with no BOSD's or issues whatsoever. until this past July. perfmon report Main Desktop PC.zip SysnativeFileCollectionApp.zip
  5. Hi, I've been getting BSOD's on two of my Win7 machines since about July. It seems to have started around the time that I upgraded to Malwarebytes 3.0, but I was never really sure because it was around that time that I did a Security Only windows update. Both systems of mine that are getting these sporadic BSOD's have Malwarebytes 3.+ and Microsoft Security Essentials. The BSOD's almost always happen around 7:30am - 8:00am. Which is the same time Malwarbytes does it's daily scan. The only thing I have been able to find out through "Who Crashed" is that it's a driver that is triggering the BSOD's (probably the IRST driver). "Who Crashed" says this is the case for both of my systems. I have tried every IRST update available, and still after a few days I wake up to one of my systems having been restarted because of a BSOD. I finally just went back to IRST version I had originally. Also, I have the most current BIOS available on both systems. Lastly, every few days (on both systems) I get some Event ID 2001 "Microsoft Antimalware has encountered an error trying to update signatures". Oh, and I already tried adding exclusions in both Malwarebytes & MSE. I will make this thread about the first one which is my HTPC then open another thread for my other main Desktop. I didn't want to mention both systems in the same thread at first, but the problems/symptoms are exactly the same for both, and the BSOD's started happening at the same time. Any help will be much appreciated. Thanks perfmon report HTPC.zip SysnativeFileCollectionApp.zip
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.