\windows\system32\config\system

[PapaBear]

My son's comp won't boot up. It says that it's missing that file, and that I need to use the repair feature on the XP disc. When I tried to do that, before I even got to the screen that gives me the option to repair, I got "SESSION8_INITIALIZATION_FAILED".

I looked up that message on Google. One of the things I found said to check if the CD was scratched. It was, so I used a different CD. I was able to get further this time. I hit "r" for repair. It got me to a screen that asked me what I wanted to repair. I hit "1" and now I get "BAD_POOL_CALLER".

What the fuck do I try now? BTW... I tried using another memory stick (even though this one is only about 2 months old). There is no new hardware either.

[patsopinion]

My son's comp won't boot up. It says that it's missing that file, and that I need to use the repair feature on the XP disc. When I tried to do that, before I even got to the screen that gives me the option to repair, I got "SESSION8_INITIALIZATION_FAILED".

I looked up that message on Google. One of the things I found said to check if the CD was scratched. It was, so I used a different CD. I was able to get further this time. I hit "r" for repair. It got me to a screen that asked me what I wanted to repair. I hit "1" and now I get "BAD_POOL_CALLER".

What the fuck do I try now? BTW... I tried using another memory stick (even though this one is only about 2 months old). There is no new hardware either.

If the computer is a desktop u can take the hd out and use it as the second drive on another desktop
once it is backed to the other pc go ahead and format and reinstall completely

you will lose all info so this should be a worse case scenario but in the mean time it wouldnt be a bad idead to back up the disk

[PapaBear]

If the computer is a desktop u can take the hd out and use it as the second drive on another desktop
once it is backed to the other pc go ahead and format and reinstall completely

you will lose all info so this should be a worse case scenario but in the mean time it wouldnt be a bad idead to back up the disk
I plan on backing it up tomorrow using a usb enclosure, but it won't even let me reinstall completely, either. I already tried to do a complete reinstall and got the same BAD_POOL thing.

[Chigworthy]

Doughboy makes a really bad pool. I'd call them up.

[MadMatt]

Which repair did you try, the first repair option that pops up or the one that will let you repair Windows instead of Reinstall? THAT is the one to use...

[PapaBear]

Which repair did you try, the first repair option that pops up or the one that will let you repair Windows instead of Reinstall? THAT is the one to use...
The second one. One more thing... I have no way of getting into safe mode, either.

[MadMatt]

Sorry to hear that friend. Best of luck getting the data off - I'll keep my fingers crossed for you.

[zentraed]

My son's comp won't boot up. It says that it's missing that file, and that I need to use the repair feature on the XP disc. When I tried to do that, before I even got to the screen that gives me the option to repair, I got "SESSION8_INITIALIZATION_FAILED".

I looked up that message on Google. One of the things I found said to check if the CD was scratched. It was, so I used a different CD. I was able to get further this time. I hit "r" for repair. It got me to a screen that asked me what I wanted to repair. I hit "1" and now I get "BAD_POOL_CALLER".

What the fuck do I try now? BTW... I tried using another memory stick (even though this one is only about 2 months old). There is no new hardware either.

I guess your thread title got cut short. What's the file that's missing? You could try copying a new version of the file onto the disk. You'd have to download a bootdisk (or maybe use the recovery console from the windows setup disk) to be able to copy it.

Are you using burned copies of Windows? I've had problems with burned discs before. Setup is really picky.

[JPMNICK]

it sounds like a bad motherboard, or bad hard drive. how old is the computer? did you have a power outage or anything recently?

[SatCam]

I dont understand... can you boot onto a cd?

Is it possible that you could move the hd to another computer or use a linux livecd to check out the hard drive?

[PapaBear]

it sounds like a bad motherboard, or bad hard drive. how old is the computer? did you have a power outage or anything recently?

The board, cpu, and ram are 2 months old. The hd is about 9 months old. He said he tripped over the power cord and unplugged it.

I dont understand... can you boot onto a cd?

Is it possible that you could move the hd to another computer or use a linux livecd to check out the hard drive?

I'm not really all that concerned with saving what's on it. I'll probably use my enclosure to save what's there, but that's not my main concern. Anything on the comp is only 2 months old, so it's not much. I just want to get the thing working.

[PapaBear]

I guess your thread title got cut short. What's the file that's missing? You could try copying a new version of the file onto the disk. You'd have to download a bootdisk (or maybe use the recovery console from the windows setup disk) to be able to copy it.

Are you using burned copies of Windows? I've had problems with burned discs before. Setup is really picky.
The thread title isn't cut short. The title is the name of the file that's missing. They aren't burned copies of Windows.

[JPMNICK]

is this a laptop or a desktop?

he could have shorted something out when he tripped over the cord. it can EASILY be the motherboard or the RAM. also, if something was happening at the time the power went out, it might have just been the hard drive.

It sounds like to me, when the cord was pulled out, it shorted something out, and you have a motherboard that has some fried components.

[Hottub]

I'll second a shorted motherboard.

Go to Tigerdirect and pick up a new one.
This is assuming the processor is not fried.

[PapaBear]

is this a laptop or a desktop?

he could have shorted something out when he tripped over the cord. it can EASILY be the motherboard or the RAM. also, if something was happening at the time the power went out, it might have just been the hard drive.

It sounds like to me, when the cord was pulled out, it shorted something out, and you have a motherboard that has some fried components.
It's a desktop. Damn. I guess I'll have to get it tested. I hope I can find a good place in town. The last place I went was run by idiots.

Edit: Firedog is 60 bucks for diagnostic. Anybody try them before?

[JPMNICK]

if it is 2 months old, try and return it to where you got it from as an RMA. it should not have shorted out, i am sure you can get it replaced for free.

[PapaBear]

if it is 2 months old, try and return it to where you got it from as an RMA. it should not have shorted out, i am sure you can get it replaced for free.
I bought the motherboard/cpu combo from Geeks.com. I don't think most places will allow for returns on stuff like that.

[JPMNICK]

I bought the motherboard/cpu combo from Geeks.com. I don't think most places will allow for returns on stuff like that.

I think you can, get an RMA number from them and then you pay to ship it back. might be worth a try

http://www.geeks.com/techhelp.asp

[PapaBear]

I think you can, get an RMA number from them and then you pay to ship it back. might be worth a try

http://www.geeks.com/techhelp.asp
I think I may try that. If it turns out to not be the problem, I'm only out the shipping, and I can still get the comp checked at Firedog.

[JPMNICK]

do not tell them you kicked the plug out, just tell them the mobo started to malfunction and caused your OS to corrupt. pretend like you had a tech look at it or something.

and firedog is going to cost you way more in the long run that just buying a new mobo and throwing the chip in it

[furie]

http://i5.photobucket.com/albums/y178/furie1335/pics/logo_apple.jpg

[zagman76]

If the motherboard was fried, it wouldn't even boot, let alone allow you to boot into a CD

\windows\system32\config\system is one of the registry files (along with \default \sam \security and \software

The problem is with the registry, and not with the motherboard.

Bad_pool_caller errors are usually RAM related - try popping the RAM out, and then back in. If you have more than one stick, try booting with only 1 at a time in, and see if you can get to the recovery console (a WinXP or W2K disk will work).

If you can get into a recovery console, do a chkdsk /r and let it run.... (and run... and run.... and run..........)

[PapaBear]

If the motherboard was fried, it wouldn't even boot, let alone allow you to boot into a CD

\windows\system32\config\system is one of the registry files (along with \default \sam \security and \software

The problem is with the registry, and not with the motherboard.

Bad_pool_caller errors are usually RAM related - try popping the RAM out, and then back in. If you have more than one stick, try booting with only 1 at a time in, and see if you can get to the recovery console (a WinXP or W2K disk will work).

If you can get into a recovery console, do a chkdsk /r and let it run.... (and run... and run.... and run..........)
That sux considering I already sent the board back. The ram is almost brand new, and I tried another stick, too. We'll see what happens when Geeks decides whether or not to replace it.

[Reynolds]

I had the same problem... twice. Had to reformat, due to a registry error. Called customer service the second time, told me to make sure I always power off with start / shutdown. Use a battery backup surge protector in case of power outages. Since then the problem hasn't happened again.

[PapaBear]

I sent the mobo back to Geeks.com and they replaced it. They are very good about that! I don't know if the bobo was actually bad or not. It did turn out to be the RAM that was bad. I can't remember if I mentioned this, but one of my other computers crapped out after a bad shut down. Turns out the RAM was bad in that one, too.

I have both comps working fine, now. In both cases, the RAM was the cheapest stuff I could find. I used to think it made now difference if you used cheap RAM or expensive RAM, but I think my mind has been changed on that.

Both of my comps are on BackUPS. I'm going to get one for my son's comp, too. Anyway... Thought I'd update this, since we all learn from shit like this. I love this forum!:thumbup:

Edit... Whoever suggested that the XP disc might be in bad shape was right, too. When I finally got the good RAM in my son's comp, I was still having problems. I cleaned the disc, and it solved the problem.

[bobrobot]

I sent the mobo back to Geeks.com and they replaced it. They are very good about that! I don't know if the bobo was actually bad or not. It did turn out to be the RAM that was bad. I can't remember if I mentioned this, but one of my other computers crapped out after a bad shut down. Turns out the RAM was bad in that one, too.

FYI, I was NOT bad!!!:devil2:

[JPMNICK]

I sent the mobo back to Geeks.com and they replaced it. They are very good about that! I don't know if the bobo was actually bad or not. It did turn out to be the RAM that was bad. I can't remember if I mentioned this, but one of my other computers crapped out after a bad shut down. Turns out the RAM was bad in that one, too.

I have both comps working fine, now. In both cases, the RAM was the cheapest stuff I could find. I used to think it made now difference if you used cheap RAM or expensive RAM, but I think my mind has been changed on that.

Both of my comps are on BackUPS. I'm going to get one for my son's comp, too. Anyway... Thought I'd update this, since we all learn from shit like this. I love this forum!:thumbup:

Edit... Whoever suggested that the XP disc might be in bad shape was right, too. When I finally got the good RAM in my son's comp, I was still having problems. I cleaned the disc, and it solved the problem.

glad to hear it is all back up and working