Hallo Zusammen,
habe heute zwei Bluescreen hintereinander bei verschiedenen Anwendungen gehabt und würde gerne wissen woran dies liegt. Hoffe mir kann hier geholfen werden.
Anbei die beiden beschreibungen.
Vielen Dank im voraus!
Teil 1:
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800033163a2, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003517100
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`033163a2 48890a mov qword ptr [rdx],rcx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9900 -- (.trap 0xfffff880009a9900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880009a9b20
rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033163a2 rsp=fffff880009a9a90 rbp=fffff880009a9b00
r8=0000000000000000 r9=0000000000000000 r10=fffffa8003c00278
r11=fffff8000351a4c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`033163a2 48890a mov qword ptr [rdx],rcx ds:01ca:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032e41e9 to fffff800032e4c40
STACK_TEXT:
fffff880`009a97b8 fffff800`032e41e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a97c0 fffff800`032e2e60 : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`035612d0 : nt!KiBugCheckDispatch+0x69
fffff880`009a9900 fffff800`033163a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9a90 fffff800`032f526d : fffffa80`035612d0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x12
fffff880`009a9ac0 fffff800`032acd6e : fffffa80`035612d0 00000000`0011cb0f 00000000`00000002 00000000`000000af : nt!MiInsertPageInFreeOrZeroedList+0x55d
fffff880`009a9bd0 fffff800`0357ffee : fffffa80`03cd0b60 00000000`00000080 fffffa80`03cd0040 fffff800`032d65d9 : nt!MmZeroPageThread+0x8f5
fffff880`009a9d00 fffff800`032d65e6 : fffff800`0345ae80 fffffa80`03cd0b60 fffff800`03468cc0 78450079`00007473 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9970 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`033163a2 48890a mov qword ptr [rdx],rcx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
Followup: MachineOwner
---------
Teil 2:
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8007bba1c0, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the objects reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x18
PROCESS_NAME: iw5mp.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003223944 to fffff80003282c40
STACK_TEXT:
fffff880`05bc8b08 fffff800`03223944 : 00000000`00000018 00000000`00000000 fffffa80`07bba1c0 00000000`00000002 : nt!KeBugCheckEx
fffff880`05bc8b10 fffff800`03579468 : fffff880`05bc8c60 fffffa80`07bba1c0 fffff880`05bc8bb8 fffff800`0327e800 : nt! ?? ::FNODOBFM::`string'+0x49d71
fffff880`05bc8b70 fffff800`03281ed3 : fffffa80`03f4db60 00000000`000005f0 fffff880`05bc8bb8 fffffa80`07aba1c0 : nt!NtWaitForSingleObject+0xf8
fffff880`05bc8be0 00000000`755b2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0ff7f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x755b2e09
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+49d71
fffff800`03223944 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+49d71
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+49d71
BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+49d71
Followup: MachineOwner
---------
