Member Avatar for bavnostroclum

Hi , I had some problems with Windows and decided to make repair using my installation disc with SP1 ( hum, hum )

( I have a Linux ( Ubuntu ) partition on the second HD and using grub to choose which OS to start )


Using installation disc with XP-pro SP1, I made repair installation during which had couple of times problems with finding couple of files , and when restarted and choose this Wind from the GRUB menu it started installation of windows ...39 minutes..and so-on but at the end it just restarted and every next time when I try to start this windows installation it just restarts straight after starting to loading it . i tried even with Safe Mode the same ..


I could get into repair with console in C: dir but I dont know which file is corrupt .

I have made virus scanning using AVK two days but found just 1-2 adware ( till that time using other Anti-Virus ).

Tried couple of times to do again repair ..the same and very often problem with foundng some file s...


I am using Ubuntu for internet now .

i ahve another the same installation of this wind on 1 my old disc from before 9-10 months , could I transfer

the files from there ...I still could see my dirs and files in this Corrupted win installation ...


i will waiting for your answears ...

  • 2 Contributors
  • 2 Replies
  • 133 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by bavnostroclum

Dani AI

Generated

Short summary: a repair install from an older XP SP1 disc started but now the system repeatedly restarts during early loading (Safe Mode also fails). GRUB/Linux is intact and the Windows partition is readable from Ubuntu. A driver named in the boot messages appears to be implicated. was right to try to capture the BSOD instead of letting Windows auto-restart; BIOS "halt on" only affects POST and will not stop Windows from rebooting on a crash.

Immediate priorities — do these in order and do not attempt risky system-file copying between installs:

  • Back up personal data now from Ubuntu. Mount the Windows partition read-only and copy the entire user profile folders (Documents and Settings), desktop, My Documents, and any mail/profile directories to an external disk or your other drive. Imaging the partition (dd or a disk-imaging tool) is also a safe option if planning deeper recovery.

  • Preserve crash evidence for diagnosis: copy any files from C:\Windows\Minidump and C:\Windows\memory.dmp, plus the driver file noted in the crash (the *.sys file) into the backup. Those dumps will let you identify the failing driver with a tool on another machine.

  • Try to disable the suspect driver before more invasive repairs. From Ubuntu or the Recovery Console rename the driver file in Windows\System32\drivers so it won’t load (append “.old”). Then attempt Safe Mode/Last Known Good.

Repair notes and cautions: repair installs using an older SP disc often fail because installed files are at a newer service-pack level; that causes "missing file" prompts during setup. Do not copy core Windows system folders from the old disk onto the damaged one — that creates mismatched registry and DLL problems. If boot records are suspect, use the Recovery Console repair commands to fix MBR/boot and rebuild the boot configuration. If the driver removal and boot-repair steps fail, a clean install from media that matches the current service-pack level (or a slipstreamed disc) after data backup is the safest way forward.

Recommended Answers

All 2 Replies

Member Avatar for nanosani

When starting up press F8 for advanced options and select disable automatically restart option. If there is blue screen of death after restart, tell us the error code.

Alternatively go to windows recovery console and run the following command:
chkdsk /f /r c: [where c: is your windows drive]

Member Avatar for bavnostroclum

I am with Asus A7N8X-E deluxw MB and I thought I have got in Bios the option to stop restart , but it was

halt on

[All Errors]
or this is the same ?
F8 just gives me the choice of Safe mode +/- Netw..and so
I tried already but it stops and restarts after asking me about a345.sys it doesnt matter if I stop it or leave it to load ( this drivers ).

In recovery console : CHKDSK has only /p and /r
I tried them but just gives me that there is 1 or more errors
I tried CHKDSK /r after that and slowly it finished but didnt show anything more ..

Could be the Grub from Linux that stop it starting properly ?
( I have heard before it is easy to use it if you have Wind before Linux , butmaybe there is a problem after I am semi-installing Win on top ..? )

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.