PC crashes

[ppppenguin]

Results of driver verifier. I think windrv6.sys may be related to some Jungo software installed by my Xilinx tools for driving programming cables. Pretty sure I had crashes before I installed this software hough can't be 100% certain.

Windows details:
W7 pro
Version 6.1
Build 7601 service pack 1

[ppppenguin]

SFC /SCANNOW

It said: Windows resource protection found corrupt files but was unable to fix some of them. Details in CBS.log

CBS.log file attached. Had to zip it as it was too large to be attached otherwise.

[ppppenguin]

Had a crash this morning. Looked for the minidump but only found ones dated 8/3/17 and 10/3/17.

[Nick]

SFC /SCANNOW

It said: Windows resource protection found corrupt files but was unable to fix some of them. Details in CBS.log

CBS.log file attached. Had to zip it as it was too large to be attached otherwise.

The main reason it had problems is that your disk is showing all sorts of issues with the file structure.

Did you run the chkdsk /F /R?

Many directories seem to have multiple owners etc. SATA III cables checked?

There are also many SFC comparison errors in there - it just looks like a really unhappy disk. Let's do the chkdsk /F /R and go from there.

Did you run the program I suggested on the mindumps you do have?

Cheers

[Nick]

Once we have the chkdsk done and we are sure that the SATA cables are REAL SATA III cables, we need to recover the SxS store which seems to have some corrupt files in it. After that, if SFC /SCANNOW is still having problems (as I suspect it will), we can firstly use DISM to recover those, and then if that doesn't work, we'll just use Windows 7 recovery for an in-place upgrade (phew!).

In 2015, Microsoft backported a DISM command from Windows 8 to Windows 7 to repair files. Look if it is possible to install KB2966583, then open a command prompt as admin and run:

Code:

DISM /Online /Cleanup-Image /Scanhealth

... to try to repair the damaged files. Note that you MUST have done the chkdsk repair first.

If this fails, we'll try the in-place upgrade (details later). Still, the best option for Windows 7 to make sure it gets fully repaired.

[ppppenguin]

How do I tell if they're real SATA III cables?

Off out now. I'll do the other stuff a bit later.

[ppppenguin]

Ran CHKDSK /r/f
Can't find the log file despite looking in the event viewer but I saw no odd comments while it was running except in stage 1 of 5:

373 large files
0 bad
2 EA
8 Reparse

Everything else completed without any warnings etc.

[Nick]

How do I tell if they're real SATA III cables?

SATA III cables should explicitly state "6 Gb" on them - they also have a separation between the two halves - see the picture below.

As your MB is a SATA III motherboard, the cables that came with it should be SATA III - they should be pretty stiff and be similar to the one below...

   

FYI: Seeing some Reparse and Extended Attribute records is perfectly normal - they are infrequently used features of NTFS which is why there are only a few of them - mostly, they are only used by Windows itself.

[ppppenguin]

Had a major SNAFU. Had a look at the SATA cables. There were 2x SATA III, the other 3 were not. As luck would have it, the SATA III cables weren't connected to the C and D drives. So I swapped over the cables but, as I found out later managed to get the D drive connected to another drive rather than the mobo. Wouldn't boot giving "The user profile service failed the login". Not entirely surprising as my user folder is on the D drive with a symlink that makes it appear to be on the C drive. Put back cables correctly, did a check in BIOS to see that the drives were all present. Still gives same fail.

I can see some fixes here but I'm not very happy about following them: http://www.expertreviews.co.uk/software/...le-service

Help!

List of SATA devices..............
C drive (512MB SSD)
D drive (1TB HDD)
2x optical drives (Presumably these don't need SATA III cables)
Internal drive caddy that I use for backups. I really ought to give this a SATA III cable.

[Nick]

Ah. I may have to think about this for a while. Its not obvious... but a corrupt profile is a pain.

Had you, by any chance, enabled the Administrator account on your host? i.e. is there another account with LocalAdmin privilege you can log in to?