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

OC = NTLDR is missing, even after reinstall?

OK, so I OC'd my AMD 3800 X2 to 2.4, upped the ram, running it 1:1. ASUS A8N-SLI Premium. Mushkin, 2 GB, XP.

Could this screw up finding NTLDR? I 0'd the drive, complete reinstall on XP. Can't find NTLDR. I also switched to my last HDD, again could not find NTLDR.

HELP!!!

Thanks!
 
SOMETHING is causing instability. Did you lower the Hypertransport multiplier? I'd also try running a higher memory divider (lower memory clock) just in case your ram can't do such a high overclock.
 
HT is at 4x
Cool and quied - disabled
cpu 240
cpu multi 10
PCI Clock 100 Mhz
DDR Volt 2.8
Chip Volt 1.6
HT Volt 1.2
CPU Volt 1.450
PCI Clock Sync AUTO

I can boot if I have the XP CD in the drive, just not without it.

Should I run the HT at 1.25? Up the CPU volts? Lower the chipset volts?

Thanks for any and all help.
 
Here is the RAM...
http://www.newegg.com/Product/Product.asp?Item=N82E16820146397
mushkin eXtreme Performance 2GB (2 x 1GB) 184-Pin DDR SDRAM Unbuffered DDR 500 (PC 4000) Dual Channel Kit System Memory - Retail

I had it set to-
3 tch
8 tras
4 trcd
3 trp
8trc
16trfe
3 trwt
3 trw
2t

When I set the ram to auto, it reset the timimgs to a much looser set, but it still would not boot. It only booted when I reset the MoBo for Setup Defaults.

Thanks!
 
I'd suggest setting the RAM to 3-4-4-8 (think that'll be 3-8-4-3 in your case) and the rest to auto. 1T will be fine aswell.

This is fairly simple to figure out really, first, put multiplier down on CPU (so roughly it's back at stock)and leave RAM as is@ whatever speed. if you still get the problem, it's probably the RAM, so OC CPU again, and put RAM on a divider.

Just because you bought the parts doesn't mean you'll instantly get the OC. There are no guarantees. You can't just throw money at it and complain you don't get what other people get.

Clearly you haven't followed any kind of OC'ing guide here, else you'd know where the problem began arising and could fix it by toning down the OC by 10Mhz or so.

Also, a quick question, your sig, is that from something, or are you that guy from the LFS forums, with geek and proud in his sig aswell as no place like...
 
Sound's like more of a Hard Drive problem then a CPU problem.

I use to get that problem sometimes with my SATA controller (in a PCI slot) on an old(er) mobo with a Athlon XP. Normally a complete reinstall with just the controller (and no other IDE drives) would fix the problem.

Are you using any special drivers ("press F6 to install third party RAID drivers") cause you might need to do this so windows can find its self.
 
I have a question. What is your boot device priority? Ive seen that happen sometimes when its set to boot from cdrom or floppy disk first.

Like wizboy also said, if you have the HD on a raid controller on mobo, youd need to have drivers installed first as well.
 
FWIW, the last & only time I ever experienced NTLDR problems, my 40G IBM Deathstar was on its way out. Hopefully, yours is for some other reason.
 
Back
Top