Windows XP forum: Bad_Pool_caller problem

Hello Kees_B,

Thank you for your reply. I ran a chkdsk scan this morning before reading your post. I am able to bootup. The system boots up every time. I have registered my Hard Drive with the maker. The maker is Seagate. The drive is a Seagate Baracuda ST3500641AS. However my efforts to be able to find and run the drive diagnostics on the web site has been elusive, faustrating to say the least. I will keep trying and post back.

I am also to inform you that system restore is now working. The system seems to work normally, so in the meantime I might just be able to check out these things and inform you in my post. Meanwhile can you tell me how to run the chkdsk since I could bootup? Should I do it from the run command dialogue box? I ask because I am also of the belief that some filed are corrupt.

Thanks again Kees and
Best Regards.

standeb,

Hello Messrs: Kees_B & Steven Haninger,

Thank you so much for your replies and suggestions. Kees with respect to your post, I did the chkdsk /f and /r. I got some relief therefrom. The WSDL and the MSSOAP stopped but I continued to get Event Viewer: Disk error detected on \Divice\Harddisk\1D during a page file operation. Disk event ID 51, so I tried Steven's suggestion.

Steve I was able to download Seatools but could not run it because I could not download the .Netframework installer to complete the installation of SeaTools. It was as if something was preventing the deownload or may be there are different .Netframework versions and I was tryuing the wrong one. I was getting an (Unspecified Error Message) when trying to install. I could ascertain that though because I was only seeing one.netframework version. I have the feeling that the drive test will shed some real light in finding the solution.

Can you guys give some further suggestions?

Further Kees, I must inform you that I run a Seagate external drive (free agent). I thought that I should either disconnect that drive and/or uninstall the Hallmark program I last recently installed. I opted for disconnecting the drive and that was how the WSDL and the MSSOAP stopped showing up in the Event Viewer. However I am aware that should I reconnect that drive, the same situation will occur so I am thinking that I am still at square one. Please be reminded that I am not knowledgeable to any extent about system internals so that I may require a step by step guide devoid of tech language so I would understand your instructions properly and be able to carry them out.

I am very grateful for the further assistance you both can provide.

Thanks again

standeb.

I encounter a lot of these errors and after watching tech after tech chase down the errors too many came down to hardware issues. Some were simple old machines that needed cleaning and replacing the heat sink compound or a failed fan but what really wasted the prior tech's time was the notion this was a driver bug. They went off for days trying this and that.

Is the machine a few years old? Has the usual work been done yet?
Bob

Page File Space 4.81 GB

How did you manage to do that on a 32 bit XP?
Bob