Bad_pool_caller Error on Windows Vista

[Oshea]

My two systems are affected on lan with this error. There is some error related to bad pool caller. I had tried to run Repair setup but that does not worked out much. The first PC atleast works fine for some hours, but the second one is crashing instantly. My friend suggested me to update the motherboard drivers instantly. I did the same and Vista detected a new hardware. I do not know what was it, but it was related to some card reader. I have a usb hub attached to the system. So the first pc went fine after getting new drivers. But I was not aware that Vista will give Bluescreen for such silly thing. It is a plug and play device.

[KittyOH]

Somehow it looks that this topic is getting a bit out of road. Here I am facing issue with a dead pc. I had read the solutions in which ample of them had told to go in Safe Mode or simply hit Last Good Known Configuration. But that did not helped much. I also tried to run the Repair setup but that one is also weird. After checking all hardware and tested the ram stuff I had found no errors at all. I had performed clean boot also but that too does not helped much. I had also restarted my computer a tons of time. But still stuck on the same problem. Any better way to get this thing work without formatting the computer.

[mvagusta]

Let me open a new topic sought after because a lot of time on several forums, I have not found any solution to my problem. I went with Linux a few days ago, While maintaining a Windows partition (XP).

When I'm in Window systematically after about a minute, the computer turns off abruptly and the famous blue screen appears with the statement:
BAD_POOL_CALLER. After having informed on several sites, I think the problem is:

• A problem of USB devices (indeed, when I go back to Linux, it says "unclean shutdown, checking drives: dev/sda2 and dev/sda3 which corresponds to the USB ports);
• And / or a graphics card (when I am under Linux, and I click on "Hibernate", he says he has encountered a problem with the ndiswrapper driver, telling me that I'm 64-bit whereas Windows only supports 32-bit, whether I understood ). I also feel that since I made an update to Linux that this problem occurred in Windows, but I'm not sure.

Is good for the attempt to identify the problem, but now I do not know at all what to do to solve it. I add that when I go into safe mode, I do not encounter this problem and when I go to Device Manager, Windows tells me that my USB ports functioning properly.

I thank in advance those who take the trouble to help me a little

[opaper]

The fact that in Safe Mode all goes well is good news:thumbup1: :biggrin: . at least you know that it is not your OS. If you think it just an update to Linux, I'll suggest if the manager allows it to cancel all updates to return to the Linux core, and try to find what set update done everything by plan.

[mvagusta]

Hi,

So the situation is really worse In ironing Linux, he once again check the drivers (sda2 and sda3), that operation could not finish. A screen bizarre happened, I did more or less nothing. After rebooting my PC was complete vacuum, I can not even get to grub, it says in effect "grub loading 1.5, error 17". And I am completely blocked ...

Upon reflection, I wonder if the problem is not that I have Windows XP 32-bit and I've installed Ubuntu 64-bit version (my processor is a 64-bit). I did not read about this, but could this such a way incompatible? I created a partition "My Documents" to which I go from Windows as Linux.

Thank you again for your help

[opaper]

this partition, you have created taking in the windows partition? if so, thou hast done using Linux software?

If this is, this may explain the crash of windows, but not that of Linux.


After, strange on your screen, there was not something "Kernel Panic!"?
If yes, you're wrong crossed, otherwise I suggest you start a live CD Linux distribution, if possible, the same as you have installed, and if you can boot from the CD. Then backup your important data by burning DVD-RW.

After, it depends. either you arrive a repair by changing your GRUB to the hard corrupted files (I do not know, but I'm not >_<), specialist or you reinstall Linux is that you see. (if necessary, reformats )

For windows, you need ais its CD / DVD on hand. You boot it and you doing "repair". If no improvement, you restarts in boot from the CD / DVD, you done "install Windows", and you check the format partition "before starting the install.

If still no improvement, you can always try to voodoo magician in your PC .:holloween

[mvagusta]

this partition, you have created taking in the windows partition? if so, thou hast done using Linux software?

Initially, I had a single partition, which contained Windows. Then I proceeded exactly as described in the tutorial Linux site. That is to say that I made two partitions from the Ubuntu Live CD: one for Ubuntu, and another for my documents (both in 'ext3').

It is in this way should be done or did I planted?

If this is, this may explain the crash of windows, but not that of Linux.

Uh yes, finally I know nothing But you think, having a XP 32-bit and 64-bit Ubuntu can cause problems? This is something I would really be sure because I need to use the faster Linux. On the other hand, if this poses no problem, then I do not understand at all where the problem I have encountered.

After, strange on your screen, there was not something "Kernel Panic!"?
If yes, you're wrong crossed, otherwise I suggest you start a live CD Linux distribution, if possible, the same as you have installed, and if you can boot from the CD. Then backup your important data by burning DVD-RW.

Yes I think it was something recorded in connection with the kernel. Here I have to reinstall XP, and for now everything is working perfectly at this level touch wood :thumbup1: :ohyeah:

After, it depends. either you arrive a repair by changing your GRUB to the hard corrupted files (I do not know, but I'm not >_<), specialist or you reinstall Linux is that you see. (if necessary, reformats )

For windows, you need ais its CD / DVD on hand. You boot it and you doing "repair". If no improvement, you restarts in boot from the CD / DVD, you done "install Windows", and you check the format partition "before starting the install.

In fact it is a new PC, so I anyway on my old PC, so from that point of view then I do not have too much stress of losing important files.

Given that Windows has air refonctionner correctly, I will try to reinstall Linux. The question is whether I take the 32 or 64 bits of Ubuntu, so I await your response with impatience

If still no improvement, you can always try to voodoo magician in your PC

LOL, hope that I should not go that far

[KittyOH]

The name calling was quite impressive. It's good that you don't represent a business here.

I have no idea nor do I care what your silver rating represents. It's certainly not for reading requests and giving valid suggestions... nor for professionalism since you seem to seriously lack that ability.

[Hawkin's]

I am facing the issue on a old system which has Windows XP SP3 installed in it. The system is a EMachine . Along with Windows there was Ubuntu installed on the same. Now the issue is that Windows is not loading at all. While the other OS works fine. If there is a faulty ram or hard drive issue, then both OS must be affected. I had checked the ram and drive by some testing software in Ubuntu. But still the error remains constant. While the report generated in Ubuntu does not showed up any error. Now when I restarted my pc in Safe Mode it loaded well. I removed some software's and old updates. On normal boot again the system crashed with Blue Screen. Last time Windows just shutdown on its own. I was playing a game. There were certain updates which installed on restart. It looks that some buggy update has caused this issue in many computers. In Windows I had used tools like MemTest and Verifiers to find any related errors. But there was nothing listed. So I am not doubtful about the hardware at all, as there is no such issue or error occurred on Ubuntu.

[Hayworth]

I want to share my experience here based on the same error. In my system it was a clear issue of corrupt driver. I was able to boot in Safe Mode and the system work well there, but when I get back to normal the system crashed. There is a bluescreen which was associated to some wdm driver. After searching on web for hours I found that the issue appears due to IFS Mount Manager Driver. If this thing is installed in your system also, then you have to remove it. You can try finding that. Go on Windows drive and look for LastGood.tmp folder. In that you can find a folder System32. Find Drivers folder inside that. And delete ifsmount.sys. If you are not able to get that then go on System32/Drivers inside Windows directory. Remove the file ifsmount.sys. You can cut paste that and keep in somewhere. MSDN has a long list of system error codes, their causes and solutions. Click here to visit the link -- System Error Codes. You can look for the error number you are getting and get right solution. Avoid running any new updates until you are sure that it will work.

[Beckinsale]

The common ways to fix a blue screen is error is first finding the associated software or hardware causing the issue. Then booting your system in Safe Mode and removing the associated program. Later on you have to find a good registry repair tool. This will wipe invalid or incomplete entries from your computer making it more reliable. If this things does not work out get a ram and fix it in your computer. Testing hardware to some extent is also recommended or else it will not work well. Some virus are also responsible for that. Troubleshooting is only possible based on the error code you have. At last I am giving you a link of Driver Verifier. You can download the same and run to check driver integrity in Windows. It is a very helpful utility which is used to find corrupt drivers. They are common cause of system failure.

Using Driver Verifier to identify issues with Windows drivers for advanced users

[Chapal]

It looks lie a issue of a malware. I am here going to give some steps to get rid of the same. There are various ways by which you can clear those infections. First getting a repair install does not work all the time. Do that whenever needed. It just fixes your startup stuff, and if there is a issue that lies with a infected files or service that cause the crash then Startup Repair will not at all work. To get rid of a malware which is causing the issue you have to first locate the associated program. You can find that in safe mode. Now do this. Download and install Hijackthis in your system. Run the setup and then it will create a log file. In the log file you can find all services which are running in your system. Locate the suspicious one and then check back.

[Eithne]

It is somehow not easy for diagnosing the Bad Pool Caller error in proper way. You cannot easily find the issue behind the error in that. It is a complicated procedure. Second thing your system fails to boot. So there can be a software or hardware or something both are the cause. Sometime the antivirus scans and shows you that the virus is removed. But there are chances that still some files are left. And those had affected any other program giving out a result of bluescreen. At maximum place I can just find only one option. Run a Repair setup. What if the Repair setup does not work. And for those system which comes with Recovery Partition, there is no way to find a Repair setup in them. Only the installation disc can provide you help for this. There is small link that I had found on web about a similar system. To ensure hardware issue I had disconnected all hardware from the computer except the hard drive and a keyboard. Sometime the simple repair process work while sometime this does not gives you a much help. Defective GPU, RAM, bad sectors, are the common issue of problems that we are discussing. If there is a defective hardware then this error will be constant and Repair setup will fail. It will not be completed. Sometime this can also led to data loss. So do take a backup if you receive any of those errors. Hard drive is the most crucial hardware which has all the data stored. So better take a backup and then go with number of troubleshooting stuff.

Setup stops responding with 34 minutes remaining

[Fajardo]

I had seen your link about 34-minute glitch. My old system has received constant blue screen. I made many changes to make it work. I had changed the ram and powersupply. But did not helped much. Later on I found that the edition of Windows I am using was buggy. So it is a bit confusing for people to find the exact answer behind this glitch. On hardware level there are number of stuff you can try, but on software level you cannot do much. Many time there are certain software which affect the ram. This is most common video games. They work fine on start, but later on the hardware is affected. This are very usual problem which is very complicated for a end user to understand.

[stRunFkzRo]

As all are talking about the error I would also like to state my problem here. I am trying to install Windows XP SP2 on my friend computer. At the time of setup all went well. I can boot from disc and format the partition. The next process that appear after that is copying files. It stuck on a file which says that it is missing. The messages on screen is press r to retry. After hitting that the pc reboots. Somehow XP installed. But I got blue screen. I had tried to run Repair setup which give me stop: 0x000000c2 error. I cannot even enter safe mode know. What should I do know.