Link to home
Start Free TrialLog in
Avatar of Squiddy2
Squiddy2

asked on

BSOD Driver error

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
Avatar of cpc2004
cpc2004
Flag of Hong Kong image

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\Session 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.)

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
Avatar of Squiddy2
Squiddy2

ASKER

Thanks for your prompt reply...

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

Running memtest now.
ASKER CERTIFIED SOLUTION
Avatar of cpc2004
cpc2004
Flag of Hong Kong image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I just purchased Symantec Security 2005 from their site and installed it. Still get the same BSOD :(
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.
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.
What is reply from Symantec? Your feedback will help us to resolve similar problem.
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.
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.
Thanks for your information. It is weired that your old RAM and Norton 2005 caused BSOD.  This is a valuable information.
@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.