• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows Won't Boot

dawks

Diamond Member
We have a Server 2003 box here that used to run Aronis. Acronis was uninstalled but two filesystem drivers were still being loaded. A tech removed the entries for those two Aronis drivers and rebooted. The system now bluescreens repeatedly just seconds after the boot screen appears. This happens even with safe mode. Is there a way to fix this? Repair CD?

Could we edit the registry offline and restore the keys that were removed? How?

I have a feeling these drivers are referenced somewhere else in the registry, we'd either need to restore the keys removed, or remove the other keys.. any clues?
 
Can you see the error on the blue screen prior to the reboot? Booting to the 2k3 cd and repairing *may fix it.*

Immediate bluescreens at boot indicate that either the driver from the disk subsystem is missing (repair should fix that) or the boot.ini is pointing at the wrong partition.
 
Can you see the error on the blue screen prior to the reboot? Booting to the 2k3 cd and repairing *may fix it.*

Immediate bluescreens at boot indicate that either the driver from the disk subsystem is missing (repair should fix that) or the boot.ini is pointing at the wrong partition.

Its just a generic bluescreen, something about running chkdsk.

I'm 99.999% certain its the acronis file system driver.. The driver is there, but the registry key pointing to it was deleted. As I said, its probably referenced somewhere else, and Windows is still trying to load it.
 
Its just a generic bluescreen, something about running chkdsk.

I'm 99.999% certain its the acronis file system driver.. The driver is there, but the registry key pointing to it was deleted. As I said, its probably referenced somewhere else, and Windows is still trying to load it.

Yeah... it should have been removed via device manager. You can grab the raw registry and open it on another computer via regedit "load hive" and correct the entry if you know what you deleted.
 
Instead of F8 Safe Mode, choose Last Known Good Configuration... otherwise manually restore a previous registry copy rather than fiddling with the bad one.
 
Back
Top