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

Athlon XP 2100+ will only boot as 1500+

S

Spiffae

Member
Hi
I'm building a new system (XP 2100+. Soyo Dragon Lite KT333 mobo, crucial DDR 2100, etc, and i'm having some probs. In my bios, i can choose the FSB speed and the DRAM clock. When i reset the CMOS, it set the FSB at 100, and the DRAM clock at "By SPD" The processor showed up as a 1500+. Now when i go into the bios and change the FSB to 133, it won't boot. it either does the bios startup, and then just goes to a black screen instead of going to windows, or it gives me a message before windows boots:
The file
<Windows Root>\System32\Ntoskrnl.exe
is corrupt. Please reinstall this file.

and then it hangs there.
when i set it back to 1500+, it works again. no corrupt file.

Now, it seems that what crash i get is dependent on what i set the DRAM clock is (100, 133, 166), but the crash only happens when i set the FSB to 133. Am i missing anything about this? is there some other setting that will allow me to run full speed?
 
ok, weird. at that site, i see at the intersection of XP Palomino and Dragon Lite, i get "Yes" for 266mhz. that's all. what does that mean? i don't even have a choice of 266. wait, do i have to do something with multipliers (also an option) something like 133 x2?

thanks
 
I just got my A7N8X Deluxe, 2100xp retail today, and had the same problem (showed @ post as 1500xp).
Changed FSB to 133, and it then auto-recognized the 2100.
I know thats prolly not what you wanted to hear, but may help on the troubleshooting.:frown:
 
Hehe, it works! ... then crashes. Are their individual settings for DDR and cpu? If so, have you tried setting the DDR to 133 and the CPU to 133. If you set the CPU FSB to 133 and the ddr is set By Speed, it might bump your 2100 to 166. Just a thought.

Edit: That is your pc2100 DDR not your athlon, sorry about being vague.
 
Originally posted by: KingofFah
Hehe, it works! ... then crashes. Are their individual settings for DDR and cpu? If so, have you tried setting the DDR to 133 and the CPU to 133. If you set the CPU FSB to 133 and the ddr is set By Speed, it might bump your 2100 to 166. Just a thought.

Edit: That is your pc2100 DDR not your athlon, sorry about being vague.
Click to expand...
/me seconds this motion... look at page 38 and following, in the manual.
 
133/133: It goes to a "windows did not start correctly" and lets me go safe mode, safe mode with command prompt, etc. no matter what i choose, it keeps resetting and taking me to the same screen.

133/166: Same message. When i choose normal windows startup, it says Ntoskrnl.exe is corrupt.

when i set it back, it works again. nothing is corrupt.
 
Maybe you have a bad mobo and/or CPU?

My other Mobo (Soyo Dragon) and CPU (Athlon T-Bird) would always crash iwth the Ntoskrnl.exe error every once in a while...
i fought with this for a good six months then just got a new mobo/cpu....

Works perfectly now.

Hope this helps =/
 
ugh. I got the dragon at CompUSA, so there's no way they'd EVER take it back, and the CPU has already been RMAd once by newegg. I really don't want another CPU. Do you really think that might be it? is there any way i can run diagnostics to see?

 
Actually, if you did overclock, there is a possibility that you did corrupt something. I assume that the Dragon Lite has a 1/5 divider, but if it does not, you were running your HDD at 41.5, which is not exactly good for it. If you can back up your files, format the drive and reinstall or run repair from the CD (is this XP or 2k?).
 
see, this happens even before i had installed windows. As far as i know, nothing is corrupt. When i set it to 2100, i get the message. When i set it back to 1500, nothing is corrupt. my guess it it's a faulty report. what is a 1/5 divider?
 
Well, to put it simply, a 1/5 PCI divider simply divides the bus. 166/5 = 33. 33mhz is the spec frequency for the PCI Interconnect. If you only have a 1/4 divider (I highly doubt that you do not have a 1/5 divider) it would be 41.5, which is too high for a hard drive (you can do permanent damage at that frequency).
 
hmmm...i just realized it's running a really crappy power supply, and the voltages are all pushing their lower limits. I think that this might have something to do with it. Anyone?
 
That's possible - the PSU might be barely able to keep the system going at the slower speed, but when the bus is bumped up to 133MHz, the extra drain just might be too much.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top