BAD_POOL_CALLER error
This is a discussion about BAD_POOL_CALLER error in the Windows Hardware category; Hi all Started getting BAD_POOL_CALLER BSOD's yesterday, had about four in total now. Think its something to do with my USB controller on my Abit KT7A RAID. I recently bought a Thrustmaster Firestorm Dual Power Gamepad, and upgraded the software and drivers from Thrustmasters website.
Hi all
Started getting BAD_POOL_CALLER BSOD's yesterday, had about four in total now.
Think its something to do with my USB controller on my Abit KT7A RAID.
I recently bought a Thrustmaster Firestorm Dual Power Gamepad, and upgraded the software and drivers from Thrustmasters website.
Now I get the crashes.
Anyone had this sort of situation before?
Homer
Started getting BAD_POOL_CALLER BSOD's yesterday, had about four in total now.
Think its something to do with my USB controller on my Abit KT7A RAID.
I recently bought a Thrustmaster Firestorm Dual Power Gamepad, and upgraded the software and drivers from Thrustmasters website.
Now I get the crashes.
Anyone had this sort of situation before?
Homer
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Nov 13
Nov 16
0
2 minutes
Responses to this topic
Oops, double post
I get the same identical error! It is getting frustrating, because this happens 3-4 times A DAY! Here are my specs:
1 Ghz Athlon T-bird (OC'ed to 1.1Ghz)
Epox 8KTA2 (Socket A)
Enlight Case (4 5.25, 3 3.5)
384 MB Crucial PC133 cas2 (7ns)
Asus V7700 GeForce2 GTS 64MB DDR
SoundBlaster Live! Value
Western Digital 20.5 GB (ATA/66) 7200RPM
Plextor 12x/10x/32x A
Logitech iFeel (Optical)
Microsoft Internet Pro Keyboard
HP 3400Cse scanner
Linksys network (5 port)
US Robotics 56k ISA Model 5687-03
Thrustmaster NASCAR Pro Digital 2 Steering Wheel (w/ pedals)
KDS V190i 19" monitor
1.44 MB Floppy
Windows XP Pro
I turned off system reboot upon error to get the BSOD to stay up there instead of rebooting to BIOS.
Thanks,
Shamrock
1 Ghz Athlon T-bird (OC'ed to 1.1Ghz)
Epox 8KTA2 (Socket A)
Enlight Case (4 5.25, 3 3.5)
384 MB Crucial PC133 cas2 (7ns)
Asus V7700 GeForce2 GTS 64MB DDR
SoundBlaster Live! Value
Western Digital 20.5 GB (ATA/66) 7200RPM
Plextor 12x/10x/32x A
Logitech iFeel (Optical)
Microsoft Internet Pro Keyboard
HP 3400Cse scanner
Linksys network (5 port)
US Robotics 56k ISA Model 5687-03
Thrustmaster NASCAR Pro Digital 2 Steering Wheel (w/ pedals)
KDS V190i 19" monitor
1.44 MB Floppy
Windows XP Pro
I turned off system reboot upon error to get the BSOD to stay up there instead of rebooting to BIOS.
Thanks,
Shamrock
Damn, I just read yesterday morning in a German magazine an article about W2K BSODs and error codes. They had a listing of all recorded BSOD causes, and yours was there, I saw it.
However I can't remember it Ill look into it though...
However I can't remember it Ill look into it though...
Not win2k Dude..WinXP Pro
but thanks for looking into it!
Shamrock
but thanks for looking into it!
Shamrock
What's the chance that many of the error codes are identical in 2000 and XP? Maybe it's because they're based on the same freaking KERNEL ???? Think...
