Member Avatar for tesskobs

Whenever I restart I'm told the comp needs to run the Chkdsk. But it freezes at 16% of stage two every time. I can restart and skip the scan, and I don't receive any other error messages while using the pc. This only happens if I want to reboot.

I also can't boot up in safemode. I can get as far as telling the comp to boot up in safemode, it starts to, and then freezes before it loads. Once again, I can power down, skip the Chkdsk scan and XP loads up.

My comp is getting slower and slower, and something at start up is running that takes literally an hour to finish. I can't indentify it, and am clueless about alot of what is supposed to be running and what isn't. If I could get into safemode, I could run the adware/spyware/etc scans but... I can't.

Help? :)

  • 3 Contributors
  • 2 Replies
  • 90 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by dcc

Dani AI

Generated

A CHKDSK hang partway through Stage 2 combined with an early Safe Mode freeze most commonly points to either filesystem/index corruption or a hardware problem that appears very early in the boot (disk/controller, bad cable, or a kernel driver). As noted, basic hardware details (drive model, interface, age, SMART status) matter; and 's suggestion to run a vendor/bootable disk check is the right direction. The steps below are a practical, low-risk triage sequence.

Useful data to capture before invasive work: the System log in Event Viewer (Start -> Run eventvwr.msc) for Disk/Ntfs/Controller errors; the boot log produced by F8 -> "Enable Boot Logging" (file at C:\WINDOWS\ntbtlog.txt); and a look at msconfig to see third‑party startup items (hide Microsoft services first). These artifacts often show either repeated disk errors or a driver that never gets loaded.

If logs point to disk issues or CHKDSK stalls repeatedly, run an offline surface/repair pass from the XP Recovery Console and a vendor surface test. From Recovery Console the common command used is:

chkdsk c: /p /r

A vendor bootable tool (Seagate SeaTools, WD Data Lifeguard, Hitachi/IBM DFT, etc.) gives a full SMART/surface check. If SMART attributes fail or the vendor test finds bad sectors, image the drive immediately (do not attempt heavy repairs first) and replace the drive if tests confirm hardware faults.

Other checks that often isolate the problem: run MemTest86+ from boot media, reseat or swap the data cable and try a different controller port, disconnect nonessential peripherals. If results are inconclusive but data is valuable, consider professional recovery. Summary: collect logs, back up/image if possible, run Recovery Console chkdsk and vendor diagnostics, then act on SMART/test outcomes.

Recommended Answers

All 2 Replies

Member Avatar for mechbas

can you give at least a clue as to what hardware you're using and for how long?

Member Avatar for dcc

Have you scanned for bugs? Most manufacturers have a downloadable diagnostic tool that you make a CD from and boot with it to check out your hdd. If you know what hdd you have try that.

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.