steve_nfi (14th January 2010)
Having great fun here... We moved to AVG 9 just before Christmas, and as soon as we installed it, we started getting blue screens left, right and center. The stop code isn't particularly helpful...
and although the location is always slightly different, the last part is always the same:
Before, it was just 1 machine at a time, but this morning I've lost 5 in our suite of 20 machines (all are running XP Pro). Any ideas? I phoned AVG, and was told to just to uninstall it to fix the problem (great, so I'd have no a/v?! AND when we've just paid for it and all?! ). Out of interest I tried the freebe version to see if that made any difference... Nope, still blue screens. Oh, the evilness...
steve_nfi (14th January 2010)
How are your machines built and imaged and have you slipstreamed them in any way? Might be worth applying updates one (or a group at a time) and seeing if you can induce failure that way.
Do you have WSUS? Might be worth temporarily disabling it until you can rule out Windows updates. I feel a machine without malware protection is at greater risk than one not up to the minute with patches.
Might also be worth checking AVG website for updates and/or KBs for the product.
IIRC AVG 8.5 broke the internet where the firewall was installed following M$ DNS update to fix a critical vulnerability there.
Install "WhoCrashed" wait for a BSOD, reboot, check logs and find detailed information on what cause everything.
This probably won't help but we had similar issues with NOD32 V4 and they recommended following the Microsoft AV exclusion recomendations. Once we did this things seemed to stabalise.
Virus scanning recommendations for computers that are running Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows 2000, Windows XP, Windows Vista, or Windows 7
I hadn't thought of Win updates being the issue... that's next then. I agree about the malware protection priority!
AVG don't have anything that I haven't already applied - and like I say, if I call them, their response is just to not use it
What were you running before moving to AVG9? And are you 100% sure all components of the old AV product are uninstalled?
I highly doubt it's to do with Windows Updates as many people use the product which is free at home. It'll be a driver or another application, something along these lines.
Though, it has to be said, that, seeing as the school is closing in 10 mins, I'm not busting a gut right now. I'll deal with it properly when we get back Is that bad of me? I'll call it research time at home! Obviously I'm very grateful for the help still
Realistically 10 minutes isn't enough time so I wouldn't blame you. I would be tempted to take a copy/image of the existing hard drive, install Windows as new, then drivers, then AVG 9 and test. If it's OK proceed to install applications one by one until it fails. It sounds long winded but without experimenting I can't see how else you can identify the problem.
Quick update - we now seem to be coming back up to speed here, despite the snow still falling!! I've used the WhoCrashed (thanks ahuxham!), and it's showing up as the driver for the network adaptor. I'm just going to try updating the drivers off the intel site, and then we start round 2!!
What a prat I am. Right, WhoCrashed worked as expected (I didn't doubt it at all) and has shown that its a NDIS driver, which sounds perfectly right, thanks for highlighting that DMcCoy.
Then I re-read the whole Thread and noticed the original Stop message, and just remembered something.
The 0x40000080 message looked very familiar, and I remembered I got this question wrong in my MCP 70-290 exam. I had never covered it in material or practice exams and kicked up stink about it, how am I supposed to know about something which isn't being taught.
Anywho, the question related to Windows XP being unable to boot and the stop message being around 0x40000080, and the correct answer was NDIS Drivers...
At least you found WhoCrashed, such an invaluable tool to have.
I may have spent a number of days getting to know Kaspersky and it's very own drivers and filesystem filters quite well :P
They even decided that the driver I told them was broken was in fact broken. Wasn't the NDIS one on this particular AV, it was the file/registry filter.
There are currently 1 users browsing this thread. (0 members and 1 guests)