Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

0xF4 BSoD has me stumped


  • Please log in to reply
22 replies to this topic

#1 ph7ryan

ph7ryan

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 12:59 PM

First let me start of with my specs. I know this is an overclocking setup, but I haven't had the time, environment, and lately the stability to even think about overclocking it right now, so everything is stock.


Specs:
PS: Corsair TX850
Mobo: EVGA P55 Classified 200
GPUs: 2 nVidia Quadro FX 3500 SLi
RAM: 4GB Corsair DDR3 1600MHz (CMX4GX3M2A1600C8)
Processor: i7 870 @2.93GHz
I do have some extra PCI cards, that I could look up their part numbers if requested, but I haven't even used them lately, and they have been installed without issue for a while, and no new drivers have been installed for them.
SSD: Crucial M4 64GB SSD
Hard Drives: 2 2TB I wanna say Seagate Barracuda drives in RAID 0 for data only
O/S: Windows 7 64 bit Pro SP1 currently up to date with all updates


Pre-Problem History:


When I built my setup, I went ahead and bought 4GB of 2400MHz Transcend RAM (404093-0081), for when I wanted to overclock, I would already have the appropriate RAM on hand. It was sitting around still in the box, so I went ahead and tossed it in a couple months back into the extra DIMM bays on the mobo. Booted it up, and the system recognized the now 8GB of RAM, but said that only 3.99GB was usable. I didn't really mind too much because I hadn't maxed out my RAM yet, so I just left it in. I had figured that maybe it would just run at a lower speed, but on the sticker, it says `1.65V, so I probably would have had to up the voltage just to get it to work. Again, not worth the hassle when I didn't even really need it. Anyways I left it in, and really didn't use the computer too much because I was doing other things for school (This was built to be a CAD machine). Well now that I am starting to get into my ME classes, I really needed to start using SolidWorks and MATLAB so I went ahead and started using this computer on a regular basis. There were still a couple kinks, like a hangup on shutdown, and a sometimes the computer wouldn't wake up after shutting the displays off. So I target those and finally worked them out after some driver updates etc. The computer was running pretty well and I decided that while I was at it, I may as well remove the extra 2400MHz RAM that was in there. Along this same time I had setup LogMeIn, and had installed their "blank screen" driver so that I would be able to control SolidWorks from my laptop when I wasn't home. The blank screen driver caused a lot of issues, but I didn't realize that it was causing the problems, so I clicked the reset CMOS button on the back of my mobo in order to be able to see the BIOS (I couldn't see anything until the windows login screen). This caused the Mobo to give me a "Check Video Card" error, so I had to restart the system with only one of the cards plugged in, and then load some default settings into the CMOS, and then I could reboot with the two graphics cards in.

Pre-Problem Changes:
Again, the only things that I really touched were the RAM, and the Graphics Cards. Everything else stayed the same. I reseated the 1600MHz RAM while I was in there, but have reseated it many times over while trying to troubleshoot this issue. The graphics cards seem to be working fine right now, but again, they are definitely a possibility.

Problem:
The problem has happened pretty much every time the computer is on, but it is after a set amount of time. Recently I haven't been using the computer a lot, so it has happened after probably a rough guess of .5 hour after boot time, after the displays have been turned off. Basically, the screens will be off, and then all of the sudden one (either) or both screens will just pop up with a BSoD screen with the 0xF4 error, and then say something about a crash dump at the bottom.

Tried Solutions:

When it first happened, I was in the middle of copying a rather large file in explorer, I was browsing the internet, and I had a slightly complex file open in SolidWorks, so I thought that it could have been the SSD, so I ran a Chkdsk /f multiple times, and every time it came up perfectly fine.

Next I thought that maybe it was the RAM, so I ran Windows Memory Checker, and that came up perfectly fine, and then I ran Memtest 86 2 times, 2 passes the first time, 3 passes the second time (second time was well passed the amount of time it would take for the BSoD error to come up) and it came up perfectly fine both times with that as well.

The graphics cards are really the next culprit, but I really do think it has something to do with the RAM, as the graphics cards haven't been forced to do anything too intensive yet. I used an ESD bracelet when removing the cards, and made sure they were seated correctly every time. Both cards have 6 pin connectors plugged in, and both have the SLi bridge connected properly.

My CPU temps are pretty low, again, nothing I have done is too intensive (around 38-42 when idle, and 48-50 when working with solidworks and other programs. I don't have a way to measure my RAM temps I don't think but when I took out the ram to reseat it, it was a little hot. They have heat sinks on them though so they should be fine. GPU cards are a little warm as well, but again, nothing too alarming, and the fans on both cards are working fine. Probably could stand to throw another fan onto the case, but I'm not overclocked right now, and not really working it too hard so I don't really see the need for it right now.

I don't have other RAM other than the 2400MHz RAM to try, and I'm not gonna overclock it just to test for faulty RAM unoverclocked. Don't really have it in my budget right now to go buy some test sticks of RAM either.

If someone knows how to read the BSoD dump files or whatever, I would be more than happy to post them up here, I don't really know where to find them though. Any help at all is greatly appreciated. Thanks Again.

BC AdBot (Login to Remove)

 


#2 Chasestar989

Chasestar989

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:31 PM

Posted 20 September 2012 - 04:33 PM

I ran across the same issue. There are two ways to handle it. You can post your question to the Microsoft forums They will ask you to upload your dump file and look at it and get back to you in a few days. (huge pain)

I resolved the issue by backing up my files and re-installing windows. Kind of a pain but you can get it done in 4 to 8 hours. If you take that route make sure to back up the data first.

Ryan Butler
Mod Edit: Removed advertising link, please read forum rules regarding such. Link to forum rules in my sign - Hamluis.

Edited by hamluis, 20 September 2012 - 05:24 PM.
Removed advertising - Hamluis.


#3 ph7ryan

ph7ryan
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 04:41 PM

Hmmm. Ok. Well It's no urgent issue, so I may try the MS help. If they can't fix it, I do have my computer backed up to a WHS, although its over a VPN, so the chances of that actually being able to restore over the VPN is probably pretty slim. Reinstalling W7 isn't really an issue, I just don't wanna have to go through that if it's a hardware issue and am going to get the same thing on the other side.

#4 caperjac

caperjac

  • Members
  • 1,649 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NS. CAN
  • Local time:09:31 PM

Posted 20 September 2012 - 05:05 PM

hi ,no need to go to Microsoft forums to have your dump files read ,lots of seasoned helpers here know how to decipher them ,they just haven't seen you post yet ,I think the above poster was just posting to show off his ZZtech support link .

for the 0xF4 error Microsoft suggest updating all device drivers /scan for viruses and check hdd for errors ,good luck .there is a program that some people use to read dump file if you want to check them t out yourself


-----------------

If you follow these directions you should end up with a few BSOD events recorded and a place for us to start looking -

Please download BlueScreenView http://www.nirsoft.net/utils/blue_screen_view.html (in zip file)•Extract (right-click > Extract all) the contents of bluescreenview.zip.

•Double-click on the BlueScreenView.exe file, to run the program. (No installation is required.)

•When scanning is done (usually complete by the time the interface appears), go ...

•Edit > Select All

•File > Save Selected Items, and save the report to your Desktop as BSOD.txt.

•Close the BlueScreenView window... ... ...

•Open BSOD.txt using Notepad and go ... .... ..

•Edit > Select All

•Edit > Copy, and then paste the entire contents of the text file into your next reply.if you wish





My answers are my opinion only,usually


#5 ph7ryan

ph7ryan
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 07:24 PM

Alrighty, thanks... Here we go:

==================================================
Dump File         : 090611-14328-01.dmp
Crash Time        : 9/6/2011 9:42:50 PM
Bug Check String  : 
Bug Check Code    : 0x00000101
Parameter 1       : 00000000`00000018
Parameter 2       : 00000000`00000000
Parameter 3       : fffff880`03115180
Parameter 4       : 00000000`00000006
Caused By Driver  : usbhub.sys
Caused By Address : usbhub.sys+1fb7
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\090611-14328-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 291,808
==================================================

==================================================
Dump File         : 103011-16031-01.dmp
Crash Time        : 10/30/2011 10:22:49 PM
Bug Check String  : WORKER_INVALID
Bug Check Code    : 0x000000e4
Parameter 1       : 00000000`00000002
Parameter 2       : fffffa80`08f002a0
Parameter 3       : fffffa80`08f002c0
Parameter 4       : 00000000`00000000
Caused By Driver  : HdAudio.sys
Caused By Address : HdAudio.sys+22ce2
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\103011-16031-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 291,808
==================================================

==================================================
Dump File         : 103111-16406-01.dmp
Crash Time        : 10/31/2011 3:38:10 PM
Bug Check String  : WORKER_INVALID
Bug Check Code    : 0x000000e4
Parameter 1       : 00000000`00000002
Parameter 2       : fffffa80`08e24930
Parameter 3       : fffffa80`08e24950
Parameter 4       : 00000000`00000000
Caused By Driver  : HdAudio.sys
Caused By Address : HdAudio.sys+22ce2
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\103111-16406-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 291,784
==================================================

==================================================
Dump File         : 111011-17968-01.dmp
Crash Time        : 11/10/2011 4:16:28 PM
Bug Check String  : WORKER_INVALID
Bug Check Code    : 0x000000e4
Parameter 1       : 00000000`00000002
Parameter 2       : fffffa80`08ba3cb0
Parameter 3       : fffffa80`08ba3cd0
Parameter 4       : 00000000`00000000
Caused By Driver  : HdAudio.sys
Caused By Address : HdAudio.sys+22ce2
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\111011-17968-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 291,808
==================================================

==================================================
Dump File         : 071212-27609-01.dmp
Crash Time        : 7/12/2012 11:23:18 AM
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : 00000000`00000000
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+17e140
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7f190
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\071212-27609-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
==================================================

==================================================
Dump File         : 082412-25250-01.dmp
Crash Time        : 8/24/2012 4:39:41 PM
Bug Check String  : CACHE_MANAGER
Bug Check Code    : 0x00000034
Parameter 1       : 00000000`00050853
Parameter 2       : fffff880`0d9546e8
Parameter 3       : fffff880`0d953f40
Parameter 4       : fffff800`0307b301
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor         : x64
Crash Address     : ntoskrnl.exe+7f1c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\082412-25250-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 291,624
==================================================


It doesn't really look like there is any from too recently. I have had multiple within the passed few days, yet the last one recorded was 8/24/12. The computer usually locks up before it BSOD's when I am working with it, usually initiated with trying to do something with explorer (ie. delete a file, copy a folder, open a folder, etc.)

If you don't mind taking a look though that'd be great.

#6 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:31 AM

Posted 20 September 2012 - 08:02 PM

The most recent minidump in the report is in fact from the 6th of September, 2012:

Dump File : 090611-14328-01.dmp
Crash Time : 9/6/2011 9:42:50 PM
Bug Check String :
Bug Check Code : 0x00000101


STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION

You report a number of recent STOP 0xF4 BSODs, and the dumps are not being saved:
  • This leads me to suspect a problem/issue with the SATA data cable connections.
See also: http://html5.litten.com/xp-wont-boot-repair-series-part-3-blue-screen-errors-at-xp-boot/

... usually it is a badly connected SATA drive. Check for loose connections or try plugging it into a different socket or with a different cable.

Please examine the SATA data cables if necessary, and let me know whether they have locking clips on their ends or are simply a push-fit.

Un-plug both ends of the SATA data cables and re-plug them back in where they came from, ensuring that the connections are fully and firmly seated in place.
  • Do the cables fit snug and tight .... or are they a loose fit?
Do likewise with the power cable connection to the hard drives/SSD.

Test by using the system to see if that has put an end to the STOP 0xF4 errors.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#7 ph7ryan

ph7ryan
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 08:11 PM

The most recent minidump in the report is in fact from the 6th of September, 2012:


Dump File : 090611-14328-01.dmp
Crash Time : 9/6/2011 9:42:50 PM
Bug Check String :
Bug Check Code : 0x00000101


STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION

You report a number of recent STOP 0xF4 BSODs, and the dumps are not being saved:
  • This leads me to suspect a problem/issue with the SATA data cable connections.
See also: http://html5.litten.com/xp-wont-boot-repair-series-part-3-blue-screen-errors-at-xp-boot/

... usually it is a badly connected SATA drive. Check for loose connections or try plugging it into a different socket or with a different cable.

Please examine the SATA data cables if necessary, and let me know whether they have locking clips on their ends or are simply a push-fit.

Un-plug both ends of the SATA data cables and re-plug them back in where they came from, ensuring that the connections are fully and firmly seated in place.
  • Do the cables fit snug and tight .... or are they a loose fit?
Do likewise with the power cable connection to the hard drives/SSD.

Test by using the system to see if that has put an end to the STOP 0xF4 errors.


I'll go ahead and check those things, but the date of that is actually from 2011.

#8 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:31 AM

Posted 20 September 2012 - 08:21 PM

... but the date of that is actually from 2011.

Ha ha ... you got me there! :thumbup2:

I am getting careless &/or blind it seems and I will give myself a good kickin'.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#9 ph7ryan

ph7ryan
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 09:07 PM

Well, I went ahead and left my computer on while I headed to the engineering lab to get my MATLAB assignment done on a school computer, and when I got back, there was a new BSoD facing me. I just checked the BlueScreenView, and that wasn't able to dump either. I took a picture, it was a 0x7a error, a little more info on this one, maybe it can give us a little more insight. I'm about ready for this stupid thing to work again.

Posted Image

Edited by ph7ryan, 20 September 2012 - 09:10 PM.


#10 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:31 AM

Posted 20 September 2012 - 09:31 PM

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

Your BSOD error message shows:
  • STOP 0x0000007A (,C000000E,,)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

This is consistent with an intermittent connection to the device (hard drive/SSD), likely a cable connection issue, and also with the subsequent lack of any associated crash dump/minidump being saved.
  • Check all the cable connections.

Edited by AustrAlien, 20 September 2012 - 09:34 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#11 ph7ryan

ph7ryan
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 09:58 PM

Ok, I went ahead and replaced the sata cable to the hard drive, hopefully that fixes things, we'll see shortly.

#12 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:31 AM

Posted 20 September 2012 - 10:08 PM

The problem is not necessarily with the SSD on which you have the Windows system installed.

Correct me if I am wrong, but I understood you to say that you have one SSD and two HDDs attached to the system. There is no way of knowing at this time which of those devices (or their connecting cable) is causing the problem. The System Event Log may give an indication, but we have not looked at that yet.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#13 ph7ryan

ph7ryan
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 10:10 PM

would we be able to see that from event viewer? I am technically A+ certified, but its been quite a while lol. I think I have enough cables to swap out for every hard drive, if this still fails, I'll go ahead and do that as well. It's just idling right now with the displays turned off by the os.

#14 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:10:31 AM

Posted 20 September 2012 - 10:17 PM

Go ahead and have a look in Event Viewer at the System Event Log.

Under Source, look for Disk errors &/or warnings.
  • Let me know what you see.
    If you can't pick it up fairly quickly, I'll get you to post the Event Logs so that I might have a look at them.

Edited by AustrAlien, 20 September 2012 - 10:18 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#15 ph7ryan

ph7ryan
  • Topic Starter

  • Members
  • 141 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Georgia, USA
  • Local time:08:31 PM

Posted 20 September 2012 - 10:30 PM

Yep, there seem to be quite a few errors in the passed few days all coming from "the driver detected a controller error on \Device\Harddisk7\DR7" as well as there is one at \Device\Harddisk7\DR9. There aren't any from today however, but I do have two from source DistributedCOM which sounds interesting as well. Now I don't think I have actually had a 0xF4 error today, so that probably is coming from the hard drive problem.

I went into disk management to figure out which drive was drive 7, and both my HDD's are 0 and 1, and my SDD is 2. I don't have a drive 7, unless thats referring to something else.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users