Looks like a bad hard drive.
System Uptime: 17 days 11:59:29.468 17 days eh?
Please back up your stuff before starting diagnostics.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8004da3950, fffffa8004da3c30, fffff80002dd7350}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Followup: MachineOwner
---------
Upload a screenshot using:
For how to upload a screenshot or file, read here
Test your Hard Drive by running:
Use the System File Checker tool and Run Disk Check:
If you get further chkdsk errors, then it's time to:
- backup your stuff/data
- ensure that you have your recovery disks on hand
- wipe the hard drive with DBAN or KillDisk (both are free - google for them)
- install Windows while connected to the internet
- install all Windows Updates, then install Service Pack 1, then install all Windows Updates that show up
- check Device Manager for any missing drivers - post back here for advice on locating the latest version
- install a free antivirus (DO NOT install an Internet Security Application)
- DO NOT install any other programs/devices/etc until we're finished testing.
- Run the system and attempt to recreate the problem.
Once done testing feel free to install whatever programs you desire - but keep track of what you install (just in case it messes things up). DO NOT have more than one Antivirus or Firewall operating at the same time!
Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:
-
For how to upload a screenshot or file, read here
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000006, fffff88000d1c0e9, fffff880062e6778, fffff880062e5fd0}
Probably caused by : hardware_disk
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff88000d1c0e9, The address that the exception occurred at
Arg3: fffff880062e6778, Exception Record Address
Arg4: fffff880062e5fd0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
FAULTING_IP:
CI!MinCrypK_GetCertAlgId+45
fffff880`00d1c0e9 66394104 cmp word ptr [rcx+4],ax
EXCEPTION_RECORD: fffff880062e6778 -- (.exr 0xfffff880062e6778)
ExceptionAddress: fffff88000d1c0e9 (CI!MinCrypK_GetCertAlgId+0x0000000000000045)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 000000000009aa04
Parameter[2]: 00000000c0000185
Inpage operation failed at 000000000009aa04, due to I/O error 00000000c0000185
CONTEXT: fffff880062e5fd0 -- (.cxr 0xfffff880062e5fd0)
rax=0000000000000200 rbx=0000000000000000 rcx=000000000009aa00
rdx=0000000000001c50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000d1c0e9 rsp=fffff880062e69b0 rbp=0000000000000000
r8=000007fffffeffff r9=fffff880062e6aa8 r10=0000000000000000
r11=0000000000000000 r12=fffff8a00000bdd0 r13=0000000000000000
r14=0000000000000000 r15=fffff88002f67f40
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
CI!MinCrypK_GetCertAlgId+0x45:
fffff880`00d1c0e9 66394104 cmp word ptr [rcx+4],ax ds:002b:00000000`0009aa04=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000000000009aa04
EXCEPTION_PARAMETER3: 00000000c0000185
IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
BUGCHECK_STR: 0x7E
EXCEPTION_STR: 0xc0000006_c0000185
FOLLOWUP_IP:
+45
00000000`0009aa04 ?? ???
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
Followup: MachineOwner
---------
Quote