Multiple BSOD's. Latest Bugcheck code: 0xF4

Welcome to the Forum.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\Danohall\022514-9141-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0324b000 PsLoadedModuleList = 0xfffff800`0348e6d0
Debug session time: Wed Feb 26 10:30:16.317 2014 (UTC + 6:00)
System Uptime: 0 days 3:01:06.971
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8019b13b30, fffffa8019b13e10, fffff800035c57b0}

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

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

A bug code F4 is usually storage (hard drive/ssd) related.

Code:

Model	Corsair Force GT ATA Device

Have you checked for firmware update for yours? Corsair SSD Hard Drives ? Solid-State Drives for laptops and desktop PCs with the highest performance Read/Write speeds of up to 555MB/s read and 525MB/s write.

Check, update and let us know if the BSODs continue.

I think I mentioned Firmware..not Drivers.

Alright..

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: https://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Attached are screen shots of my 2 hard drives using CrystalDiskInfo. The third drive is a new one with nothing on it so I didn't include that one. I ran Seatools on both drives and both passed. I ran the "short drive self test" and "long generic tests" on both.

Is this all the info you wanted to see?

The latest BSOD is not in the same line to the original issue. It is a stop 0x3B, caused either by failing memory or by some device driver passing bad info to the memory.

Code:

BugCheck 3B, {c0000005, fffff8000359744e, fffff880096d75e0, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )

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

But nothing more information can be digged out from the crash dump.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Hi danohall, welcome to 7F! :)

In addition to what Arc has posted, and you should follow his advice first; I found this in your system information report, If you would have supplied your full System Specs I would have been able to find more help for your Motherboard (MB) and the USB drivers for it.

Code:

Generic- USB3.0 CRW-SD/MS USB Device    USBSTOR\DISK&VEN_GENERIC-&PROD_USB3.0_CRW-SD/MS&REV_1.00\201006010301&4    Error Code 39

Please fill out your System Specs: System Info - See Your System Specs

As it stands you should follow this:

Code:

Code 39    Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. Uninstall and reinstall the driver

Code 39
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

Cause
There are several causes of Code 39 errors:

• A required device driver is missing.
• A required binary file is corrupted.
• There is a problem with the file I/O process.
• A driver that is referencing an entry point in another binary file is unable to load.

Recommended resolution Uninstall and reinstall the driver
Uninstall the driver from Device Manager, and then scan for new hardware to install the driver again.

1. In the device's Properties dialog box, click the Driver tab, and then click Uninstall. Follow the instructions.
2. Restart your computer.
3. Open Device Manager, click Action, and then click Scan for hardware changes. Follow the instructions.

Note You may be prompted to provide the path of the driver. Windows may have the driver built-in, or may still have the driver files installed from the last time that you set up the device. However, sometimes, it will open the New Hardware Wizard which may ask for the driver. If you are asked for the driver and you do not have it, you can try to download the latest driver from the hardware vendor's website.

The Vendor for

Code:

USB 3.0 eXtensible Host Controller    PCI\VEN_8086&DEV_8C31&SUBSYS_50071458&REV_04\3&11583659&0&A0

is Intel and you may be able to find updates or a fresh copy of the Driver for the Controller if the uninstall/reinstall doesn't work here: https://USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family | downloadcenter.intel.com/