computer shutdown and recovered from a serious error??

[umcpgrad]

I don't know why but these days my comp kept giving me this system has recovered from a serious error message...
the error signature is
bccode: fe bcp1: 00000002 bcp2: 8455a2cb bcp3: 835a5008

bcp4: 849beda0...
from the error report ...?

can I get some help?

[umcpgrad]

help?

I have 3.0e ghz p4 intel 478pin and ecs 661-m m/b with 1 gig of ram
and xp os sp2..
and 6800nu and audigy 2 zs plat.

and 300 gig and 300 gig seagate hd. :confused:
brand new just setup 2 days ago.

[beanman101283]

Does it let you send an error report? Send one and see if it pops up with a web page with a fix for it, i've had that happen before.

[kdheads]

see if this helps you

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21485954.html

[umcpgrad]

I sent it in, it said something about driver problem..
but not sure which one.. the computer been giving me problems the last 2 days..
i oced on the first day.. to 3.4ghz but I lowered it back on the 3.0 ghz now.. the last two days..

:(

[umcpgrad]

I think it said I need to pay to see the solutions..

[kdheads]

yea it did that for me too this time...so i found the link i used on google and went to the cached one it had so heres what was on that page:


Hi, Getting BSOD after system runs for a while. Doesnt seem to follow any particular pattern and is drivign me nuts.

I have reinstalled the OS and all the drivers for the hardware. I had not installed any new hardware or software prior to this happening.

Error codes are:

BCCode : 100000d0 BCP1 : 00000008 BCP2 : 00000002 BCP3 : 00000000
BCP4 : 805492EC OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 44 BCP1 : 853FF8C0 BCP2 : 00000D62 BCP3 : 00000000
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 100000d0 BCP1 : 00000008 BCP2 : 00000002 BCP3 : 00000000
BCP4 : 805492EC OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 1000008e BCP1 : 80000003 BCP2 : 18000003 BCP3 : 80042000
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 100000d0 BCP1 : 00000008 BCP2 : 00000002 BCP3 : 00000000
BCP4 : 805492EC OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 100000d0 BCP1 : 00000008 BCP2 : 00000002 BCP3 : 00000000
BCP4 : 805492EC OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 100000d0 BCP1 : 00000004 BCP2 : 00000002 BCP3 : 00000001
BCP4 : 80549318 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 100000d0 BCP1 : 00000004 BCP2 : 00000002 BCP3 : 00000001
BCP4 : 80549318 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

BCCode : 100000d0 BCP1 : 00000000 BCP2 : 00000002 BCP3 : 00000001
BCP4 : 8054946A OSVer : 5_1_2600 SP : 2_0 Product : 256_1

Thanks for your help...

--
Nicholas


Comment from cpc2004
Date: 07/09/2005 01:09PM PDT
Comment


Cause
The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.

In most cases, this bug check results if a driver corrupts a large allocation (PAGE_SIZE or larger). Smaller allocations result in bug check 0xC5 (DRIVER_CORRUPTED_EXPOOL).

Bug Check 0xD0: DRIVER_CORRUPTED_MMPOOL
The DRIVER_CORRUPTED_MMPOOL bug check has a value of 0x000000D0. This indicates that the system attempted to access invalid memory at a process IRQL that was too high

Resolving the Problem
If you have recently installed any new software, check to see if it is properly installed. Check for updated drivers on the manufacturer's website.

To debug this error, use the special pool option of Driver Verifier. If this fails to reveal the driver that caused the error, use the Global Flags utility to enable the special pool by pool tag.

For information about the special pool, consult the Driver Verifier section of the Windows DDK.

An alternate method is to open the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Sessio n Manager\Memory Management registry key. In this key, create or edit the ProtectNonPagedPool value, and set it equal to DWORD 1. Then reboot. Then the system will unmap all freed nonpaged pool. This will prevent drivers from corrupting the pool. (This does not protect the pool from DMA hardware, however.)



Comment from cpc2004
Date: 07/09/2005 01:15PM PDT
Comment


When Windows crashes with blue screen, it writes a system event 1001 and a minidump to the folder \windows\minidump. Zip 5 to 6 minidumps and attach the zip files at any webspace. I will study the dump and find out the culprit.

Run memtest to make sure that the ram is healthy. http://www.memtes86.com


Comment from Squiddy2
Date: 07/09/2005 01:50PM PDT
Author Comment


Thanks for your prompt reply...

http://members.optusnet.com.au/n_rob/minidump.zip

Running memtest now.

Accepted Answer from cpc2004
Date: 07/09/2005 02:10PM PDT
Grade: A
Accepted Answer


The culprit is NAVAP which is Norton Auto Protect and your version is outdated for almost 2 years. Your Norton AV is a up-to-date vrsion. De-install or upgrade NAVAP.SYS will resolve your problem.


NAVAP.SYS Sat Nov 01 07:01:30 2003 (3FA2E9CA)
SYMEVENT.SYS Sat Apr 30 03:00:28 2005 (4272844C)

BugCheck 100000D0, {0, 2, 1, 8054946a}
Probably caused by : Pool_Corruption ( nt!ExFreePool+f )

STACK_TEXT:
f3c5a86c 8054ab8b 00000004 859af248 00000000 nt!MiFreePoolPages+0x2e7
f3c5a8ac 8054b0b9 816e9000 00000000 f3c5a8cc nt!ExFreePoolWithTag+0x1b7
f3c5a8bc f3955c75 816e9000 816e9008 f3c5a904 nt!ExFreePool+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
f3c5a8cc f3955f07 816e9000 f395390b 816e9008 NAVAP+0x2c75
f3c5a904 f39719b9 f3971dbd f3c5a9b0 f3c5a928 NAVAP+0x2f07
f3c5a9b4 f5f88888 00000000 e2603750 f5f8abd6 NAVAP+0x1e9b9
e14d89a8 00000000 00000000 00000000 00000000 SYMEVENT+0x10888

Comment from Squiddy2
Date: 07/09/2005 04:15PM PDT
Author Comment


I just purchased Symantec Security 2005 from their site and installed it. Still get the same BSOD :(

Comment from Squiddy2
Date: 07/09/2005 04:28PM PDT
Author Comment


What's worse, after that last BSOD, the system freezes after the welcome screen and goes no further.

Im going to have to try remove it.

Comment from Squiddy2
Date: 07/09/2005 05:14PM PDT
Author Comment


All seems to be working well again after removing Symantec Internet Security and NAV from my system. THE BSOD have stopped.

Thank you for your help. I now need to speak with Symantec on Monday to have them explain why their program no longer runs on my older server.

Comment from cpc2004
Date: 07/23/2005 09:17PM PDT
Comment


What is reply from Symantec? Your feedback will help us to resolve similar problem.

Comment from Squiddy2
Date: 07/24/2005 03:05AM PDT
Author Comment


Symantec suggested that the only reason the BSOD were comming up was due to faulty RAM and that the errors could have been caused by any program, not just NAV.

I replaced the RAM and reinstalled Norton Security andit seems to have worked. No more BSOD. I have since run memtest86 on both sticks and it looks like they each have errors.

I gave the ram to a friend, and there doesnt seem to be an issue on his PC. He doesn't use Symantec products however.

Again a big thanks for all your help.

Comment from cpc2004
Date: 07/24/2005 04:49AM PDT
Comment


Thanks for your reply. As you told me that after you de-instaledl Norton AV and BSOD was stopped. It seems that the problem is related to software error at Norton AV. Recently I have several cases at EE of BSOD at Norton AV and they are using exactly the same version of Norton AV as yours. As I am not convincing so many PCs have bad RAM recently. What version of Norton Security Audit did you install? Did you install the same version or the lateset version?

Comment from Squiddy2
Date: 07/24/2005 06:56AM PDT
Author Comment


I went from the 2002 version, which I was keeping up to date with the latest live updates, to the 2005 Norton Internet Security.

The trouble is that after I updated to 2005, on your suggestion it might be aspects of 2002 that causing it, the BSOD still occurred.

After installing 2005 I couldnt even start the PC, I had to uninstall it alltogether and wait for the new RAM.

With the new RAM I havent had a BSOD since.

Comment from Squiddy2
Date: 07/24/2005 06:59AM PDT
Author Comment


The funny thing is I guess that the errors I found in the RAM were only set off by Norton. Like I said, the guy I gave it to has had no a single issue with it but he uses AVG.

Comment from cpc2004
Date: 07/24/2005 08:01AM PDT
Comment


Thanks for your information. It is weired that your old RAM and Norton 2005 caused BSOD. This is a valuable information.


Edit* as I read that post i see its not your error codes, when i did the search i used 00000002, but thats under your bcp1 not the one listed under bcp2, so its probably not useful to you.

the whole error string you provided did not yield results when i searched

[lesman]

I think it said I need to pay to see the solutions..
What? That's rediculous...email Microsoft about it...their tech support is incredibly helpful, they're bound to give you some sort of solution.....and, if I had anything to say about it, I'd say that somehow something got damaged due to that OC you did.

[Ranma_Sao]

Help Me to Help You:

http://www.hardforum.com/showthread.php?t=828696

[umcpgrad]

seem like a bad ram or bad nav eh?

[umcpgrad]

just tested the ram, nothing wrong with them.. :(

[Mav451]

If you are getting good temps...then this is a real stumper. The fact that you BSODs at random times (not just hard-hitting apps like games/compiling/etc.) takes the RAM out.

PSU? And I'm fairly confident Intel chipset drivers aren't hardcore like nForce...if we would even call out IDE/Miniport drivers here.

If are really serious, I say get a new mobo (all other components the same). If you still BSOD, I'm thinking you got a weird CPU? Though I've never heard of a bad CPU...it either POSTs and works, or it doesn't.

[umcpgrad]

i have a 6800u and audigy zs..
really a m/b problem?
it might also be a software problem rights?
:confused:

o and the cpu temp is 36 degrees.