• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1170
  • Last Modified:

Roll-Back Device Driver (Unbootable Machine)

We have a client whos PC cannot boot in any mode (safe mode, normal), as it either stops responding after MUP.SYS, or in a normal boot, blue-screens with a nvatabus.sys error.

We simply cannot get in to roll back this driver to the Windows standard driver, so need to do it from the recovery console or from a linux live CD (registry modification, maybe?)

Any ideas?
0
tnesupport
Asked:
tnesupport
  • 3
  • 2
1 Solution
 
tnesupportAuthor Commented:
By the way, the system is a striped RAID array.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
1.  Create an "Ultimate Boot CD for Windows" (www.ubcd4win.com) to boot the system.  I would NOT recommend relying on Linux to fix an unbootable Windows partition (recover data, ok, but not repair anything except possibly a lost admin password - it's like asking an airplane mechanic to fix your car - they both have engines, wheels, and help you travel, but they are EXTREMELY different).
2.  Replace the .SYS file(s) that appear corrupt (replace by RENAMING - you can easily rename back if it causes worse problems or if it doesn't work - undeleting can be a huge pain).  I usually rename the .SYS to .SYS.BAD.  Then put in prior versions (search the disk for prior versions in the $NTUninstall folders OR download them if they are drivers.
3.  If #2 fails to cure the problem, follow the registry repair directions from here (I usually go with the repairs where I pull backups out of the System Volume Information from a few days earlier).  And again, where the document says delete, RENAME instead.  http://support.microsoft.com/kb/307545

Note: a repair install is likely pointless - the REGISTRY in addition to the drivers will likely need to be restored.  And in theory, if you have similar hardware, you can pull the drivers from there - or even do a parallel install and then copy the drivers over.
0
 
tnesupportAuthor Commented:
Replacing the driver did not help.  I need to load an alternative generic driver in place of the nvatabus.sys, which is why I need to figure out how to roll back the driver (or simply enable the correct driver) from a recovery console.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Why are you using the recovery console - I said you should create an Ultimate Boot CD for Windows.

I also said if the driver swap didn't work, then you should roll back the registry (and you can also simply REMOVE (by renaming) the driver and NOT replacing it.
0
 
tnesupportAuthor Commented:
Yes, but this leads to a 0x0000007B blue screen due to the fact that nvatabus.sys is the hard drive driver.  Nonetheless, the issue was with the physical drive (read Dell error code 7--max bad sectors allowed).  Issue resolved.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now