BSOD Problem

[Peter Schacknow]

For the last two weeks, I've been constantly getting the BSOD with Windows
XP. I've tried to use the information given to interpret the error message,
but all I've been able to determine is that it involves a device driver,
antivirus program, or firewall software.

I haven't installed anything new lately .. and by coincidence, I'd just
gotten a new version of both my anti-virus and firewall software, but
installing those didn't help.

The only usable clues I have (since it often happens overnight when the
computer is unattended) are the times I was able to make it happen on my
own:

1)When running an anti-virus scan.

2)When downloading and processing the weekly listings for my Guide-Plus
software .. it's a TV Guide program that comes with the ATI All-In-Wonder
graphics card.

Those are the only two circumstances I've encountered where it happens every
single time.

I've run Windows update and also taken care to make sure the drivers are up
to date.

Any help appreciated.

Peter

 

[Perdita X. Dream]

For the last two weeks, I've been constantly getting the BSOD with
Windows XP. I've tried to use the information given to interpret the
error message, but all I've been able to determine is that it
involves a device driver, antivirus program, or firewall software.

I haven't installed anything new lately .. and by coincidence, I'd
just gotten a new version of both my anti-virus and firewall
software, but installing those didn't help.

The only usable clues I have (since it often happens overnight when
the computer is unattended) are the times I was able to make it
happen on my own:

1)When running an anti-virus scan.

2)When downloading and processing the weekly listings for my
Guide-Plus software .. it's a TV Guide program that comes with the
ATI All-In-Wonder graphics card.

Those are the only two circumstances I've encountered where it
happens every single time.

I've run Windows update and also taken care to make sure the drivers
are up to date.

Any help appreciated.

Peter

"The BSOD" there's no such thing as *THE* BSOD - there are many and they all
say different things. You have neglected to give us the exact error, without
which we cannot make a diagnosis.

 

[Knack]

For the last two weeks, I've been constantly getting the BSOD with Windows
XP. I've tried to use the information given to interpret the error message,
but all I've been able to determine is that it involves a device driver,
antivirus program, or firewall software.

I haven't installed anything new lately .. and by coincidence, I'd just
gotten a new version of both my anti-virus and firewall software, but
installing those didn't help.

The only usable clues I have (since it often happens overnight when the
computer is unattended) are the times I was able to make it happen on my
own:

1)When running an anti-virus scan.

2)When downloading and processing the weekly listings for my Guide-Plus
software .. it's a TV Guide program that comes with the ATI All-In-Wonder
graphics card.

Those are the only two circumstances I've encountered where it happens every
single time.

I've run Windows update and also taken care to make sure the drivers are up
to date.

Any help appreciated.

First of all, what is the STOP error number? In order to debug it, you'll
have to run with the big dogs.

Approach-1
-------------

The easiest thing you can do is to set WinXP to write an event log message
with bugcheck information. Need some help here folks. Anybody out there know
how to do that?

Approach-2
-------------

You can debug this problem via another computer connected to your problem
computer. Other computer must be WinNT/2000/XP.

Use the switch /DEBUG for boot.ini

The debugger is loaded when you start WinNT/2000/XP, and can be activated at
any time by a host debugger connected to the computer. This is the mode to
use when you're debugging problems that are regularly reproducible.

Approach-3
-------------

Check to be sure that your paging file in Control Panel > System > Advanced

Performance Options > Advanced is at least equal to 1.5x total RAM, and

that it's to be found on the sysstem partition. Only then will the file
Memory.dmp be created when you get the BSOD.

Then get the utility Kanalyze from www.winternals.com It obsoletes the
Resource Kit utility dumpchk.exe provided by Microsoft for analyzing the
file Memory.dmp. There also used to be a program call dumpexam.exe included
on Windows installation CDs for this purpose, but it's not to be found on
the WinXP CD.

See
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=16425

 

[Knack]

First of all, what is the STOP error number? In order to debug it, you'll
have to run with the big dogs.

Approach-1
-------------

The easiest thing you can do is to set WinXP to write an event log message
with bugcheck information. Need some help here folks. Anybody out there know
how to do that?

Approach-2
-------------

You can debug this problem via another computer connected to your problem
computer. Other computer must be WinNT/2000/XP.

Use the switch /DEBUG for boot.ini

The debugger is loaded when you start WinNT/2000/XP, and can be activated at
any time by a host debugger connected to the computer. This is the mode to

use when you're debugging problems that are regularly reproducible.

Approach-3
-------------

Check to be sure that your paging file in Control Panel > System > Advanced
that it's to be found on the sysstem partition. Only then will the file
Memory.dmp be created when you get the BSOD.

Then get the utility Kanalyze from www.winternals.com It obsoletes the
Resource Kit utility dumpchk.exe provided by Microsoft for analyzing the
file Memory.dmp. There also used to be a program call dumpexam.exe included
on Windows installation CDs for this purpose, but it's not to be found on
the WinXP CD.

See
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=16425

For Approach-1:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314084&Product=winxp

BTW, if you have a retail version of WinXP, it might still be under warranty
and you can get customer support from Microsoft. You first need to have
those 21 answers (at the bottom of KBA 314084) before calling them.