Windows 7 Service Pack 1 failed install

TheGTShortBus · 12 Apr 2015

I was afraid that it might be hardware. I have run Memtest 86 a couple times and the windows memory diagnostic tool and it has always come back with no errors. I did install a new SSD a while back too and had to install a USB SATA III adapter for that, which didn't go too smoothly if I remember correctly but that was a while ago so I can't remember exactly what all I had to do to get it to work. Regardless, I ran the chkdsk, so here are the files that I got back:

Attachment 355927

NoelDP · 12 Apr 2015

The CHKDSK log is interesting - we don't often see crosslinks nowadays...

Code:

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x10723b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x1025c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 66140.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x12723b for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x25091 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 151697.
284416 file records processed. File verification completed.
Deleting orphan file record segment 90083.
418 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
Index entry SYF836~1.DLL of index $I30 in file 0xeb1f points to unused file 0x15fe3.
Deleting index entry SYF836~1.DLL in index $I30 of file 60191.
Index entry System.Data.Entity.Design.dll of index $I30 in file 0xeb1f points to unused file 0x15fe3.
Deleting index entry System.Data.Entity.Design.dll in index $I30 of file 60191.
335726 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
284416 file SDs/SIDs processed. Cleaning up 307 unused index entries from index $SII of file 0x9.
Cleaning up 307 unused index entries from index $SDH of file 0x9.
Cleaning up 307 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 66140.
Inserting data attribute into file 151697.
25658 data files processed. CHKDSK is verifying Usn Journal...
37069480 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
284400 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
12830885 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
117218303 KB total disk space.
65411352 KB in 144369 files.
91944 KB in 25657 indexes.
0 KB in bad sectors.
391463 KB in use by the system.
65536 KB occupied by the log file.
51323544 KB available on disk.
4096 bytes in each allocation unit.
29304575 total allocation units on disk.
12830886 allocation units available on disk.

You also have a number of EventID 12 from HAL - which indicates that you should check for a BIOS update for your machine.
Event ID 12 Microsoft-Windows-HAL - TechNet Articles - United States (English) - TechNet Wiki

TheGTShortBus · 19 Apr 2015

Ok, after doing some guessing and checking based on what you said above I finally got the update to install. After you mentioned that there might be a hardware or BIOS issue happening, I decided to put my machine back to the last configuration that I knew that it worked in, which meant removing the Storage Controller card that I installed when I added my SSD. Once I did this, the update still didn't install, but I followed up by doing a non-destructive reinstall of windows onto the SSD using the SATA II ports directly on my motherboard (which does have up to date BIOS) and then letting the system go through installing all of the updates during this process. Low and behold, everything installed correctly and my machine is now up to date. Hopefully uninstalling that card and removing it from my board will fix this issue for good. Thanks for all your help, you guys are awesome!

Layback Bear · 19 Apr 2015

A ssd will work quite well on sata II.

Could you post exactly what Storage Controller card you used. I'm really not sure what one of those cards are or what they do.

TheGTShortBus · 19 Apr 2015

Yeah, I was using a "Marvell 91xx sata 6g controller". Basically, my SSD that I bought is SATA III and my board only has SATA II connections. I figured that I would get a little better performance if I could use a SATA III connection instead, so I bought a PCIe expansion card that gave me some extra SATA inputs and was SATA III compatible. Everything seemed to work correctly, but now that I have it out, I think that it was the source of a lot of the problems that I was having. In the end, I don't think that it even gave me any faster performance, my boot time just plugging directly into the mother board seems to be just as good as it was before.