Main Forum > General Computer Support
Windows 7 Ult 64 bit trapped by BSD and can not get out.
satrow:
The J: is the drive flagged as having file system errors according to your logs.
If you'd like to stress test your drivers for stability now, you can - but it's not without risks and will usually trigger a BSOD, sometimes as a False Positive or occasionally pointing to a hardware problem. It might also make Windows unbootable - you need to have a Restore Point set and tested before utilising it.
https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-blue-screen-death-related.html. Study this and double-check everything before trying it out. Personally, I'd want to get the PC fully cleaned/patched up before using it.
FreeCat:
Howdy,
I ran the SFC and posted the results here twice, but they did not poste. What could be wrong?
FreeCat:
Howdy here are sfc results again - attached one at a time --- first is beginning and end of log file plus sfc cmd stream messages..
Re-posting as maybe the combined attachments were too big.
My question, when you have time, is is SFC complete?
Should it be run again?
What cause it and what can I do to stope these errors in the future?
Thanks.
FreeCat:
Here is the CBS.log itself --- attached.
Boggin:
My eyes blur over trying to read a full CBS log.
Run the sfc /scannow again and if it reports it is unable to repair all files then copy & paste this cmd to the prompt and press enter.
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > %userprofile%\Desktop\sfcdetails.txt
This will put an icon onto the desktop which when double clicked will open the CBS log in Notepad with what it could and couldn't repair.
You can then copy and paste that into your reply box.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version