BSOD after starting a full scan with Avast! Free; Curious about possible cause?

Good afternoon everyone,

 I've been using Avast! free since August 2011 with no issues to speak of.  Yesterday evening I went to run a full scan, and within a few seconds I got the BSOD with the following message at the top of the screen:  "Driver_IROL_Not_Less_Or_Equal."  (The IROL could be IROC.  I wrote it down rather fast).

At the time I ran the scan, I had been offline for about an hour; No browsers were open.

The system did a minidump. I rebooted and performed the following actions:

  1. Ran CHKDSK /R command. NO hard drive errors or bad sectors found.
  2. Ran Avast! FULL scan. NO issues found & NO BSOD again either.
  3. Ran MBAM FULL scan. NO issues found.
  4. Ran FULL scan with SAS. NO issues found.

Updates for all programs including Avast Free are current.

I’m thinking this is probably just a fluke since I’ve not experienced any similar issues in the time I’ve been using Avast! Free, and the subsequent FULL scan I ran executed without incident.

My question: Any thoughts as to what might cause this type of BSOD to occur?

P.S. - I’m not familiar with how to examine a minidump file. System specs & installed security software are shown in my signature line.

Thank you for your time and any comments! :slight_smile:

Regards,

Well It would usually mean that an improper memory read of address had occored when doing the scan, but also another element to the stop error is CPU Resources that tend to trigger the Mis-Read of the address where the scan is doing it(due to too much CPU is Processing and can’t reach the offset), something that is to be concerned on those with Windows 2000 and Windows XP because of the version of NTOSKRNL, as well as CPUs under 1.5 GHz will have this issue too.

I appreciate your feedback, JeffChao284.