BSOD BAD_POOL_HEADER. Not sure what to do?

Toggle sidebar Toggle sidebar
KingLira

KingLira

Reputable
Jan 31, 2015
27
0
4,530
Hello to everyone that reads this. BSOD BAD_POOL_HEADER for a while now and im not really sure whats going on. I open the crash dumps which im not all that sure how read. so i googled it and found out that most of these are caused by Norton which I do have installed and i been able to mach the PROCESS_NAME with a few i found online so i thought that was my problem. but today i got one that the PROCESS_NAME says System and on top of that says WIN8_DRIVER_FAULT. So now im not sure what happen. I've checked my drivers and they are up to date.

What i was doing when it happen was downloading GTA 5 from steam and writing my paper with Word. other then that nothing else was running well Norton was in the background but im not sure if that's what caused it at this moment. anyone got any ideas? Ill post the bug check below.

My pc is about 5 months old give or take

Spec:
Mobo: Z97-GD65 GAMING (msi)

CPU: i7 - 4790k 4.0ghz (not over clocked but will sometimes run as high as 4.30 some intel boost thing that's in the CPU itself is what i understand from the box.)

Gx card: Nvidia GeForce GTX760

RAM: 2 X 8GB DDR3 1600Mhz (total 16GB)

HDD: 1TB HDD

PSU: 750W cx Corsair

Win 8 64-bit installed


this is what the bug check said:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, ffffc000715fbcd0, ffffc0007157bcd0, ffffc000715fbcd0}

*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
Probably caused by : SYMEVENT64x86.SYS ( SYMEVENT64x86+eddd )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
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 then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: ffffc000715fbcd0, the pool entry being checked.
Arg3: ffffc0007157bcd0, the read back flink freelist value (should be the same as 2).
Arg4: ffffc000715fbcd0, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR: 0x19_3

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 1

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

DEVICE_OBJECT: ffffffff80000b30

LAST_CONTROL_TRANSFER: from fffff803662c27c1 to fffff8036616dca0

STACK_TEXT:
ffffd000`238aac18 fffff803`662c27c1 : 00000000`00000019 00000000`00000003 ffffc000`715fbcd0 ffffc000`7157bcd0 : nt!KeBugCheckEx
ffffd000`238aac20 fffff800`7eb22aec : ffffe000`00000004 ffffe000`fb1188c8 ffffc000`745f7b30 ffffc000`00000001 : nt!ExAllocatePoolWithTag+0x18d1
ffffd000`238aacf0 fffff800`7eb3c637 : ffffc000`5e3fd701 ffffe000`fb110011 fffffa80`0c5d3800 fffff803`6608fd8e : Ntfs!FindFirstIndexEntry+0x28c
ffffd000`238aad80 fffff800`7eb1dd99 : ffffc000`728f15a0 ffffc000`5e3fd780 ffffe001`01f503f8 00000000`0000002a : Ntfs!NtfsRestartIndexEnumeration+0x147
ffffd000`238aafd0 fffff800`7eb3a652 : 00000000`00000000 ffffe001`01f50010 00000000`00000000 ffffe000`fb2f40c0 : Ntfs!NtfsQueryDirectory+0x9c9
ffffd000`238ab380 fffff800`7eb3ab46 : 00000000`00000000 ffffe001`01f50010 ffffe001`01f50001 ffffd000`238ab480 : Ntfs!NtfsCommonDirectoryControl+0xa2
ffffd000`238ab3c0 fffff800`7e63bb1e : ffffe001`01f503f8 ffffe001`01f50010 ffffe000`fb1188c8 ffffd000`238ab3e8 : Ntfs!NtfsFsdDirectoryControl+0xc6
ffffd000`238ab430 fffff800`7e63a0c2 : ffffd000`238ab4f0 ffffe000`fb67ba50 ffffe000`fe62f640 ffffe001`01f50010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2ce
ffffd000`238ab4d0 fffff803`663bf578 : 00000000`00000002 ffffd000`238ab5b1 ffffe000`fe62f640 ffffe000`fe62f640 : fltmgr!FltpDispatch+0xb2
ffffd000`238ab530 fffff803`663bf3ff : ffffffff`80000b30 00000000`00000000 00000000`00000000 ffffe000`fa5ba880 : nt!IopSynchronousServiceTail+0x170
ffffd000`238ab600 fffff803`661794b3 : 00000000`00000001 00000000`00000000 00000000`00000060 00000000`38766553 : nt!NtQueryDirectoryFile+0xcb
ffffd000`238ab6c0 fffff803`66171900 : fffff800`7f451ddd 00000000`00000000 00000000`00000000 ffffc000`7e420d20 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`238ab8c8 fffff800`7f451ddd : 00000000`00000000 00000000`00000000 ffffc000`7e420d20 ffffc000`00000000 : nt!KiServiceLinkage
ffffd000`238ab8d0 fffff800`7f451095 : ffffe000`fb720f20 00000000`00000000 ffffc000`727841c0 ffffc000`825c7ae0 : SYMEVENT64x86+0xeddd
ffffd000`238aba80 fffff800`7f4504dd : 00000000`000023f0 ffffe000`00000040 00000000`00000000 ffffd000`233ec300 : SYMEVENT64x86+0xe095
ffffd000`238abac0 fffff800`7f4524b5 : ffffd000`233ec3f0 ffffd000`233ec490 ffffe000`fb720f20 00000000`00000001 : SYMEVENT64x86+0xd4dd
ffffd000`238abb10 fffff803`660ca6bc : ffffe001`01e8a1c0 fffff800`7f452470 ffffe000`fa5ba880 fffff803`00000000 : SYMEVENT64x86+0xf4b5
ffffd000`238abb50 fffff803`6611d36c : 00000000`00000001 ffffe000`fa5ba880 00000000`00000080 ffffe000`fa5ba880 : nt!ExpWorkerThread+0x28c
ffffd000`238abc00 fffff803`661742c6 : fffff803`66320180 ffffe000`fa5ba880 fffff803`66379a00 ffffe000`fa7ed290 : nt!PspSystemThreadStartup+0x58
ffffd000`238abc60 00000000`00000000 : ffffd000`238ac000 ffffd000`238a6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
SYMEVENT64x86+eddd
fffff800`7f451ddd 85c0 test eax,eax

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: SYMEVENT64x86+eddd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SYMEVENT64x86

IMAGE_NAME: SYMEVENT64x86.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 51f32ff2

FAILURE_BUCKET_ID: 0x19_3_SYMEVENT64x86+eddd

BUCKET_ID: 0x19_3_SYMEVENT64x86+eddd

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x19_3_symevent64x86+eddd

FAILURE_ID_HASH: {8a9ed9bc-babc-c0cc-0140-f0ce5fdad789}

Followup: MachineOwner
---------
 
Solution
J
yep, you can but bugs like this don't actually have to be in the actual RAM modules, they can be timing errors in the BIOS settings. Best to run the memtest and find a bad location in RAM, move the RAM to new slots and run the test again and find that the bad spot moved with the RAM. That way you know it is the RAM and which one you should remove.

if you move the ram to different slot, it can just be bad secondary timings in your BIOS settings for the RAM.
(it is generally why you want to update the BIOS before you start testing, vendors fix the timing settings with BIOS updates)

Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
run memtest86 and confirm your memory works as expected.

the bugcheck looks like you got a single bit corrupted in your memory.

binary 1111 was saved as 0111 and the system caught it.

it can also be a driver problem, very hard to tell.

best to test with memtest86 and if you get a failure, reset your BIOS to defaults or update the BIOS
and run memtest86 again and see if you get a clean test run.
 
Upvote 0 Downvote
KingLira

KingLira

Reputable
Jan 31, 2015
27
0
4,530


Could i just switch them out with my new RAM that will be here tomorrow? I had already order some new ones last week since the ones i actually wanted to begin with were on sale on New Egg :3. or should i still test the Memtest86 which ill probably have to look up how to use but that's fine. As for the Bios i had to update them since i was getting a lot of blue screens when i first put this PC together and a friend recommend i try that and sure enough they stopped so really rather not go back to defaults. Its just this damn BAD_POOL_HEADER one i can not seem to fix.

And thank you for taking the time to help me.

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
yep, you can but bugs like this don't actually have to be in the actual RAM modules, they can be timing errors in the BIOS settings. Best to run the memtest and find a bad location in RAM, move the RAM to new slots and run the test again and find that the bad spot moved with the RAM. That way you know it is the RAM and which one you should remove.

if you move the ram to different slot, it can just be bad secondary timings in your BIOS settings for the RAM.
(it is generally why you want to update the BIOS before you start testing, vendors fix the timing settings with BIOS updates)



 
Upvote 0 Downvote
Solution
KingLira

KingLira

Reputable
Jan 31, 2015
27
0
4,530


Alright I'll give it go then thanks for the help
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom