For the Windows Update issue, I would start a new thread here - Windows Updates & Activation - Windows 7 Help Forums
Code:
BugCheck F4, {3, fffffa800ae66b30, fffffa800ae66e10, fffff8000337e0d0}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Code:
0: kd> !process fffffa800ae66b30 3
GetPointerFromAddress: unable to read from fffff800032af000
PROCESS fffffa800ae66b30
SessionId: none Cid: 0278 Peb: 7fffffdd000 ParentCid: 024c
DirBase: 1e5bc0000 ObjectTable: fffff8a00adae470 HandleCount: <Data Not Accessible>
Image: csrss.exe
VadRoot fffffa800b8b4290 Vads 145 Clone 0 Private 571. Modified 1705. Locked 0.
DeviceMap fffff8a000008aa0
Token fffff8a00adb6060
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 174264
QuotaPoolUsage[NonPagedPool] 17408
Working Set Sizes (now,min,max) (1394, 50, 345) (5576KB, 200KB, 1380KB)
PeakWorkingSetSize 8816
VirtualSize 50 Mb
PeakVirtualSize 63 Mb
PageFaultCount 118117
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 795
Code:
0: kd> !dpx
Start memory scan : 0xfffff8800c7bc738 ($csp)
End memory scan : 0xfffff8800c7be000 (Stack Base)
rax : 0xfffff8800c7bc7c8 : 0xfffff80003331ec4 : nt!NtTerminateProcess+0xf4
rsp : 0xfffff8800c7bc738 : 0xfffff80003405d92 : nt!PspCatchCriticalBreak+0x92
rbp : 0xfffff8000337e0d0 : !da ""Terminating critical process 0x%p (%s).""
rsi : 0xfffffa800ae66e10 : !da "csrss.exe"
r9 : 0xfffffa800ae66e10 : !da "csrss.exe"
r11 : 0xfffff8800c7bc848 : 0xfffff80003076e13 : nt!KiSystemServiceCopyEnd+0x13
0xfffff8800c7bc738 : 0xfffff80003405d92 : nt!PspCatchCriticalBreak+0x92
0xfffff8800c7bc758 : 0xfffffa800ae66e10 : !da "csrss.exe"
0xfffff8800c7bc760 : 0xfffff8000337e0d0 : !da ""Terminating critical process 0x%p (%s).""
0xfffff8800c7bc7c8 : 0xfffff80003331ec4 : nt!NtTerminateProcess+0xf4
0xfffff8800c7bc848 : 0xfffff80003076e13 : nt!KiSystemServiceCopyEnd+0x13
0xfffff8800c7bc9b8 : 0xfffff800030733d0 : nt!KiServiceLinkage
0xfffff8800c7bcd90 : 0xfffff800031f2e00 : nt!KiInitialPCR+0x100
0xfffff8800c7bcde8 : 0xfffff8000304e55e : nt!KiOpDecode+0xf6
0xfffff8800c7bce78 : 0xfffff80003075d7a : nt!KiPageFault+0x23a
0xfffff8800c7bd0c8 : 0xfffff8000310344c : nt!RtlpCopyXStateChunk+0x5c
0xfffff8800c7bd0e8 : 0xfffff8000306acd4 : nt!RtlpCopyLegacyContextAmd64+0x144
0xfffff8800c7bd118 : 0xfffff80003077d33 : nt!KeContextToKframes+0x83
0xfffff8800c7bd1f8 : 0xfffff800030c4790 : nt!KiRaiseException+0x1b4
0xfffff8800c7bd538 : 0xfffff8000304d9d2 : nt!MiCopyDataPageToImagePage+0xa66
0xfffff8800c7bd5a8 : 0xfffff88000ccd577 : CI!CiValidateImageData+0x343
0xfffff8800c7bd678 : 0xfffff800030a5521 : nt!MiResolveMappedFileFault+0x971
0xfffff8800c7bd6d8 : 0xfffff80003089fd2 : nt!MiUpdateWsle+0x1b2
Code:
0: kd> !error 0xc0000005
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
A page fault was called to most likely add pages to the working set of the process, but because the amount of available pages may have been exhausted already, and no trimming took place, then the system crashed.
Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours: