• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Need help, bad_pool_caller

T

Traveler

Senior member
Ever since last night, my PC keeps crashing within a hour, bad_pool_caller.

I'm not sure what's going on. The last thing I remember was to have java updated and installed. It failed the first time because of bad connection. Then I restarted my machine and have it installed. Then I left my machine on to do bitorrent jobs.

This morning I found it crashed. For several times, I restart and start bitcomet to download. It keeps crashing within a hour. I don't believe it's bitcomet causing it because I've been using it for a while already.

What would cause bad_pool_caller? Any idea?
 
Sounds like a virus or something... most definately from bitcomet.

Have tried booting in safe mode? Run a virus scan if you can, try to find this bad_pool_caller.
 
As I searched through google, bad_pool_caller doesn't seem like a virus attack. It crashes with a blue screen giving out bad_pool_caller message.
 
whats the actual stop code of the blue screen? is anything overclocked by the way?
http://support.microsoft.com/kb/314492/en-us the article you read? i think you should use the windows debugger tool to troubleshoot the error, especially since you probably have several dump files about it by now. http://support.microsoft.com/kb/315263/ in additon to that, if you find that the things the bluescreens are bombing out on are slightly different and dont seem related, run memtest+ and see if the memory is causing the problem.

if your to lazy to read that MS article, below is a summary i go off of..

Most of the time installing Windows Debugger, and using it to check the dump file will tell why windows crashed. after installing run !analyze -v and lmv commands to find out what did it.
**** after dbg_x86_6.6.07.5.exe installed, open windbg, set FILE|symbol file path to click "reload" box, then ok.
SRV*c:\local cache*http://msdl.microsoft.com/download/symbols

**** then file|open crash dump and run the commands

!analyze -v will tell you the error, click the link on the drive
under Debugging Details:
DEFAULT_BUCKET_ID -tells the general category of the failure
IMAGE_NAME -tells what driver is at fault, like if DRIVER_FAULT
click on the driver highlighted under MODULE_NAME it tells info like path to that module

lmv -tells loaded modules in detail, then click edit|find for that driver listed under IMAGE_NAME
 
Originally posted by: AFurryReptile
Sounds like a virus or something... most definately from bitcomet.

Have tried booting in safe mode? Run a virus scan if you can, try to find this bad_pool_caller.
Click to expand...


Why do people insist on opening their mouth when they have absolutely no idea what they are talking about?

Most commonly, Bad_Pool_Caller and the related errors are due to either a corrupted driver in the system or due to a USB device / cable that isn't playing nice.

Do a search for "Bad Pool Caller" without the underscores and WITH the quotes on google and you will find many suggestions on what to try.
 
Another thing I did before this started was to update video card driver with ATI's latest Radeon driver.

Here is what I got with the blue screen:

==================================================
A problem has been detected and windows has been shut down to prevent damage
to your computer.

BAD_POOL_CALLER

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical information:

*** STOP: 0x000000C2 (0x00000007,0x00000CD4,0x02100003,0x88C4EAD8)

Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.
===================================================


I tried with my BIOS. But my Asus P5P800-VM does not have option for caching or shadowing.
 
Don't worry about that then. Just start in safe mode and remove all of your video card drivers, then reboot and reinstall them off of the installation disk that came with the card.

What card do you have?

I hope you didn't try to install, say, ATI drivers on a, say, Sapphire card....
 
I uninstalled the video driver, but it detected the same driver and used it again once windows restarted. I have no old backup driver to replace it. That was a day ago. And the machine crashed as I found out.

I switched to an old video card, a rage 128 card. That was a hour ago. So far so good. Hopefully it won't crash. If not, then the problem was certainly from ati's latest video radeon driver.
 
~_~ it just crashed again.

It might last 3 hours more, but it crashed. And I still don't know what the cause is.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top