Bad pool header BSOD

[impudence]

Everytime I download large files from the internet, I eventually get a BSOD which says there is a bad pool header. Does anyone have ANY idea what could be causing this??? It usually happens after about an hour or two of downloading. It happens when I download from WinMX or when I'm downloading game patches from gamespot. I have searched the internet and found little explaining a resolution to this problem. But this is very frustrating. Please see my rig for spec on my PC.

Thanks In Advance

 

[impudence]

bump

 

[stevty2889]

Your link to your rig isn't working..

Are you doing any overclocking? The only time I've seen that specific error is when I have my prescott running at more than 4ghz, not sure other than that..

 

[impudence]

Sorry about the rig link, I added a description to my sig. Anyway I am not overclocking at all. This computer hasn't been overclocked because it obviously has enough trouble running at stock. Anyway it BSOD'ed twice last night I wrote down all the numbers associated with it:

0x00000019 (0x00000020, 0x8855a20, 0x88855a48, 0x0a0500bd) The last three sets of numbers change everytime it happens but the first two don't. I knkow the first number is the bad pool header error code but I dont know about the rest.

It seems to happen the most when I have multiple downloads happening at once. But will happen with only one download.

Thanks in advance for any help

 

[montag451]

Can you also look in event viewer.
See if there are any X's that have the same timestamp as your bsod's

 

[impudence]

I just looked no x coincides with the BSOD's. The only thing that happens at the same time is that the Event log service was started and then one second later there is a save dump with the following description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x8879c858, 0x8879ca48, 0x0a3e0008). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

 

[montag451]

Have you installed in hardware recently?

 

[impudence]

The only thing I installed was another stick of ram, but the problem happened before that. Just in case however I intend to run memtest once I can find my floppy drive

 

[impudence]

Well it just happened again and there was an event with an x that happened at the same time. Here it is:


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/12/2005
Time: 4:14:55 PM
User: N/A
Computer: LUCY
Description:
Error code 00000019, parameter1 00000020, parameter2 8881d9b0, parameter3 8881da48, parameter4 0a13010c.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 38 31 64 39 62 30 8881d9b0
0040: 2c 20 38 38 38 31 64 61 , 8881da
0048: 34 38 2c 20 30 61 31 33 48, 0a13
0050: 30 31 30 63 010c

 

[montag451]

Could try setting the virtual memory to 0, reboot and delete the pagefile.sys file. Then set the virtual memory back to normal.Reboot.

 

[Smilin]

You've got pool corruption of some sort.

This is either a badly behaving driver or possibly a hardware failure. In the absense of any other types of dumps you can probably lean towards driver problems for starters.

You probably need someone to analyze this dump for you Pool corruption is one of the harder memory dumps to read so a Microsoft CPR escalation engineer may be needed. Since this would involve a $245 paid incident you may want to start with some of the basics to troubleshoot this instead.

First, be sure your BIOS and drivers for *everything* are up to the latest versions available. This includes not just video and sound, but NIC drivers, chipset drivers, anything.

Next, you'll want to enable driver verifier and special pool tagging. Driver verifier, to put it simply, will be very strict with drivers as they load. If one misbehaves it will immediately crash with a much more informative explanation about what failed. If, after enabling verifier, you crash with a particular driver as the culprit, replace that driver. Special pool tagging will cause a special tag to be placed at the end of pool allocations. It is illegal to touch these tags so if a misbehaving driver goes to corrupt something there is a chance it may touch a tag and cause a crash. If this happens you'll get an immediate pointer to the likely culprit.

If you get a CPR engineer from MS, he'll likely have you complete these steps right away. It puts more information in the memory dump that makes it possible to troubleshoot (nearly impossible to debug pool corruption without).

Troubleshooting this successfully on your own is going to take a LOT of luck. Let's hope updating drivers does the trick. Here is how to enable driver verifier:

1. From a command line, run "Verifier /flags 9 /all"
2. Reboot for changes to take effect.
3. Do NOT log in right away. There is a chance you'll have a crash as a faulty driver starts. If this happens, boot with last known good and it will undo your change. Once you log on, last known good is GONE so if you then crash you are stuck in a crash loop (tough to dig out from, but possible).
4. Once you wait a few minutes for all automatic services to start (say 5 min first time) go ahead a log in. Run as normal and hopefully the next crash will give a better indication of what's bombing.
5. If you no longer want driver verifier, run "Verifier /reset" to turn it off, reboot.

For special pool tagging, simply make the following registry changes and reboot to take effect.
To enable special pool tagging: http://support.microsoft.com/default.aspx?scid=kb;en-us;188831

Additional info for ya: http://support.microsoft.com/default.aspx?scid=kb;en-us;244617

I hope this helps. Reading a dump with pool corruption is well above my head I'm afraid.

 

[impudence]

Thanks that is an amazing amount of help!! I'll give your instructions a try and see what happens.

 

[imthebadguy]

whats your status on this? i just started getting this on my laptop today......i havent done anything to it either, it just started happening and it happens as soon as i log on