Several BSOD's (at desktop or startup) cause unknown

[SG2009592]

I have been having an issue with several different BSOD for the past 2 or so weeks. The Critical_Object_Termination (Bug code F4) will often happen at startup (before the login screen) usually on another reboot it works fine. I received a BSOD that isn't in BlueScreenView (bug code D4 issue with my NIC driver bflwfx64.sys), I have downloaded the updated driver for that and about to install it. All of the blue screens I have been at the desktop (not gaming).

I am currently not overclocking, CPU,GPU, and RAM are at stock clocks. I ran a Memtest86+ overnight for 6 passes no errors, and I have downgraded my VGA driver from 320.49 to 320.18 without any success. I have also had unexplainable system freezes and hard locks. I have tried driver verifier using the steps on here (http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html) and when the system boots up I immediately get a BSOD.

Update: Removed Killer NIC drivers rebooted and it took 5 tries to get to the login screen before I could login and reinstall.

My system is as follows:
4770k
16GB 2133 (G.Skill)
nVidia 770
512GB Samsung 840 Pro
SeaSonic X-850

 

[Arc]

Hi SG2009592.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Update Asmedia 106x SATA Host Controller Driver.

fffff880`00cc0000 fffff880`00cd0000   asahci64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\asahci64.sys
[COLOR=Red]    Image name: asahci64.sys
    Timestamp:        Wed Jul 18 08:45:00 2012[/COLOR] (50062A34)
    CheckSum:         0000C85B
    ImageSize:        00010000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get it from ASMedia Technology Inc. ????

* And, make it sure that the Samsung SSD 840 is running with the latest firmware.
Samsung SSD | Samsung Semiconductor Global Website

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.
____________________________________________________________________________________
BSOD ANALYSIS:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8011605240, fffffa8011605520, fffff80003d8a350}

----- 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: fffffa8011605240, Terminating object
Arg3: fffffa8011605520, Process image file name
Arg4: fffff80003d8a350, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa8011605240

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (Win32) 0x5 (5) - Access is denied.

BUGCHECK_STR:  0xF4_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`095ed9c8 fffff800`03e11d22 : 00000000`000000f4 00000000`00000003 fffffa80`11605240 fffffa80`11605520 : nt!KeBugCheckEx
fffff880`095ed9d0 fffff800`03dbe08b : 00000000`00000001 fffffa80`119f1060 fffffa80`11605240 fffff880`095edae0 : nt!PspCatchCriticalBreak+0x92
fffff880`095eda10 fffff800`03d3e144 : 00000000`00000001 00000000`00000001 fffffa80`11605240 0000007f`00000000 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`095eda60 fffff800`03a82e93 : 00000000`00000008 00000000`00000005 fffffa80`119f1060 00000000`003f5cb8 : nt!NtTerminateProcess+0xf4
fffff880`095edae0 00000000`76ff15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0021fba8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ff15da


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_5_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_5_IMAGE_wininit.exe

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

 

[SG2009592]

I removed Daemon Tools, ran the SPTD uninstaller, removed Intel RST and uninstalled the driver in device manager. Unable to find new ASMedia drivers except on some unknown site where the drivers are unsigned, I don't feel comfortable installing those.

Also grabbed the latest Realtek drivers, BIOS, Intel USB 3.0 (don't have anything on the 3.0 controllers though), Intel Management Engine drivers (Probably unneeded) from MSI's website. Samsung SSD is running latest firmware.

Disabled a few startup options because at that point (a dozen or so reboots) I didn't blue screen once. Will keep monitoring the situation and will post back tomorrow or when I blue screen next, as I have been unable to go 24 hours without a BSoD.

Thank you for your assistance thus far.

 

[SG2009592]

Unfortunately today on startup I got another BSOD (F4). I have just disabled everything except for ESET. But when these BSOD's happen it is pre login screen (black screen with mouse cursor in the middle where it hangs for a few seconds) then BSOD F4's.
If helpful I have attached the new dump files (from SF_diagnostics).

Will also try and see if it is possible to disable the ASMedia controller in the BIOS.

 

[Arc]

Yes, it is another stop 0xF4.

As far as I have noticed, a stop 0xF4 is a storage related error. Somehow the storage access is getting blocked and this particular BSOD occurs.

The things that can cause are a failing HDD/SSD, not up-to-date firmware/BIOS, not up-to-date storage controllers, programs or applications controlling storage device (say backup or defrag tool), virus infection or even a filter driver of an antivirus programs.

• The BIOS is up to date here.So leave it as it is.
• You are saying the the SSD firmware is up to date. And the SSD is the only storage device here.
• As you cannot update Asmedia driver, disabling it will be a good idea. If it run on the native AHCI controller then the situation will expected to be a bit more stable.
• Uninstall EaseUS Todo Backup Advanced Server 4.5.
• Scan the system for possible virus infection with the following programs.
  
  • Anti-rootkit utility TDSSKiller
  • Windows Defender Offline
• Uninstall ESET, at least as a test. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
  Download, install and update those, and then run full system scans with both of them, one by one.
• How old the Logitech Keyboard/Mouse are? The drivers goes back to June 2009. As those are set to startup, those may be the root of the issues, too. If those are really old, try to update the drivers from Logitech Support - Downloads, Manuals, FAQs & More .

Let us know the results.
__________________________________________________________________________
BSOD ANALYSIS:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800fb5bb30, fffffa800fb5be10, fffff80003d8e350}

----- 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: fffffa800fb5bb30, Terminating object
Arg3: fffffa800fb5be10, Process image file name
Arg4: fffff80003d8e350, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa800fb5bb30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (Win32) 0x5 (5) - Access is denied.

BUGCHECK_STR:  0xF4_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`083f19c8 fffff800`03e15d22 : 00000000`000000f4 00000000`00000003 fffffa80`0fb5bb30 fffffa80`0fb5be10 : nt!KeBugCheckEx
fffff880`083f19d0 fffff800`03dc208b : 00000000`00000001 fffffa80`0fb5db50 fffffa80`0fb5bb30 fffff880`083f1ae0 : nt!PspCatchCriticalBreak+0x92
fffff880`083f1a10 fffff800`03d42144 : 00000000`00000001 00000000`00000001 fffffa80`0fb5bb30 0000007f`00000000 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`083f1a60 fffff800`03a86e93 : 00000000`00000008 00000000`00000005 fffffa80`0fb5db50 00000000`00495cb8 : nt!NtTerminateProcess+0xf4
fffff880`083f1ae0 00000000`771b15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011fb18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771b15da


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_5_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_5_IMAGE_wininit.exe

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

 

[SG2009592]

I believe I have disabled the ASMedia controller in the BIOS (External SATA 6GB's controller). On boot Windows reinstalled ATA Chennel 0, ATA Channel 1, and Standard Dual Channel PCI IDE Controller using Microsoft's drivers.
In Samsung Magician it reports the currently installed firmware is DXM05B0Q and says that this is the latest firmware.
I have gone ahead and removed ESET, and EaseUS.

Both those links you put for the Anti-rootkit utility and WDO direct to the same link (about WDO).
I doubt it is a virus issue but it is worth checking none the less. But I grabbed TDS Killer from CNET and ran that (no issues). Will grab a flash drive and run WDO and update in abit.

The Logitech SetPoint drivers and software are rather old, I have had issues with newer versions where it will randomly accelerate my mouse for a moment which is rather frustrating in both gaming and non gaming applications. And I unfortunately need something like the SetPoint software installed because my middle mouse is broken (sensor randomly likes to push itself down and you cant really do anything in the Windows GUI until you un-press it or do a CAD).

Update: Ran WDO, Anti-rootkit and also did a quick MSE scan 0 results. Kicking off a full MSE scan doubt anything will change though.
Haven't gotten the BSoD yet but unfortunately it is rather random.

 

[Arc]

All is good. At least it will narrow the probable causes of a stop 0xF4 down.

Now observe the situation and let us know about it when it is needed