bollemania
Schraubenverwechsler(in)
Hallo zusammen,
habe das Problem dass mein Lappi immer wenn ich ihn runterfahre oder den Deckel schliesse sich seit geraumer Zeit immer mit Bluescreen verabschiedet.
im Bluescreen steht immer was von Framework, habe den Bluescreen mal ausgewertet, verstehe aber nur Bahnhof ( Noob ) vielleicht könnt Ihr mir da weiterhelfen.
Acer Aspire 8920G Win7 Ultimate x86
Danke
-------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\090110-157015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8304f000 PsLoadedModuleList = 0x83197810
Debug session time: Wed Sep 1 22:57:09.631 2010 (UTC + 2:00)
System Uptime: 0 days 14:57:38.613
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
..................................................
1: kd> !analyze –v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {d, 85f28158, 8ad2b610, 8b247650}
Probably caused by : WUDFRd.sys ( WUDFRd!RdPnpTracker::RdPnpProcessor+2bd )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000d, A power irp was received for the device but the irp was not
requested by the device (the power policy owner). Possibly there
are multiple power policy owners. Only one driver in the stack can
be the power policy owner. A KMDF driver can change power policy
ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: 85f28158, Device object pointer.
Arg3: 8ad2b610, Power Irp.
Arg4: 8b247650, Reserved.
Debugging Details:
------------------
BUGCHECK_STR: 0x10D_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8b46af9e to 8312bd10
STACK_TEXT:
8d917b7c 8b46af9e 0000010d 0000000d 85f28158 nt!KeBugCheckEx+0x1e
8d917b98 8b47df72 8b247650 0000000d 85f28158 Wdf01000!FxVerifierBugCheck+0x24
8d917bb4 8b47dfce 8b247650 8d917be0 8b471e02 Wdf01000!FxPkgFdo:
ispatchDeviceSetPower+0x6e
8d917bc0 8b471e02 85f4d0d0 8d917be8 8ad2b610 Wdf01000!FxPkgFdo::_DispatchSetPower+0x23
8d917be0 8b44ea3f 8ad2b610 8d917c08 8b44ec63 Wdf01000!FxPkgPnp:
ispatch+0x207
8d917bec 8b44ec63 85f28158 8ad2b610 8ad2b610 Wdf01000!FxDevice:
ispatch+0x7f
8d917c08 8305ad16 85f28158 8ad2b610 00000016 Wdf01000!FxDevice:
ispatchWithLock+0x7b
8d917c20 8308b4ae 85ea2868 85f28158 8d917c38 nt!IopPoHandleIrp+0x28
8d917c30 8305d049 8d917c8c adb97735 85f28158 nt!IofCallDriver+0x55
8d917c38 adb97735 85f28158 8ad2b610 8ad2b610 nt!IoCallDriver+0x10
8d917c8c adb97551 85ea2868 adbacb80 adbabe58 WUDFRd!RdPnpTracker::RdPnpProcessor+0x2bd
8d917cd8 adb979c4 89f5cf78 86241ee8 831895bc WUDFRd!RdPnpTracker::RdPnpProcessor+0xd9
8d917cec 8326f815 86241ee8 85ea2868 859e24c0 WUDFRd!RdPnpTracker::RdPnpCallbackAtPassiveInSystemProcess+0x46
8d917d00 830bcf3b 89f5cf78 00000000 859e24c0 nt!IopProcessWorkItem+0x23
8d917d50 8325d6d3 00000001 a4b94ffa 00000000 nt!ExpWorkerThread+0x10d
8d917d90 8310f0f9 830bce2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
adb97735 e9e6010000 jmp WUDFRd!RdPnpTracker::RdPnpProcessor+0x4a8 (adb97920)
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: WUDFRd
IMAGE_NAME: WUDFRd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc854
FAILURE_BUCKET_ID: 0x10D_d_WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
BUCKET_ID: 0x10D_d_WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
Followup: MachineOwner
---------
habe das Problem dass mein Lappi immer wenn ich ihn runterfahre oder den Deckel schliesse sich seit geraumer Zeit immer mit Bluescreen verabschiedet.
im Bluescreen steht immer was von Framework, habe den Bluescreen mal ausgewertet, verstehe aber nur Bahnhof ( Noob ) vielleicht könnt Ihr mir da weiterhelfen.
Acer Aspire 8920G Win7 Ultimate x86
Danke
-------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\090110-157015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8304f000 PsLoadedModuleList = 0x83197810
Debug session time: Wed Sep 1 22:57:09.631 2010 (UTC + 2:00)
System Uptime: 0 days 14:57:38.613
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
..................................................
1: kd> !analyze –v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {d, 85f28158, 8ad2b610, 8b247650}
Probably caused by : WUDFRd.sys ( WUDFRd!RdPnpTracker::RdPnpProcessor+2bd )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000d, A power irp was received for the device but the irp was not
requested by the device (the power policy owner). Possibly there
are multiple power policy owners. Only one driver in the stack can
be the power policy owner. A KMDF driver can change power policy
ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: 85f28158, Device object pointer.
Arg3: 8ad2b610, Power Irp.
Arg4: 8b247650, Reserved.
Debugging Details:
------------------
BUGCHECK_STR: 0x10D_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8b46af9e to 8312bd10
STACK_TEXT:
8d917b7c 8b46af9e 0000010d 0000000d 85f28158 nt!KeBugCheckEx+0x1e
8d917b98 8b47df72 8b247650 0000000d 85f28158 Wdf01000!FxVerifierBugCheck+0x24
8d917bb4 8b47dfce 8b247650 8d917be0 8b471e02 Wdf01000!FxPkgFdo:
ispatchDeviceSetPower+0x6e8d917bc0 8b471e02 85f4d0d0 8d917be8 8ad2b610 Wdf01000!FxPkgFdo::_DispatchSetPower+0x23
8d917be0 8b44ea3f 8ad2b610 8d917c08 8b44ec63 Wdf01000!FxPkgPnp:
ispatch+0x2078d917bec 8b44ec63 85f28158 8ad2b610 8ad2b610 Wdf01000!FxDevice:
ispatch+0x7f8d917c08 8305ad16 85f28158 8ad2b610 00000016 Wdf01000!FxDevice:
ispatchWithLock+0x7b8d917c20 8308b4ae 85ea2868 85f28158 8d917c38 nt!IopPoHandleIrp+0x28
8d917c30 8305d049 8d917c8c adb97735 85f28158 nt!IofCallDriver+0x55
8d917c38 adb97735 85f28158 8ad2b610 8ad2b610 nt!IoCallDriver+0x10
8d917c8c adb97551 85ea2868 adbacb80 adbabe58 WUDFRd!RdPnpTracker::RdPnpProcessor+0x2bd
8d917cd8 adb979c4 89f5cf78 86241ee8 831895bc WUDFRd!RdPnpTracker::RdPnpProcessor+0xd9
8d917cec 8326f815 86241ee8 85ea2868 859e24c0 WUDFRd!RdPnpTracker::RdPnpCallbackAtPassiveInSystemProcess+0x46
8d917d00 830bcf3b 89f5cf78 00000000 859e24c0 nt!IopProcessWorkItem+0x23
8d917d50 8325d6d3 00000001 a4b94ffa 00000000 nt!ExpWorkerThread+0x10d
8d917d90 8310f0f9 830bce2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
adb97735 e9e6010000 jmp WUDFRd!RdPnpTracker::RdPnpProcessor+0x4a8 (adb97920)
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: WUDFRd
IMAGE_NAME: WUDFRd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc854
FAILURE_BUCKET_ID: 0x10D_d_WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
BUCKET_ID: 0x10D_d_WUDFRd!RdPnpTracker::RdPnpProcessor+2bd
Followup: MachineOwner
---------
. Ohne klappts normal.