TechSpot

New Windows 7 build - BSOD after "sleep mode"

By TBearOK
May 10, 2010
Topic Status:
Not open for further replies.
  1. Howdy,

    I have 2 identical machines. They are HP machines with quad-core CPU's, 8 GB of RAM, 1 TB drive partitioned into the primary (100G) and data drives (840ishG)

    I have Windows 7 Ultimate installed on the machines. They work great until you bring them back from "sleep mode".

    The crash file is as follows:

    Problem signature:

    Problem Event Name: BlueScreen

    OS Version: 6.1.7600.2.0.0.256.1

    Locale ID: 1033
    Additional information about the problem:

    BCCode: f4

    BCP1: 0000000000000003

    BCP2: FFFFFA8007ABFB30

    BCP3: FFFFFA8007ABFE10

    BCP4: FFFFF80002BD4540

    OS Version: 6_1_7600

    Service Pack: 0_0

    Product: 256_1

    Attached are the dump files from one of the machines.

    Any help would be greatly appreciated.

    Attached Files:

  2. raybay

    raybay TS Evangelist Posts: 10,716   +6

    Memory error? Have you tried running a memory test...
    Reseat your memory, then run the free MemTest you can get with a download search.
  3. webscaper

    webscaper TS Rookie Posts: 51

    It seems there is a problem with the hard drive during a paging operation. Check this Microsoft support article: http://support.microsoft.com/kb/330100. Also check the connections. Do a hard drive diagnostic from the manufacturer of the hard drive:http://www.tacktech.com/display.cfm?ttid=287

    I have underlined the important areas of the dump.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Webscaper\AppData\Local\Temp\Rar$DI00.872\051010-28938-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*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.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a52e50
    Debug session time: Mon May 10 10:11:36.553 2010 (UTC - 4:00)
    System Uptime: 0 days 6:10:07.004
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa8007b18b30, fffffa8007b18e10, fffff80002b91540}
    
    Probably caused by : [U]hardware_disk[/U]
    
    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: fffffa8007b18b30, Terminating object
    Arg3: fffffa8007b18e10, Process image file name
    Arg4: fffff80002b91540, Explanatory message (ascii)
    
    Debugging Details:
    ------------------
    
    
    PROCESS_OBJECT: fffffa8007b18b30
    
    IMAGE_NAME:  hardware_disk
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAULTING_MODULE: 0000000000000000 
    
    PROCESS_NAME:  csrss.exe
    
    EXCEPTION_RECORD:  fffff88007635b78 -- (.exr 0xfffff88007635b78)
    ExceptionAddress: 000000007799548f
       ExceptionCode: c0000006 ([U]In-page I/O error[/U])
      ExceptionFlags: 00000000
    NumberParameters: 3
       Parameter[0]: 0000000000000000
       Parameter[1]: 000007fefd8fd8a8
       Parameter[2]: 00000000c000000e
    Inpage operation failed at 000007fefd8fd8a8, due to I/O error 00000000c000000e
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  000007fefd8fd8a8
    
    EXCEPTION_PARAMETER3:  00000000c000000e
    
    IO_ERROR: (NTSTATUS) 0xc000000e - [U]A device which does not exist was specified.[/U]
    
    EXCEPTION_STR:  0xc0000006_c000000e
    
    FAULTING_IP: 
    +23a
    00000000`7799548f ??              ???
    
    BUGCHECK_STR:  0xF4_IOERR_C000000E
    
    FOLLOWUP_IP: 
    +23a
    000007fe`fd8fd8a8 ??              ???
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware_disk
    
    STACK_COMMAND:  kb
    
    FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
    
    BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
    
    Followup: MachineOwner
    ---------
  4. webscaper

    webscaper TS Rookie Posts: 51

    You also may want to try this hotfix: http://support.microsoft.com/default.aspx/kb/977178/?p=1

    Consider the following scenario:

    * You have a computer that is running Windows 7 or Windows Server 2008 R2.
    * The computer has a Serial Advanced Technology Attachment (SATA) hard disk.
    * The size of the SATA hard disk is large. For example, the size of the SATA hard disk is 1 terabyte (TB).
    * You put the computer into the Sleep state or into the Hibernate state.
    * You try to resume the computer.

    In this scenario, you receive one of the following Stop error messages:

    * STOP 0x0000007A
    * STOP 0x00000077
    * STOP 0x000000F4

    When you resume a computer from sleep or from hibernation, the SATA hard disk drivers require the SATA hard disks to be ready within 10 seconds. However, a large SATA hard disk may take longer than 10 seconds to be ready. In this situation, the resume operation times out.
Topic Status:
Not open for further replies.


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.