PC problem - Slow shutdown and or constant BSODs 0x000000f4

[James]

Major problem here.

Starting from yesterday I had a slow shutdown when I was compiling and watching a Youtube video. It has repeated itself frequently in states of idle and or stress. My temperatures and voltage seem to be okay. Normally it starts off with a program freezing and then saying "Microsoft Windows is not responding" or something (will edit with proper details later), anything that isn't frozen except for explorer.exe (including taskbar) can still be accessed but I am unable to open anymore content (however I am able to access my drives). Eventually this leads me to force shutting it down or waiting for a BSOD to occur. Other programs run fine while the former event is happening but it will eventually halt with the BSOD.

My first step was to have perform a clean install of my operating system, as I didnt wanna pinpoint drivers. Also, Ive updated my firmware for my SSD drive. After much tweaking these problems still persist. I have tried removed all hard drives and RAM DIMM and tried with separate instances of each part in. I have also tried multiple analytic tools and cannot find my problems.

I need your help. All I know that this is an error caused by memory.

Specs
CPU: Intel I7-3770K
MOBO: P8Z77-V (BIOS version 906)
RAM: Corsair Vengeance 4GB 1600Mhz DDR3 x 4
GPU: Nvidia GTX 670
PSU: XFX Pro750W XXX Edition
DVD: PIONEER DVD-RW DVR-215D ATA Device
Harddrives:

M4-CT256M4SSD2 ATA Device
Maxtor 7V250F0 ATA Device
SAMSUNG HD 103SJ ATA Device

COOLING:

Cooler Master HAF-X Fans
Corsair H100

BSOD Information
CRITICAL_OBJECT_TERMINATION
0x000000f4
00000000`00000003
fffffa80`0dc346a0
fffffa80`0dc34980
fffff800`0df87350
ntoskrnl.exe
ntoskrnl.exe+75c00
6.1.7601.18113 (win7sp1_gdr.130318-1533) x64

An info dump of my processes in multiple areas using PCHF has been attached to this post. You may need to use WinZIP or 7Zip to extract or browse this archive.

Seriously, where do I go from here to find the problem. Please point me into the right direction to pinpoint it.

Tomorrow I will run Prime95 and in the evening I will try running MemTest while I'm asleep.

[Alex]

A lot of people having this BSOD find that it has to do with a harddrive though. You state you removed all harddrives, did you also run the system with only 1 drive on it and did you get the BSOD then as well?

And what kind of analytics tools did you run? Did you run a tool that checks your harddrives for errors?

[Aidan]

Yeah, even though you can still pull data off doesn't mean the drives are okay. They could be failing.

Most (even the strangest of) issues are resolved by HDD replacement.

Another reason could be corrupt drivers.



Get "PC Check" by Eurosoft if you can. It's seriously the best software. It'll let you know what's up.

[James]

trying with just one dimmers and the ssd now. Alex has a point I always kept the SSD in.

I used chkdsk. System Repair, Win-7 disc Repair, whocrashed, BIOS Memory test, other stuff. Nothing out of the usual happened.

Trying with just SSD and 1 Dimm in. No clue what next, remove SSD and try different drive?

[Aidan]

Alex has a point I always kept the SSD in.

This explains everything.

[Alex]

Could you try HD Tune? It has a pro trial version available:
http://www.hdtune.com/files/hdtunepro_550_trial.exe

You can use it for up to 15 days.

It has both a "Health" tab and Error Scan, the Health tab basically shows you the S.M.A.R.T. values of your drive ( http://en.wikipedia.org/wiki/S.M.A.R.T. ), it could tell you some stuff (and it will mark things afaik), and the Error Scan basically just scans the drive.

I'm not sure if it finds stuff that chkdsk cannot find, but it's worth the shot. Especially the SMART values.

[James]

Going out soon but got a new error with what I said above. 0x0000007a or something

[Alex]

Was your Samsung drive in your PC at the time?

If so, you could try this:
http://support.microsoft.com/kb/977178/en-us

It specifically mentions large drives, 1TB and higher.

[James]

Samsung drive was detatched from SATA leads but connected to power supply. Only drive attached was SSD. Took 40 mins bsod ffail on individual dimms on 2 occasions.

on way hhome

[James]

I've not ignored any advice as I'm going through processes before I try these programs. Just waiting to check each Dimm then going to install Win7 on a spare HD with that (being connected only) to see if errors continue.

Here's that chkdsk log if anyone can find anything weird in it.

Code: Select all

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  192512 file records processed.                                          File verification completed.
  293 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              27 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  272578 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  192512 file SDs/SIDs processed.                                         Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
Security descriptor verification completed.
  40034 data files processed.                                            CHKDSK is verifying Usn Journal...
  34628144 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  192496 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  10083775 free clusters processed.                                         Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

  62280703 KB total disk space.
  21535444 KB in 147529 files.
    113800 KB in 40035 indexes.
         0 KB in bad sectors.
    296355 KB in use by the system.
     65536 KB occupied by the log file.
  40335104 KB available on disk.

      4096 bytes in each allocation unit.
  15570175 total allocation units on disk.
  10083776 allocation units available on disk.

Internal Info:
00 f0 02 00 b7 dc 02 00 bd 0a 06 00 00 00 00 00  ................
b0 00 00 00 1b 00 00 00 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

[James]

Been asleep. Computer turned itself off (guess?) on my 3rd out of 4 tests. Boot device wasnt able to be found until hard shutdown and repower.

[clyzm]

Have you overclocked your CPU?

Does the problem seem to happen when the computer is in standby?

[James]

No but I may have accidentally left some stupid auto tuning on this week on the Win7 GUI BIOS settings. Occurred to me it may be voltage but don't know how to default my BIOS without fucking it up.

It's happened in a lot of situations. During videogames, video, compiling videos, login screen, desktop, scanning, browsing Firefox. That 0x7A error happened during idle when I was nearly asleep.

Safe to say it isnt a dimm though.

[James]

also I set all my stuff to high performance/non shutdown when idle except mmonitor. checked slate and pagefile management etc

[James]

oh and I have bbeen stupidly defragging my ssd for 11 months every month or so. didn5 know I shouldnt do that. that's why I'm focused on it

[James]

Give up for today. Broke my old Maxtor's port trying to plug in the ata lead back in. Reinstalling OS tomorrow aand trying Alex's link of an diagnostic tool.

Fuckin' computers.

[Aidan]

Fuckin' computers.

This is why I need to quit my job.

[James]

Using HD Tune Pro now.

Noticed something before the error scan, the Samsung drive's C7 ID (interface CRC error count...?) is highlighted in blue and wants my attention. It suggests that there were communication errors and this may be caused by a damage cable. I'll try to sort that out.
The M4 SSD appears to have no problems with the Health tab.

Running error scan now.

[Psychotic]

Fuckin' computers.

This is why I need to quit my job.

They are honestly the curse of my existence. I can't live without them, but I barely live with them.

[James]

No errors found on either drive. Do I just give up and buy new hard drive(s) already?

[synthetic]

When it comes to SSDs I hear about similar issues almost every time SSD is mentioned somewhere. Have you verified that you are still experiencing the problem with SSD switched out? Two SSDs my friend used failed one after another after almost precisely 6 months and started giving him bsod hell

[Aidan]

James, install windows on either drive and run them separately on Prime95. It's bound to BSOD on the def HDD, then you'll know where the issue is.

[James]

yup did that without prime tho (which doesn't test harddrives anyway). lasted 10 hours with just samsung. that's alright for me instead of bsodding an hour idle or in game wwith that ssd tho

[James]

just checking again, 100% my ssd.

thanks for all the help guys!