Member Avatar for Kevin Magee

I have a MSI PC running W2K & it won't load Windows. I was running some PC software to backup the settings just in case I have a problem (I haven't got the backup but did receive the problem).
Whilst gathering the info the software crashed, my computer blue screened and did a complete Memory Dump and since than I haven't been able to run Windows.
I have access to the Bios screens but can't get past this.
I don't have a recovery disc.

Appreciate any help as it was a reliable PC until this point :confused:

Thanks
Kev

  • 6 Contributors
  • 5 Replies
  • 134 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by dcc

Dani AI

Generated

Immediate priority: preserve the disk image and user data before running repairs. A sector‑level image keeps an untouched copy to work from if repairs fail. Bootable rescue media (Linux LiveCD/USB or a Windows PE environment) can attach the drive to another system and create an image; an example Linux command is shown below (adjust device and destination paths as needed):

dd if=/dev/sda of=/mnt/usb/win2k_disk.img bs=4M conv=noerror,sync

After imaging, attempt logical repairs from the Windows 2000 Recovery Console (boot from the install CD). These commands repair file-system errors and common boot-record problems:

chkdsk /r
fixboot
fixmbr
bootcfg /rebuild

If those do not restore booting and the backup tool likely altered system files, a controlled restore of the registry hives from the system repair folder is an option. From Recovery Console (typical WINNT path), rename the existing hives and copy the repair versions:

cd \winnt\system32\config
ren system system.bak
ren software software.bak
copy \winnt\repair\system system
copy \winnt\repair\software software

Caveats: restoring from the repair folder returns the registry to the state at OS install and may remove drivers/service pack entries. Always work from an image and verify data recovery before destructive steps. Parallel hardware checks—memory testing (Memtest86+), SMART diagnostics, swapping cables or ports, and connecting the drive to another machine—help rule out physical failure. This workflow blends the hardware and software angles raised by , , , and picks up on ’s point about the backup tool: knowing which tool was used matters because some utilities modify boot or MBR structures. If imaging or DIY repair is not possible, professional data recovery is the safest next step.

Recommended Answers

All 5 Replies

Member Avatar for jbennet

it sounds more to me like his windows install is just borked. bad hdd maybe? but thats unlikely

can you manage to get into safemode ? (just after the bios bit start hammering f8 repeatedly and you should get a menu)

Member Avatar for MidiMagic

I'd say he did a restore instead of a backup. It copied the default file to the BIOS instead of copying the BIOS to the backup file.

As a result, the computer doesn't know what hard drive it has, so it can't access it.

There should be a utility in the BIOS to identify the hard disk. Use it.

But do NOT use a format utility - it will erase the disk.

Member Avatar for anlogue

sounds like this software has damaged windows files to me .... can you press F8 on start up and choose LAST GOOD CONFIG ? whats the last message you see ?

Member Avatar for dcc

Kevin...what software were you using?

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.