BSOD 0xF4 CRITICAL_SYSTEM_TERM, Csrss.exe & wininit.exe, New Instal

I Installed Windows 7 SP1 x64 on my custom computer two nights ago. I've been running Linux as of late, but I really wanted to play a Windows exclusive game that I have been having my eye on. I received a CRITICAL_OBJECT_TERMINITATION (0xF4) error code that points to "csrss.exe" and "wininit.exe" as the culprits.

Some history on my build and previous problem:
I assembeled my computer during May of 2015. (Note: this was a Windows 7 x64 NOT SP1). It was working relatively well after the install was complete, but I was gradually getting an increasing amount of Bluescreens. I can't remember the error code, but it kept saying the culprit was "csrss.exe", which as we know is a vital system process (which makes me think it was 0xF4 error). I tried troubleshooting that by:

1. Running sfc/scannow
2. Malwarebytes (to rule out viruses naming themselves as "csrss.exe")
3. Changing the account priviliages && creating a new account due to an article suggesting that "csrss.exe" could corrupt accounts.
4. Driver verifier, which ended up screwing up my system and preventing my from getting past the log-in screen into Windows. Microsoft drivers were not selected.
5. MemTest86+ accross all 4 of my RAM sticks for approximately 12-24 hours each (dependent on when I got home from work/school). All sticks passed.
5. Fresh, clean install of windows 7 (did this about 4 additional times, all with the same outcome. Certain Windows update always caused a crash, so I could not update to Win10.).

Fast forward to March 2016:
Fresh, clean install of Windows 7 SP1 x64. Updated all Windows updates to whatever was current as of March 3, 2016 with no "important" updates remaining, I restarted my computer.

I installed the "recommended" NVIDIA update for the GTX 960, 970, 980, 980Ti, Titan series cards, which resulted in a crash (no BSOD was showing, it just instantly rebooted).

It requested that I restore from the most recent, stable point, so I did so. Upon rebooting, I checked to see if all my Windows updates were still up-to-date (they were), so then I proceeded to try and get my desired driver from NVIDIA. After the prompt to restart, my computer crashed at the login screen. It was left unattended for approximately 5 minutes.

There were a few additional crashes because I left it at the log-in page to see what would happen. Flash of a black screen followed by an instant reboot. No BSOD was showed. The average time of the crashes was always less than 5 minutes.

I restored my computer to the last stable/working restore point. I CAN boot into SAFE MODE and did so for 20 minutes IDLE with no crashes.

I used WinDBG in my VM on my Linux SSD (separate from Windows, I have two SSDs) to view the the MiniDumps. All four were the CRITICAL_OBJECT_TERMINIATION (0xF4) and two of those crashes were for "csrss.exe" and two were for "wininit.exe".

I ran the DM LOG COLLECTOR in safe mode with no issues.

I am hoping to have the SevenForums community walk me through this attempt at fixing my computer step by step.

Would it be OK to run the test & update the firm ware in safe mode? Will it allow me to update the firmware in safe mode?

Thanks,

Omni

Omnisophic said:

Would it be OK to run the test & update the firm ware in safe mode? Will it allow me to update the firmware in safe mode?

Thanks,

Omni

New problem. After pressing F8 to boot into safe mode, it is not recognizing any USB devices, such as my mouse and keyboard. Consequently, I cannot log in to preform the Disk Check.
Edit: Or even when booting in normally.
Ignore the above. Power isn't going to my peripherals... hmmm...
Edit: Peripherals still work in BIOS and in Linux. I'm really confused. Did my Windows suddenly become corrupted?

BorisTheAnimal said:

Hello Omni.

In what ports are your peripherals connected?

Directly to my motherboard. I have tried two USB 2.0 ports and all four of my USB 3.0 ports.
I have not tested the headers on the front of my case.

BorisTheAnimal said:

Omnisophic said:

BorisTheAnimal said:

Hello Omni.

In what ports are your peripherals connected?

Directly to my motherboard. I have tried two USB 2.0 ports and all four of my USB 3.0 ports.
I have not tested the headers on the front of my case.

Well there would be a BIOS update for your motherboard, I'm wondering if it would be a cause.

MSI support page:
https://www.msi.com/product/motherbo...html#down-bios

How-to guide:
https://www.msi.com/files/pdf/How_to_flash_the_BIOS.pdf

Cheers, Boris :)

I'm really nervous about flashing the BIOS, but I'll report back on this same comment once I do so.
Edit: It worked & peripherals are accepting input. You're my hero.

axe0 said:

This is a common error with the 0xF4, input/output errors what basically means the data of your hard drive can't be accessed properly.
Please make sure your SSD's firmwares are up to date.

Diagnostics Test

 HDD TEST

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa800e8b2060, Terminating object
Arg3: fffffa800e8b2340, Process image file name
Arg4: fffff80003399e80, Explanatory message (ascii)

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

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

KERNEL_LOG_FAILING_PROCESS:  

PROCESS_OBJECT: fffffa800e8b2060

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - De instructie op 0x%p verwijst naar geheugen op 0x%p. De benodigde gegevens zijn niet in het geheugen geplaatst vanwege een I/O-foutstatus van 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`02e0d9c8 fffff800`034286f2 : 00000000`000000f4 00000000`00000003 fffffa80`0e8b2060 fffffa80`0e8b2340 : nt!KeBugCheckEx
fffff880`02e0d9d0 fffff800`0334d14b : ffffffff`ffffffff fffffa80`0eaf4b50 fffffa80`0e8b2060 fffffa80`0e8b2060 : nt!PspCatchCriticalBreak+0x92
fffff880`02e0da10 fffff800`03349cd8 : ffffffff`ffffffff 00000000`00000001 fffffa80`0e8b2060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29746
fffff880`02e0da60 fffff800`03091653 : fffffa80`0e8b2060 00000000`c0000006 fffffa80`0eaf4b50 ffffffff`00008000 : nt!NtTerminateProcess+0xf4
fffff880`02e0dae0 00000000`7723d67a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01fbff48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7723d67a


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

Attached is the output from CHKDSK and the results for BOTH SSDs from HDTune.
Installed the Samsung Magician Software to check for firmware updates. My resolution is not supported as I do not yet have the video driver to support the screen size (1024x768?), so it cuts the update button off the screen. Additionally, it is not resizable. Even with networking enabled in safe mode, I can't update because it won't connect to my network. Samsung requires a network connection to check for firmware.
I'll try booting normally, but I wanted to ship these results off to you.

Edit: Still cannot update Firmware because of screen resolution limitations.
I did, however, notice that some Microsoft Updates were available that I thought were updated. They must have been undone when I rolled back. I apologize for the discrepancy because I thought I was all up-to-date. Do you happen to recognize any of these as problematic updates?
Thanks for all your help so far.