SFC Scannow on a USB Hard Drive - where is the CBSlog?

[Modular]

Hi all,

So, some backstory: my PC was running just fine for a few days. I restarted it and was met with the "Windows needs to run CHKDSK". I let it run, and it said it found bad sectors on my SSD, and restarted the computer again. Since then, the PC is stuck in a reboot loop. It makes it the windows screen and then black screens and restarts every time.

I've run sfc scannow from the repair environment and it says that it has found corrupt files but is unable to repair them. Details can be found in the CBSlog. I cannot find the CBS log through the command line, so I took the suspect drive out and put it in a USB case and ran SFC scannow on it there, but I have no idea where it's placing the CBS log.

Can someone please help me?


Some other things I've tried:
I've run malwarebytes and chkdsk on the ssd again and it says that there are no problems. The only thing that is causing issues seems to be the corrupted files that SFC scannow finds. I heard that it's best to run scannow 3 times in a row, so I ran it 4...still nothing.

I've also checked and I can access all of my files that are on the drive, but I cannot get it to boot.

Many thanks!

 

[Layback Bear]

Welcome to our Forum.
I would suggest installing the ssd back where it belongs.

Please read and understand completely the tutorial by Brink.
Pay attention to the rebooting and posting logs.
We have some good members that can read and understand the log.
I'm not one of them. I will find one if need be.
Windows 7 System Files must be correct.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Another option if needed by Bare Foot Kid.

http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[Modular]

Thanks for the reply.

I followed brink's tutorial when I initially ran the sfc scannow command. The problem I'm having is that I have no way to access the cbs log because my PC will not boot into Windows.

Where can I find the log file that sfc scannow creates?

 

[Ztruker]

Normally it's placed in: "C:\Windows\Logs\CBS\CBS.log"

That would be on whatever computer you run sfc on.

 

[Modular]

OK, thanks for the continued help. Here's where I'm at now.

I re-installed the SSD into the computer it came from and ran the Windows Repair from the CD. I followed Brinks' instructions on how to run Scannow and was able to access my CBS log from the CMD prompt using "notepad D:\windows\logs\cbs\cbs.log"

Here's where it gets weird again - the final entry in the log occurred on 3/17/2014. I've run scannow on this hard drive 3 time today alone and the log hasn't been updated. Am I missing something here? Again, I can still access all the files on this drive when I put it into a USB enclosure and view it from another computer, so the drive isn't likely to be bricked.

Thanks!

 

[Ztruker]

When you boot the repair DVD (not CD, right) the boot drive is normally X:. It's a virtual drive carved out of memory. See if there is a X:\windows\logs\cbs\cbs.log after you run SFC.

Try dir x:\cbs.log /s - see if it finds anything.

 

[Modular]

Yes, I was using the windows DVD. I ended up just getting frustrated and reinstalling Windows. Everything seems fine now. I wish I would have read this first!

 

[Ztruker]

I wish I had thought of it earlier!!! Glad you have it fixed though.