New
#1
MapleSEA BSOD
MapleSEA BSOD upon login page.
System Specs:
- Windows 7 Home Premium 32-bit
- OEM Windows Vista upgraded to Windows 7 using CD
- 2.5 year-old Aspire 4736G
Thank you. :3
MapleSEA BSOD upon login page.
System Specs:
- Windows 7 Home Premium 32-bit
- OEM Windows Vista upgraded to Windows 7 using CD
- 2.5 year-old Aspire 4736G
Thank you. :3
Maple doesnt play well with win 7 and the developers know it. You should go to them for the latest patch. Your newest crash was from february so I have no idea of what is happening now.
related to USBSTOR.SYS
Please run system file check to verify and repair your OS and read here. USB Driver - General Fix for Problems
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\021211-26956-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82d7cad4? Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *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 Personal Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x82c56000 PsLoadedModuleList = 0x82d9e810 Debug session time: Sat Feb 12 00:53:34.045 2011 (GMT-4) System Uptime: 1 days 0:10:38.058 Loading Kernel Symbols ............................................................... ................................................................ .......................................... Loading User Symbols Loading unloaded module list ..... 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: 88bdbc90, Physical Device Object of the stack Arg3: 82d7cae0, Functional Device Object of the stack Arg4: 85820930, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: 85820930 DEVICE_OBJECT: 88bda460 DRIVER_OBJECT: 86f09e30 IMAGE_NAME: USBSTOR.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc877 MODULE_NAME: USBSTOR FAULTING_MODULE: 8c25f000 USBSTOR CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 82c92054 to 82d32d10 STACK_TEXT: 82d7ca94 82c92054 0000009f 00000003 88bdbc90 nt!KeBugCheckEx+0x1e 82d7cb00 82c918e8 82d7cba0 00000000 82d89280 nt!PopCheckIrpWatchdog+0x1f5 82d7cb38 82cc004d 82d97a20 00000000 cd583f89 nt!PopCheckForIdleness+0x73 82d7cb7c 82cbfff1 82d7fd20 82d7cca8 00000001 nt!KiProcessTimerDpcTable+0x50 82d7cc68 82cbfeae 82d7fd20 82d7cca8 00000000 nt!KiProcessExpiredTimerList+0x101 82d7ccdc 82cbe20e 0055223e 88d1d510 82d89280 nt!KiTimerExpiration+0x25c 82d7cd20 82cbe038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 82d7cd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0x9F_IMAGE_USBSTOR.SYS BUCKET_ID: 0x9F_IMAGE_USBSTOR.SYS Followup: MachineOwner ---------
Thanks zigzag. But my latest crash is in May. And uninstall USB Root Hub too?