BSOD & Non-BSOD Crashes, Display Driver Issue?

[Jimulacrum]

I'm running:

Windows 7 Home Premium, 64-bit, OEM, never reinstalled
HP model #p6654y, approx. 1 year old, no major problems until now

I've attached the BSOD Dump and System File Collection, but Windows refuses to produce a System Health Report because I have to run in safe mode. If you have an alternative method, I'll be glad to try it, but normal mode seems to be producing crashes more and more quickly.

First BSOD was 12/25, then 12/29, then 12/31. There have been more than 3 crashes, but not every crash has produced a minidump; several times, the crash has been a sudden black screen. One time, display froze with a bunch of horizontal lines/distortion and stuck like that until I hard restarted. I have had to hard restart every time (except for 2 occasions during which hard restart would not work, and I had to pull the power cord).

System Restore had me up and running for a whole day yesterday, and then it crashed again today. I was playing Zynga Poker on Facebook during at least 2 crashes, but crashes have happened without it open as well.

Running 2 passes of the memory checker did not detect any memory issues. From my experience, it doesn't seem like a hardware problem, but I could be wrong.

Please help.

 

[zigzag3143]

Really easy. Your AVG.

I notice your AVG which is often at least a contributing cause of BSOD'S . Please remove and replace your AVG with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows

 

[Jimulacrum]

Seriously? AVG is causing this? I've been using it on this machine since the day I got it. I also used it on my previous machine (Win XP SP2) without incident. It seems incredible that it would run flawlessly for 12 months and then start causing repeated fatal errors out of nowhere.

I'm killing AVG and installing MSE right now. Be back when it's done.

 

[zigzag3143]

Seriously? AVG is causing this? I've been using it on this machine since the day I got it. I also used it on my previous machine (Win XP SP2) without incident. It seems incredible that it would run flawlessly for 12 months and then start causing repeated fatal errors out of nowhere.

I'm killing AVG and installing MSE right now. Be back when it's done.

Just an FI, might be as simple as a recent definition update, or version change. As in all BSOD's they are a combination of things, perhaps you added some software lately that doesnt like avg.

Anyway

Unable to load image AVGIDSFilter.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys


Good Luck

 

[Jimulacrum]

OK, AVG is out and MSE is in (and about 1/3 into its first-time scan at the moment). I'm running Windows in normal mode, and my System Health Report is attached.

Anything else you can tell me?

Oh, and thank you. I've been using PCs since Win 3.11 was the top of the line, so I'm not the average halfwit end user, but this one nearly had me pulling out my hair.

 

[zigzag3143]

OK, AVG is out and MSE is in (and about 1/3 into its first-time scan at the moment). I'm running Windows in normal mode, and my System Health Report is attached.

Anything else you can tell me?

Oh, and thank you. I've been using PCs since Win 3.11 was the top of the line, so I'm not the average halfwit end user, but this one nearly had me pulling out my hair.

Jim


I wish they were all this easy. I have been there like you and I am just glad I could be of some assistance. After all you fixed it, I just helped.


Good luck and let us know if you need help


ken

 

[Jimulacrum]

Hi again. Apparently AVG was not the lone culprit. I have not installed any new programs or made any major changes to the computer since my last post.

I just caught another BSOD. I tried to get into normal mode so I could run a System Health Report, and it went blue again during the Windows loading screen.

I've attached the file collection again. The dump file dated 12/25/2010 appears to be new, somehow. I didn't have any problems with the machine on that date.

Whaddya reckon?