- Blue Screen of Death Help
- Posted by Databoy2k on January 9th, 2006
Hey All,
I'm trying to troubleshoot a friend's computer. His machine is giving a BSoD
on account of a Bad_Pool_Caller. The first paramater is 0x43, wich the MSDN
says is "The current thread attempted to free a virtual address that was
never in any pool." This happens at logon - Windows successfully boots but
fails trying to log in. This happens in safe mode as well.
Can anybody give me suggestions on troubleshooting this? I've created a
Kernel mode memory dump, but I do not know how to acquire the dump file
without booting into windows, which is sadly not possible.
Can anybody help me interpret what COULD be wrong here? I don't understand
the "The current thread attempted to free a virtual address that was never in
any pool." What does this mean? Is it a device driver issue? Any
clarification would be greatly appreciated. Thanks so much!
--Databoy2k
- Posted by needlove on January 9th, 2006
have you tried "last known good configuration that worked"
"Databoy2k" <Databoy2k@discussions.microsoft.com> wrote in message
news:9E302641-678A-45A4-8124-C23991853641@microsoft.com...
> Hey All,
> I'm trying to troubleshoot a friend's computer. His machine is giving a
> BSoD
> on account of a Bad_Pool_Caller. The first paramater is 0x43, wich the
> MSDN
> says is "The current thread attempted to free a virtual address that was
> never in any pool." This happens at logon - Windows successfully boots but
> fails trying to log in. This happens in safe mode as well.
> Can anybody give me suggestions on troubleshooting this? I've created a
> Kernel mode memory dump, but I do not know how to acquire the dump file
> without booting into windows, which is sadly not possible.
> Can anybody help me interpret what COULD be wrong here? I don't understand
> the "The current thread attempted to free a virtual address that was never
> in
> any pool." What does this mean? Is it a device driver issue? Any
> clarification would be greatly appreciated. Thanks so much!
> --Databoy2k
>
- Posted by Unk on January 9th, 2006
On Sun, 8 Jan 2006 22:07:02 -0800, Databoy2k <Databoy2k@discussions.microsoft.com> wrote:
>Hey All,
>I'm trying to troubleshoot a friend's computer. His machine is giving a BSoD
>on account of a Bad_Pool_Caller. The first paramater is 0x43, wich the MSDN
>says is "The current thread attempted to free a virtual address that was
>never in any pool." This happens at logon - Windows successfully boots but
>fails trying to log in. This happens in safe mode as well.
>Can anybody give me suggestions on troubleshooting this? I've created a
>Kernel mode memory dump, but I do not know how to acquire the dump file
>without booting into windows, which is sadly not possible.
>Can anybody help me interpret what COULD be wrong here? I don't understand
>the "The current thread attempted to free a virtual address that was never in
>any pool." What does this mean? Is it a device driver issue? Any
>clarification would be greatly appreciated. Thanks so much!
>--Databoy2k
See if this helps: Right-hand column, 'C2: Bad Pool Caller"
http://aumha.org/win5/kbestop.htm
