View Single Post
18 Feb 2012  
QUADratic

Windows 7 Ultimate x64
 
 
BSOD 0x000000f4 on Cold Boot Up

Hi,

I have for about 6 months now been experiencing ‘random’ BSODs relating to 0x000000f4.
This has gotten so bad that 2 weeks ago I did a full clean install of Win 7 64 ultimate having previously updated all my BIOS, Firmware etc. to latest versions and am running latest drivers and updates for everything else.
I have replaced all my RAM and reconfigured the PCIe order of my GPU and Revo to a variety of set ups.
I have tried running basics installs with minimum Software, am running completely new A/V software and tried stabilising my BIOS by setting fixed voltages and removing Marvell driver components (neither have worked – I had read these may be issues).
Nothing has worked and I am getting so annoyed I might go and buy an iMac

As for the system, main hardware parts as follows (all have latest drivers, bios, firmware etc):

CPU = Intel i7 980x
MOBO = ASUS Rampage 3 Extreme
RAM = Corsair Dominator GT 2000 3 x 4Gb
Primary Drive = OCZ Revodrive 3 X2
Other Drives = 1x OCZ Vertex 2 + 2x WDC Raptors (mk2s)
GPU = Asus GTX580 Direct Cu II
Blu Ray = 2 x LG


Software I have kept to a minimum ATM to make things easier on myself (all latest patches):

Existing
Win 7 Ultimate 64bit
Office 2010 64bit
Skype
Citrix Xenapps
EaseUS BackUp
iTunes
Frostwire

New
Webroot


What happens is fairly typical and will always be from a cold standing boot, usually the machine has not been active for about an hour. The PC boots up as normal Windows loads and then anywhere from about 1 – 5 mins the screen starts to freeze up, the mouse moves but programs stop responding. . then graphics go a bit weird, task bar disappears etc and then BSOD.
Once I reboot after this its fine . . no problem, but that’s not the point and I feel I have tried everything and am not getting any closer to either a culprit or a solution.
I've been watching Event Viewer like a hawk to see what is happening . . as follows is a highlight form the last week and a new Crash dump from an hour ago, there is never any Warning / Error / Critical logged prior to one of these crashes (after boot up). Ironically this time I was actually looking as Event Viewer and waiting for the logs to load, that’s when it crashed . . someone clearly has a sense of humour, but it’s not me anymore !


This is the latest BSOD message

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c3e0630, 0xfffffa800c3e0910, 0xfffff800041d88b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021812-18876-01.





These are errors seen over the last few days . . . none of which happened before the crash as noted above and no crashes ever seemed to happen in their vicinity, but they could be indicative. .my gut feeling is its something to do with one of the drives but they have all been tested and seem to be working fine.



------------- 1

An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\??\GLOBALROOT\Device\HarddiskVolumeShadowCopy13\ Users\default\ntuser.dat'.


------------- 2

Volume Shadow Copy Error: An error 0x00000000c000014d was encountered while Registry Writer was preparing the registry for a shadow copy. Check the Application and System event logs for any related errors.

Operation:
OnFreeze event
Freeze Event

Context:
Execution Context: Registry Writer
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {5f9fce2d-391f-43c1-9df0-96c6c4016397}


------------- 3

The content source <csc://{S-1-5-21-3823838570-2202061524-1894531514-1001}/> cannot be accessed.

Context: Application, SystemIndex Catalog

Details:
The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d)


------------- 4

The content source <mapi://{S-1-5-21-3823838570-2202061524-1894531514-1001}/> cannot be accessed.

Context: Application, SystemIndex Catalog

Details:
A server error occurred. Check that the server is available. (HRESULT : 0x80041206) (0x80041206)


------------- 5

Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3823838570-2202061524-1894531514-1001:
Process 5840 (\Device\HarddiskVolume2\Windows\System32\msiexec. exe) has opened key \REGISTRY\USER\S-1-5-21-3823838570-2202061524-1894531514-1001\Software\Microsoft\Windows\CurrentVersion\Exp lorer


------------- 6

Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3823838570-2202061524-1894531514-1001:
Process 1668 (\Device\HarddiskVolume4\Windows\System32\svchost. exe) has opened key \REGISTRY\USER\S-1-5-21-3823838570-2202061524-1894531514-1001


------------- 7

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
Freeze Event

Context:
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {5f9fce2d-391f-43c1-9df0-96c6c4016397}
Command Line: C:\Windows\system32\vssvc.exe
Process ID: 5616


------------- 8

BITS has encountered an error communicating with an Internet Gateway Device. Please check that the device is functioning properly. BITS will not attempt to use this device until the next system reboot. Error code: 0x80040501.








All other BSODs logs since fresh install last weekend


The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c1977d0, 0xfffffa800c197ab0, 0xfffff800031978b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021812-21543-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c489480, 0xfffffa800c489760, 0xfffff8000318d8b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021712-20576-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c4a2060, 0xfffffa800c4a2340, 0xfffff8000318a8b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021712-18720-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa80075fb8c0, 0xfffffa80075fbba0, 0xfffff800031828b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021412-19515-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa8007b78b30, 0xfffffa8007b78e10, 0xfffff800031dc8b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021212-18938-01.



I feel like I have tried everything but am hoping you know what I've missed !!!!
My System SpecsSystem Spec