BSOD Purgatory

[jrmsp]

Been having error after error the past few weeks; I've tried replacing drivers, re-seating cards, blowing out the swap file, no changes. I've attached a couple mini-dumps; any help appreciated!

 

[peterdiva]

Uninstall Kaspersky AV to see if it solves the problem. You can always try reinstalling it (with update) if it does, or you can just try another AV program.

 

[cpc2004]

Hi,

Two minidumps have the footprints of KAV. The other minidumps may be caused by KAV as well although their symptoms seems to be related to faulty ram. Recently KAV has a lot of problem.

The following two versions of KAV have known software problem.
Thu Aug 04 23:19:22 2005
Fri Aug 04 19:00:23 2006

Your version is at Mon Oct 03 22:59:40 2005 and you had better upgrade or de-install KAV.

 

[jrmsp]

Thanks. Removed KAV, cleaned up, put in new version, no change. Took it out again, cleaned up, no change. Will put up a couple more. Thanks for your help so far, it's about the only thing keeping me from slashing my wrists heh

 

[cpc2004]

Hi,

According to the minidump, you haven't upgraded or de-install KAV. I find the same version of KAV is installed at your windows. One windows crash is crashed by KAV. Two system crashes are caused by faulty RAM.

Mini121806-01.dmp BugCheck 19, {20, e171b580, e171b580, 80002b0}
Probably caused by : klif.sys ( klif+14d1c ) <-- KAV

Mini121806-02.dmp BugCheck A, {a8fffffc, ff, 0, 804db973}
Probably caused by : ntoskrnl.exe ( nt!SwapContext+4f ) <-- Faulty RAM

Mini121806-03.dmp BugCheck 50, {bad0b158, 0, 80566a37, 2}
Probably caused by : ntoskrnl.exe ( nt!ObpCloseHandleTableEntry+13 ) <-- Faulty RAM

 

[jrmsp]

I think kav is totally gone...

Heres's a couple more. Ran memtest b4, will let it run all night now.

 

[cpc2004]

Hi,

The latest 2 minidump is related to faulty ram. Memtest is not 100% correct as some faulty ram can pass memtest.

Mini121906-01.dmp BugCheck 1000008E, {c0000005, bf820d5d, a940dcb0, 0}
Probably caused by : win32k.sys ( win32k!GetDesktopView+8 )

Mini121906-02.dmp BugCheck 50, {bad0b158, 0, 80566a37, 2}
Probably caused by : ntoskrnl.exe ( nt!ObpCloseHandleTableEntry+13 )

 

[jrmsp]

Nuts. Ran memtest all night long and came up clean. Would it perhaps help to pull it out and clean contacts....or just start over with some new?

 

[jrmsp]

And now getting cmos/gpnv checksum bad. Related, or a coincidental battery failure?

 

[cpc2004]

Maybe it is related to battery of m/b. As you know the symptom of hardware error is unpredicatable (ie no pattern).

 

[jrmsp]

Gonna toss up one more. Just not sure what to do....replace the ram? Upgrade the bios? Start over?

 

[jrmsp]

Anyone? Buehler? Buehler?