Die Minidumps sind erwatungsgemäß unergiebig, ein randalierdender Treiber ist nicht auszumachen.
>OC auf 5.00 GHz<
Hier könnte instabiler RAM oder instabiler MemoryController die Ursache sein, entsprechend die Spannung des RAM oder QPI/VTT vorsichtig anpassen.
Eventuell kann auch der Driver verifier etwas bringen, der "beobachtet" laufende Treiber, bei Fehlern gibts dann einen beabsichtigten Bugcheck (Bluescreen) mit dem "schuldigen" Treiber.
Driver Verifier - Windows drivers | Microsoft Docs
*******************************************************************************
*******************************************************************************
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\HELP\Blackwolf\021519-8453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff804`7c606000 PsLoadedModuleList = 0xfffff804`7ca21ad0
Debug session time: Fri Feb 15 19:04:44.765 2019 (UTC + 1:00)
System Uptime: 0 days 4:41:30.777
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {4588c122, ff, 0, fffff8047c7baabc}
Probably caused by : ntkrnlmp.exe ( nt!KiInterruptSubDispatch+1c )
Followup: MachineOwner
---------
11: 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: 000000004588c122, memory referenced
Arg2: 00000000000000ff, 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: fffff8047c7baabc, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 000000004588c122
CURRENT_IRQL: 0
FAULTING_IP:
nt!KiInterruptSubDispatch+1c
fffff804`7c7baabc 440f22c1 mov cr8,rcx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from fffff8047c7cac69 to fffff8047c7b9440
STACK_TEXT:
ffffd900`8b33bcb8 fffff804`7c7cac69 : 00000000`0000000a 00000000`4588c122 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffd900`8b33bcc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!KiInterruptSubDispatch+1c
fffff804`7c7baabc 440f22c1 mov cr8,rcx
SYMBOL_NAME: nt!KiInterruptSubDispatch+1c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0xA_nt!KiInterruptSubDispatch+1c
BUCKET_ID: X64_0xA_nt!KiInterruptSubDispatch+1c
Followup: MachineOwner
---------
11: kd> kb
RetAddr : Args to Child : Call Site
fffff804`7c7cac69 : 00000000`0000000a 00000000`4588c122 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
11: kd> kv
Child-SP RetAddr : Args to Child : Call Site
ffffd900`8b33bcb8 fffff804`7c7cac69 : 00000000`0000000a 00000000`4588c122 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffd900`8b33bcc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69