Stop Errors Continue!!

[Guest]

Hello,
After numerous types of blue screen stop messages, I have done the
following so far to alleviate this problem:

* Upgraded flash bios
* Upgraded RAM from 256mb to 512mb
* Re-installed original operating system software that was done at the factory
* Upgraded as many device drivers that were available online
* Performed manufacturer's hardware diagnostics which showed everything ok

Currently all software installed is original except for Mcafee virus scan.

But the following blue screen errors continue:

A) Stop C000021A - Fatal System Error - System has shut down with a status
of OxC0000005 (0x00000023, 0x0052f2a4).

or with a status of
0xC0000005 (0x75e9d4e3, 0x0069dcd4)

This error usually occurs when downloading files from the internet and no
errors are recorded in the event viewer.

B) Stop 0x0000008e with parameters (0xC00000005, 0x00000061, 0xf3b938f4,
0x00000000)

This error is followed up with a microsoft online crash analysis of "Error
caused by Device Driver" and can occur at any time.

C) While working online the following message sometimes can occur:

"NT On-Access Scanner Service encountered a problem and needs to close."

The errors above can occur while in safe mode.

So where can I go from here and how can I access a physical memory dump when
the blue screens occur.

Thanks!!
Chuck W

 

[David Candy]

NT On-Access Scanner Service is McAfee.

For C000021A only 3 or 4 could help.

For 0x8E any might help.

As the common thread above (assuming that they are related which we don't know) is caused by a Service. Try uninstalling McAfee (you can use AVG in the meantime www.grisoft.com) and see if it goes away.

For 0x8e, assuming you have listed the full error message do the following.

Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.

You will be creating a crash dump file in c:\windows\minidump every blue screen.

Then

If you have the XP SP2 Security Update CD

Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg (File - Load Crash Dump and it's in c:\windows\minidump) and READ WHAT IT SAYS, then
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash and one from your next crash after you turn verifier on. And only one per mail.

From Help (you want small memory dumps)
==================================
To specify what Windows does if the system stops unexpectedly

You must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. If your computer is connected to a network, network policy settings might also prevent you from completing this procedure.

1.. Open System in Control Panel.
2.. On the Advanced tab, under Startup and Recovery, click Settings.
3.. Under System Failure, select the check boxes that correspond to the actions you want Windows to perform if a Stop error occurs:
a.. Write an event to the system log specifies that event information will be recorded in the system log.
b.. Send an administrative alert specifies that your system administrator will be notified.
c.. Automatically reboot specifies that Windows will automatically restart your computer.
4.. Under Write Debugging Information, choose the type of information you want Windows to record when the system stops unexpectedly:
a.. Small Memory Dump records the smallest amount of information that will help identify the problem. This option requires a paging file of at least 2 MB on the boot volume of your computer and specifies that Windows will create a new file each time the system stops unexpectedly. A history of these files is stored in the directory listed under Small Dump Directory.
b.. Kernel Memory Dump records only kernel memory, which speeds up the process of recording information in a log when the system stops unexpectedly. Depending on the amount of RAM in your computer, you must have 50 MB to 800 MB available for the paging file on the boot volume. The file is stored in the directory listed under Dump File.
c.. Complete Memory Dump records the entire contents of system memory when the system stops unexpectedly. If you choose this option you must have a paging file on the boot volume large enough to hold all of the physical RAM plus one megabyte (MB). The file is stored in the directory listed under Dump File.
Notes

a.. To open System, click Start, click Control Panel, and then double-click System.
b.. You must have at least a 2-MB paging file on the computer's boot volume if you select Write an event to the system log or Send an administrative alert.
c.. If you choose either Kernel Memory Dump or Complete Memory Dump and select the Overwrite any existing file check box, Windows always writes to the same file name. To save individual dump files, clear the Overwrite any existing file check box and change the file name after each Stop error.
d.. You can save some memory if you clear the Write an event to the system log and Send an administrative alert check boxes. The memory saved depends on the computer, but typically about 60 KB to 70 KB are required by these features.
e.. If you contact Microsoft Product Support Services about a Stop error, they might ask for the system-memory dump file generated by the Write Debugging Information option.
Related Topics