Author Topic: Eco Manager Caused Blue Screen Of Death (BSOD)  (Read 1156 times)

Johnny

  • Calf
  • *
  • Posts: 2
Eco Manager Caused Blue Screen Of Death (BSOD)
« on: February 18, 2010, 06:58:38 am »
   

Product: 1.0TB HD-CE1.0TU2

Firmware : 3.0

DriveNavi v1.4.0.1

Eco manager fw 1.0.1.0

My system: Windows 7 RTM7600 32-bit

 

I get BSOD when the external hdd wake up from sleep after a few minutes.

From the Windbg below, you can see it is caused by bautopw.sys.

 

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: C:\Symbols;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a0c000 PsLoadedModuleList = 0x82b54810
Debug session time: Wed Feb 17 00:29:22.114 2010 (GMT+8)
System Uptime: 0 days 23:11:42.112
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols

Loading unloaded module list
...........
0: kd> !analyze v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 875e9030, 82b32ae0, 88b538c8}

*** ERROR: Module load completed but symbols could not be loaded for bautopw.sys
Probably caused by : bautopw.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 875e9030, Physical Device Object of the stack
Arg3: 82b32ae0, Functional Device Object of the stack
Arg4: 88b538c8, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  88b538c8

DEVICE_OBJECT: 860fb188

DRIVER_OBJECT: 877656e0

IMAGE_NAME:  bautopw.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4885362a

MODULE_NAME: bautopw

FAULTING_MODULE: a05fa000 bautopw

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82a48044 to 82ae8e10

STACK_TEXT:  
82b32a94 82a48044 0000009f 00000003 875e9030 nt!KeBugCheckEx+0x1e
82b32b00 82a478d8 82b32bac 00000000 82b3f280 nt!PopCheckIrpWatchdog+0x1f5
82b32b38 82a7612d 82b4da20 00000000 32025cba nt!PopCheckForIdleness+0x73
82b32b7c 82a760d1 82b35d20 82b32ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82b32c68 82a75f8e 82b35d20 82b32ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82b32cdc 82a7430e 0051acd9 87c3e7f0 82b3f280 nt!KiTimerExpiration+0x25c
82b32d20 82a74138 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82b32d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_bautopw.sys

BUCKET_ID:  0x9F_IMAGE_bautopw.sys

Followup: MachineOwner
---------

 

Do Buffalo have updated version


Johnny

  • Calf
  • *
  • Posts: 2
Re: Eco Manager Caused Blue Screen Of Death (BSOD)
« Reply #1 on: February 22, 2010, 01:55:39 pm »
   Can Buffalo Tech people see in this issue and provide solution. Thanks.