System crashing during anti-malware scanning

[Jon Boyes]

My PC crashes whenever I try to run Adaware, the spyware cleaner, also with
Windows Defender and when I try and run the malware detection tool at:
http://www.bitdefender.com/scan8/ie.html

In all cases the crash occurs at some point during the scan. With the first
two applications above, I can run a quick scan without a problem, but the
crash always occurs when I run a full system scan.

When the system crashs, it reboots and and I get the error message saying it
has recovered from a serious error. After sending the error reort to
Microsoft, I get the following page:
http://oca.microsoft.com/en/response.aspx?SGD=263fb666-30e3-49b4-b410-f68ef7c727cb&SID=10

My installed AVG Antivirus software tells me my system is clean.

This has been happening for a few weeks, beforehand I had no problems
running either scanner. I have not installed any new hardware. So far I have
not found anything else that crashes the system.

I am running XP pro with service pack 2, updated, as an admin user.

Any help appreciated, thanks.

 

[glee]

Right -click "My Computer" in the Start Menu and click Properties on the menu that
appears.
Click the Advanced tab, then click the Settings button under "Startup and Recovery".
In the "System Failure" section, uncheck the box for "Automatically Restart" and
click OK, then OK.

Now run Ad-Aware or go to the BitDefender online tool, and when the system crashes
it *should* give you a blue screen STOP error, instead of rebooting automatically.

Write down the relevant data in the blue screen and post back with the information,
as described here:
http://www.mvps.org/marksxp/WindowsXP/bsod.php

"It is important to note a few key bits of information, firstly if a system file is
mentioned....., secondly make a note of the eight digit hex number such as
0x0000001e and also the error text part of the error message such as
IRQL_NOT_LESS_OR_EQUAL or DATA_BUS_ERROR."

 

[Jon Boyes]

Now run Ad-Aware or go to the BitDefender online tool, and when the system

crashes it *should* give you a blue screen STOP error, instead of
rebooting automatically.

Write down the relevant data in the blue screen and post back with the
information,

OK, thanks for your help. Here's whats it says on the blue screen:

"A problem has been detected and windows has been shut down.. (etc)

If this is the first time you've seen this stop error screen... (etc)

Run a system diagnostic utility supplied by your hardware manufacturer. Run
a memory check... (etc)

Disable or remove any newly installed hardware.. (etc)

Technical information:

*** STOP: 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000)

Beginning dump of physical memory ... (etc)"


Jon

 

[glee]

OK, thanks for your help. Here's whats it says on the blue screen:

"A problem has been detected and windows has been shut down.. (etc)

If this is the first time you've seen this stop error screen... (etc)

Run a system diagnostic utility supplied by your hardware manufacturer. Run a
memory check... (etc)

Disable or remove any newly installed hardware.. (etc)

Technical information:

*** STOP: 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000)

Beginning dump of physical memory ... (etc)"

You managed to post most of the irrelevant data while leaving out most of the
relevant, except for STOP:0x0000007f
;-)

It is the lines right below there that name the error and possibly a filename, as
described on the page I linked.

In your case, STOP: 0x0000007f should state below it UNEXPECTED_KERNEL_MODE_TRAP

Have a look here:
General causes of "STOP 0x0000007F" errors
http://support.microsoft.com/?kbid=137539
Yours is a Divide by Zero error, which can be caused by memory corruption, other
hardware problems, or software failures.

The most common cause is hardware failure, and the most likely cause is defective or
mismatched memory modules. Overheating or overclocking can also cause it. There
could also be a corrupt or incompatible driver causing the error. Have you disabled
your virus scanner before running the scans that are causing the error? Do you have
Symantec (Norton) Anti-Virus installed on this system?

From MVP Jim Eshelman's extensive pages,
http://www.aumha.org/win5/kbestop.htm
comes:
http://www.aumha.org/win5/kbestop.php#0x7f

<quote>
One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2)
Software problems. (3) A bound trap (i.e., a condition that the kernel is not
allowed to have or intercept).

Hardware failures are the most common cause (many dozen KB articles exist for this
error referencing specific hardware failures) and, of these, memory hardware
failures are the most common.

General Causes {KB 137539} Win NT, Win 2000, Win XP
Windows Stops Responding with Stop Error 0x7F Error Message {KB 814789} Win 2000,
Win XP (when running Terminal Services)
Windows NT 4.0 Setup Troubleshooting Guide {KB 126690} NT 4 (Recommendations for the
current error message are buried down inside this article, which isn't necessarily
limited to NT 4.)
</quote>

A variety of other suggestions are offered here:
http://www.computerhope.com/issues/ch000830.htm

 

[Jon Boyes]

Technical information:

You managed to post most of the irrelevant data while leaving out most of
the relevant, except for STOP:0x0000007f
;-)

It is the lines right below there that name the error and possibly a
filename, as described on the page I linked.

No, I didn't leave anything relevant out, there was nothing below that STOP
line. I included everything in the technical info section, and only cut off
the end of the text in each paragraph because all that stuff is standard.

In your case, STOP: 0x0000007f should state below it
UNEXPECTED_KERNEL_MODE_TRAP

Have a look here:
General causes of "STOP 0x0000007F" errors
http://support.microsoft.com/?kbid=137539
Yours is a Divide by Zero error, which can be caused by memory corruption,
other hardware problems, or software failures.

In other words, just about anything ;-)

The most common cause is hardware failure, and the most likely cause is
defective or mismatched memory modules. Overheating or overclocking can
also cause it. There could also be a corrupt or incompatible driver
causing the error. Have you disabled your virus scanner before running
the scans that are causing the error? Do you have Symantec (Norton)
Anti-Virus installed on this system?

My system is not overclocked and shouldn't not be overheating - it does this
when it is cold. I do not have Norton AV installed. I do not normally
disable my AV software, it has never caused a conflict in the past.

Thanks.

PS - sorry for posting this to your email - just realised!

 

[glee]

Try an overnight memory test loop from a floppy or CD boot, using Windows Memory
Tester:
http://oca.microsoft.com/en/windiag.asp