Solved Bad_Pool_Header BSOD; no real reason for it

[Rufin]

Hey.
So I just got a BSOD with a reason cited as Bad_Pool_Header. It just popped up while I was browsing the internet. Wasn't watching any videos or anything, just going through some forums.

I've attached the file, any help is greatly appreciated.

 

[Skylais]

IDSvia64.sys : Norton internet security. Ok 1st i suggest backing up your information with norton, just in case if u want to re install it. Next uninstall it using the setup in my link here : https://www.dropbox.com/sh/xvzy3qdl1yrr6e1/GC23HmVvYK
I will look further into the dumps soon.
Also i suggest this free antivirus here : http://windows.microsoft.com/en-US/windows/products/security-essentials
IT is basic, really strong, and free.
I also want u to use this : http://biosagentplus.com/ami.php
Edit :
NEXT
1.: cfosspeed6.sys: cFosSpeed - The Internet Accelerator
I am not sure what this is, but i belive its some kind of software. I suggest uninstalling it as well, and if you want to optimize internet speed. Follow my link : https://www.dropbox.com/sh/qsojbfmeg9jr92u/lKvDjXuRPo

2.atikmdag.sys: http://support.amd.com/us/gpudownload/windows/Pages/auto_detect.aspx
Update them drivers automatically with that link.

 

[Rufin]

The Internet Accelerator I'm not going to get rid of because it came with my Mobo's drivers. Last time I messed around with things that came with the mobo bad things started happening, so I'm just letting it sit for now.

Following up on everything else you recommended though. Thanks.

 

[Rufin]

BSOD Memory_Management

As stated above.
A few hours ago I had a Bad_Pool_Header BSOD (to try and fix I uninstalled Norton, installed Windows Security Essential) and now I just got one with Memory_Management stated as the problem.
This occurred while I was running a quick scan with WSE.

 

[koolkat77]

Please do not create new threads. Update your dumps to your existing thread.

Seeing the bug checks cause:

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

Run memtest on each stick of ram for 8 passes (overnight preferable)
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

If the ram tests come out clean we'll enable driver verifier.

 

[Rufin]

Just had another BSOD, this time while playing World of Warcraft, about 15 minutes after logging in.
This is getting a bit out of hand.

As for the RAM test, how do I make my USB Boot first? I went into my BIOS with F2 but I couldn't find a setup option.

 

[Rufin]

Another BSOD while playing WoW, about 5 minutes in this time.

 

[koolkat77]

Go through your mobos manual to search for the boot menu key, its different in brand to brand, model to model.

Since its crashing during games, temp, dust, driver dates and the card itself has to be checked..

Use speccy to monitor temps:
:ar: Speccy - System Information - Free Download

 

[Skylais]

hmm as i was looking at another recent dump i found this :Unable to verify timestamp for SRTSP64.SYS = Symantec Real Time Storage Protection. I am not sure, but you may want to try uninstalling other Symantec programs.

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Skyler\AppData\Local\Temp\Rar$DIa0.885\092812-25381-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03092670
Debug session time: Fri Sep 28 00:24:48.660 2012 (UTC - 5:00)
System Uptime: 0 days 1:33:01.472
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa8006636c80, fffffa8006636c00, fffffa8006636c00}

*** WARNING: Unable to verify timestamp for [COLOR="Red"]SRTSP64.SYS[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

Followup: Pool_corruption
---------

1: 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: fffffa8006636c80, the pool entry being checked.
Arg3: fffffa8006636c00, the read back flink freelist value (should be the same as 2).
Arg4: fffffa8006636c00, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ff74b3 to fffff80002ecd1c0

STACK_TEXT:  
fffff880`031baa48 fffff800`02ff74b3 : 00000000`00000019 00000000`00000003 fffffa80`06636c80 fffffa80`06636c00 : nt!KeBugCheckEx
fffff880`031baa50 fffff880`087962d4 : 00000000`00000003 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`031bab40 00000000`00000003 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`0b127000 : SRTSP64+0x862d4
fffff880`031bab48 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff8a0`0b127000 fffff880`0b65cbbc : 0x3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a53
fffff800`02ff74b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a53

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

Followup: Pool_corruption
---------

It could be worth a shot to remove other NORTON programs, as they do cause quite a few issues sometimes. This is all i wanted to say, but KoolKat is much much more experienced

 

[Rufin]

Well it wasn't a temperature problem.

As for Norton, it's all gone. I'll take a look at that Symantec thigamabob.

 

[Rufin]

All right, I return. S
o, I'd been having blue screens on my newly built computer for a while now. These always occurred shortly after entering WoW and randomly while on other games (Diablo 3, Supreme Commander, and Black and White 2 [the god game, not Pokemon] all suffered as well). Occasionally they would occur when browsing the internet but this happened only twice I believe.
A list of what I can remember being problems:
Bad_Pool_Header
0x3b
0x24
System_Service_Exception
0x7
0x0c5
IRQL_Not_Equal
Memory_Management

There were probably others.

ANYWAYS

Today the computer told me my Hard Drive was screwed and to back up my data before shutting down. So I shut it down, and now when I log onto my OS (Windows 7) I get to my desktop for a second before the computer shuts down and I get "No Signal" from the monitor.

This all brings me to my grand question: Is there a high likelihood that it was my HDD that was causing the BSODs, or is there still a possibility it was my RAM or something?