Help for BSOD 0xF4 (Win7 x64 Ultimate sp1)


  1. Posts : 3
    Windows 7 Ultimate x64 sp1
       #1

    Help for BSOD 0xF4 (Win7 x64 Ultimate sp1)


    Hi, all,

    Please see the attachment for detail.

    basic system information :

    Is Windows 7 . . .- x86 (32-bit) or x64 ?
    x64 Ultimate SP1 simp-chinese
    - the original installed OS on the system?
    Yes.
    - an OEM or full retail version?
    OEM
    - What is the age of system (hardware)?
    start to use from 05/10/2010.
    - What is the age of OS installation (have you re-installed the OS?)
    Just re-installed win7 sp1 on a new intel SSD HD. The last installed win7 x64(without sp1) had the same problem.



    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    Loading Dump File [C:\Windows\Minidump\030211-21871-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*D:\SymCache*http://msdl.microsoft.com/download/symbols
    
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`02859000 PsLoadedModuleList = 0xfffff800`02a96e50
    Debug session time: Wed Mar  2 18:05:55.522 2011 (UTC + 8:00)
    System Uptime: 0 days 0:13:27.022
    Loading Kernel Symbols
    ...............................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck F4, {3, fffffa800b1a6b30, fffffa800b1a6e10, fffff80002bd22d0}
    Probably caused by : csrss.exe
    Followup: MachineOwner
    ---------
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa800b1a6b30, Terminating object
    Arg3: fffffa800b1a6e10, Process image file name
    Arg4: fffff80002bd22d0, Explanatory message (ascii)
    Debugging Details:
    ------------------
    
    PROCESS_OBJECT: fffffa800b1a6b30
    IMAGE_NAME:  csrss.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: csrss
    FAULTING_MODULE: 0000000000000000 
    PROCESS_NAME:  csrss.exe
    EXCEPTION_RECORD:  fffff880082f5b78 -- (.exr 0xfffff880082f5b78)
    ExceptionAddress: 00000000776a57bd
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 0000000000590fe8
    Attempt to write to address 0000000000590fe8
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
    EXCEPTION_PARAMETER1:  0000000000000001
    EXCEPTION_PARAMETER2:  0000000000590fe8
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b010e0
     0000000000590fe8 
    FOLLOWUP_IP: 
    +3665383436353339
    00000000`776a57bd ??              ???
    FAULTING_IP: 
    +3665383436353339
    00000000`776a57bd ??              ???
    FAILED_INSTRUCTION_ADDRESS: 
    +3665383436353339
    00000000`776a57bd ??              ???
    BUGCHECK_STR:  0xF4_C0000005
    STACK_TEXT:  
    fffff880`082f50f8 fffff800`02c55f62 : 00000000`000000f4 00000000`00000003 fffffa80`0b1a6b30 fffffa80`0b1a6e10 : nt!KeBugCheckEx
    fffff880`082f5100 fffff800`02bfda23 : ffffffff`ffffffff fffffa80`0b35e540 fffffa80`0b1a6b30 fffffa80`0b1a6b30 : nt!PspCatchCriticalBreak+0x92
    fffff880`082f5140 fffff800`02b8590c : ffffffff`ffffffff 00000000`00000001 fffffa80`0b1a6b30 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17666
    fffff880`082f5190 fffff800`028c8993 : fffffa80`0b1a6b30 fffff800`c0000005 ffffc422`10fb1271 fffffa80`0b35e540 : nt!NtTerminateProcess+0x20c
    fffff880`082f5210 fffff800`028c4f30 : fffff800`02903dbc fffff880`082f5b78 fffff880`082f58e0 fffff880`082f5c20 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`082f53a8 fffff800`02903dbc : fffff880`082f5b78 fffff880`082f58e0 fffff880`082f5c20 00000000`00592270 : nt!KiServiceLinkage
    fffff880`082f53b0 fffff800`028c8d82 : fffff880`082f5b78 00000000`00013220 fffff880`082f5c20 00000000`00591d48 : nt!KiDispatchException+0x53b
    fffff880`082f5a40 fffff800`028c78fa : 00000000`00000001 00000000`00013220 00000000`00000001 fffffa80`0b355e60 : nt!KiExceptionDispatch+0xc2
    fffff880`082f5c20 00000000`776a57bd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    00000000`00590ff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776a57bd
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
    BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
    Followup: MachineOwner
    ---------
    xclimbing
      My Computer


  2. Posts : 3
    Windows 7 Ultimate x64 sp1
    Thread Starter
       #2

    Please forgive my bad English. But I really need your help about the problem. I have no idea about it. it comes out too often.
      My Computer


  3. Posts : 13,354
    Windows 7 Professional x64
       #3

    Hello,

    This seems like a hardware problem. First, do you have another hard drive you can try installing to?

    Also, run Memtest86: RAM - Test with Memtest86+

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Wed Mar  2 05:05:55.522 2011 (UTC - 5:00)
    System Uptime: 0 days 0:13:27.022
    Probably caused by : csrss.exe
    PROCESS_NAME:  csrss.exe
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xF4_C0000005
    FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
    SystemProductName = GA-MA785GT-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  4. Posts : 1,360
    win7 ultimate / virtual box
       #4

    thanks for the info but struggling to read anything but the minidump as its in chinese

    what antivirus are you using ?

    can you please check your ram by burn to CD (using an ISO burner) & run from boot memtest86+ for at least 5 passes, please move the sticks singly and together between slots to verify motherboard ram slots work as well as the ram sticks.

    can you tell me how many instances of csrss.exe you have running by checking in Task Manager ? Also right click each instance and check they are all in your system 32 folder ?

    do you get the crashes with all peripheral devices unplugged ?
      My Computer


  5. Posts : 3
    Windows 7 Ultimate x64 sp1
    Thread Starter
       #5

    thanks a lot for reply.

    Jonathan_King said:
    Hello,

    This seems like a hardware problem. First, do you have another hard drive you can try installing to?

    Also, run Memtest86: RAM - Test with Memtest86+
    I just fresh installed the OS on the new Intel SSD HD. the previous install was on a RAID0 of two 500G Seagate harddisks and had the same problem. and the thing goes well since last night BSOD of 0xf4.


    ickymay said:

    what antivirus are you using ?

    can you please check your ram by burn to CD (using an ISO burner) & run from boot memtest86+ for at least 5 passes, please move the sticks singly and together between slots to verify motherboard ram slots work as well as the ram sticks.

    can you tell me how many instances of csrss.exe you have running by checking in Task Manager ? Also right click each instance and check they are all in your system 32 folder ?

    do you get the crashes with all peripheral devices unplugged ?
    I have no antivirus in the new OS. it was Microsoft Security Essential in the old OS.

    there are two instances of csrss.exe in Task Manager and I'm sure they are same file in the %windir%\system32.

    I had no peripheral device plugged when got the crashes.

    I will test the memory sticks and the slots as your advice. I think it will take a long long time. I'm not sure I can have time to finish it.
      My Computer


  6. Posts : 13,354
    Windows 7 Professional x64
       #6

    You can run Memtest86 overnight; you don't have to actually watch or be there.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 17:32.
Find Us