🔒 Locked

Bad Pool Call?

Started by Null and Void Nov 13, 2001 at 4:27 PM 12 replies 13.7k views

Original Post

Nov 13, 2001 at 4:27 PM

Well, when I go to boot Win2K I get greeted with a warm blue screen

. The error is "BAD_POOL_CALL". I tried to boot into safe mode, but it locks after I select "Safe Mode" or "Safe Mode with X". I haven''t added any hardware, or changed any drivers (that I know of, at least). Linux boots fine (I''m using it right now, and I have access to my Windows hard drive from it without a problem). So, what should I do (I''ll be researching this on my own as well, but I haven''t found anything useful yet). Thanks in advance

. [Resist Windows XP''s Invasive Production Activation Technology!]

griffenjam

Nov 13, 2001 at 4:42 PM

Try "2 ball in the corner pocket" and that should work fine.
All joking aside it sounds like re-install time.

Jason Mickela
ICQ : 873518
E-Mail: jmickela@sbcglobal.net
------------------------------
"Evil attacks from all sides
but the greatest evil attacks
from within." Me
------------------------------

Martee

Nov 13, 2001 at 4:45 PM

Try booting off the install CD, going to the recovery console, and running chkdsk.

GuyJohnston

Nov 13, 2001 at 4:45 PM

Interesting error.
More interesting that you can''t get into Windows
through safe mode.

I''m paranoid about corrupt registries. You might try
to restore it with one of the backed up versions.

Also, do some of the standard diags. Can you run standard
hardrive diagnostics from Linux ? Like scandisk or something similar ?

You should check for file corruption of Windows main files if you can. But I can see how that might be a problem if you can''t get into Windows to run sfc.

I would think your first step would be to at least get into Windows in safe mode.

Guy

Null and Void

Nov 13, 2001 at 4:47 PM

Well, since I partition intelligently (and because I have Linux on another HD) I can backup or won''t loose anything (I even have a somewhat recent registry backup

). I reinstalled less than a month ago (with Win2K didn''t like my new motherboard, and it died). Oh well, I''ll look for an answer for a little more before I give up

.

[Resist Windows XP''s Invasive Production Activation Technology!]

Null and Void

Nov 13, 2001 at 4:49 PM

Ah, people reply while I''m posting

. It gets past the part where it runs scan disk. It has got to the login screen once, then it died after I typed in my password. I''ll try to do the recovery console thing though.

[Resist Windows XP''s Invasive Production Activation Technology!]

DenburgEngelfun

Nov 13, 2001 at 5:47 PM

Oh dear! You have quite a problem there. I do believe that you need to fix your computer. I took my computer to a WinAmp shop and gave them payments of AOL. They helped me out and fixed my computer. It was spiffy. The service was just dandy as well. I had a swell time.

Maybe you should bring your computer to a WinAmp shop.

Aces!

Agent1

Nov 13, 2001 at 5:58 PM

I do believe that the previous post is an example of what happens when you let idiots use the Internet.

-Agent1

SHilbert

Nov 13, 2001 at 6:28 PM

quote:
Original post by Agent1
I do believe that the previous post is an example of what happens when you let idiots use the Internet.

-Agent1

Agreed.

nes8bit

Nov 13, 2001 at 6:37 PM

*points and laughs at Agent1*

---------------------------------------------
My useless posts have been viewed gotta view images to view the couNter

times
TIM: God@totalim.com

Null and Void

Nov 13, 2001 at 6:39 PM

Well, I dskchk''ed all of my partitions, they were all fine (as I thought). So, I just reinstalled it. It works now (I don''t know if it is a good thing that it works, or a bad thing that it needs to be reinstalled in the first place

).

[Resist Windows XP''s Invasive Production Activation Technology!]

Agent1

Nov 13, 2001 at 6:45 PM

First order of business: Since your problem seems fixed, I am declaring this thread hijacked

quote:
Original post by nes8bit
*points and laughs at Agent1*

You mean with, right?

-Agent1

arcane_mantis

Nov 3, 2003 at 9:01 PM

I get that same message in a BSOD! In windows XP this just aint supposed to happen... but it does! I have had it happen a few times now so it aint just a one off thing. Anyone with any clue as to what is actually causing it?

I would like to fix this without reinstalling if possible.

Programmer One

Nov 3, 2003 at 9:06 PM

...this thread is almost 2 years old...

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.