doctorultra
Experte
Thread Starter
- Mitglied seit
- 23.07.2017
- Beiträge
- 140
Mein PC ist übertaktet, liegt es vielleicht am Speicher?
Code:
Microsoft (R) Windows Debugger Version 10.0.17674.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\070718-7390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`a4a0c000 PsLoadedModuleList = 0xfffff803`a4dc61f0
Debug session time: Sat Jul 7 11:52:45.976 2018 (UTC + 2:00)
System Uptime: 0 days 14:45:51.721
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 139, {0, 0, 0, bb0cba10}
Probably caused by : ntkrnlmp.exe ( nt!guard_icall_bugcheck+1b )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff803`a4ba4330 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803`a705c8e0=0000000000000139
0: 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: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheck
Arg4: 00000000bb0cba10, Reserved
Debugging Details:
------------------
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: SKU
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 4011
BIOS_DATE: 04/19/2018
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: PRIME X370-PRO
BASEBOARD_VERSION: Rev X.0x
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: bb0cba10
TRAP_FRAME: 0000000000000000 -- (.trap 0x0)
EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000
CPU_COUNT: 10
CPU_MHZ: e6d
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 1
CPU_STEPPING: 1
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x139
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: PC-GROESER
ANALYSIS_SESSION_TIME: 07-07-2018 12:12:08.0868
ANALYSIS_VERSION: 10.0.17674.1000 amd64fre
LAST_CONTROL_TRANSFER: from fffff803a4bac90b to fffff803a4ba4330
STACK_TEXT:
fffff803`a705c8d8 fffff803`a4bac90b : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff803`a705c8e0 fffff803`a4aa5ff7 : ffffffff`ffffffff fffff803`a705ca10 00000000`0002625a 00000000`00000000 : nt!guard_icall_bugcheck+0x1b
fffff803`a705c910 fffff803`a4aa564b : 00000000`00000018 00000000`00000000 00000000`003707e6 00000000`00000019 : nt!KiExecuteAllDpcs+0x2e7
fffff803`a705ca50 fffff803`a4ba7a8a : 00000000`00000000 fffff803`a3532180 00000000`001a6560 fffff803`a4e83400 : nt!KiRetireDpcList+0x1db
fffff803`a705cc60 00000000`00000000 : fffff803`a705d000 fffff803`a7057000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
THREAD_SHA1_HASH_MOD_FUNC: 1768079eea2f1f670377627e597f76dcc286def9
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f8d2a0f9135e0b64acdc61708343d3fdbdea700d
THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
FOLLOWUP_IP:
nt!guard_icall_bugcheck+1b
fffff803`a4bac90b 90 nop
FAULT_INSTR_CODE: ccccc390
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!guard_icall_bugcheck+1b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5b1a4590
IMAGE_VERSION: 10.0.17134.112
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1b
FAILURE_BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck
BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck
PRIMARY_PROBLEM_CLASS: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck
TARGET_TIME: 2018-07-07T09:52:45.000Z
OSBUILD: 17134
OSSERVICEPACK: 112
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-06-08 11:00:00
BUILDDATESTAMP_STR: 180410-1804
BUILDLAB_STR: rs4_release
BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
ANALYSIS_SESSION_ELAPSED_TIME: 8b84
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_0_legacy_gs_violation_nt!guard_icall_bugcheck
FAILURE_ID_HASH: {9bee41a7-2ef9-07ca-7e59-7d5a0c6e2d05}
Followup: MachineOwner
---------