Avast internet security causing BSOD

Avast Free Antivirus / Premium Security
1

Hi,

For the last month or so I have been getting a BSOD whenever I boot up my pc. As long as I leave the pc on it doesn’t happen
again and I’ve been trying to narrow down the cause for the last few weeks by uninstalling/installing all possible drivers and bootup
programs. The BSOD message is IRQL_GT_ZERO_AT_SYSTEM_SERVICE

Today I tried to do both a smart scan and a full scan and got instantly this exact same BSOD and I finally think I have found the cause :
Avast. Tried full scan 4 times and got this every single time right as I click it. I uninstalled and used the Avast remover program in
safe mode and then reinstalled Avast but it didn’t change anything, same BSOD everytime I use a Full scan.

I have the paid version of Avast internet security (licence paid until October 2015).

Anyone have a fix for this problem?

2

Don’t know if there is any correlation or not, but I too was getting the BSOD on every other boot. Weird, because it only happens on every other boot. The error code always refers to “iastor.sys”. This is a Dell XP Pro machine. Anyway, after pulling out what’s left of my hair, defragging, running SFC and blowing away a lot of stuff I don’t use any longer, I finally removed Avast. Guess what…no more BSOD. And way faster on boot up. At least I didn’t pay for it like you, but I am now using Norton Online Security and it seems to be working great.

3

See if this is of any help to you:
http://www.solvusoft.com/en/errors/blue-screen-errors/microsoft-corporation/windows-operating-system/bug-check-0x4a-irql-gt-zero-at-system-service/

4

Hi Bob.

He decided to uninstall Avast.
https://forum.avast.com/index.php?topic=166187.0

5

Someone else who doesn’t have the patience to get ot the bottom of hi/her problem and
simply takes the easy way out. The problem hasn’t been solved and will show up again only more masked than before.

6

Well… I just wanted to see if the iastor error was caused by the rootkit scan like in my case with the RAID driver and XP, but like you said people don´t have patience to try an solve issues.

7

The majority of people of the Avast user base are not going to debug items.
You guys here are the 1%-ers…the 99%-ers don’t have the desire or knowledge to do this…it should not be a surprise.
If another AV does the job they are going to move to it.
Although perhaps not for this thread’s possible issue, IMHO Avast releases product from BETA to release WAY too early.
Obviously, this is the pressure from their marketing team to roll things out…with the excuse it is better for you.
Ultimately it is…just think Avast rolls out “beta” code and waits to see impact on its user base.

The other issue I see is Avast’s release notes rarely cover even a fraction of the things fixed or known bugs.

8

Sorry but at this stage in the users correspondence, it hasn’t been determined what caused the BSOD.
It could just as well have been an outdated driver or the use of a registry cleaner gone sour or a number
of many other things.
Blaming Avast without actual proof is totally out of line.

9

Agreed…that’s why I had stated the Although perhaps not for this thread’s possible issue preface.
My comment was about the expectation the 99%-ers are going to debug issues when another A/V works.

10

I have this problem, too. BSOD occures every time in 5-10 minutes after boot (or resuming from hibernation). Every single time, it happens once after boot, then it works without any problem hours, at least.

I have tried anything possible; upgrading/downgrading drivers (GPU, NIC, etc), swapping and testing memory and HD, etc. Nothing seems to help. I really wouldn’t like to uninstall avast, but I see no other option if I can’t find solution for the problem :frowning:

This all started on January 16. I think, there was some Microsoft updates happening the day before, maybe it’s somehow related. If I recall correctly, I have seen some user reporting the similar problem with another AV software since then.

However, here is a crash analyze, based on the dump file:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff80003052000 PsLoadedModuleList = 0xfffff80003295890
Debug session time: Mon Jan 26 05:27:45.337 2015 (UTC - 5:00)
System Uptime: 0 days 0:08:21.242

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 0000000075492e09, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88007a30ca0, 0

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

PROCESS_NAME: AvastSvc.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

FAULTING_IP:
+0
00000000`75492e09 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800030c8429 to fffff800030c8e80

STACK_TEXT:
fffff88007a30a68 fffff800030c8429 : 000000000000004a 0000000075492e09 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff88007a30a70 fffff800030c8360 : ffffffff00000004 c720000129605867 fffffa8000000000 0000098000000000 : nt!KiBugCheckDispatch+0x69
fffff88007a30bb0 0000000075492e09 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x245
000000000eb5f098 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x75492e09

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`030c8360 4883ec50 sub rsp,50h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExit+245

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 548a6e28

FAILURE_BUCKET_ID: X64_RAISED_IRQL_FAULT_AvastSvc.exe_nt!KiSystemServiceExit+245

BUCKET_ID: X64_RAISED_IRQL_FAULT_AvastSvc.exe_nt!KiSystemServiceExit+245

11

And more information… Tried uninstalling/reinstalling Avast and twiddled every possible setting.

So, BSOD occurs about 8-9 minutes after the boot AND almost immediately when starting scan (quick scan, smart scan, etc.)
Today I installed the newest Beta version, but the same problem again.

I have used avast for year without any problem, but the last month has been painful. So, I’ll uninstall Avast now, but would be glad to try again if someone suggested fix for this issue.

12

Could you try the support utility here https://forum.avast.com/index.php?topic=166443.0

13

Hi,

try to update your Intel RST drivers. It seems that old versions of this driver causes BSOD even with other AVs…