none
Multiple BSOD with error code f4 and 7a

    Question

  • I've been having daily crashes with these codes, most of them 0xf4.

    The other ones were:

    0x0000007a  KERNEL_DATA_INPAGE_ERROR

    and they mentioned volmgr.sys.  

    Some patterns I've seen in the Event Logs (not consistent enough to isolate a cause, however):
    * Cascade of drivers failing to load, something to do with Windows Driver Foundation - User Mode
    * The driver detected a controller error on \Device\Harddisk1\DR1.

    I uninstalled some recent software (Broadcom Widdcom application), and did a System Restore. That seems to have taken care of the 7a errors, but the others remain.

    I tried using WinDbg but I can't get the Symbols path to work. Dmpchk does produce some output (I've uploaded .dmp files and msinfo32 .nfo output to Skydrive http://sdrv.ms/185YnnK )

    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: csrss

    FAULTING_MODULE: 0000000000000000 

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    PROCESS_OBJECT: fffffa80084d3b30

    IMAGE_NAME:  csrss.exe

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xF4

    CURRENT_IRQL:  0

    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    BUCKET_ID:  WRONG_SYMBOLS

    Followup: MachineOwner


    Wednesday, July 10, 2013 5:53 AM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm
    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency

    Wanikiya & Dyami--Team Zigzag

    Wednesday, July 10, 2013 5:56 PM
  • Yes, I've already uploaded them. The link is in my original post, and here:

    http://sdrv.ms/185YnnK  

    Friday, July 12, 2013 5:53 AM
  • Help!
    Saturday, July 13, 2013 9:30 PM
  • Guys?  Anyone?
    Sunday, July 14, 2013 5:16 AM