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
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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
Thanks for your prompt reply...
http://members.optusnet.co
Running memtest now.
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
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.
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?
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.
@cpc2004: I notice that you are able to pull apart and read the dump files with great accuracy. I am constantly trying to find new tools to aid in diagnosing BSOD errors and was wondering if you would offer up what you are using to read the dump files. Your time and answer is greatly appreciated. Thanks in advance.
Business Accounts
Answer for Membership
by: cpc2004Posted on 2005-07-09 at 13:09:42ID: 14404781
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\SYSTE