Hallo
Den Rest habe ich auch analysiert
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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8003f8193f3, address which referenced memory
SYMBOL_NAME: rtp_filter+4f457
MODULE_NAME: rtp_filter
IMAGE_NAME: rtp_filter.sys
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
the pagefile offset. Parameter 3 contains the page CRC value.
Parameter 4 contains the expected CRC value.
Arg2: 0000000000050d9b
Arg3: 0000000000050d9b
Arg4: 000000000005109b
SYMBOL_NAME: PAGE_HASH_ERRORS_INPAGE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffff968175315360, Physical Device Object of the stack
Arg3: fffff80127a93850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff96818b2979e0, The blocked IRP
STACK_COMMAND: .process /r /p 0xffff96817387e040; .thread 0xffff968173894040 ; kb
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_DXG_POWER_IRP_TIMEOUT_IMAGE_amdkmdag.sys
Liebe grüße UWE