[tinman283]

Hello, I have a similar problem as discribed below, AOL ran fine on my computer for about a year and a half. Then I started to get the BSOD windows crashes with the bad_pool_header as noted below. Uninstalled AOL reinstalled AOL with no change, it does the same with all AOL products (desktop/older versions of AOL). I don't think its a hardware problem because I use the AOL toolbat through the Internet Explorer without any problems. I have seen the same issue from other people on the net, but no one has an answer. The below topic I found on your site was never completed. The link to the orginal was====>http://www.geekstogo...L-t224850.html. Thanks, Steve



hi guys n gals,
here is my problem!
Out of the blue, I started getting the blue screen when opening aol. It was working flawlessly for over a year before this.
the first time it did this, i was using aol, and all of a sudden, there was the blue screen.
i removed that version of aol, and have downloaded both older versions and the most recent, no change. as soon as it tries to connect (via my aircard), it goes to the blue screen.
i have downloaded and used a couple of registry scans, no change. i swapped the ram from my wifes laptop (same make etc) to mine, no change.
I have Norton 360 premier, and it says no problems after scans. the windows defender gives me an error of "security center service is turned off", but when i try to activate it, i get "security center can't be started". i can run scans from defender, but always get the error message at startup. never did this before the blue screen.
i have changed the virtual memory settings as per a tech advise line. no change.
i got 2 cans of compressed air and used them both. i could not remove the cover for my laptop (satellite a215-s4747) so i used the air in all the openings i could find. after doing this, it did start aol and it ran fine for about an hour or so, then the same blue screen.
i have searched and searched, and everything from bad ram, to bad software comes up! i am no computer genius but do follow the instructions as best i can.
here are the messages on the blue screen of death!
"BAD_POOL_HEADER"
then warning etc.
then
"STOP: 0x00000019 (0x00000020, 0x85251320, 0x08030009)"

[Advertisements]

Locate the memory dumps associated with this error (usually in C:\Windows\Minidump - it may be hidden), zip them up and upload them to your next post. We'll have a look at 'em and let you know what we find.

[usasma]

Locate the memory dumps associated with this error (usually in C:\Windows\Minidump - it may be hidden), zip them up and upload them to your next post. We'll have a look at 'em and let you know what we find.

[tinman283]

Hello, the file size is bigger than the 500K allowed even when zipped, so I am sending part of the file. Thanks, Steve

Attached Files

•  Minidump2.zip   442.85KB   349 downloads

[usasma]

The 4 dumps from 28 April all point to ATWPKT2.SYS
This is a part of the AOL Connectivity service (more info here: http://www.file.net/...twpkt2.sys.html )

I'd suggest downloading a new copy of the AOL software, then uninstalling the current software.
Then reboot and install the new copy.

[tinman283]

Hello, I have already installed/reenstalled the AOL software using AOL 9.0VR and a newer version 9.5 with the same crashes, I can cancel the connectivity search and manually enter the access source. It will work for a while but will shut down with the same "Bad_Pool_Header" error. The funny part of this is the fact I ran AOL on this computer for a year and a half with no problems. I connect to the internet using a Verizon USB70 card. I will check the AOL site for any additional information on that file, currently the file is nowhere to be found on the hard drive. Thanks, Steve

[usasma]

It's possible that something in the chain (from your computer to the internet) isn't compatible with the AOL Connectivity service.
Here's a link to an AOL troubleshooting page for this error: http://help.channels...rticleId=219969

[tinman283]

It's possible that something in the chain (from your computer to the internet) isn't compatible with the AOL Connectivity service.
Here's a link to an AOL troubleshooting page for this error: http://help.channels...rticleId=219969


The article you mentioned pertains to windows 98, XP, ME, 2000, my system is vista. I will download the program, reboot and install and I will let you know what happens. Thanks, Steve

[tinman283]

Hello, downloaded AOL 9.5, rebooted the computer and then I reinstalled AOL 9.5, I still got the BSOD with the problem bad_pool_header when AOL looks for a way to connect. I am going to manually enter the information for the USB720 connection and see what happens then. The below message is the problem report from windows. Maybe you can tell something from this error report. Thanks, Steve


Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini050209-02.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 19
BCP1: 00000020
BCP2: 85299D88
BCP3: 85299DA0
BCP4: 08030005
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

[usasma]

From what you've provided, this dump is similar to the others that I looked at. The BCC (Bug Check Code) is the same as the others (STOP 0x19) and the first parameter is the same also (0x20). This means that the "The pool block header size is corrupt."

To further check it out, you can run Driver Verifier with the Pool Checking options enabled - but, frankly, I don't think that this will yield any different results. The issue here is a problem with ATWPKT2.SYS - and AOL's way of dealing with it is to suggest workarounds (rather than fixing their file).

The AOL manual fix should work for Vista also - but I'm not sure of the construction of the downloaded fix (if it's looking in the correct places for the file). I'd try the downloaded fix and if you're still getting BSOD's, then there's likely to be another copy of it on your system.

You can also try this free program to stop the ATWPKT2.SYS driver from loading: http://www.microsoft...s/Autoruns.mspx

Here's a copy of the Mini042809-04.dmp dump file. I've bolded the significant parts. You can either upload your dump files, or you can perform the analysis yourself using this link: http://usasma.vox.co...ed-02oct08.html

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\Downloads\_DumpFiles\Minidump2\Mini042809-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81c01000 PsLoadedModuleList = 0x81d18c70
Debug session time: Tue Apr 28 17:23:47.769 2009 (GMT-4)
System Uptime: 0 days 0:03:40.502
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 85d97280, 85d97298, 8030007}

*** WARNING: Unable to verify timestamp for ATWPKT2.SYS
*** ERROR: Module load completed but symbols could not be loaded for ATWPKT2.SYS
Probably caused by : ATWPKT2.SYS ( ATWPKT2+1613 )

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

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: 00000020, a pool block header size is corrupt.
Arg2: 85d97280, The pool entry we were looking for within the page.
Arg3: 85d97298, The next pool entry.
Arg4: 08030007, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 81d38868
Unable to read MiSystemVaType memory at 81d18420
85d97280

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: AOLacsd.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81cef00c to 81cce0e3

STACK_TEXT:
87f6ab04 81cef00c 00000019 00000020 85d97280 nt!KeBugCheckEx+0x1e
87f6ab7c abd2a613 85d97288 00000000 000007ff nt!ExFreePoolWithTag+0x17f
WARNING: Stack unwind information not available. Following frames may be wrong.
87f6abbc abd2aa08 87f6abd0 87f6abd4 81cee53f ATWPKT2+0x1613
87f6abec abd2ad06 85c45f88 803d1c78 963f0ed0 ATWPKT2+0x1a08
87f6ac2c 81cbcfd3 85743368 963f0e60 963f0e60 ATWPKT2+0x1d06
87f6ac44 81e4d5e5 85528810 963f0e60 963f0ed0 nt!IofCallDriver+0x63
87f6ac64 81e4dd8a 85743368 85528810 01ae4300 nt!IopSynchronousServiceTail+0x1d9
87f6ad00 81e37a5d 85743368 963f0e60 00000000 nt!IopXxxControlFile+0x6b7
87f6ad34 81c58a1a 00000344 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
87f6ad34 778c9a94 00000344 00000000 00000000 nt!KiFastCallEntry+0x12a
03b7f314 00000000 00000000 00000000 00000000 0x778c9a94


STACK_COMMAND: kb

FOLLOWUP_IP:
ATWPKT2+1613
abd2a613 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: ATWPKT2+1613

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ATWPKT2

IMAGE_NAME: ATWPKT2.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 48909605

FAILURE_BUCKET_ID: 0x19_20_ATWPKT2+1613

BUCKET_ID: 0x19_20_ATWPKT2+1613

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

Edited by usasma, 02 May 2009 - 06:46 PM.

[tinman283]

Hello, I changed the file extension of the file ATWPKT2.SYS to ATWPKT2.OLD in the windows system folder and the AOL folder, this caused the AOL program to skip the step looking for a connection and went directly to the the connection setup, this could either be done manually of automatically. So far I haven't had a crash of the 9.5 version of AOL. I still don't understand how the computer could have run for 1.5 years then starts to have the problem unless that file was never there and then installed with one of AOL updates. Steve

[usasma]

Programs and drivers are complex pieces of software. A small change to them can cause issues that don't normally show up. Also, they may not change at all, but the other software that they access may have - and they may not be able to cope with that change (hence the BSOD).

[tinman283]

I changed the file extension of the file ATWPKT2.SYS to ATWPKT2.OLD and its been over a month without a problem. Thanks again, Steve

[technicure]

Following What was Said above and a little bit of PC Know how have resolved this issue

Fixed one pc By jsut changing the ATWPKT2.sys in System32/Drivers to ATWPKT2.old

However this didnt work on a secondary Computer

Solution...

Go to C:/Programfiles/Common files/ aol/ acs and change both the ATWPKT2 files in there to .old aswell. this resolved my issue.

Stops Aol Connectivity Service from Starting.

Good luck

Technicure.co.uk

[Reza_Sadeghi]

Hoooorrraaa
I had this Problem with AOL 9.5 on Windows 7 x86 exactly issue explained on this Topic.
I am so haapy found this Solution on this Topic by using Search on Google i found it.

after read this Topic i renamed all "ATWPKT2.sys" on C:/ Drive to "ATWPKT2.old" (these are 4 files) and for now my Problem crashing and show Blue Screen while running AOL 9.5 has solved.
Thank you so much for this nice Guidance.

anyway...
my another problem is that i can't completely uninstall AOL software package.
in ADD/Remove Program found just "AOL Uninstaller (chose which products to Remove)" and whenever i double click it a window appear shows just some AOL applications to Remove.
i removed all of them but i want to Remove AOL 9.5 from my computer colmpletely but i doesn't uninstalled.
an AOL icon is reamined on System Tray still and i don't like using AOL at all.

could you please tell me how to remove AOL completely or would you please try to Uninstall AOL from your system too and show me the correct way to Uninstall completely AOL 9.5 from Windows OS?

[tota]

I recently got this exact same problem. I got the same message as tinman. I can't use my AOL software because it will cause the blue screen.AOL was not able to help. My Norton antivirus was completely knocked off and it was giving a message about no connectivity and as if it was trying to find a modem - never got this message from Norton whether I was on or off line in the past!

What is the problem here?

Edited by tota, 18 July 2010 - 05:33 PM.