Bluescreen Win 7

[Thomas-Penner]

Hallo,

Ich verzweifle schon langsam, ich bekomme seit ca 1 Woche ab und zu einen bluescreen
Ich weiss aber nicht warum, es hat bis dahin auch immer alles funktioniert, mindestens ein Jahr lang.

hier die genaue bezeichnung, vielleicht kann mir von euch jemand helfen:

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7600.2.0.0.256.1
Gebietsschema-ID: 3079

Zusatzinformationen zum Problem:
BCCode: d1
BCP1: 0000000000002A18
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF88005D627CF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


Hoffe auf eure Hilfe, Vielen Dank
Mfg

 

[simpel1970]

Mache bitte ein Auswertung der Minidump (Crashdump), die zum Bluescreen geschrieben wurde. Dies kann für die weiter Fehlersuche sehr hilfreich sein (da Ursache für die Fehlermeldung i.d.R. ein fehlerhafter Gerätetreiber ist). Eine Anleitung dazu findest du in meiner Signatur. Falls du Probleme damit haben solltest, packe die Minidump in eine Zip oder RAR-Datei und lade sie ins Forum hoch.

Des weiteren mache bitte noch ein paar Screenshots von CPU-Z (Reiter Mainboard, CPU, Memory und SPD), damit wir etwas mehr über dein System erfahren.

 

[Sir @ndy]

na dann schreib noch den rest dazu nicht alle haben ne glaskugel :-)

dein system 32 oder 64 bit
deine hardware

wann passiert es ?
bei spielen oder im 2d betrieb usw...

 

[schmu1982]

eventuell ein ram baustein defekt geowrden? überprüf mal deinen ram mittels memtes86+: https://www.computerbase.de/downloads/systemtools/memtest86-plus/

 

[Kenshin]

Hi,

MSDN sagt zu diesem Fehler "A hardware device, its driver, or related software might have caused this error."

0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

http://msdn.microsoft.com/en-us/library/ff560244(v=VS.85).aspx

Und genau das ist auch meine Erfahrung. Hatte den Bluescreen schon bei allen möglichen Hardware Problemen, aber auch Software kann daran Schuld sein.

Mehr Infos sind also notwendig, z.B.

Hast du schon Fehlersuche betrieben bzw. schon was geändert?
Seit wann tritt der Fehler auf, erst seit nem Treiberupdate oder sowas?
Wie lange dauert es bis das Problem auftritt?
Treten sonst irgendwelche Probleme in anderen Programmen auf?
...
Sonst noch irgendwelche Auffälligkeiten?

Wie gesagt der Fehler ist nicht besonders eindeutig, ich würd auf jeden Fall mal Temperatur checken evtl. auch mal die Spannungen des Netzteils bzw. SMART Werte der HDD abfrage. Vieleicht auch nen Ram Check.
Ansonsten einfach mal nen Linux über nen USB Stick starten oder auf noch freier Partition Windows Draufklatschen und halt schauen obs da Auffäligkeiten gibt.

Gruß
Kenshin

 

[Thomas-Penner]

Ok, ich hab jetzt das mit dem Minidump gemacht, da steht aber ziemlich viel

Hier die Liste:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Wed Sep 15 00:43:49.200 2010 (GMT+2)
System Uptime: 0 days 5:17:22.511
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {2a18, 2, 1, fffff88005d627cf}

*** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000002a18, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005d627cf, address which referenced memory

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


WRITE_ADDRESS: 0000000000002a18

CURRENT_IRQL: 2

FAULTING_IP:
WUSB54Gv4x64+2d7cf
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002f1b5c0 -- (.trap 0xfffff88002f1b5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002a00 rbx=fffff88002f1b800 rcx=fffffa8008825ff0
rdx=0000000000000002 rsi=fffffa80089e5a20 rdi=fffffa80089ecb90
rip=fffff88005d627cf rsp=fffff88002f1b750 rbp=0000000000000000
r8=fffffa800876d300 r9=0000000000000000 r10=fffffa8006a634e0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1 ds:cda0:2a18=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c84b69 to fffff80002c85600

STACK_TEXT:
fffff880`02f1b478 fffff800`02c84b69 : 00000000`0000000a 00000000`00002a18 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b480 fffff800`02c837e0 : fffffa80`0a02eb60 fffffa80`0880dc40 fffff880`02f1b608 fffff800`02c90ab7 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b5c0 fffff880`05d627cf : fffffa80`08826000 fffff880`02f1b800 fffffa80`06a634e0 fffffa80`0880dc40 : nt!KiPageFault+0x260
fffff880`02f1b750 fffff880`05d62a1a : fffffa80`08812000 fffffa80`089ecda0 00000000`00000000 fffffa80`07f74ee0 : WUSB54Gv4x64+0x2d7cf
fffff880`02f1b7a0 fffff880`05d6296a : fffffa80`08812000 fffffa80`086f1840 fffffa80`00000000 00000000`00000000 : WUSB54Gv4x64+0x2da1a
fffff880`02f1b7d0 fffff880`00e3922b : 0000057f`f77f23b8 0000057f`f807f1b8 fffffa80`0876d318 fffffa80`086f1840 : WUSB54Gv4x64+0x2d96a
fffff880`02f1b850 fffff880`00e0fc9b : fffffa80`07f80e40 fffffa80`07f80e40 fffffa80`07f80e50 fffffa80`07f42001 : Wdf01000!FxRequestBase::CompleteSubmitted+0x177
fffff880`02f1b8d0 fffff880`00e0fdc4 : fffffa80`080f3a02 fffff880`042a40d8 00000000`00000000 fffffa80`00000009 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`02f1b940 fffff800`02c6ffd5 : fffffa80`07fddc50 fffff880`042a4d70 fffffa80`07fdddc0 fffff880`042a40d8 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`02f1b970 fffff800`02c87c26 : fffffa80`0880dbdb 00000000`00000000 00000000`00000000 fffffa80`0880da30 : nt!IopUnloadSafeCompletion+0x55
fffff880`02f1b9a0 fffff880`0428a5d9 : fffffa80`080f3050 fffffa80`0876d300 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f1ba80 fffff880`0428aab7 : fffffa80`0a798002 fffffa80`0880da30 00000000`ffffffff fffffa80`080f3ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f1bb60 fffff880`0428864f : fffffa80`080f3ea8 fffffa80`080f31a0 fffffa80`080f4040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f1bbc0 fffff880`04279f89 : fffffa80`080f3050 00000000`00000000 fffffa80`0804a702 fffffa80`080f3ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f1bc00 fffff880`00ef64ce : fffffa80`0804a000 fffffa80`080f3ea8 fffffa80`0804a750 fffffa80`080f3ec0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bc30 fffffa80`0804b12d : fffffa80`080f3ec0 fffff880`04279db0 00000000`00000001 fffff880`009e9180 : sptd+0x424ce
fffff880`02f1bca0 fffffa80`080f3ec0 : fffff880`04279db0 00000000`00000001 fffff880`009e9180 fffff880`009e9180 : 0xfffffa80`0804b12d
fffff880`02f1bca8 fffff880`04279daf : 00000000`00000001 fffff880`009e9180 fffff880`009e9180 fffff800`02c90cdc : 0xfffffa80`080f3ec0
fffff880`02f1bcb0 00000000`00000001 : fffff880`009e9180 fffff880`009e9180 fffff800`02c90cdc fffffa80`080f3ec0 : USBPORT!USBPORT_Xdpc_End+0x26f
fffff880`02f1bcb8 fffff880`009e9180 : fffff880`009e9180 fffff800`02c90cdc fffffa80`080f3ec0 fffffa80`080f3ea8 : 0x1
fffff880`02f1bcc0 fffff880`009e9180 : fffff800`02c90cdc fffffa80`080f3ec0 fffffa80`080f3ea8 00000000`00000000 : 0xfffff880`009e9180
fffff880`02f1bcc8 fffff800`02c90cdc : fffffa80`080f3ec0 fffffa80`080f3ea8 00000000`00000000 00000000`00000000 : 0xfffff880`009e9180
fffff880`02f1bcd0 fffff800`02c8ddfa : fffff880`009e9180 fffff880`009f3fc0 00000000`00000000 fffffa80`0804b0f0 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
WUSB54Gv4x64+2d7cf
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: WUSB54Gv4x64+2d7cf

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: WUSB54Gv4x64

IMAGE_NAME: WUSB54Gv4x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45923fcb

FAILURE_BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000002a18, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005d627cf, address which referenced memory

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


WRITE_ADDRESS: 0000000000002a18

CURRENT_IRQL: 2

FAULTING_IP:
WUSB54Gv4x64+2d7cf
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002f1b5c0 -- (.trap 0xfffff88002f1b5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002a00 rbx=fffff88002f1b800 rcx=fffffa8008825ff0
rdx=0000000000000002 rsi=fffffa80089e5a20 rdi=fffffa80089ecb90
rip=fffff88005d627cf rsp=fffff88002f1b750 rbp=0000000000000000
r8=fffffa800876d300 r9=0000000000000000 r10=fffffa8006a634e0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1 ds:cda0:2a18=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c84b69 to fffff80002c85600

STACK_TEXT:
fffff880`02f1b478 fffff800`02c84b69 : 00000000`0000000a 00000000`00002a18 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b480 fffff800`02c837e0 : fffffa80`0a02eb60 fffffa80`0880dc40 fffff880`02f1b608 fffff800`02c90ab7 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b5c0 fffff880`05d627cf : fffffa80`08826000 fffff880`02f1b800 fffffa80`06a634e0 fffffa80`0880dc40 : nt!KiPageFault+0x260
fffff880`02f1b750 fffff880`05d62a1a : fffffa80`08812000 fffffa80`089ecda0 00000000`00000000 fffffa80`07f74ee0 : WUSB54Gv4x64+0x2d7cf
fffff880`02f1b7a0 fffff880`05d6296a : fffffa80`08812000 fffffa80`086f1840 fffffa80`00000000 00000000`00000000 : WUSB54Gv4x64+0x2da1a
fffff880`02f1b7d0 fffff880`00e3922b : 0000057f`f77f23b8 0000057f`f807f1b8 fffffa80`0876d318 fffffa80`086f1840 : WUSB54Gv4x64+0x2d96a
fffff880`02f1b850 fffff880`00e0fc9b : fffffa80`07f80e40 fffffa80`07f80e40 fffffa80`07f80e50 fffffa80`07f42001 : Wdf01000!FxRequestBase::CompleteSubmitted+0x177
fffff880`02f1b8d0 fffff880`00e0fdc4 : fffffa80`080f3a02 fffff880`042a40d8 00000000`00000000 fffffa80`00000009 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`02f1b940 fffff800`02c6ffd5 : fffffa80`07fddc50 fffff880`042a4d70 fffffa80`07fdddc0 fffff880`042a40d8 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`02f1b970 fffff800`02c87c26 : fffffa80`0880dbdb 00000000`00000000 00000000`00000000 fffffa80`0880da30 : nt!IopUnloadSafeCompletion+0x55
fffff880`02f1b9a0 fffff880`0428a5d9 : fffffa80`080f3050 fffffa80`0876d300 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f1ba80 fffff880`0428aab7 : fffffa80`0a798002 fffffa80`0880da30 00000000`ffffffff fffffa80`080f3ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f1bb60 fffff880`0428864f : fffffa80`080f3ea8 fffffa80`080f31a0 fffffa80`080f4040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f1bbc0 fffff880`04279f89 : fffffa80`080f3050 00000000`00000000 fffffa80`0804a702 fffffa80`080f3ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f1bc00 fffff880`00ef64ce : fffffa80`0804a000 fffffa80`080f3ea8 fffffa80`0804a750 fffffa80`080f3ec0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bc30 fffffa80`0804b12d : fffffa80`080f3ec0 fffff880`04279db0 00000000`00000001 fffff880`009e9180 : sptd+0x424ce
fffff880`02f1bca0 fffffa80`080f3ec0 : fffff880`04279db0 00000000`00000001 fffff880`009e9180 fffff880`009e9180 : 0xfffffa80`0804b12d
fffff880`02f1bca8 fffff880`04279daf : 00000000`00000001 fffff880`009e9180 fffff880`009e9180 fffff800`02c90cdc : 0xfffffa80`080f3ec0
fffff880`02f1bcb0 00000000`00000001 : fffff880`009e9180 fffff880`009e9180 fffff800`02c90cdc fffffa80`080f3ec0 : USBPORT!USBPORT_Xdpc_End+0x26f
fffff880`02f1bcb8 fffff880`009e9180 : fffff880`009e9180 fffff800`02c90cdc fffffa80`080f3ec0 fffffa80`080f3ea8 : 0x1
fffff880`02f1bcc0 fffff880`009e9180 : fffff800`02c90cdc fffffa80`080f3ec0 fffffa80`080f3ea8 00000000`00000000 : 0xfffff880`009e9180
fffff880`02f1bcc8 fffff800`02c90cdc : fffffa80`080f3ec0 fffffa80`080f3ea8 00000000`00000000 00000000`00000000 : 0xfffff880`009e9180
fffff880`02f1bcd0 fffff800`02c8ddfa : fffff880`009e9180 fffff880`009f3fc0 00000000`00000000 fffffa80`0804b0f0 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
WUSB54Gv4x64+2d7cf
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: WUSB54Gv4x64+2d7cf

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: WUSB54Gv4x64

IMAGE_NAME: WUSB54Gv4x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45923fcb

FAILURE_BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000002a18, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005d627cf, address which referenced memory

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


WRITE_ADDRESS: 0000000000002a18

CURRENT_IRQL: 2

FAULTING_IP:
WUSB54Gv4x64+2d7cf
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002f1b5c0 -- (.trap 0xfffff88002f1b5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002a00 rbx=fffff88002f1b800 rcx=fffffa8008825ff0
rdx=0000000000000002 rsi=fffffa80089e5a20 rdi=fffffa80089ecb90
rip=fffff88005d627cf rsp=fffff88002f1b750 rbp=0000000000000000
r8=fffffa800876d300 r9=0000000000000000 r10=fffffa8006a634e0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1 ds:cda0:2a18=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c84b69 to fffff80002c85600

STACK_TEXT:
fffff880`02f1b478 fffff800`02c84b69 : 00000000`0000000a 00000000`00002a18 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b480 fffff800`02c837e0 : fffffa80`0a02eb60 fffffa80`0880dc40 fffff880`02f1b608 fffff800`02c90ab7 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b5c0 fffff880`05d627cf : fffffa80`08826000 fffff880`02f1b800 fffffa80`06a634e0 fffffa80`0880dc40 : nt!KiPageFault+0x260
fffff880`02f1b750 fffff880`05d62a1a : fffffa80`08812000 fffffa80`089ecda0 00000000`00000000 fffffa80`07f74ee0 : WUSB54Gv4x64+0x2d7cf
fffff880`02f1b7a0 fffff880`05d6296a : fffffa80`08812000 fffffa80`086f1840 fffffa80`00000000 00000000`00000000 : WUSB54Gv4x64+0x2da1a
fffff880`02f1b7d0 fffff880`00e3922b : 0000057f`f77f23b8 0000057f`f807f1b8 fffffa80`0876d318 fffffa80`086f1840 : WUSB54Gv4x64+0x2d96a
fffff880`02f1b850 fffff880`00e0fc9b : fffffa80`07f80e40 fffffa80`07f80e40 fffffa80`07f80e50 fffffa80`07f42001 : Wdf01000!FxRequestBase::CompleteSubmitted+0x177
fffff880`02f1b8d0 fffff880`00e0fdc4 : fffffa80`080f3a02 fffff880`042a40d8 00000000`00000000 fffffa80`00000009 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`02f1b940 fffff800`02c6ffd5 : fffffa80`07fddc50 fffff880`042a4d70 fffffa80`07fdddc0 fffff880`042a40d8 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`02f1b970 fffff800`02c87c26 : fffffa80`0880dbdb 00000000`00000000 00000000`00000000 fffffa80`0880da30 : nt!IopUnloadSafeCompletion+0x55
fffff880`02f1b9a0 fffff880`0428a5d9 : fffffa80`080f3050 fffffa80`0876d300 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f1ba80 fffff880`0428aab7 : fffffa80`0a798002 fffffa80`0880da30 00000000`ffffffff fffffa80`080f3ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f1bb60 fffff880`0428864f : fffffa80`080f3ea8 fffffa80`080f31a0 fffffa80`080f4040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f1bbc0 fffff880`04279f89 : fffffa80`080f3050 00000000`00000000 fffffa80`0804a702 fffffa80`080f3ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f1bc00 fffff880`00ef64ce : fffffa80`0804a000 fffffa80`080f3ea8 fffffa80`0804a750 fffffa80`080f3ec0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bc30 fffffa80`0804b12d : fffffa80`080f3ec0 fffff880`04279db0 00000000`00000001 fffff880`009e9180 : sptd+0x424ce
fffff880`02f1bca0 fffffa80`080f3ec0 : fffff880`04279db0 00000000`00000001 fffff880`009e9180 fffff880`009e9180 : 0xfffffa80`0804b12d
fffff880`02f1bca8 fffff880`04279daf : 00000000`00000001 fffff880`009e9180 fffff880`009e9180 fffff800`02c90cdc : 0xfffffa80`080f3ec0
fffff880`02f1bcb0 00000000`00000001 : fffff880`009e9180 fffff880`009e9180 fffff800`02c90cdc fffffa80`080f3ec0 : USBPORT!USBPORT_Xdpc_End+0x26f
fffff880`02f1bcb8 fffff880`009e9180 : fffff880`009e9180 fffff800`02c90cdc fffffa80`080f3ec0 fffffa80`080f3ea8 : 0x1
fffff880`02f1bcc0 fffff880`009e9180 : fffff800`02c90cdc fffffa80`080f3ec0 fffffa80`080f3ea8 00000000`00000000 : 0xfffff880`009e9180
fffff880`02f1bcc8 fffff800`02c90cdc : fffffa80`080f3ec0 fffffa80`080f3ea8 00000000`00000000 00000000`00000000 : 0xfffff880`009e9180
fffff880`02f1bcd0 fffff800`02c8ddfa : fffff880`009e9180 fffff880`009f3fc0 00000000`00000000 fffffa80`0804b0f0 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
WUSB54Gv4x64+2d7cf
fffff880`05d627cf c6401801 mov byte ptr [rax+18h],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: WUSB54Gv4x64+2d7cf

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: WUSB54Gv4x64

IMAGE_NAME: WUSB54Gv4x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45923fcb

FAILURE_BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

BUCKET_ID: X64_0xD1_WUSB54Gv4x64+2d7cf

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

 

[trillian]

Das: WUSB54Gv4x64.sys scheint der Fehlerhafte Treiber, bzw. der Teiber für die fehlerhafte Hartware zu sein. Wenn man danach googelt scheint es öfters random BSODs damit zu geben. Du könntest dir ja mal die ersten (z.B. diesen) Lösungsvorschläge ansehen, ob das bei dir auch hilft .

 

[simpel1970]

Trilian hat ja schon alles wissenswerte geschrieben. Ursache an dem ausgewerteten Bluescreen war die Datei "WUSB54Gv4x64.sys" (IMAGE_NAME: WUSB54Gv4x64.sys). Diese gehört zum Treiber für den Linksys Wireless-G USB. Installiere dir den aktuellsten Treiber für das Gerät: http://homesupport.cisco.com/en-us/home?referrer=www.linksysbycisco.com.

Sofern es keine anderen Stopfehler bei den aufgetretenen Bluescreen gibt/gab, könnte dein Problem mit dem aktuellsten Treiber gelöst sein.

Es steht übrigens so viel in der Auswertung, da du 3x !analyze -v eingegeben hast. Zwei Passagen kannst du aus dem Text wieder löschen, dann wird es auch ein bischen übersichtlicher.

 

[Thomas-Penner]

Es steht übrigens so viel in der Auswertung, da du 3x !analyze -v eingegeben hast. Zwei Passagen kannst du aus dem Text wieder löschen, dann wird es auch ein bischen übersichtlicher.

Ok, Sorry, dass war mein fehler
Vielen Dank für die antworten, wie ich die Crash Dump Datei gelesen habe, habe ich auch sofort an das gedacht, aber mein Problem bis dahin war, dass ich nicht wusste wie man so eine Datei ausliest.

Vielen Dank

 

[simpel1970]

Ist ja nicht schlimm

Hast du einen aktuelleren Treiber schon testen können?

 

[Thomas-Penner]

Nein, für das Ding gibt es keinen aktuellen, es ist leider schon zu alt.

 

[simpel1970]

Der installierte ist also der Aktuellste? Das ist ärgerlich.