• 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.

Computer won't run Xp at more than 100mhz!

phamtastic

Junior Member
This is my problem. My friend came over to use my athlon xp 1700+ oem cpu to test out in his new system, he didn't have his cpu yet. I left the room and he installed it without the heatsink. And of course, after a short while the cpu fried! Well, he bought me a new retail boxed athlon 1700+. I installed it, but it wouldn't load Winxp up! It gave me an error that told me that there was a change in hardware and that I needed to restart. Ok, I did that, but I then got this error that said "ntoskrnl.exe was missing or corrupted, please re-stall." Ok, I tried booting off the cd-rom, but it would freeze at the very beginning of the install process. I couldn't even get to recovery mode, it would freeze and give me that damn error saying it couldn't load ntoskrnl. I then decided to mess with the cmos settings. I changed the frequency from 133 to 100mhz and guess what? It worked?
XP loaded fine, but my system was running at 1100mhz instead of 1700. I went to many websites that said solution the the error "missing or corrupted ntoskrnl" was to fix the boot.ini. I did that and it still doesn't work.

What is the problem? My system will only run the chip at 100 frequency. I never had this problem before the burnout. Is this a cpu problem or a motherboard problem? Or is there something wrong with windows xp?
 
This is most likely a problem with your WinXP OS itself.

I had the same problem with NT 4.0 on my old laptop last month, and Win2k on my main machine about 3 months ago.

Try to re-install it (a full clean install) at 100 FSB, then move up to 133FSB.

Nothing else seemed to correct the "ntoskrnl.exe was missing or corrupted, please re-install" error that I had.

The only puzzle : why would XP tell you about a change of hardware ?! (... since there was none, as far as Windows is concerned...) Mystery ...

 
I think there are unique ids in the chips and I am betting that XP reads them and uses them as part of the activation data.
 
Back
Top