- #1
D
Damy
Neues Mitglied
Themenersteller
- Dabei seit
- 17.02.2015
- Beiträge
- 2
- Reaktionspunkte
- 0
Hallo zusammen habe ein problem,
habe immer wieder einen Bluscreen und komme nicht weiter ...
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021715-19734-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 Longhorn Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Kernel base = 0xfffff800`03804000 PsLoadedModuleList = 0xfffff800`03a48890
Debug session time: Tue Feb 17 20:13:28.762 2015 (GMT+1)
System Uptime: 0 days 2:39:51.605
Loading Kernel Symbols
..........................................................................................................................................................................
Loading unloaded module list
......
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {5, 0, 1202, fffffa800953d110}
Probably caused by : Wdf01000.sys ( Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a )
Followup: MachineOwner
---------
4: kd> g
^ No runnable debuggees error in 'g'
4: kd> .restart
Loading Dump File [C:\Windows\Minidump\021715-19734-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 Longhorn Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Kernel base = 0xfffff800`03804000 PsLoadedModuleList = 0xfffff800`03a48890
Debug session time: Tue Feb 17 20:13:28.762 2015 (GMT+1)
System Uptime: 0 days 2:39:51.605
Loading Kernel Symbols
..........................................................................................................................................................................
Loading unloaded module list
......
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {5, 0, 1202, fffffa800953d110}
Probably caused by : Wdf01000.sys ( Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
DESCRIPTION
The Windows Driver Framework has detected that a violation has occurred This resulted
in a condition where the machine would hang forever. By crashing, the Windows Driver
Framework is attempting to get enough information into the minidump such that somebody
can pinpoint the machine crash's cause, which is inside this driver.
Arguments:
Arg1: 0000000000000005, Device object of the failing device
Arg2: 0000000000000000, State that timed out
Arg3: 0000000000001202
Arg4: fffffa800953d110
Debugging Details:
------------------
OVERLAPPED_MODULE: HIDCLASS
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x10D
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88000d8ea46 to fffff80003878ec0
STACK_TEXT:
fffff880`0a8a5618 fffff880`00d8ea46 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : nt!KeBugCheckEx
fffff880`0a8a5620 00000000`00000000 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x8a
FOLLOWUP_IP:
Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
fffff880`00d8ea46 cc int 3
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51c51641
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0x10D_Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
BUCKET_ID: X64_0x10D_Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
Followup: MachineOwner
---------
Das war in der Minidump Datei vom neusen Bluscreen
danke für jede Hilfe im voraus
habe immer wieder einen Bluscreen und komme nicht weiter ...
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021715-19734-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 Longhorn Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Kernel base = 0xfffff800`03804000 PsLoadedModuleList = 0xfffff800`03a48890
Debug session time: Tue Feb 17 20:13:28.762 2015 (GMT+1)
System Uptime: 0 days 2:39:51.605
Loading Kernel Symbols
..........................................................................................................................................................................
Loading unloaded module list
......
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {5, 0, 1202, fffffa800953d110}
Probably caused by : Wdf01000.sys ( Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a )
Followup: MachineOwner
---------
4: kd> g
^ No runnable debuggees error in 'g'
4: kd> .restart
Loading Dump File [C:\Windows\Minidump\021715-19734-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 Longhorn Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Kernel base = 0xfffff800`03804000 PsLoadedModuleList = 0xfffff800`03a48890
Debug session time: Tue Feb 17 20:13:28.762 2015 (GMT+1)
System Uptime: 0 days 2:39:51.605
Loading Kernel Symbols
..........................................................................................................................................................................
Loading unloaded module list
......
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {5, 0, 1202, fffffa800953d110}
Probably caused by : Wdf01000.sys ( Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
DESCRIPTION
The Windows Driver Framework has detected that a violation has occurred This resulted
in a condition where the machine would hang forever. By crashing, the Windows Driver
Framework is attempting to get enough information into the minidump such that somebody
can pinpoint the machine crash's cause, which is inside this driver.
Arguments:
Arg1: 0000000000000005, Device object of the failing device
Arg2: 0000000000000000, State that timed out
Arg3: 0000000000001202
Arg4: fffffa800953d110
Debugging Details:
------------------
OVERLAPPED_MODULE: HIDCLASS
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x10D
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88000d8ea46 to fffff80003878ec0
STACK_TEXT:
fffff880`0a8a5618 fffff880`00d8ea46 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : nt!KeBugCheckEx
fffff880`0a8a5620 00000000`00000000 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x8a
FOLLOWUP_IP:
Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
fffff880`00d8ea46 cc int 3
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51c51641
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0x10D_Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
BUCKET_ID: X64_0x10D_Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+8a
Followup: MachineOwner
---------
Das war in der Minidump Datei vom neusen Bluscreen
danke für jede Hilfe im voraus