Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Multiple BSOD's. Latest Bugcheck code: 0xF4

26 Feb 2014   #1
danohall

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
Multiple BSOD's. Latest Bugcheck code: 0xF4

Hello All,

My computer has been suffering BSOD's for months and I'm at wits end. I built a new system awhile back and the only thing carried over was the SSD. Crashes were happening on the old computer too. Crashes happen randomly so I can't say "if I do this then it crashes". Thought it was maybe my Norton antivirus so I completely unistalled it and tried Security Essentials but no luck. Uninstalled video drivers for awhile but, again, no luck. I pretty much suck at being able to interpret anything related to the crashes, so I thought I'd ask the experts!! :-)

I've attached a zip file with, hopefully, everything that needs to be looked at.

Thank You very much in advance for any guidance.

Dan


My System SpecsSystem Spec
.
26 Feb 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

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.
My System SpecsSystem Spec
26 Feb 2014   #3
danohall

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Yes I have the latest drivers. I actually have a different ssd than what I had when I built it. Took this ssd from a laptop that I gave a cousin. This error code is the first time I've seen this one. This is what the prior crash said (from WhoCrashed).

On Tue 2/25/2014 12:59:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-9562-01.dmp
uptime: 00:11:04
This was probably caused by the following module: ntoskrnl.exe (nt+0x35A826)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003562826, 0xFFFFF88003993828, 0xFFFFF88003993080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
My System SpecsSystem Spec
.

26 Feb 2014   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

I think I mentioned Firmware..not Drivers.
My System SpecsSystem Spec
26 Feb 2014   #5
danohall

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

My bad. Yes, I have the latest firmware.
My System SpecsSystem Spec
26 Feb 2014   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Alright..

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

Run a Hard Drive test: http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html
My System SpecsSystem Spec
27 Feb 2014   #7
danohall

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

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?
My System SpecsSystem Spec
27 Feb 2014   #8
danohall

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Just crashed again and have uploaded all new info. I was downloading updates to spybot when the crash occurred. Spybot does not run at startup (only when I run a scan then I shut it down).
My System SpecsSystem Spec
28 Feb 2014   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
28 Feb 2014   #10
Anak

Microsoft Community Contributor Award Recipient

Win 7 Home Premium 64bit Ver 6.1.7600 Build 7601 - SP1
 
 

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:
Quote:
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/
My System SpecsSystem Spec
Reply

 Multiple BSOD's. Latest Bugcheck code: 0xF4




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
bsod error code 0xF4 physical memory dump
I have problems with win xp laptop all is fine when i turn on and after 10-20 min he fail at blue screen with error code 0x000000F4 or 0xF4 error code this happened 3 times,right now is fine i use defaggment and waiting to finish yesterday i used driver scanner registered and after updated drivers...
BSOD Help and Support
Problems with booting (The bugcheck was: 0xF4)
Hi I've got a Windows 7 Home Premium x64 computer that occasionally can't be booted. When its power if first turned off and then on it boots. Subsequently though, when it's shut down from Windows, it won't boot again. It will show the "Starting Windows" screen with the windows logo animation as...
BSOD Help and Support
Random BSOD occuring only in a particular account. Bugcheck code: 0xF4
I have been getting random BSOD only in a particular account. The BSOD is very random. In the other account I have tried running Driver verifier however I could not see any crashes. Here is a short report on the bugcheck This was probably caused by the following module: ntoskrnl.exe...
BSOD Help and Support
BSOD Installing drivers after a fresh windows install, Code 0xf4
My computer was suffering from random bsods and viruses before. I atributed the bsods to viruses, but after reinstalling windows 7, I found that the bsods still happened. It seems to happen when installing drivers, or running prime95. Booting into safe mode allows me to pretty much do anything. ...
BSOD Help and Support
BSOD again. Bugcheck 0xF4 Unknown Critical Object.
Once again I humbly approach the alter of debuggers. BSOD have begun again at random times. I've run Malewarebytes and found nothing. Whocrashed doesn't help much: crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown () Bugcheck code:...
BSOD Help and Support
Multiple BSOD Win 7 x64 - BugCheck Code 0x50 -- PLEASE HELP!
As of early this morning, I've been getting several BSODs upon booting to desktop on my system. :mad: The computer was working perfectly for the past few months and my OS was recently installed (2 months ago) after I got 2 Corsair Force GT SSDs and put them in RAID-0 as my OS drive. I have the...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 06:03.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App