BSoD & Avast -> Anyone else have a problem

1dmf · 2 Feb 2009 at 10:10

I got rid of AVG and put Avast on.

It seem ever since my machine has started to BSoD.

IRQ not less than or equesl to, or is it greater than or equal to... anyways..

Anyone else having this problem, or is it coincidence and there is an issue else where?

Cheers,

1DMF

Kennysevenfold · 2 Feb 2009 at 10:53

hi mate, what operating system are you using.?

JoDaMa · 2 Feb 2009 at 11:05

I'm having a similar problem, exactly the same kind of blue screen, but with Kaspersky Internet Security 2009. I think the problem with mine is some kind of conflict going on with the university network settings, I took my laptop home with me over Christmas and I didn't get a single BSoD. Would be awesome if someone had a solution.

1dmf · 2 Feb 2009 at 11:17

I'm running Vista x64 with SP1.

1dmf · 2 Feb 2009 at 14:36

did a bit of googling and found the following....

Here's the fix for it and it has nothing to do with drivers but with the PC
trying to over run the BIOS' IRQ device assignemt.

When you get such an error message. Perform the following steps.

To resolve this problem, perform the following steps:

1. Restart the computer.

2. Press the <F8> key to display the Windows XP startup menu.

3. Press the <Down Arrow> key to select Safe Mode Command Prompt and then
press the <Enter> key.

4. Click to select the Administrator account.

5. Type cd\ and then press the <Enter> key.
The c:\> prompt appears.
c:\> attrib -r boot.ini

6. Type edit boot.ini and then press the <Enter> key.
The boot.ini screen appears.

7. Under the boot.ini screen under the Operating system section you will
have a path as shown below.
[operating system]
device=multi(0)disk(0)rdisk(0)partition(1)"Microsoft windows xp home
edition"

8. Type a switch "/pcilock" after typing you will see the path as shown
below.
Multi(0)disk(0)rdisk(0)partition(1)"Microsoft windows xp home edition"
/pcilock

9. By doing so windows stops dynamically assigning the irq's(Interrupt
Request) to the devices and
It takes the irq's assigned by the BIOS.

10. So this is going to solve the issue and also by following this article
we can
Even overcome the bangs on the cd drives.dvd drives after upgrading the
system to windows xp from windows me/98 etc.

AND

Of course, there is a still easier solution instead of
using the switch. It is to turn off, or disable, PnP OS
in the bios setup. Does the same thing.

(As an aside, most well-behaving applications should not
trip this BSOD. However, some games do take over or need
their own, unique resource settings that may conflict
with those forced by the Windows OS. These conflicts can
occur at any time since PC's are not a monolithic platform
but a hodgepodge of similar parts coming from a number of
different manufacturers.)

What's others thoughts on this being the problem / resolution?

1dmf · 2 Feb 2009 at 18:29

Well , so far so good, though I bet as soon as I post this i'll get a BSoD - rofl

What i've done , which seems to be working.

1stly, disabled Marvell IDE controller alltogether, I left it enabled even though it didn't work with SCSI in the PCI-X slot, so thought to be on safe side, i'd just disable it.

I then changed PnP OS to 'No' , as per above post.

I also noticed leaving vCore on Auto , Asus was putting 1.45v through it, so I dropped it manually to 1.35v, booted fine , still OC @ 3.37ghz!

I then started a thourough scan in Avast and been running for @ 20mins now, no problems.

Running scan, reading email and suring net, PC-Probe showing CPU temp @ 25c , so all good there! Infact Mobo temp shows higher @ 27c

One thing that scared the hell out of me, Avast found a trojan in my temp files ? dunno where from..

Jezus, that alarm and voice, wasn't expecting that, nearly fell out my chair!

let's hope it finishes scan without any more BSoD's or hiccups!

1dmf · 2 Feb 2009 at 19:30

Typical, went to watch TV came back system frozen.

Checked Event Viewer, something to do with SysTools64.sys , couldn't find much but I got the impression it was to do with Nvidia drivers, so am loading direct from Nvidia.

I did do the stupid thing and allow MS Updates to update my nVidia driver, so it's posible that is the cause.

Though I also get the feeling the machine only freezes / crashes when competely idle, the only powersaving setting I use is switch off monitor after 20 mins, could this be the cause?

I've turned off all powersaving setting now, see if that also help!

swinnie · 2 Feb 2009 at 20:32

1dmf said:
I did do the stupid thing and allow MS Updates to update my nVidia driver, so it's posible that is the cause.

Yes - had that problem before.

MS seems to like 'old' drivers.

1dmf · 3 Feb 2009 at 14:52

Well I installed the nVidia drivers direct, and had no power saving setting on what so ever... Avast ran for 1.5 hours before crashing!!!

So certainly progress....then I thought I'd go check OCZ website as the crash showed MEMORY_MANAGEMENT in the BSoD.

It turns out having memory voltage on 'Auto' in the BIOS just wasn't cutting it....

Interestingly enough, on the OCZ site it shows my memory as 5-5-5-18 - 1.8v / 2.1v-2.3v

But the packaging, the place I bought them and the SPD shows them as 5-5-5-15 - 1.8v / 2.1v

I changed the BIOS Memory Voltage to 2.3v and so far so good.

So for now it seems like it was a juice thing... I ran MemTest for @ an hour, it got to 42% , but then it was late so went to bed and shut PC down....so fingers crossed!