• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why would windows XP install tell me it does not recognize what kind of system i have?

dalearyous

Senior member
i should probably back up and give some background info. i was using windows vista for a while but i started getting blue screens usually saying bad pool caller but only when i was doing something like burning files or converting video files. everything else including heavy gaming ran fine so i dealt with it. now, however, i am in heavy video editing and could not put up with it any longer. so i figured i would install windows xp because when i had it on the machine, my video editing ran flawless. so i popped in xp disc and when i got to the part where i manually install raid drivers from floppy during windows xp install, it said that it did not recognize the type of computer i was using and gave me two options: other and (i can't remember exact wording) something something i486 PC. so i chose the only option i had (i486) one and half way during the install computer blue screens, bad pool caller, 0x19. so i tried again, this time i got into windows only to find device manager looked like a bomb went off. all my drivers were installed and yet there were exclamations all over the place, especially on my controller cards and basic devices.

i am kinda at a fork in the road here because i NEED a computer in the next week more than ever. i am currently using my media-center pc right now which is e6300 with 4gigs memory and should be ok for my work this week.

i am going to start running diagnostics tonight but i may be at the point of building a new machine (machine i am having trouble with is in my sig).

has anyone ran across this problem before? im leaning towards bad memory but not %100 sure yet.
 
http://www.registrysimple.com/bad-pool-caller-fix.php

Perhaps this might be of use to use (if you haven't already google'd it)

That device manager thing sounds pretty crazy... I'd maybe do a chkdsk /f ((http://www.ehow.com/how_205229...dsk-f-windows-xp.html) this webpage explains more detail than I currently can )) to ensure that all system files are correct and complete. I don't know if this would help but its worth mentioning. also maybe remove the ram and clean the contacts real good and blow some compressed air into the dimm slots and make sure that there is no flaky connections if you can. That is a weird problem for sure, I'd try everything possible and see if it gets fixed. It does sound like a memory related issue I'd think as the error happened during times of high amounts of mem reads and writes, but this is only a guess so don't quote me on that 🙂
 
Back
Top