Member Avatar for compdoc

A customer brings me a computer telling me that it had a virus and a family member cleaned it for them and now the computer won't boot.

When I turned the computer on it said Ntldr missing

ok simple enough, I tried to copy Ntldr from the recovery console but it failed. and I could not access any file or directory on C:

so from this point I tried to reinstall windows. I deleted the C: and then partitioned and formated the drive and once setup started to copy the files I started getting errors, random files could not be copied and then a BSOD.

I have tried 3 different install cd's. I replaced the cd drive. I striped the computer to barebones. and I'm still getting the errors.

I am currently running Memtest on it. It's on test 3 with no errors yet.

I am going to run chkdsk next and I'm thinking about trying yet another (4th) install cd.

does anyone have any ideas I might try if I still cant install windows.

  • 2 Contributors
  • 2 Replies
  • 210 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by compdoc

Dani AI

Generated

Good follow-up from — the mix of bootloader errors and intermittent file-copy/BSOD failures is classic for memory faults, and ’s suggestion to consider the hard drive is reasonable only after memory has been ruled out. The important takeaway for future repairs: transient memory corruption can mimic failing media or corrupted system files, so test RAM early in the troubleshooting sequence.

Why memory shows those symptoms: installers and boot code live in RAM while they run. A bad DIMM or bad slot can flip bits, corrupt NT boot code, scramble file buffers during copy, and produce random read/write errors that look like a bad CD, optical drive, or HDD. That explains inconsistent copy failures and unexplained blue screens even with multiple install discs.

Practical diagnostic workflow (apply in this order):

  1. Run a dedicated memory tester (memtest86/86+) for multiple full passes — intermittent faults often need many passes to appear.
  2. Test modules one at a time in the primary slot and try each slot to separate bad DIMMs from bad slots.
  3. Reseat modules, clean contacts lightly, and verify BIOS voltage/timings are at defaults (no overclock/XMP).
  4. If RAM passes, verify HDD health (SMART, vendor diagnostics) and check data cables; then confirm install media integrity (checksum the ISO, try a USB installer).
  5. If faults persist with new memory, check PSU voltages and motherboard for physical damage.

Extra notes: borrow a known-good stick to confirm quickly; always test memory before buying a replacement drive; take ESD precautions when swapping modules. After replacing faulty RAM, repeat a full memory run and then a fresh OS install to ensure stability.

Recommended Answers

All 2 Replies

Member Avatar for inkcoder

Hmm...
If you formated and reinstalled windows XP with a working disk it should not still be getting errors. It sounds like there is either a problem with your windows install disk or a problem with the actual hard disk. Format the C: drive and try a new Windows XP install disk. If this fails you might have to order them a new hard drive and charge them for the parts and then install windows on the new hard drive.

Hope this helps,
Inkcoder

Member Avatar for compdoc

ok I solved it. it turned out to be bad RAM

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.