Hilfe bluscreen !!!

Dieses Thema Hilfe bluscreen !!! im Forum "Windows 7 Forum" wurde erstellt von Damy, 17. Feb. 2015.

Thema: Hilfe bluscreen !!! Hallo zusammen habe ein problem, habe immer wieder einen Bluscreen und komme nicht weiter ... Microsoft (R)...

  1. 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
     
  2. hp
    hp
    Ist die Kiste auf dem aktuellsten Stand was Treiber und Patche angeht? Sieht so aus , als ob einige Treiber aus dem WDF nicht aktuell wären ...
     
  3. ich habe mit einem Programm die Treiber aktualisieren lassen trotzdem bekomme ich einen Bluscreen allerdings hat sich da im Bericht was geändert


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


    Loading Dump File [C:\Windows\Minidump\022615-23368-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`03814000 PsLoadedModuleList = 0xfffff800`03a58890
    Debug session time: Thu Feb 26 22:13:44.949 2015 (GMT+1)
    System Uptime: 0 days 0:00:42.745
    Loading Kernel Symbols
    ...........................................................................................................................................................................
    Loading unloaded module list
    ......
    Loading User Symbols
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8008840028, be000000, 800400}

    Probably caused by : ntkrnlmp.exe ( nt!WheaReportHwError+263 )

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

    1: kd> g
    ^ No runnable debuggees error in 'g'
    1: kd> .restart

    Loading Dump File [C:\Windows\Minidump\022615-23368-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`03814000 PsLoadedModuleList = 0xfffff800`03a58890
    Debug session time: Thu Feb 26 22:13:44.949 2015 (GMT+1)
    System Uptime: 0 days 0:00:42.745
    Loading Kernel Symbols
    ...........................................................................................................................................................................
    Loading unloaded module list
    ......
    Loading User Symbols
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8008840028, be000000, 800400}

    Probably caused by : ntkrnlmp.exe ( nt!WheaReportHwError+263 )

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

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

    Unknown bugcheck code (124)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000000
    Arg2: fffffa8008840028
    Arg3: 00000000be000000
    Arg4: 0000000000800400

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


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x124

    CURRENT_IRQL: f

    LAST_CONTROL_TRANSFER: from fffff80003e0da3b to fffff80003888ec0

    STACK_TEXT:
    fffff880`009f2b58 fffff800`03e0da3b : 00000000`00000124 00000000`00000000 fffffa80`08840028 00000000`be000000 : nt!KeBugCheckEx
    fffff880`009f2b60 fffff800`039a0713 : 00000000`00000001 fffffa80`082168b0 00000000`00000000 fffffa80`08216900 : hal!HalBugCheckSystem+0x1e3
    fffff880`009f2ba0 fffff800`03e0d700 : 00000000`00000728 fffffa80`082168b0 fffff880`009f2f30 fffff880`009f2f00 : nt!WheaReportHwError+0x263
    fffff880`009f2c00 fffff800`03e0d052 : fffffa80`082168b0 fffff880`009f2f30 fffffa80`082168b0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`009f2d50 fffff800`03e0cf0d : 00000000`00000008 00000000`00000001 fffff880`009f2fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`009f2d90 fffff800`03e00e88 : 00000000`02b20000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`009f2dc0 fffff800`038877ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`009f2df0 fffff800`03887613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`009f2f30 00000000`77653d45 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0033e3c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77653d45


    FOLLOWUP_IP:
    nt!WheaReportHwError+263
    fffff800`039a0713 e985000000 jmp nt!WheaReportHwError+0x2ed (fffff800039a079d)

    SYMBOL_STACK_INDEX: 2

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt!WheaReportHwError+263

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 54b5f6ff

    STACK_COMMAND: kb

    FAILURE_BUCKET_ID: X64_0x124_nt!WheaReportHwError+263

    BUCKET_ID: X64_0x124_nt!WheaReportHwError+263

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

    jetzt hatt er sogar beim Hochfahren einen Bluscreen bekommen
     
Die Seite wird geladen...

Hilfe bluscreen !!! - Ähnliche Themen

Forum Datum
BOOTMGR fehlt HILFE Windows 7 Forum 7. Nov. 2016
probleme mit windows 7 update bitte um hilfe. Windows 7 Forum 4. Nov. 2016
Windows 8.1 Neuinstallation auf neuer Festplatte nicht möglich. Hilfe! Windows 8 Forum 11. Okt. 2016
Bitte Hilfe :( Driver_Verifier_Detected_violation (excsd.sys) Windows 10 Forum 30. Aug. 2016
HILFE!!!!! mitten in win10 neu Installation hängengeblieben Windows 10 Forum 24. Juli 2016