BSOD from Windows Update

Actually, I found I can just remove the drive and run chkdsk on another computer. So far, no bad sectors. :)

OK, here is the event log for chkdsk, run as f: on another laptop, along wtih the XML stuff:

Code:

Log Name: Application
Source: Chkdsk
Date: 24/12/2012 10:52:22 PM
Event ID: 26214
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Shire
Description:
Chkdsk was executed in read/write mode. 
Checking file system on F:
The type of the file system is NTFS.
CHKDSK is verifying files (stage 1 of 3)...
952320 file records processed. 
File verification completed.
449 large file records processed. 
0 bad file records processed. 
0 EA records processed. 
60 reparse records processed. 
CHKDSK is verifying indexes (stage 2 of 3)...
1061882 index entries processed. 
Index verification completed.
0 unindexed files scanned. 
0 unindexed files recovered. 
CHKDSK is verifying security descriptors (stage 3 of 3)...
952320 file SDs/SIDs processed. 
Cleaning up 2978 unused index entries from index $SII of file 0x9.
Cleaning up 2978 unused index entries from index $SDH of file 0x9.
Cleaning up 2978 unused security descriptors.
CHKDSK is compacting the security descriptor stream
54782 data files processed. 
CHKDSK is verifying Usn Journal...
34116528 USN bytes processed. 
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
117115903 KB total disk space.
51454200 KB in 622060 files.
288188 KB in 54785 indexes.
0 KB in bad sectors.
1056443 KB in use by the system.
65536 KB occupied by the log file.
64317072 KB available on disk.
4096 bytes in each allocation unit.
29278975 total allocation units on disk.
16079268 allocation units available on disk.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Chkdsk" />
<EventID Qualifiers="0">26214</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-12-25T03:52:22.000000000Z" />
<EventRecordID>40589</EventRecordID>
<Channel>Application</Channel>
<Computer>Shire</Computer>
<Security />
</System>
<EventData>
<Data>
Checking file system on F:
The type of the file system is NTFS.
CHKDSK is verifying files (stage 1 of 3)...
952320 file records processed. 
File verification completed.
449 large file records processed. 
0 bad file records processed. 
0 EA records processed. 
60 reparse records processed. 
CHKDSK is verifying indexes (stage 2 of 3)...
1061882 index entries processed. 
Index verification completed.
0 unindexed files scanned. 
0 unindexed files recovered. 
CHKDSK is verifying security descriptors (stage 3 of 3)...
952320 file SDs/SIDs processed. 
Cleaning up 2978 unused index entries from index $SII of file 0x9.
Cleaning up 2978 unused index entries from index $SDH of file 0x9.
Cleaning up 2978 unused security descriptors.
CHKDSK is compacting the security descriptor stream
54782 data files processed. 
CHKDSK is verifying Usn Journal...
34116528 USN bytes processed. 
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
117115903 KB total disk space.
51454200 KB in 622060 files.
288188 KB in 54785 indexes.
0 KB in bad sectors.
1056443 KB in use by the system.
65536 KB occupied by the log file.
64317072 KB available on disk.
4096 bytes in each allocation unit.
29278975 total allocation units on disk.
16079268 allocation units available on disk.
</Data>
<Binary>00880E00F7530A002801120000000000A80000003C0000000000000000000000</Binary>
</EventData>
</Event>

That's not as bad as I was expecting.

I'd suggest another SFC and CheckSUR now - post the logs, and we'll see if anything has changed.

I've been noticing something strange. While the BSODs seem to occur even when I am doing next to nothing, as much as when I am running Windows Update, (and at other times, such as running Internet Explorer) and whatnot, when Windows Update is run in the background, it seems to install all the updates it likes. At least this is true on the native HD. I should try it on the SSD also, although I know that there are certain updates that it will not install on the SSD.

Since the most recent BSODs occured on a different drive, I won't report them to avoid confusion. But it seems to suggest that it is not the hard drive. The fact that the SSD had an old Windows 7 image (accounting for its huge footprint early on should have told me something. What I did by using a Windows 7 Upgrade DVD to, in fact, upgrade a W7 installation from an older computer, was to install on top of an old installation. I didn't notice until a couple of days ago that the partition was never reformatted, and that all my old programs from before the installation were still there, now completely useless. I have read that not doing a fresh install can invoke certain BSODs.

I don't know what to do at this point, except look for an OEM of W7 HE.

I have downloaded the individual drivers and programs from the HP website, and I will attempt to install them on the SSD. Right now, Windows Update is installing 91 updates (it did this without my help) and won't shut down until it does.

I will not comment on Staples' "offer" - except to say that it's not worth the paper it's [not] printed on.

Glad you seem to be all sorted now - good luck!