Blue screen loop...

[chronodeco]

Downloaded Tweak last Friday because I will getting error codes 0001 and 0002 when I tried to install my new Canon printer in Windows 8. Ran the program per instructions and when finished the blue screen came up. The only thing I can access is the command prompt. It will not respond to F4 when trying to get into the same mode. All other attempts bring it back the the same advanced option screen or shuts it down. I am an amateur at this so simple instructions are needed - please advise. Thanks, Craig

[Boggin]

In which mode are you able to access the Command Prompt ?

If it is in normal mode what do these cmds report -

sfc /scannow

dism /online /cleanup-image /restorehealth

If in the advanced boot options -

chkdsk c:

With this cmd take note of any KBs in bad sectors.

[chronodeco]

I am in the advanced options. I have attached a pic of the screen to make sure I have explained this correctly. Does chkdsk c: go after the prompt?
Also as a non computer person, please explain: With this cmd take note of any KBs in bad sectors. Thanks

[Boggin]

Those tell me that you are in the Recovery Environment at the X prompt outside of Windows.

Enter bcdedit |find "osdevice" and using whichever partition letter that gives, enter chkdsk x: /f where x is the partition letter.

That is a Pipe symbol before find and is the uppercase of \

As regards the KBs  in bad sectors, below is an example of my Win 7 chkdsk in read-only mode and near the end of the report you will see where it displays 0 KB in bad sectors, but while you aren't likely to have any, they are always worth making a note of.

Hopefully the /f parameter will repair any file corruption on your machine, but BSODs (Blue Screen of Death) are usually caused by 3rd party driver problems.

The 0001 and 0002 errors are a known Windows problem going by this article  http://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/error-message-0001-0002-when-installing-printer/4032320e-b632-4dd6-8e86-b0ae384808cd but I don't know why the WR program should have caused the BSOD.

If the chkdsk x: /f doesn't repair your files, then this will need to be something for Shane to resolve.

The MS Fixit link referenced in the article is for https://support.microsoft.com/en-us/mats/windows_file_and_folder_diag/en-sg but you won't be able to access that from the RE.

If it had some Fix it yourself steps then you may have been able to access the registry with the command regedit but as things stand....

What are you using to post ?

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is WINDOWS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  198656 file records processed.
File verification completed.
  319 large file records processed.
  0 bad file records processed.
  0 EA records processed.
  47 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
  250844 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  198656 file SDs/SIDs processed.
Security descriptor verification completed.
  26095 data files processed.
CHKDSK is verifying Usn Journal...
  36474424 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

 624719871 KB total disk space.
  50895696 KB in 104790 files.
     67788 KB in 26096 indexes.
         0 KB in bad sectors.
    320943 KB in use by the system.
     65536 KB occupied by the log file.
 573435444 KB available on disk.

      4096 bytes in each allocation unit.
 156179967 total allocation units on disk.
 143358861 allocation units available on disk.

C:\Windows\system32>