locked
BSOD when idle on battery RRS feed

  • Question

  • Good morning to everybody!

    My almost new Acer Travelmate TM8372T-S454G32Mnbb with W7-64 Prof. (6.1 build 7600 German) drives me nuts, especially as I am currently on a business trip and exactly at at the time of presentations I get a BSOD.

    The recent Minidumps are here: http://cid-b696547f8700694e.office.live.com/self.aspx/MINIDUMP

    I tried already KB  977186 without much success though.

    Appreciate any help!

    Best regards from China

    Saturday, December 4, 2010 2:27 AM

Answers

  • I'd venture a guess that the system is having an issue with powering on/off the DVD drive. I'd see if the latest BIOS update helps the issue,
    http://us.acer.com/acer/service.do?LanguageISOCtxParam=en&miu10einu24.current.attN2B2F2EEF=3750&sp=page15e&ctx2.c2att1=25&miu10ekcond13.attN2B2F2EEF=3750&CountryISOCtxParam=US&ctx1g.c2att92=453&ctx1.att21k=1&CRC=2054404012

    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8004943680, fffff80000b9c518, fffffa8003f18c60}
    
    Probably caused by : atapi.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8004943680, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa8003f18c60, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE: 3
    
    DRIVER_OBJECT: fffffa800491ae70
    
    IMAGE_NAME: atapi.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc113
    
    MODULE_NAME: atapi
    
    FAULTING_MODULE: fffff88000e2f000 atapi
    
    CUSTOMER_CRASH_COUNT: 1
    
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    
    BUGCHECK_STR: 0x9F
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 2
    
    STACK_TEXT: 
    fffff800`00b9c4c8 fffff800`02ae4273 : 00000000`0000009f 00000000`00000003 fffffa80`04943680 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02a8129e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
    fffff800`00b9c570 fffff800`02a80dd6 : fffffa80`053da530 fffffa80`053da530 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02a814be : 00000027`2ba75436 fffff800`00b9cc58 00000000`0010749d fffff800`02bf3628 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02a80cb7 : 00000009`2e5168cd 00000009`0010749d 00000009`2e516855 00000000`0000009d : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02a7deea : fffff800`02befe80 fffff800`02bfdc40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND: kb
    
    FOLLOWUP_NAME: MachineOwner
    
    FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys
    
    BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa8003f18c60
    Irp is active with 5 stacks 3 is current (= 0xfffffa8003f18dc0)
     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
     [ 0, 0]  0 0 00000000 00000000 00000000-00000000  
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]  0 e1 fffffa8004943680 00000000 fffff80002a600b0-fffffa8007325e90 Success Error Cancel pending
    	    \Driver\atapi	nt!IopUnloadSafeCompletion
    			Args: 00000000 00000001 00000001 00000000
     [ 16, 2]  0 e1 fffffa8004f4dc70 00000000 fffff80002a600b0-fffffa8005fe3790 Success Error Cancel pending
    	    \Driver\cdrom	nt!IopUnloadSafeCompletion
    			Args: 00000000 00000001 00000001 00000000
     [ 0, 0]  0 0 00000000 00000000 00000000-fffffa8004819f30  
    
    			Args: 00000000 00000000 00000000 00000000
    0: kd> !devobj fffffa8004943680
    Device object (fffffa8004943680) is for:
     Cannot read info offset from nt!ObpInfoMaskToOffset
     \Driver\atapi DriverObject fffffa800491ae70
    Current Irp 00000000 RefCount 1 Type 00000002 Flags 00005050
    DevExt fffffa80049437d0 DevObjExt fffffa8004943f90 Dope fffffa80053c64f0 DevNode fffffa8004948d90 
    ExtensionFlags (0x00000800) 
                   Unknown flags 0x00000800
    AttachedDevice (Upper) fffffa8005161030Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PxHlpa64.sys
    *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
     \Driver\PxHlpa64
    Device queue is not busy.
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.6, DMIVersion 38, Size=2214]
    BiosMajorRelease = 3
    BiosMinorRelease = 240
    BiosVendor = Acer
    BiosVersion = V1.03
    BiosReleaseDate = 06/24/2010
    SystemManufacturer = Acer
    SystemProductName = TravelMate 8372
    SystemFamily = Intel_Mobile
    SystemVersion = V1.03
    SystemSKU = Calpella_CRB
    BaseBoardManufacturer = Acer
    BaseBoardProduct = TravelMate 8372
    BaseBoardVersion = PSMBOU-1234567
    
    

    -- Mike Burr
    MS Technologies - Development - *nix
    • Proposed as answer by Andre.Ziegler Saturday, December 4, 2010 1:33 PM
    • Marked as answer by RoadWarrior99 Sunday, December 5, 2010 4:35 AM
    Saturday, December 4, 2010 9:18 AM

All replies

  • I'd venture a guess that the system is having an issue with powering on/off the DVD drive. I'd see if the latest BIOS update helps the issue,
    http://us.acer.com/acer/service.do?LanguageISOCtxParam=en&miu10einu24.current.attN2B2F2EEF=3750&sp=page15e&ctx2.c2att1=25&miu10ekcond13.attN2B2F2EEF=3750&CountryISOCtxParam=US&ctx1g.c2att92=453&ctx1.att21k=1&CRC=2054404012

    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8004943680, fffff80000b9c518, fffffa8003f18c60}
    
    Probably caused by : atapi.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8004943680, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa8003f18c60, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE: 3
    
    DRIVER_OBJECT: fffffa800491ae70
    
    IMAGE_NAME: atapi.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc113
    
    MODULE_NAME: atapi
    
    FAULTING_MODULE: fffff88000e2f000 atapi
    
    CUSTOMER_CRASH_COUNT: 1
    
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    
    BUGCHECK_STR: 0x9F
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 2
    
    STACK_TEXT: 
    fffff800`00b9c4c8 fffff800`02ae4273 : 00000000`0000009f 00000000`00000003 fffffa80`04943680 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02a8129e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
    fffff800`00b9c570 fffff800`02a80dd6 : fffffa80`053da530 fffffa80`053da530 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02a814be : 00000027`2ba75436 fffff800`00b9cc58 00000000`0010749d fffff800`02bf3628 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02a80cb7 : 00000009`2e5168cd 00000009`0010749d 00000009`2e516855 00000000`0000009d : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02a7deea : fffff800`02befe80 fffff800`02bfdc40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND: kb
    
    FOLLOWUP_NAME: MachineOwner
    
    FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys
    
    BUCKET_ID: X64_0x9F_3_IMAGE_atapi.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa8003f18c60
    Irp is active with 5 stacks 3 is current (= 0xfffffa8003f18dc0)
     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
     [ 0, 0]  0 0 00000000 00000000 00000000-00000000  
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]  0 e1 fffffa8004943680 00000000 fffff80002a600b0-fffffa8007325e90 Success Error Cancel pending
    	    \Driver\atapi	nt!IopUnloadSafeCompletion
    			Args: 00000000 00000001 00000001 00000000
     [ 16, 2]  0 e1 fffffa8004f4dc70 00000000 fffff80002a600b0-fffffa8005fe3790 Success Error Cancel pending
    	    \Driver\cdrom	nt!IopUnloadSafeCompletion
    			Args: 00000000 00000001 00000001 00000000
     [ 0, 0]  0 0 00000000 00000000 00000000-fffffa8004819f30  
    
    			Args: 00000000 00000000 00000000 00000000
    0: kd> !devobj fffffa8004943680
    Device object (fffffa8004943680) is for:
     Cannot read info offset from nt!ObpInfoMaskToOffset
     \Driver\atapi DriverObject fffffa800491ae70
    Current Irp 00000000 RefCount 1 Type 00000002 Flags 00005050
    DevExt fffffa80049437d0 DevObjExt fffffa8004943f90 Dope fffffa80053c64f0 DevNode fffffa8004948d90 
    ExtensionFlags (0x00000800) 
                   Unknown flags 0x00000800
    AttachedDevice (Upper) fffffa8005161030Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PxHlpa64.sys
    *** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
     \Driver\PxHlpa64
    Device queue is not busy.
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.6, DMIVersion 38, Size=2214]
    BiosMajorRelease = 3
    BiosMinorRelease = 240
    BiosVendor = Acer
    BiosVersion = V1.03
    BiosReleaseDate = 06/24/2010
    SystemManufacturer = Acer
    SystemProductName = TravelMate 8372
    SystemFamily = Intel_Mobile
    SystemVersion = V1.03
    SystemSKU = Calpella_CRB
    BaseBoardManufacturer = Acer
    BaseBoardProduct = TravelMate 8372
    BaseBoardVersion = PSMBOU-1234567
    
    

    -- Mike Burr
    MS Technologies - Development - *nix
    • Proposed as answer by Andre.Ziegler Saturday, December 4, 2010 1:33 PM
    • Marked as answer by RoadWarrior99 Sunday, December 5, 2010 4:35 AM
    Saturday, December 4, 2010 9:18 AM
  • Many thanks Mike for your quick answer!

    Did not think about a bios problem as I kept the system clean as from installation end of July without any drivers outside W7 and as you could see the problems became worse by the day.

    Have installed now V 1.05 bios and the updated Intel drivers - so far so good - will report at the end of coming week about the results 'on the road'

    Best regards / Ron

    Sunday, December 5, 2010 4:45 AM
  • Mike,

     

    many thanks again - you saved my trip!

     

    No problem ever since!

     

    Best regards

    Saturday, December 11, 2010 4:58 AM