Leandros
PCGH-Community-Veteran(in)
Bluescreens, Olé
Moin,
ich habe in letzter Zeit oft Bluescreens. Vllt könnt ihr mir helfen ...
1. Bluescreen: (Bild:
2. Bluescreen (IRQL_NOT_LESS_OR_EQUAL)
3. Bluescreen (Bild:
Meine Meinung, alles ein Treiber versagen, oder? AMD's Treiber für den Arsch?
Moin,
ich habe in letzter Zeit oft Bluescreens. Vllt könnt ihr mir helfen ...
1. Bluescreen: (Bild:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (124)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: fffffa8004b38028
Arg3: 00000000b44fa000
Arg4: 0000000000000135
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x124
CURRENT_IRQL: f
STACK_TEXT:
FOLLOWUP_IP:
nt!KeBugCheckEx+0
fffff800`02eced00 48894c2408 mov [rsp+0x8],rcx
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeBugCheckEx+0
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
BUCKET_ID: ZEROED_STACK
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
Code:
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
OVERLAPPED_MODULE: rspndr
EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x1E
CURRENT_IRQL: 2
STACK_TEXT:
FOLLOWUP_IP:
nt!KeBugCheck+0
fffff800`02ed5cd0 4883ec28 sub rsp,0x28
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeBugCheck+0
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
BUCKET_ID: ZEROED_STACK
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
Code:
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 0000000000000e20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002e93a6b, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to get MiSystemVaType - probably bad symbols
0000000000000e20
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiInsertTimerTable+bb
fffff800`02e93a6b 4c8d4320 lea r8,[rbx+0x20]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from fffff80002e872a9 to fffff80002e87d00
STACK_TEXT:
fffff880`0d27e748 fffff800`02e872a9 : 00000000`0000000a 00000000`00000e20 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d27e750 fffff800`02e85f20 : fffffa80`03b9aed0 ffffffff`ffffd8f0 00000000`00000000 fffffa80`04098120 : nt!KiBugCheckDispatch+0x69
fffff880`0d27e890 fffff800`02e93a6b : fffffa80`04cd7690 fffffa80`04cd74a0 00000000`11b0fd40 fffff880`00000034 : nt!KiPageFault+0x260
fffff880`0d27ea20 fffff800`02e8d0f2 : fffffa80`04098060 00000000`00000000 00000000`00000000 fffffa80`00000003 : nt!KiInsertTimerTable+0xbb
fffff880`0d27ea80 fffff800`02e8f7af : 00000000`0000099c 00000000`7eee8000 fffff880`00000061 00000000`0995f118 : nt!KiCommitThreadWait+0x332
fffff880`0d27eb10 fffff800`0317db2e : fffff880`0d27ec00 fffffa80`00000006 00000000`00000001 fffffa80`0543bc01 : nt!KeWaitForSingleObject+0x19f
fffff880`0d27ebb0 fffff800`02e86f93 : fffffa80`04098060 00000000`00000000 fffff880`0d27ebf8 fffffa80`03d98d60 : nt!NtWaitForSingleObject+0xde
fffff880`0d27ec20 00000000`746f2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0995f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x746f2e09
FOLLOWUP_IP:
nt!KiInsertTimerTable+bb
fffff800`02e93a6b 4c8d4320 lea r8,[rbx+0x20]
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiInsertTimerTable+bb
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+bb
BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+bb
Followup: MachineOwnerMeine Meinung, alles ein Treiber versagen, oder? AMD's Treiber für den Arsch?
.
