BlueScreen

[flirtcheckers]

Hallo,

bekam heute folgenden BluScreen (ausgewertet mit BlueScreenViewer)

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

DRIVER_POWER_STATE_FAILURE

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000009f (0x00000003, 0x866ff030, 0x866f3858, 0x868b0498)

*** ntoskrnl.exe - Address 0x8290791f base at 0x8284c000 DateStamp 0x4f79a9be

Mein System:
Windows Vista Home Edition
Service Pack 2
Samsung Notebook
Intel Core 2 Duo CPU T7250 2.00 GHZ
2GB Ram
ATI Mobility Radeon X2300

Was kann das sein ?

 

[Joggel4]

https://www.google.de/search?q=0x00...pw.r_qf.&fp=6fc323c5cbf40317&biw=1400&bih=728


Schon mal den Hotfix ausprobiert?

 

[simpel1970]

Werte den Bluescreen mit dem Debugger von Microsoft aus. Bluescreenview arbeitet viel zu oberflächlich für eine genauere Analyse. Eine kurze Anleitung für die Auswertung mittels Debugging Tools findest du in meiner Signatur.

 

[flirtcheckers]

hab das ganze nun nach deiner Anleitung gemacht und folgendes hat er ausgeworfen:

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


Loading Dump File [C:\Windows\Minidump\Mini082612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18607.x86fre.vistasp2_gdr.120402-0336
Machine Name:
Kernel base = 0x8284c000 PsLoadedModuleList = 0x82959930
Debug session time: Sun Aug 26 18:49:57.743 2012 (UTC + 2:00)
System Uptime: 0 days 7:42:14.661
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 866ff030, 866f3858, 868b0498}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
***                                                                   ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\AiCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : AiCharger.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 (usually 10 minutes).
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 866ff030, Physical Device Object of the stack
Arg3: 866f3858, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: 868b0498, The blocked IRP

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
***                                                                   ***
*************************************************************************

DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: 866f3858

DRIVER_OBJECT: 840857d8

IMAGE_NAME:  AiCharger.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4be12e52

MODULE_NAME: AiCharger

FAULTING_MODULE: 88343000 AiCharger

IRP_ADDRESS:  868b0498

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFFFFF8069E000

STACK_TEXT:  
8069dd6c 82876cd0 0000009f 00000003 866ff030 nt!KeBugCheckEx+0x1e
8069ddc8 8287730e 8069de34 8069def0 00000001 nt!PopCheckIrpWatchdog+0x1ad
8069de08 828b72e0 82950ca0 00000000 d35de730 nt!PopCheckForIdleness+0x343
8069df28 828b6ea0 8069df70 8293b902 8069df78 nt!KiTimerListExpire+0x367
8069df88 828b6a63 00000000 00000000 001b20ba nt!KiTimerExpiration+0x22a
8069dff4 828b4ff5 b5af7d10 00000000 00000000 nt!KiRetireDpcList+0xba
8069dff8 b5af7d10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
828b4ff5 00000000 0000001b 00c7850f bb830000 0xb5af7d10


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_AiCharger.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_AiCharger.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 (usually 10 minutes).
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 866ff030, Physical Device Object of the stack
Arg3: 866f3858, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: 868b0498, The blocked IRP

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
***                                                                   ***
*************************************************************************

DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: 866f3858

DRIVER_OBJECT: 840857d8

IMAGE_NAME:  AiCharger.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4be12e52

MODULE_NAME: AiCharger

FAULTING_MODULE: 88343000 AiCharger

IRP_ADDRESS:  868b0498

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFFFFF8069E000

STACK_TEXT:  
8069dd6c 82876cd0 0000009f 00000003 866ff030 nt!KeBugCheckEx+0x1e
8069ddc8 8287730e 8069de34 8069def0 00000001 nt!PopCheckIrpWatchdog+0x1ad
8069de08 828b72e0 82950ca0 00000000 d35de730 nt!PopCheckForIdleness+0x343
8069df28 828b6ea0 8069df70 8293b902 8069df78 nt!KiTimerListExpire+0x367
8069df88 828b6a63 00000000 00000000 001b20ba nt!KiTimerExpiration+0x22a
8069dff4 828b4ff5 b5af7d10 00000000 00000000 nt!KiRetireDpcList+0xba
8069dff8 b5af7d10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
828b4ff5 00000000 0000001b 00c7850f bb830000 0xb5af7d10


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_AiCharger.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_AiCharger.sys

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

 

[simpel1970]

Der Auswertung zufolge, wird das Problem durch das Asus Tool "AI Charger" verursacht. Deinstalliere das Tool und beobachte, ob das Problem erneut auftritt.

 

[flirtcheckers]

das is ja scheiße....

hatte nun endlich ein tool um mein iPad 2 am Lappi zu laden :-(

 

[simpel1970]

Hört sich so an, als ob du das Tool nur ungern wieder aufgeben würdest.

In diesem Fall könntest noch das Tool "Driver Verifier" bemühen, um zu kontrollieren, ob evtl. noch ein anderer Treiber (der aktualisiert werden müsste) dazwischen funkt.

http://support.microsoft.com/kb/244617