Bluescreen driver irql not less or equal

CSharper

Software-Overclocker(in)
Abend

könnte mir jemand vielleicht diesen Bluescreen auswerten?hab ihn mit dem Bluescreenviewer ausgelesen,leider fand ich keine näheren Info's. Falls ich noch was an Info's "besorgen" soll bitte sagen.

Ich danke euch herzlich.

Edit: hab den angepinnten Thread gefunden, werd es morgen mal mit der im Thread beschriebenen Methode versuchen zu lösen.
 

Anhänge

  • BL.jpg
    BL.jpg
    1,5 MB · Aufrufe: 164
Zuletzt bearbeitet:
Ich habe den Fehlercode bei Google eingegeben und den ersten Link angeklickt.

Dieses Verhalten kann auftreten, wenn Sie eine Logitech-Maus verwenden und die Version von Logitech MouseWare-Programms, das auf dem Computer installiert ist, veraltet ist. Dieses Verhalten wird bezeichnet mit Logitech MouseWare der Version 9.10 und 9.24 auftreten.

Um dieses Verhalten zu beheben, entfernen Sie das Logitech MouseWare-Programm von Ihrem Computer, und aktualisieren Sie auf die neueste Version von Logitech MouseWare.

Ist das so schwer?
Oder hast du das bereits versucht?
 
Siehe Startpost habe ihn ergänzt, meine Logitech Maus hab ich seit 3 Wochen nicht mehr genutzt. Dachte nicht dass es so leicht ist oder wäre..
 
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`ace79000 PsLoadedModuleList = 0xfffff802`ad152850
Debug session time: Mon May 25 15:24:58.874 2015 (UTC + 2:00)
System Uptime: 0 days 0:08:14.509
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffffd001cc96a250, ffffd001cc96a1a8, 0}

Probably caused by : USBXHCI.SYS ( USBXHCI!Isoch_Transfer_CompleteCancelable+a6 )

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

1: kd> analyze -v
Couldn't resolve error at 'nalyze -v'
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd001cc96a250, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd001cc96a1a8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


TRAP_FRAME: ffffd001cc96a250 -- (.trap 0xffffd001cc96a250)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe000baeeea78 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe000baee1438 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80159c1a96e rsp=ffffd001cc96a3e8 rbp=ffffd001cc96a4a0
r8=ffffe00107b0e278 r9=0000000000000000 r10=ffffd001cc940fa0
r11=ffffe0010bdcf430 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
Wdf01000!FxIrpQueue::RemoveIrpFromListEntry+0x32:
fffff801`59c1a96e cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffd001cc96a1a8 -- (.exr 0xffffd001cc96a1a8)
ExceptionAddress: fffff80159c1a96e (Wdf01000!FxIrpQueue::RemoveIrpFromListEntry+0x0000000000000032)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000409 - Das System hat in dieser Anwendung den berlauf eines stapelbasierten Puffers ermittelt. Dieser berlauf k nnte einem b sartigen Benutzer erm glichen, die Steuerung der Anwendung zu bernehmen.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Das System hat in dieser Anwendung den berlauf eines stapelbasierten Puffers ermittelt. Dieser berlauf k nnte einem b sartigen Benutzer erm glichen, die Steuerung der Anwendung zu bernehmen.

EXCEPTION_PARAMETER1: 0000000000000003

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFFD001CC971FB0

LAST_CONTROL_TRANSFER: from fffff802acfd57e9 to fffff802acfc9ca0

STACK_TEXT:
ffffd001`cc969f28 fffff802`acfd57e9 : 00000000`00000139 00000000`00000003 ffffd001`cc96a250 ffffd001`cc96a1a8 : nt!KeBugCheckEx
ffffd001`cc969f30 fffff802`acfd5b10 : 00000000`00000000 00000000`00000006 ffffe000`bb149001 fffff802`ace0f58f : nt!KiBugCheckDispatch+0x69
ffffd001`cc96a070 fffff802`acfd4d34 : 00000000`00000000 fffff801`5c9e63b8 00000000`00000001 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd001`cc96a250 fffff801`59c1a96e : fffff801`59c1be32 ffffe001`07b0e190 00000000`00000002 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd001`cc96a3e8 fffff801`59c1be32 : ffffe001`07b0e190 00000000`00000002 00000000`00000000 ffffe000`ba7b6710 : Wdf01000!FxIrpQueue::RemoveIrpFromListEntry+0x32
ffffd001`cc96a3f0 fffff801`59c1be89 : ffffe000`be1b4c60 ffffe000`baeee9d0 ffffe000`ba7b6700 ffffd001`cc96a4e0 : Wdf01000!FxIrpQueue::RemoveIrpFromQueueByContext+0x56
ffffd001`cc96a420 fffff801`59c1aa56 : ffffe001`0bdcf520 ffffe000`be1b4c60 ffffe000`ba7b6700 00000000`000004c0 : Wdf01000!FxRequest::RemoveFromIrpQueue+0x25
ffffd001`cc96a460 fffff801`59c1bf4e : 00000000`00000002 ffffe000`be1b4c60 ffffe000`ba7b6710 00001fff`41e4b398 : Wdf01000!FxIoQueue::RequestCancelable+0xde
ffffd001`cc96a4c0 fffff801`5c94dbaa : ffffe000`be1b4e00 00000000`00000000 ffffe000`be1b4c60 ffffe000`b7b163c0 : Wdf01000!imp_WdfRequestUnmarkCancelable+0x76
ffffd001`cc96a520 fffff801`5c94e2ba : ffffe001`07b0e570 00000000`000000b0 ffffe000`be1b4e80 ffffe000`be1b4e00 : USBXHCI!Isoch_Transfer_CompleteCancelable+0xa6
ffffd001`cc96a580 fffff801`5c94e606 : ffffe000`be1b4e00 00000000`00000000 ffffe001`07b0e570 00000000`00000003 : USBXHCI!Isoch_Stage_CompleteTD+0x16e
ffffd001`cc96a600 fffff801`5c940c4e : ffffe000`b7b18700 ffffe001`07b0a050 ffffd001`cc96a7f9 ffffd001`cc940180 : USBXHCI!Isoch_ProcessTransferEventWithED1+0x252
ffffd001`cc96a690 fffff801`5c959567 : 00000000`00000004 ffffd001`cc96a7d0 ffffd001`cc96a7f9 ffffd001`cc96a7b0 : USBXHCI!Endpoint_TransferEventHandler+0x4e
ffffd001`cc96a700 fffff801`5c943042 : 00000000`00000000 ffffe000`b7b062b0 ffffe000`b99feff8 00001f80`00f40070 : USBXHCI!UsbDevice_TransferEventHandler+0x87
ffffd001`cc96a760 fffff801`59c99c81 : ffffd001`00000000 00000000`00000f44 00001fff`466012c8 00000000`00400a02 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x456
ffffd001`cc96a860 fffff802`acf1fc00 : ffffd001`cc942f00 ffffd001`cc96ab20 ffffe000`b99fed30 ffffd001`cc96aa20 : Wdf01000!FxInterrupt::DpcHandler+0xc1
ffffd001`cc96a890 fffff802`acf1eeb7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x1b0
ffffd001`cc96a9e0 fffff802`acfcd7ea : ffffd001`cc940180 ffffd001`cc940180 ffffd001`cc94c3c0 ffffe000`b7571480 : nt!KiRetireDpcList+0xd7
ffffd001`cc96ac60 00000000`00000000 : ffffd001`cc96b000 ffffd001`cc965000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
USBXHCI!Isoch_Transfer_CompleteCancelable+a6
fffff801`5c94dbaa 85c0 test eax,eax

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: USBXHCI!Isoch_Transfer_CompleteCancelable+a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 54337388

IMAGE_VERSION: 6.3.9600.17393

BUCKET_ID_FUNC_OFFSET: a6

FAILURE_BUCKET_ID: 0x139_3_USBXHCI!Isoch_Transfer_CompleteCancelable

BUCKET_ID: 0x139_3_USBXHCI!Isoch_Transfer_CompleteCancelable

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_3_usbxhci!isoch_transfer_completecancelable

FAILURE_ID_HASH: {c0cf8491-cc50-a95f-bce2-0e1e5cab98ce}

Followup: MachineOwner
---------
So hab ihn mit dem Debugger Tool ausgelesen.







Mal Driver Verifier drüber laufen lassen, wieder Bluescreen mit dieser Dump Datei Auswertung.

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


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff800`8648a000 PsLoadedModuleList = 0xfffff800`86763850
Debug session time: Tue May 26 20:47:19.439 2015 (UTC + 2:00)
System Uptime: 0 days 0:00:05.118
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {21f, fffff80086b1f934, ffffcf80556f6dc0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ViGenericDriverEntry+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000021f, A driver has not filled out a dispatch routine for a required IRP major function.
Arg2: fffff80086b1f934, The address in the driver's code where the error was detected.
Arg3: ffffcf80556f6dc0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR: 0xc9_21f

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 21f

FAULTING_IP:
nt!ViGenericDriverEntry+0
fffff800`86b1f934 4883ec38 sub rsp,38h

FOLLOWUP_IP:
nt!ViGenericDriverEntry+0
fffff800`86b1f934 4883ec38 sub rsp,38h

IRP_ADDRESS: ffffcf80556f6dc0

DEVICE_OBJECT: ffffe0008924d3b0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LOCK_ADDRESS: fffff8008676e220 -- (!locks fffff8008676e220)

Resource @ nt!PiEngineLock (0xfffff8008676e220) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff8008676e220
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff80086b0f6b0 to fffff800865daca0

STACK_TEXT:
ffffd001`af9a91a8 fffff800`86b0f6b0 : 00000000`000000c9 00000000`0000021f fffff800`86b1f934 ffffcf80`556f6dc0 : nt!KeBugCheckEx
ffffd001`af9a91b0 fffff800`86b12171 : fffff800`86b02470 fffff800`86b1f934 ffffcf80`556f6dc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd001`af9a91f0 fffff800`86b1b72e : ffffcf80`556f6dc0 00000000`0000021f fffff800`86b1f934 00000000`00000000 : nt!ViErrorFinishReport+0x10d
ffffd001`af9a9250 fffff800`86b11c6b : ffffd001`af9a9358 ffffe000`8924d3b0 ffffe000`86ff0788 ffffe000`8924d670 : nt!VfWmiVerifyIrpStackDownward+0xfe
ffffd001`af9a92f0 fffff800`86b087dd : ffffe000`8924d670 ffffd001`af9a9450 ffffcf80`556f6dc0 ffffe000`86ff0788 : nt!VfMajorVerifyIrpStackDownward+0x83
ffffd001`af9a9350 fffff800`86b0ed59 : ffffcf80`556f6dc0 00000000`00000000 ffffe000`8924d670 ffffe000`87a60800 : nt!IovpCallDriver1+0x5e5
ffffd001`af9a94a0 fffff800`86b0388c : ffffcf80`556f6dc0 00000000`00000002 00000000`00000000 00000000`00000000 : nt!VfBeforeCallDriver+0x165
ffffd001`af9a94d0 fffff800`86b1fec9 : ffffcf80`556f6dc0 ffffe000`8924d3b0 00000000`00000002 ffffe000`87a60800 : nt!IovCallDriver+0x348
ffffd001`af9a9520 fffff800`86b03911 : ffffe000`8924d500 ffffcf80`556f6dc0 00000000`00000000 fffff800`86b0f471 : nt!ViFilterDispatchGeneric+0xd1
ffffd001`af9a9560 fffff800`86b0f3d6 : ffffcf80`556f6dc0 ffffe000`8924d3b0 00000000`00000000 ffffe000`879f6190 : nt!IovCallDriver+0x3cd
ffffd001`af9a95b0 fffff800`86b1b626 : ffffe000`84f6b060 ffffd001`af9a9769 00000000`00000001 ffffe000`84f6b060 : nt!VfIrpSendSynchronousIrp+0x11e
ffffd001`af9a9620 fffff800`86b11b56 : 00000000`00000000 ffffd001`af9a9769 00000000`00000001 ffffe000`84f6b060 : nt!VfWmiTestStartedPdoStack+0x5a
ffffd001`af9a96c0 fffff800`868faea8 : 00000000`00000000 ffffd001`af9a9769 00000000`00000001 ffffd001`af9a9769 : nt!VfMajorTestStartedPdoStack+0x56
ffffd001`af9a96f0 fffff800`86878e53 : ffffe000`84f6bd30 ffffd001`00000001 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase3+0xb8
ffffd001`af9a97d0 fffff800`869a2d9f : 00000000`00000000 00000000`00000001 00000000`00000000 fffff800`8687dbd6 : nt!PipProcessDevNodeTree+0x377
ffffd001`af9a9a50 fffff800`86566ba8 : 00000001`00000003 00000000`00000000 ffffe000`84e44040 ffffe000`84e44180 : nt!PiProcessStartSystemDevices+0x87
ffffd001`af9a9aa0 fffff800`865376bc : fffff800`865667ec fffff800`8676cc40 ffffe000`84e44040 00000000`00000000 : nt!PnpDeviceActionWorker+0x3bc
ffffd001`af9a9b50 fffff800`8658a36c : 00000000`00000000 ffffe000`84e44040 00000000`00000080 ffffe000`84e44040 : nt!ExpWorkerThread+0x28c
ffffd001`af9a9c00 fffff800`865e12c6 : ffffd001`b55d1180 ffffe000`84e44040 ffffd001`b55dd3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd001`af9a9c60 00000000`00000000 : ffffd001`af9aa000 ffffd001`af9a4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

SYMBOL_NAME: nt!ViGenericDriverEntry+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6

IMAGE_VERSION: 6.3.9600.17736

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0xc9_21f_VRF_nt!ViGenericDriverEntry

BUCKET_ID: 0xc9_21f_VRF_nt!ViGenericDriverEntry

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc9_21f_vrf_nt!vigenericdriverentry

FAILURE_ID_HASH: {604d8ad3-8bdc-afd2-7008-966616cba61a}

Followup: MachineOwner
---------
 
Zuletzt bearbeitet:
Lade bitte mal die Dumps hier hoch.

Sieht so aus als ob du ein Problem mit einem USB3 Port hast. Was für Geräte hängen an den USB3 Ports?
-> Testweise die USB2 Ports nutzen.

Driver Verifier (für den Test über die USB 2 Ports) wieder deaktivieren.
 
Danke für deine Hilfe. Ich hab wahrscheinlich beim entmisten des Rechners eine Datei gelöscht die mit den Usb Ports etwas am Hut hatte. Hab Windows repariert ,der Rechner lief heute sauber den ganzen Tag:) Ausser einmal hat mir Asus Sorge Protection den Pc neugestartet. Passiert mir in Tw3 öfters.
 
Kein Ding ;)
Freut mich, dass du das Problem lösen konntest.

Jaja, die Sorge Protecten. Ist ziemlich empfindlich dieses Feature.
 
Zurück