locked
BSOD bccode 9f Locale ID 1033 RRS feed

  • Question

  • Over the last few weeks, there have been a handful of times where I'll try to wake my desktop from sleep/hibernation only to find it shut off due to a BSOD bccode 9f Locale ID 1033 error. I haven't changed any hardware recently.

    The Windows error that shows points to the minidump file, which i've uploaded along with the MSinfo file.

    Any help would be appreciated!

    https://onedrive.live.com/redir?resid=E7A1FA3963A70287!115&authkey=!AOj70_Ts8NaYmns&ithint=file%2czip

    Saturday, January 17, 2015 3:59 PM

Answers

  • CY

    This was Related to Rt86win7.sys 8101E/8168/8169 NDIS 6.2 32-bit Driver from Realtek Corporation.  I would remove the  current driver and install the newest driver available

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\DMPFiles\011715-40716-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`1aa31022?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`2757e022?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0e8d70e2?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`18a45ae2?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`207ab562?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`18e6fc32?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9a500?
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
    Machine Name:
    Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c51890
    Debug session time: Fri Jan 16 18:17:32.147 2015 (UTC - 5:00)
    System Uptime: 2 days 14:55:16.458
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................
    Loading User Symbols
    Loading unloaded module list
    .............................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800dbada10, fffff80000b9a518, fffffa8011a27180}
    
    Probably caused by : pci.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800dbada10, Physical Device Object of the stack
    Arg3: fffff80000b9a518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa8011a27180, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000e00000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA0FB0
    
    STACK_TEXT:  
    fffff800`00b9a4c8 fffff800`02af3922 : 00000000`0000009f 00000000`00000003 fffffa80`0dbada10 fffff800`00b9a518 : nt!KeBugCheckEx
    fffff800`00b9a4d0 fffff800`02a8fb5c : fffff800`00b9a600 fffff800`00b9a600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00b9a570 fffff800`02a8f9f6 : fffff800`02c34140 00000000`00dd8f80 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9a5e0 fffff800`02a8f8de : 0000020f`66548dfc fffff800`00b9ac58 00000000`00dd8f80 fffff800`02c02288 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9ac30 fffff800`02a8f6c7 : 00000089`c5ed21c1 00000089`00dd8f80 00000089`c5ed2114 00000000`00000080 : nt!KiTimerExpiration+0x1be
    fffff800`00b9acd0 fffff800`02a7cb8a : fffff800`02bfee80 fffff800`02c0ccc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9ad80 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ad40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_VERSION:  6.1.7601.17514
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_rt64win7_image_pci.sys
    
    FAILURE_ID_HASH:  {041ba02b-99ae-ff7a-d9e6-d2dba0b936e9}
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa8011a27180
    Irp is active with 3 stacks 2 is current (= 0xfffffa8011a27298)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa800f5a0050 00000000 fffff80002cd0210-fffffa8013ac6220 Success Error Cancel pending
    	      Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     \Driver\RTL8167	nt!PopSystemIrpCompletion
    			Args: 00015400 00000000 00000005 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8013ac6220    
    
    			Args: 00000000 00000000 00000000 00000000
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Yolanda Zhu Thursday, January 22, 2015 1:07 AM
    • Marked as answer by ZigZag3143x Thursday, January 22, 2015 2:06 AM
    Saturday, January 17, 2015 4:16 PM

All replies

  • Have you checked that you have the latest drivers installed from the manufacturer's site?

    Especially drivers for the chipset.

    -----

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80002a0e000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  548a6e28

    DRVPOWERSTATE_SUBCODE:  3

    IRP_ADDRESS: fffffa8011a27180

    DEVICE_OBJECT: fffffa800dbada10

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    CURRENT_IRQL:  0

    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

    LAST_CONTROL_TRANSFER:  from fffff80002af3922 to fffff80002a84e80

    STACK_TEXT: 
    fffff800`00b9a4c8 fffff800`02af3922 : 00000000`0000009f 00000000`00000003 fffffa80`0dbada10 fffff800`00b9a518 : nt+0x76e80
    fffff800`00b9a4d0 00000000`0000009f : 00000000`00000003 fffffa80`0dbada10 fffff800`00b9a518 fffffa80`11a27180 : nt+0xe5922
    fffff800`00b9a4d8 00000000`00000003 : fffffa80`0dbada10 fffff800`00b9a518 fffffa80`11a27180 00000000`c00000bb : 0x9f
    fffff800`00b9a4e0 fffffa80`0dbada10 : fffff800`00b9a518 fffffa80`11a27180 00000000`c00000bb 00000000`00000000 : 0x3
    fffff800`00b9a4e8 fffff800`00b9a518 : fffffa80`11a27180 00000000`c00000bb 00000000`00000000 fffff800`02c33d40 : 0xfffffa80`0dbada10
    fffff800`00b9a4f0 fffffa80`11a27180 : 00000000`c00000bb 00000000`00000000 fffff800`02c33d40 fffff800`00000002 : 0xfffff800`00b9a518
    fffff800`00b9a4f8 00000000`c00000bb : 00000000`00000000 fffff800`02c33d40 fffff800`00000002 00000000`00018000 : 0xfffffa80`11a27180
    fffff800`00b9a500 00000000`00000000 : fffff800`02c33d40 fffff800`00000002 00000000`00018000 fffff800`02c33d30 : 0xc00000bb


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt+76e80
    fffff800`02a84e80 48894c2408      mov     qword ptr [rsp+8],rcx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt+76e80

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  ntoskrnl.exe

    Saturday, January 17, 2015 4:16 PM
  • CY

    This was Related to Rt86win7.sys 8101E/8168/8169 NDIS 6.2 32-bit Driver from Realtek Corporation.  I would remove the  current driver and install the newest driver available

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\DMPFiles\011715-40716-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`1aa31022?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`2757e022?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0e8d70e2?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`18a45ae2?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`207ab562?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`18e6fc32?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9a500?
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
    Machine Name:
    Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c51890
    Debug session time: Fri Jan 16 18:17:32.147 2015 (UTC - 5:00)
    System Uptime: 2 days 14:55:16.458
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................
    Loading User Symbols
    Loading unloaded module list
    .............................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa800dbada10, fffff80000b9a518, fffffa8011a27180}
    
    Probably caused by : pci.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800dbada10, Physical Device Object of the stack
    Arg3: fffff80000b9a518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: fffffa8011a27180, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000e00000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA0FB0
    
    STACK_TEXT:  
    fffff800`00b9a4c8 fffff800`02af3922 : 00000000`0000009f 00000000`00000003 fffffa80`0dbada10 fffff800`00b9a518 : nt!KeBugCheckEx
    fffff800`00b9a4d0 fffff800`02a8fb5c : fffff800`00b9a600 fffff800`00b9a600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00b9a570 fffff800`02a8f9f6 : fffff800`02c34140 00000000`00dd8f80 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9a5e0 fffff800`02a8f8de : 0000020f`66548dfc fffff800`00b9ac58 00000000`00dd8f80 fffff800`02c02288 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9ac30 fffff800`02a8f6c7 : 00000089`c5ed21c1 00000089`00dd8f80 00000089`c5ed2114 00000000`00000080 : nt!KiTimerExpiration+0x1be
    fffff800`00b9acd0 fffff800`02a7cb8a : fffff800`02bfee80 fffff800`02c0ccc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9ad80 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ad40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_VERSION:  6.1.7601.17514
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_rt64win7_image_pci.sys
    
    FAILURE_ID_HASH:  {041ba02b-99ae-ff7a-d9e6-d2dba0b936e9}
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa8011a27180
    Irp is active with 3 stacks 2 is current (= 0xfffffa8011a27298)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa800f5a0050 00000000 fffff80002cd0210-fffffa8013ac6220 Success Error Cancel pending
    	      Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     \Driver\RTL8167	nt!PopSystemIrpCompletion
    			Args: 00015400 00000000 00000005 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8013ac6220    
    
    			Args: 00000000 00000000 00000000 00000000
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Yolanda Zhu Thursday, January 22, 2015 1:07 AM
    • Marked as answer by ZigZag3143x Thursday, January 22, 2015 2:06 AM
    Saturday, January 17, 2015 4:16 PM