BSOD on startup. Sopt code F4

Hi Jimbo15,

It seems you are running a counterfeit installation.
Troubleshooting a counterfeit installation is useless because it is not known what has been modified to your system.

Likely I made a huge mistake

How have you activated Windows?

It is likely that I just made a huge mistake about your activation

I am not sure anymore, but I am extremely sorry about it :O

Back to the crashes, there are I/O errors. This means that the data can't be read from your hard drive.
Please test your hard drive

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check

Code:

BugCheck F4, {3, fffffa8008132b10, fffffa8008132df0, fffff800031d9e70}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8008132b10, Terminating object
Arg3: fffffa8008132df0, Process image file name
Arg4: fffff800031d9e70, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

DISK_IO_READ_FAILURE:  WARNING: Disk IO Read of 0 Bytes Occurred 4 time(s).

PROCESS_OBJECT: fffffa8008132b10

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

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.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`073a79c8 fffff800`0326bcb2 : 00000000`000000f4 00000000`00000003 fffffa80`08132b10 fffffa80`08132df0 : nt!KeBugCheckEx
fffff880`073a79d0 fffff800`03222d8b : ffffffff`ffffffff fffffa80`08136b50 fffffa80`08132b10 fffffa80`08132b10 : nt!PspCatchCriticalBreak+0x92
fffff880`073a7a10 fffff800`0318d484 : ffffffff`ffffffff 00000000`00000001 fffffa80`08132b10 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29ce6
fffff880`073a7a60 fffff800`02ed4853 : fffffa80`08132b10 00000000`c0000006 fffffa80`08136b50 000007ff`fffd9000 : nt!NtTerminateProcess+0xf4
fffff880`073a7ae0 00000000`77a3dc7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012f838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a3dc7a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_wininit.exe

FAILURE_ID_HASH:  {7e8d25f6-54c6-2456-f4df-269f2fd35200}

Followup: MachineOwner

Not needed if SeaTools fails at the short test.
The short test is the test where hard drives usually passes, but the long test should then determine it.

Backup your data and replace the hard drive as soon as possible.