0xC2 or 0x00000024 before WinXP Install

Sysjack

Limp Gawd
Joined
Oct 6, 2003
Messages
339
I've been working on a friend's new system for the better part of the day today, and we can't get WinXP to install. After the drive is partitioned and formatted, it loads drivers and whatnot, but before restarting to load the windows install GUI, it grives a BSOD and one of two error pages, one of which shows a stop error 0xC2 BAD_POOL_CALLER, with the other being 0x00000024. There are several other codes on both screens, but I didn't write them down. The error codes can be found HERE, with the 0xC2 code further down on the list to the left. System specs are:

AMD Althon 64 3200+ (CG Rev Clawhammer)
Abit KV8 Pro socket 754
512x1 Kingston HyperX PC-4000
GeForce 4 Ti 4200
Creative Audigy 2
Maxtor 80gb HD
Dynex 16X DVD-ROM
Antec Smartpower 350Watt

The CPU is definitely not overheating at present. It runs around 38C idle at 32C ambient. It may have overheated before I looked at it however, as the heat sink was improperly mounted (very loose) and there was far too much thermal compound on it.

Any ideas what is causing these problems?

Thanks
 
Well, it just may be memory related. Memtest86 displays between 2000 and 5000 errors no matter what voltage we throw at it (2.65, 2.7, 2.8), so we're going to try exchanging or RMAing it and trying again.
 
Sounds like you found it. For new system builds around here, I don't even try an OS install until the hard drive has passed it's manufacturer's own diagnostics a couple of times, and Memtest86+ runs "all tests" overnight, with no errors.....

Good Luck - B.B.S.
 
Yeah, well, the aggravating thing is I thought to run Memtest96 about 6 hours ago when we were a little into the troubleshooting but never did for whatever reason. Dumb.
 
Sounds like memory to me. Had a similiar problem with my latest system, only there was so much memory that Windows loaded and everything really ran fine, except for Battlefield 1942. Every time it ran, Battlefield would crash to desktop. Finally ran a Memtest and found that the 980MB range was the cause. RMA and haven't had a problem since.
 
Back
Top