zamnut6
02-14-2009, 07:32 PM
I have had my sr71c for a day and it was working fine. A few hours ago I came out of standby mode and my XP (tablet PC edition 2005, version 2002, sp3) computer went into blue screen. It said I have a BAD_POOL_HEADER. Now the only way that I can prevent this fault from happening is to pull out my sr71c and reboot. If I plug in the card now - the computer immediately blue screens. It also does this at some point during PC bootup if it has the card in it. Since I have installed the software for the card, I notice that during normal boot up, an application flashes on the screen then disappears (it seems to be about the same point that BSoD occurs if the card is inserted). I don't see any new application in the quick launch manager and the sr71c software did not install anything that appears under All Programs.
The driver I am using is the one included in the CD that came with the card. The disk says that it is a driver and management utility - but i dont see the management utility showing up anywhere. The software is called:
ubnt_sr71.exe and shows a date of 11/05/2008 3:38AM and is 4957KB. I didnt notice any updates available on the website.
Some processes now running on my PC: ACU.exe and ADU.exe (cisco) - I dont know if the ACU is new or an old one that I use to run. I do wireless testing so I have installed quite a few wireless cards on this PC. ACS.exe is not showing up as running.
I also use the src card, but it was not installed at the time of the fault.
Any help would be greatly appreciated. Let me know if I need to provide any other info.
The mini-dump as shown by windbg is shown below:
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: 00000020, a pool block header size is corrupt.
Arg2: 8a2fc000, The pool entry we were looking for within the page.
Arg3: 8a2fc128, The next pool entry.
Arg4: 1a250000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: 8a2fc000
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: acs.exe
IRP_ADDRESS: 8862ccc0
LAST_CONTROL_TRANSFER: from 8054b583 to 804f9f43
STACK_TEXT:
9ced1bb4 8054b583 00000019 00000020 8a2fc000 nt!KeBugCheckEx+0x1b
9ced1c04 804f4c20 8a2fc008 00000000 8862cd00 nt!ExFreePoolWithTag+0x2a3
9ced1c5c 804ff853 8862cd00 9ced1ca8 9ced1c9c nt!IopCompleteRequest+0xf4
9ced1cac 80503864 00000000 00000000 00000000 nt!KiDeliverApc+0xb3
9ced1cc4 804fb078 00000000 00000000 00000000 nt!KiSwapThread+0xa8
9ced1cec 805c075c 00000001 00000006 9ced1d01 nt!KeWaitForSingleObject+0x1c2
9ced1d50 8054162c 000001b8 00000000 00000000 nt!NtWaitForSingleObject+0x9a
9ced1d50 7c90e4f4 000001b8 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00cefa90 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
PROCESS_OBJECT: 89d8db28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: acs
IMAGE_NAME: acs.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x19_20_IMAGE_acs.exe
BUCKET_ID: 0x19_20_IMAGE_acs.exe
Followup: MachineOwner
---------
The driver I am using is the one included in the CD that came with the card. The disk says that it is a driver and management utility - but i dont see the management utility showing up anywhere. The software is called:
ubnt_sr71.exe and shows a date of 11/05/2008 3:38AM and is 4957KB. I didnt notice any updates available on the website.
Some processes now running on my PC: ACU.exe and ADU.exe (cisco) - I dont know if the ACU is new or an old one that I use to run. I do wireless testing so I have installed quite a few wireless cards on this PC. ACS.exe is not showing up as running.
I also use the src card, but it was not installed at the time of the fault.
Any help would be greatly appreciated. Let me know if I need to provide any other info.
The mini-dump as shown by windbg is shown below:
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: 00000020, a pool block header size is corrupt.
Arg2: 8a2fc000, The pool entry we were looking for within the page.
Arg3: 8a2fc128, The next pool entry.
Arg4: 1a250000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: 8a2fc000
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: acs.exe
IRP_ADDRESS: 8862ccc0
LAST_CONTROL_TRANSFER: from 8054b583 to 804f9f43
STACK_TEXT:
9ced1bb4 8054b583 00000019 00000020 8a2fc000 nt!KeBugCheckEx+0x1b
9ced1c04 804f4c20 8a2fc008 00000000 8862cd00 nt!ExFreePoolWithTag+0x2a3
9ced1c5c 804ff853 8862cd00 9ced1ca8 9ced1c9c nt!IopCompleteRequest+0xf4
9ced1cac 80503864 00000000 00000000 00000000 nt!KiDeliverApc+0xb3
9ced1cc4 804fb078 00000000 00000000 00000000 nt!KiSwapThread+0xa8
9ced1cec 805c075c 00000001 00000006 9ced1d01 nt!KeWaitForSingleObject+0x1c2
9ced1d50 8054162c 000001b8 00000000 00000000 nt!NtWaitForSingleObject+0x9a
9ced1d50 7c90e4f4 000001b8 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00cefa90 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
PROCESS_OBJECT: 89d8db28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: acs
IMAGE_NAME: acs.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x19_20_IMAGE_acs.exe
BUCKET_ID: 0x19_20_IMAGE_acs.exe
Followup: MachineOwner
---------