Remove Driver from Bootable OS

I was installing a windows update last night and I guess the driver was bad for my onboard secondary Marvel RAID controller (it holds 1 extra drive).

I guess it didn't install properly and now when I try to turn on the computer as the windows 7 logo fades in it stops and just sits there.  Occasionally when I restart it will try to repair itself  but I get a bad driver install in the diagnostic details.

I have a copy of a fully backed up system (via the Windows Backup) from a while and but it has all the right drivers on it.  Can I restore to that only and not have it delete my files?

Or is there a way I can boot to BartPE load the registry and disable that device so the driver doesn't try to load?

JOe K.
Who is Participating?
DavidConnect With a Mentor PresidentCommented:
So two controllers?  Well, now all sorts of horrible things come to mind, especially if controllers are the same, but may have different versions of firmware.   Anything from total confusion like it decided to mirror the wrong disks come to mind.

I would use another PC and go to and download either a live USB or live CD, so you can boot that system to LINUX and safely look around.  This gives you a workable O/S and you can do a read-only mount.   No telling what the problem is.  This will let you use the PC in a ramdisk.  I would go to the motherboard and controller vendor sites, and look at help, release notes, see if firmware/drivers/bios are current.   Dont change anything.

Do not attempt to boot this to windows or do a fixmbr or chkdsk. That could do a heck of a lot of damage.  

You could also go to and download their NTFS getdataback (and/or RAID reconstructor if this is a RAID array, which you did not mention).   They have instructions on how to use the software and boot on a USB stick.

The software is free to try, you pay to recover.  Let it have a go at things.  I fear that it will be just too difficult to get to the bottom of things w/o looking at hexdumps and running specialized software.  YOu could have anything from overwritten blocks from another disk to just a munged up registry, but based on what you report, root cause is clearly a "bug" or incompatibility.  So in that case, the only thing you can expect is unpredictability.


 * Assess hardware / run disk diagnostics for bad blocks, - easy with ubuntu
 * Look at release notes, bug fixes, notes on configuring multiple controllers, etc.  if not current then READ release notes.  It is RARE, but I have seen situations where an update is destructive, and you have to take a full backup, update, then restore.  I hope that is not the case.
 * and let it try to make sense of the file systems.  If it can recover, then it will be well worth the money, I'm sure.
If the driver was busted, then it wouldn't have gotten that far.  You would get an error message indicating no boot device found.
This looks like file system corruption.  I would step back, and run hardware diagnostics first.

Use something like an ubuntu live USB or live CD, so you can run hardware diagnostics that they bundle with the O/S.
ClaudeWalkerAuthor Commented:
The secondary RAID controller has a non-OS drive on it.  Would that make a difference with regards to how far it gets?  
ClaudeWalkerAuthor Commented:
I got it!

I disabled the secondary RAID controller from the BIOS.  Then it booted.  I uninstalled the driver rebooted and re-enabled the controller.  7 booted and installed the old functional driver.  Now it's working perfect!

Thanks for taking the time to help.

JOe K.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.