• 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.

Oops...disabled driver, now BSOD

  • Thread starter Thread starter JC
  • Start date Start date
JC

JC

Diamond Member
Short version: XP sp3, whilst trying to fix a Google redirect bug, disabled volsnap.sys (yeah, I know...now). Of course, it won't load windows now. I can get to the recovery console, but I"ve never used that. I installed a second HDD with XP (as boot) so I can get to the files on the fnorked drive. Problem is, I don't know where to look to re-enable volsnap.sys on that drive...registry somewhere, I presume.

Little help? Thanks.
 
The simplest thing is to just paste an image you created earlier back to the disk.

If you never made any, so that's not possible, did you try a restore point from Safe mode?
 
What you could do is mount the registry hive from the borked install of XP from within the working one.
 
that one is a pain to clean off.

1) if you can I would do a system restore which should allow you to boot back up into normal mode.

2) if you that does not work, you can use the recovery console to enable that service again, you would have to use listsvc to find the right service and use enable to start it back up

3) or you can load probably the system hive from \windows\system32\config\system and look under currentcontrolset\service to find the service that wants the volsnap.sys driver and re-enable it.

once that is done get combofix from bleepingcomputer and that should clean it off
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top