BAD_POOL_HEADER BSOD, not the first time computer has BSOD

[GCFSA]

Hey guys,

I recently have been getting some BSODs but this is the first 'BAD_POOL_HEADER' I would like to ask for some help in resolving this issue. Thankyou very much, attatched is my minidumps of ALL my previous BSODs.


Thanks in advance.

GCFSA


Edit: my computer is a HP Pavillion DV6 3132tx.

 

[Arc]

Hello GCFSA.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]BAD_POOL_HEADER (19)[/COLOR]
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and[COLOR=Red] then special pool applied to the suspect tags or the driver
verifier to a suspect driver.[/COLOR]
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00e8f25a0, The pool entry we were looking for within the page.
Arg3: fffff8a00e8f27c0, The next pool entry.
Arg4: 0000000005220010, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a00e8f25a0 Paged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800037f6cae to fffff800036cbfc0

STACK_TEXT:  
fffff880`03d70b68 fffff800`037f6cae : 00000000`00000019 00000000`00000020 fffff8a0`0e8f25a0 fffff8a0`0e8f27c0 : nt!KeBugCheckEx
fffff880`03d70b70 fffff800`039ace83 : fffff800`038c9600 fffff800`039ab730 fffff800`624e4d43 fffff880`04c5ee90 : nt!ExDeferredFreePool+0x12da
fffff880`03d70c20 fffff800`039aba6e : fffff8a0`15433cc0 00000000`361076d3 fffff8a0`00bef410 00000000`00000000 : nt!CmpFreeKeyControlBlock+0x123
fffff880`03d70c50 fffff800`036d5641 : fffff800`038692d8 fffffa80`03cebb50 00000000`00000000 fffffa80`03cebb50 : nt!CmpDelayDerefKCBWorker+0x33e
fffff880`03d70cb0 fffff800`03962e5a : fffff880`03d6c040 fffffa80`03cebb50 00000000`00000080 fffffa80`03cd7b30 : nt!ExpWorkerThread+0x111
fffff880`03d70d40 fffff800`036bcd26 : fffff880`03b67180 fffffa80`03cebb50 fffff880`03b720c0 fffff800`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03d70d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpFreeKeyControlBlock+123
fffff800`039ace83 e90effffff      jmp     nt!CmpFreeKeyControlBlock+0x36 (fffff800`039acd96)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!CmpFreeKeyControlBlock+123

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

Followup: MachineOwner
---------

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[GCFSA]

Hello GCFSA.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]BAD_POOL_HEADER (19)[/COLOR]
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and[COLOR=Red] then special pool applied to the suspect tags or the driver
verifier to a suspect driver.[/COLOR]
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00e8f25a0, The pool entry we were looking for within the page.
Arg3: fffff8a00e8f27c0, The next pool entry.
Arg4: 0000000005220010, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8a00e8f25a0 Paged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800037f6cae to fffff800036cbfc0

STACK_TEXT:  
fffff880`03d70b68 fffff800`037f6cae : 00000000`00000019 00000000`00000020 fffff8a0`0e8f25a0 fffff8a0`0e8f27c0 : nt!KeBugCheckEx
fffff880`03d70b70 fffff800`039ace83 : fffff800`038c9600 fffff800`039ab730 fffff800`624e4d43 fffff880`04c5ee90 : nt!ExDeferredFreePool+0x12da
fffff880`03d70c20 fffff800`039aba6e : fffff8a0`15433cc0 00000000`361076d3 fffff8a0`00bef410 00000000`00000000 : nt!CmpFreeKeyControlBlock+0x123
fffff880`03d70c50 fffff800`036d5641 : fffff800`038692d8 fffffa80`03cebb50 00000000`00000000 fffffa80`03cebb50 : nt!CmpDelayDerefKCBWorker+0x33e
fffff880`03d70cb0 fffff800`03962e5a : fffff880`03d6c040 fffffa80`03cebb50 00000000`00000080 fffffa80`03cd7b30 : nt!ExpWorkerThread+0x111
fffff880`03d70d40 fffff800`036bcd26 : fffff880`03b67180 fffffa80`03cebb50 fffff880`03b720c0 fffff800`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03d70d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpFreeKeyControlBlock+123
fffff800`039ace83 e90effffff      jmp     nt!CmpFreeKeyControlBlock+0x36 (fffff800`039acd96)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!CmpFreeKeyControlBlock+123

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

BUCKET_ID:  X64_0x19_20_nt!CmpFreeKeyControlBlock+123

Followup: MachineOwner
---------

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Thankyou for your reply, I will run DV and post any results in the next 48 hours.

 

[GCFSA]

Sorry about the late reply, I have done the DV check and have come up with one BSOD. here are the new dump files

Thankyou in advance.

 

[Arc]

Please make it sure that you have enabled DV properly. Follow it, step by step.
:ar: Driver Verifier - Enable and Disable

 

[GCFSA]

Thankyou for your reply, I'll re run DV and post the results.

 

[GCFSA]

Here are the results from the DV check

Thanks in advance

 

[Arc]

This one is verifier enabled, for sure. But, not showing a driver as a probable cause.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck A[/COLOR], {fffff9800ab9cf98, 2, 0, fffff80003b362b9}

Probably caused by : ntkrnlmp.exe ( nt!ViPendingCompleteAfterWait+49 )

Followup: MachineOwner
---------

So the root of the problem is in somewhere else.

A virus scanner amy sometimes cause such a situation. Uninstall Kaspersky using Kaspersky Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install those, and then run full system scans with both of them, one by one.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

 

[GCFSA]

Thanks for your quick reply, will run all the tests and post results. However, it may take me 2-3 days to complete them, until then, thankyou very much for your help so far.

Gabriel

 

[GCFSA]

I have run the virus/malware checks and they've come up with a few things detected, however, they wre just a few programs and were perfectly safe.

Then I proceeded to do the ram check, it came back with 13 errors, I've attatched a picture of it.

I have not yet run the GPU and CPU checks, should I or should I just change the ram stick?


Thankyou very much.

 

[Arc]

As RAM sticks are showing errors, you have to change those. You may either try to determine which stick is bad actually by following the Part 3: If You Have Errors: of the tutorial http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html; or just plan to replace a new kit.

After this replacement, if those crashes continue to occur, you may need to perform the further tests. But, upto that point, let us know the results with the replacement RAM.

 

[GCFSA]

Thanks for that reply.

I'll replace the ram but unfortunately, I dont think I'll be able to do this until next month. Is there any risk of using a faulty ram?


Thankyou very much for your help. It is greatly appreciated.


GCFSA


Edit: I'll certainly post after changing the ram, but that may take quite a while.

Edit 2: I only have one ram stick (4gb) so that's a definite that the ram is at fault, unless it's the motherboard but I would still need to get more ram sticks first.

 

[Arc]

Dont be in a hurry, do it only when you will have the opportunity.

 

[GCFSA]

I've managed to purchase some 2x4GB RAM and have run the ram test. it came up as being fine

thankyou so much for helping me solve this problem.

GCFSA

 

[Arc]

You are welcome. We are glad that we could help you.

If there is a further issue, let us know

 

[GCFSA]

Unfortunately.... my comp BSODed again.

attached are the dump files

 

[GCFSA]

My computer BSODed a second time today... I don't know what the problem is, but according to the 'title' given to the BSOD, im assuming it's got something to do with my comp not being supplied sufficient power?

Thanks in advance.

GCFSA

 

[Arc]

It is caused by Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer).

Irp is active with 4 stacks 2 is current (= 0xfffffa800e06aa18)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa8008726050 00000000 00000000-00000000    
[COLOR=Red]          Unable to load image \SystemRoot\system32\DRIVERS\netr28x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr28x.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
*** WARNING: Unable to verify timestamp for ndis.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
 \Driver\netr28x[/COLOR]
            Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 fffffa80086c7040 00000000 fffff80003911200-fffffa800a7ec5f0 Success Error Cancel pending
           \Driver\vwifibus    nt!PopSystemIrpCompletion
            Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800a7ec5f0    

            Args: 00000000 00000000 00000000 00000000

And that is somehow old.

fffff880`05c5c000 fffff880`05dac000   netr28x  T (no symbols)           
    Loaded symbol image file: netr28x.sys
    Image path: \SystemRoot\system32\DRIVERS\netr28x.sys
[COLOR=Red]    Image name: netr28x.sys
    Timestamp:        Mon Mar 07 07:23:24 2011[/COLOR] (4D743A94)
    CheckSum:         00156629
    ImageSize:        00150000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from MediaTek - Downloads Windows.

 

[GCFSA]

Thanks for you reply, my network card however, is the Ralink RT3090 802.11b/g/n WiFi Adapter (found under device manager-> network adapters). I'll update this one and see how things go.

Thankyou so much once again for helping me with my bsods

 

[GCFSA]

new BSOD error, most likely relating to GPU

Hey guys,

I was installing a new graphics card driver (whilst doing other things like browsing the web and working on a word document) and the computer bsoded whilst installing the driver. I have previously had BSODs before such as BAD_POOL_HEADER and NTFS_FILE_SYSTEM. I would like to ask if anyone would know how to resolve this issue.

attached are the log files of previous and current bsods (current one titled 102813-97921-01)

ps: I have tried to use the SF Diagnostic tool following all instructions, but even after it's finished, no file appears in the desktop. (I have right clicked- run as admin and the .exe is in the desktop)

Thankyou in advance.