Member Avatar for Helltech

So, we decide to have a LaN party. Everyting is going good. Until one more guy shows up. Well we all have to move pc's to make room. After getting one of my buddies pc's back hooked up, it freezes. It freezes during window's loading screen, with the blue horizontal scroll. Well naturally he wait about 10 minutes, the screen is still there. He the shut down the computer manually. Restarts, goes to safe mode. Then shuts down the computer. Then he turns it back on after about 5 minutes of waiting, and the screen freezes again. Of cource this cuases a viscous cycle. I have done my best of knowledge. It doesn't sound like the HDD to me because we can get into an account on safe mode.

I can always system restore if I need to, but I don't belive that will be nessessary. If you guys could help that would be great.

  • 2 Contributors
  • 3 Replies
  • 126 Views
  • 14 Hours Discussion Span
  • Latest Post Latest Post by caperjack

Dani AI

Generated

Key clues from the thread: the machine hangs at the Windows splash/progress bar after being moved, yet it will boot into a minimal/diagnostic environment (per ). That pattern usually means something that only loads during a normal boot is failing — most often a third‑party driver, a startup service, or a component that gets initialized only in full mode.

Start with non‑destructive triage from the minimal/diagnostic boot:

  • Perform a clean startup with msconfig: hide all Microsoft services, disable the rest, and turn off nonessential startup items. Reboot. If normal boot succeeds, re-enable services/startup entries in halves to find the culprit.
  • Enable boot logging and inspect C:\Windows\ntbtlog.txt for the last drivers attempted; the point where the list stops is a good lead.
  • In Device Manager, remove or roll back the video driver (let Windows use the generic adapter) and test. Video/drivers commonly hang a normal boot while leaving diagnostics untouched.
  • Check the System and Application logs with Event Viewer for errors timestamped at the failed boot.
  • Run chkdsk /f /r (requires reboot) and sfc /scannow to rule out disk or system‑file corruption.

Because the PC was physically moved, also check hardware: reseat IDE/SATA/power cables, RAM sticks, and the graphics card; confirm the monitor cable is snug or try another monitor/cable. Back up important files from the diagnostic environment (or via a rescue/live disk) before doing anything invasive. As suggested, try alternate boot options early; if isolation points to a driver or service that cannot be fixed, consider a repair install after backing up data.

Recommended Answers

All 3 Replies

Member Avatar for caperjack

maybe hes not getting enough power !!

Member Avatar for Helltech

maybe hes not getting enough power !!

No ... because it doesn't work this morning .... and its the only pc here on its own powerstrip.

Member Avatar for caperjack

have you tried F8 and choose last know configeration ,

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.