Alright so the source of that blue screen is actually one very simple registry setting which we're going to try to fix. The best possible way of doing this would be to create the .reg file per the instructions below on a different computer and then transfer it to the desktop of the infected PC by some removable storage (CD, USB drive, etc.) and then run it from there. If it takes you multiple boots to get the file onto the infected PC and then to run it by whatever means you can that's fine, don't worry about it.1. Registry Fixes
We're going to use a registry file to make the some changes to your registry. Please copy the complete
contents of the box below to a new notepad file (Start
). Ensure that the code in notepad looks exactly as it does in the box, with no blank lines before the first line of text
. Please click on File
. In the Save as type:
box click the drop-down menu and change the save as type to All files
. Then please save the file to your desktop, naming it fix.reg (this name is important and should not be changed)
Now please doubleclick on fix.reg
. Your computer will ask you if you are sure you would like to merge this file with the registry, click Yes
. The registry fix will then be imported into your registry.
It may be that the screen is gone now. If you still get the screen after importing that reg fix, reboot your PC into normal mode and let me know if it still happens. If the screen is indeed gone, please do this for me:2. OTM
Please download OTM
If a file or folder cannot be moved immediately you may be asked to reboot the machine to finish the move process. If you are asked to reboot the machine choose Yes
. In this case, after the reboot, navigate to the open C:\_OTMoveIt\MovedFiles
folder. Open the newest .log file present in notepad and post its contents in your next reply.
Let me know how everything went once you've given that a try.
Edited by Transience, 14 July 2009 - 08:09 PM.