Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Help with Bad_Pool_Caller stop 0xc2 0x43 BSOD


  • Please log in to reply

#1
ptkelley

ptkelley

    New Member

  • Member
  • Pip
  • 3 posts
My Windows XP Pro SP3 Dell 8400 is completely non-bootable. I keep getting STOP error Bad_Pool_Caller 0x000000c2 (0x00000043, 0x_________, 0x000000000, 0x0000000000).
Wife powered on computer, said she got a blue screen with message about checking disks, bad file, removing file, then got the STOP error. Now the STOP error appears when I try to boot system. Startup progresses through the Windows XP splash screen, then black for a few seconds, then the STOP error.

Same thing if try to boot in Safe Mode or Last Known Good Configuration. In Safe Mode boot, it progresses through loading drivers, then STOP error.

If I go into Recovery Console, pick 1 for Windows, hit ENTER and STOP error appears.

If I boot from Windows XP CD, try install, then R for repair, F8 to accept license agreement, then STOP error. Tried several CD's and even a clean rc.iso disk.

I have re-seated all motherboard connectors, switched RAM modules, and run extensive hardware diagnostics from Dell and others. All hardware checks out okay.

No new software, drivers, or hardware added recently. I use Microsoft Automatic Updates, and this occurred on a Thursday, so conceivably could have been from a Windows update.

It sounds like CHKDSK ran and "repaired or removed" a critical file in MBR, or some file critical to the early startup process.

I was finally able to get into the system with Active@ Boot Disk http://www.livecd.com/ . I am able to get into the system and have saved a complete drive image to an external hard drive,so I feel better now. I can see all of my C: drive, and I can backup all of my files to the external drive if I have to, but it will be a long and arduous task. I should mention that I have two 250GB drives in a RAID 0 array, so simply removing the drive and installing it as a slave in another computer I don't think is an option.

Now that I have a backed-up drive image, what can I try to diagnose and fix the STOP error?

I came across a thread from a couple of years ago, where someone was having an identical problem, which was ultimately fixed by deleting a partition and re-creating it.

Wannabe1 and Tuxmaster were helping that member solve his problem. Are you out there and can you help me?

Sorry for the long post, but I wanted to cut through the usual fixes first.

Thanks in advance for anyone who can help
  • 0

Advertisements


#2
ptkelley

ptkelley

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Here is some more info on my problem. As I suspected from what wife told me, CHKDSK ran when system powered-up. I found this "bootex.log" file which was written right before the STOP error started appearing. The text is below.


Checking file system on C:
The type of the file system is NTFS.

The volume is dirty.
The USA check value, 0x433, at block 0x3 is incorrect.
The expected value is 0x432.
The multi-sector header signature in file 0x1438 is incorrect.
42 41 41 44 30 00 03 00 e8 cf 22 40 61 00 00 00 BAAD0....."@a...
46 1a 01 00 38 00 03 00 50 02 00 00 00 04 00 00 F...8...P.......
Deleting corrupt file record segment 5176.
Index entry RP1949 of index $I30 in file 0x1073 points to unused file 0x1438.
Deleting index entry RP1949 in index $I30 of file 4211.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Cleaning up 4460 unused index entries from index $SII of file 0x9.
Cleaning up 4460 unused index entries from index $SDH of file 0x9.
Cleaning up 4460 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

483355687 KB total disk space.
206341712 KB in 324065 files.
150152 KB in 31652 indexes.
0 KB in bad sectors.
852199 KB in use by the system.
65536 KB occupied by the log file.
276011624 KB available on disk.

4096 bytes in each allocation unit.
120838921 total allocation units on disk.
69002906 allocation units available on disk.

Internal Info:
90 1e 06 00 8e 6d 05 00 09 8e 08 00 00 00 00 00 .....m..........
36 3f 00 00 06 00 00 00 d4 1f 00 00 00 00 00 00 6?..............
52 cc 64 22 00 00 00 00 7a d0 7b de 00 00 00 00 R.d"....z.{.....
18 0b 85 d9 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 28 aa e1 ea 01 00 00 00 ........(.......
20 3a 0b d6 00 00 00 00 80 38 07 00 e1 f1 04 00 :.......8......
00 00 00 00 00 40 19 32 31 00 00 00 a4 7b 00 00 .....@.21....{..

Windows has finished checking your disk.
Please wait while your computer restarts.


I don't know what happened that prompted CHKDSK to run when computer was powered-up, but Window Update ran the night before. I have a "WindowsUpdate.log" file from the session, but it is long so I won't paste it here. I don't see anything obviously wrong in it. I have uploaded a text file "WindowsUpdateLogExcerpt.txt" which shows what occurred during the WindowsUpdate session.

I also found this "WIADEBUG.LOG" file that was written just before CHKDSK ran. The text is posted below.


====================Start 'wiaservc.dll' Debug - Time: 2010/05/27 17:14:10:718====================
*> StiServiceMain entered, Time: 2010/05/27 17:14:10:718
<* StiServiceMain ended, Time: 2010/05/28 14:19:02:459
StiLockMgr::CheckDeviceInfo, ACTIVE_DEVICE is not valid!


Please, if anyone can help. There are some System Restore points, which I can see on my C: drive through Active@ Boot Disk, but I can't get into windows to do a system restore.

Attached Files


  • 0

#3
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
because you have a RAID 0 array you may have to reinstall everything...thats been my experience using RAID 0...
you can try the Raid Recovery Tool here but I wouldn't get my hopes up
for the future...if you really need the speed of RAID 0...then go with RAID 0+1...stripped and mirrored...
  • 0

#4
ptkelley

ptkelley

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
happyrock,
That's what I'm afraid of. I can however get into the system with a WinPE disk that I downloaded from Active@ Boot Disk. Active@ Boot Disk.
After I get all of my files backed up, I'm going to try running FixMBR.
Any other suggestions for trying to fix the problem?
It has to be a file critical to the inital Windows boot process that has gotten corrupted or deleted.
  • 0

#5
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts

It has to be a file critical to the inital Windows boot process that has gotten corrupted or deleted.

I agree...the problem is widows divides the reading and writing between the 2 drives...you can try fixing the MBR but when I spent about a year playing/fighting with a RAID 0 setup and had to do a complete reinstall about 4 times and several image restores that actually worked (about half failed) in one year...I gave up on raid completely...good luck

Edited by happyrock, 03 June 2010 - 08:51 AM.

  • 0

#6
diabillic

diabillic

    Member 1K

  • Member
  • PipPipPipPip
  • 1,370 posts
RAID0 is usually, in my opinion, for a home based setup. Consumer based drives really dont benefit a huge amount from striping and just causes a huge headache if they blow up. I had to reinstall Windows about 3 times to get the drives to work properly, that was after I removed and rebuilt the array twice.
  • 0

#7
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts

RAID0 is usually, in my opinion, for a home based setup. Consumer based drives really dont benefit a huge amount from striping and just causes a huge headache if they blow up. I had to reinstall Windows about 3 times to get the drives to work properly, that was after I removed and rebuilt the array twice.

yep...if I do a RAID setup anymore for a client they get a taillight guarantee...
that means as soon as my tail lights are out of sight the guarantee expires
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP