locked
BSOD Help? RRS feed

  • Question

  • Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 7a
      BCP1: FFFFF6FC80621920
      BCP2: FFFFFFFFC0000185
      BCP3: 000000007481A880
      BCP4: FFFFF900C4324000
      OS Version: 6_1_7600
    Didn't install anything recently, and this has been happening periodicaly.
    Sunday, September 25, 2011 1:48 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: fffff6fc80621920, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc0000185, error status (normally i/o status code)
    Arg3: 000000007481a880, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff900c4324000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc0000185 - Le p riph rique d

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c0000185

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  dwm.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  fffff8800d6bc8e0 -- (.trap 0xfffff8800d6bc8e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff900c4324000 rbx=0000000000000000 rcx=000000000000233a
    rdx=fffffa8007f55c05 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff9600022265c rsp=fffff8800d6bca70 rbp=0000000000000001
     r8=0000000000000bbf  r9=00000000000035eb r10=fffff900c29a82a0
    r11=fffff8800d6bca90 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    win32k+0x20265c:
    fffff960`0022265c ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80002cfc168 to fffff80002c87740

    STACK_TEXT: 
    fffff880`0d6bc5c8 fffff800`02cfc168 : 00000000`0000007a fffff6fc`80621920 ffffffff`c0000185 00000000`7481a880 : nt!KeBugCheckEx
    fffff880`0d6bc5d0 fffff800`02c7952b : fffffa80`04646940 fffff880`0d6bc740 fffff880`02b69c00 fffffa80`08d4b770 : nt! ?? ::FNODOBFM::`string'+0x34c0e
    fffff880`0d6bc6b0 fffff800`02ca25c4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000689 : nt!MiIssueHardFault+0x28b
    fffff880`0d6bc780 fffff800`02c8582e : 00000000`00000000 fffff900`c00bf010 00000000`00000000 fffff900`c29a82a0 : nt!MmAccessFault+0x11c4
    fffff880`0d6bc8e0 fffff960`0022265c : fffff900`00000000 00000000`00000000 fffffa80`80000000 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`0d6bca70 fffff900`00000000 : 00000000`00000000 fffffa80`80000000 00000000`00000000 00000000`00021000 : win32k+0x20265c
    fffff880`0d6bca78 00000000`00000000 : fffffa80`80000000 00000000`00000000 00000000`00021000 fffff960`00222939 : 0xfffff900`00000000


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    win32k+20265c
    fffff960`0022265c ??              ???

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  win32k+20265c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x7a_c0000185_win32k+20265c

    BUCKET_ID:  X64_0x7a_c0000185_win32k+20265c

    Followup: MachineOwner

    ------------------------------------------------------------------------------------------

    Please check your disk cables, disable all security softwares, update all possible drivers. Also, uninstall all unused programs and run msconfig to disable all startup items except Microsoft ones.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator

    • Proposed as answer by Cloud_TS Thursday, September 29, 2011 6:32 AM
    • Marked as answer by Cloud_TS Monday, October 3, 2011 2:13 AM
    Monday, September 26, 2011 12:20 PM

All replies

  • Hello,

     Bug Check Code 0x7A: http://msdn.microsoft.com/en-us/library/ff559211(v=VS.85).aspx

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here.

    You can also contact Microsoft CSS.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    Monday, September 26, 2011 7:57 AM
  • https://skydrive.live.com/redir.aspx?cid=a97aed2e54c0b7c3&resid=A97AED2E54C0B7C3!103
    Monday, September 26, 2011 11:00 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: fffff6fc80621920, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc0000185, error status (normally i/o status code)
    Arg3: 000000007481a880, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff900c4324000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    ERROR_CODE: (NTSTATUS) 0xc0000185 - Le p riph rique d

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR:  0x7a_c0000185

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  dwm.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  fffff8800d6bc8e0 -- (.trap 0xfffff8800d6bc8e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff900c4324000 rbx=0000000000000000 rcx=000000000000233a
    rdx=fffffa8007f55c05 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff9600022265c rsp=fffff8800d6bca70 rbp=0000000000000001
     r8=0000000000000bbf  r9=00000000000035eb r10=fffff900c29a82a0
    r11=fffff8800d6bca90 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    win32k+0x20265c:
    fffff960`0022265c ??              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80002cfc168 to fffff80002c87740

    STACK_TEXT: 
    fffff880`0d6bc5c8 fffff800`02cfc168 : 00000000`0000007a fffff6fc`80621920 ffffffff`c0000185 00000000`7481a880 : nt!KeBugCheckEx
    fffff880`0d6bc5d0 fffff800`02c7952b : fffffa80`04646940 fffff880`0d6bc740 fffff880`02b69c00 fffffa80`08d4b770 : nt! ?? ::FNODOBFM::`string'+0x34c0e
    fffff880`0d6bc6b0 fffff800`02ca25c4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000689 : nt!MiIssueHardFault+0x28b
    fffff880`0d6bc780 fffff800`02c8582e : 00000000`00000000 fffff900`c00bf010 00000000`00000000 fffff900`c29a82a0 : nt!MmAccessFault+0x11c4
    fffff880`0d6bc8e0 fffff960`0022265c : fffff900`00000000 00000000`00000000 fffffa80`80000000 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`0d6bca70 fffff900`00000000 : 00000000`00000000 fffffa80`80000000 00000000`00000000 00000000`00021000 : win32k+0x20265c
    fffff880`0d6bca78 00000000`00000000 : fffffa80`80000000 00000000`00000000 00000000`00021000 fffff960`00222939 : 0xfffff900`00000000


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    win32k+20265c
    fffff960`0022265c ??              ???

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  win32k+20265c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x7a_c0000185_win32k+20265c

    BUCKET_ID:  X64_0x7a_c0000185_win32k+20265c

    Followup: MachineOwner

    ------------------------------------------------------------------------------------------

    Please check your disk cables, disable all security softwares, update all possible drivers. Also, uninstall all unused programs and run msconfig to disable all startup items except Microsoft ones.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator

    • Proposed as answer by Cloud_TS Thursday, September 29, 2011 6:32 AM
    • Marked as answer by Cloud_TS Monday, October 3, 2011 2:13 AM
    Monday, September 26, 2011 12:20 PM
  • Thank you 
    Monday, September 26, 2011 10:24 PM