TechSpot

Windows 7 BSOD BCCode:f4

By QUADratic
Oct 1, 2011
Post New Reply
  1. Hi,

    new to here as have recently started to experience random BSODs. Details as follows :

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 2057

    Additional information about the problem:
    BCCode: f4
    BCP1: 0000000000000003
    BCP2: FFFFFA800CE66B30
    BCP3: FFFFFA800CE66E10
    BCP4: FFFFF800037968B0
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Any advice as to cause / fix greatly appreciated !

    Thanks in advance
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    How to find and post your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually
     
  3. QUADratic

    QUADratic TS Rookie Topic Starter

    Hi thanks very much . . 3 logs attached
     

    Attached Files:

  4. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    All three of your errors are 0xF4:CRITICAL_OBJECT_TERMINATION
    One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message.

    The driver cited is the csrss.exe which stands for Client/Server Run-Time Subsystem, and is an essential subsystem of your Windows OS that must be running at all times. Csrss is responsible for console windows, creating and/or deleting threads, and implementing some portions of the 16-bit virtual MS-DOS environment.

    Now the thing with Windows drivers is that they are rarely the cause but more so point out that there is a problem but not much more diagnostic information.

    1. You mention random BSODs. Can you remember if you might have been doing something specific when they occur?

    2. What security software do you have installed? Run a virus/malware scan.
     
  5. QUADratic

    QUADratic TS Rookie Topic Starter

    Thanks Route44 . . the last time I was in the middle of trying to upgrade Acronis TrueImage (which is now well and truely corrupted - I can;t even uninstall it).

    Other times was using iTunes and before that clicking on a web link in Firefox . . I have noticed a few 'fail' messages come up about Comodo FW in the pasdt few weeks however so I have now removed that and just running Windows FW incase it was causing any issues.

    I am still using Avast for Virus / Malware and its reporting no issues after a full deep scan.

    Nothing to report since. I guess I just need to keep an eye on things and if it happens again see if there is any pattern.

    Thanks for all your advice.
     
  6. QUADratic

    QUADratic TS Rookie Topic Starter

    Arrgh

    now a different one

    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 3b
    BCP1: 00000000C0000005
    BCP2: FFFFF9600029C63D
    BCP3: FFFFF88005924A40
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
     

    Attached Files:

  7. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    This time the error code is 0x3B and though nothing definitive was cited these codes are usually caused by defective video card drivers. In light of your symptoms this may be the cause. I suggest doing the following...

    1. Go to our Download section and click on Utilities and then download Driver Sweeper 3.1 to your desktop screen and install.

    2. Download the latest diver(s) for your video card but don't install them.

    3. Uninstall your video card drivers and reboot your PC into Safe Mode. Run Driver Sweeper and remove ONLY the video card drivers. I had someone use it on their chipset drivers! If it doesn't find any video card drivers that is quite okay; just leave all other drivers alone.

    4. Reboot and install new video card drivers.
     
  8. QUADratic

    QUADratic TS Rookie Topic Starter

    Thanks will give it a go now I am back . . however had a totally new one this morning : (

    something so weird go on
     
  9. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    Attach that minidump.
     
  10. QUADratic

    QUADratic TS Rookie Topic Starter

    Sure thing . . one from last night one form this morning . .

    Thanks, really appreciate your help with this !
     

    Attached Files:

  11. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    One error code is the same as I mentioned in my second response to you and it contained nothing significant.

    The second error code is 0x74: BAD_SYSTEM_CONFIG_INFO
    This can be caused when critical registry keys and values are not present. This might be resolved by booting from the last restore point prior to these issues.

    Do you have your Windows OS CD because a Windows Repair may be needed?
     
     
  12. QUADratic

    QUADratic TS Rookie Topic Starter

    Thanks . .hopefully now fixed

    Hi sorry for the delay, I finally had time to reconfig the PC . . .

    followed the steps as outlined and everything is working with now errors so far.

    If I don't see anything weird in the next month I'm hoping its fixed .

    Many thanks for your time and advice

    NCF
     
  13. QUADratic

    QUADratic TS Rookie Topic Starter

    Hi,

    So for the last few months nothing has really improves and in some cases I have seen other codes and failures. KERNEL errors etc.

    This weekend I have done a complete rebuild and refresh. All latest drivers, firmwares and bios. New software. removed some devices and even swapped round some RAM a complete from scratch restore. I even bough Webroot and Bitfender to scan my machine incase there was anything lurking about.

    Everything was bang on yesterday. Turned the machine on this morning . .. F4 again

    About to throw this computer out the window ! I wouldn't mind but I know that this machine worked perfectly for a good 6 months with all the exisiting components.

    Dump attached. If anyone has any ideas please let me know !

    Thanks
     

    Attached Files:

  14. QUADratic

    QUADratic TS Rookie Topic Starter

    And here comes the next one . . a 1000007e this time
     
  15. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    Minidump was the same 0xF4.

    The error 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED means that a system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues.

    Check Event Viewer (EventVwr.msc) for additional information and tell us if there are any Yellow Triangles and/or Red X's and what they flag.

    Also, please tell us what of your old hardware and old software if any that went into this rebuild.
     
  16. QUADratic

    QUADratic TS Rookie Topic Starter

    I think I might be getting somewhere . . . famous last words

    The 1000007e I am pretty sure is related to me trying different RAM configs. I think I might have a dodgy stick. Since I went back to using 6 Gb (3x2) instead of the full 12gb its not showed up and does seem to be limited in appearing around this period of investigation.

    Back to the F4, I took a look in Event viewer and found some repeated Errors and Warnings.
    I looked at the timing of the last critical Kernel crash and and worked back form there looking for any preceding errors or warnings.

    I found some errors relating to my LCD case display drivers and some relating to ASPI32. I am running a 64bit system and found a number of refs about this ASPI32 causing issues so I have disabled it in the Registry. I also removed the LCD drivers and will live without it . . its just a magpie device (SDC megtron). Only remaining error relates to something called trufos not being allowed to run . . something new for me and related to BitDender I beleive.

    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 1600 (7-7-7-20) . . was 12Gb now 6Gb
    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
    BitDefender (not using AV)
    Webroot (not using FW)
     
  17. QUADratic

    QUADratic TS Rookie Topic Starter

    Yep spoke too soon . .

    am trying lots of shut down and start ups to flush it out as in most cases it fails early on after a cold boot up

    and its done it again F4

    nothing obvious in the Event Logger
     
  18. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    Sorry if you have already answered this but have you run a hard drive diagnostic on your Raptors?
     
  19. QUADratic

    QUADratic TS Rookie Topic Starter

    Hi, yes and nothing idenitified as wrong / potential issue.

    Having for the last week put the mahcine through a number of power cycle tests it would seem the issue happens under the following circumstances :

    Cold boot . . if the machine has been off for approx 40 mins + (I am trying to figure out the ciritical window) and then turned on, it seems to crash after running for about 5 mins.

    Once that crash has happened it is hit or miss if it will then fully reload after a reboot . . it usually does but sometimes i've had other issues in the following cycle. but once its fully rebooted again its fine.

    Generally speaking if its been running fine and is put through a rebooted cycle its ok . . even shut down and restart is usually ok if its not that long inbetween cycles . . 5 > 10 mins seem OK.

    Its making me wonder if it is hardware issue where by after a peiod of being switched off maybe power is dropped to a device and then when its turned on again its in some weird half asleep state . . whilst power is being ramped up during boot up its OK but when all the services have loaded and the HW settles down maybe the drop in power truggers the failure . . its only a hunch at the moment but there does seem to be a pattern to it happening.
     
  20. QUADratic

    QUADratic TS Rookie Topic Starter

    Hi . .back again, been continuing the review and diagnostics . . Have replaced all my RAM with new sticks and shut down / removed all Marvell drivers

    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 and 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 wiaitng for the logs to load, thats when it crashed . . someone has a sense of humour.


    This is the BSOD message regards the dump attached before

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



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

    Attached Files:



Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.