Ich bekomme ständig Bluescreens mit unterschiedlichen Meldungen aber immer mit ntkrnlmp.exe

Hallo,


ich komme hier irgendwie nicht weiter. Seit 2 Wochen bekomme ich unregelmäßig Bluescreens. Den letzten poste ich mal:


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffff80000003, fffff80342571b08, 0, ffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KiFatalExceptionHandler+22 )

Followup: MachineOwner
---------

5: 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: ffffffff80000003, The exception code that was not handled
Arg2: fffff80342571b08, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000ffffffff, Parameter 1 of the exception

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z370 AORUS Gaming 7

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F4

BIOS_DATE: 10/30/2017

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z370 AORUS Gaming 7

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff80342571b08

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffff

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.

FAULTING_IP:
nt!memset+88
fffff803`42571b08 2bc1 sub eax,ecx

EXCEPTION_PARAMETER2: 00000000ffffffff

BUGCHECK_STR: 0x1E_80000003

CPU_COUNT: c

CPU_MHZ: e70

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 70'00000000 (cache) 70'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MATZE

ANALYSIS_SESSION_TIME: 01-11-2018 23:23:13.0544

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

EXCEPTION_RECORD: ffff88000766f370 -- (.exr 0xffff88000766f370)
ExceptionAddress: 0000547600000010
ExceptionCode: 4275dac0
ExceptionFlags: fffff803
NumberParameters: 6
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Parameter[2]: 0000000000000000
Parameter[3]: ffffbc05ba3f87b0
Parameter[4]: 0000000000000000
Parameter[5]: 0000000000000000

LAST_CONTROL_TRANSFER: from fffff803425fe24e to fffff803425650e0

STACK_TEXT:
ffff8800`0766e488 fffff803`425fe24e : 00000000`0000001e ffffffff`80000003 fffff803`42571b08 00000000`00000000 : nt!KeBugCheckEx
ffff8800`0766e490 fffff803`4256b88d : fffff803`427a1000 fffff803`42401000 00054c54`008d2000 ffff8800`0766eb00 : nt!KiFatalExceptionHandler+0x22
ffff8800`0766e4d0 fffff803`4241bd60 : 00000000`00000000 ffff8800`0766f3d8 ffff8800`00000003 fffff808`c25733c9 : nt!RtlpExecuteHandlerForException+0xd
ffff8800`0766e500 fffff803`4241c8e4 : ffff8800`0766f3d8 ffff8800`0766f120 ffff8800`0766f3d8 ffff8800`0766f3d8 : nt!RtlDispatchException+0x430
ffff8800`0766ebf0 fffff803`42570ace : ffff8800`0766f370 fffff803`42492968 00000000`05075fb8 00001f80`00000201 : nt!KiDispatchException+0x144
ffff8800`0766f2a0 fffff803`4256deaa : 00000000`00000000 00000000`00000fff 7f800000`7f800000 7f800000`7f800000 : nt!KiExceptionDispatch+0xce
ffff8800`0766f480 fffff803`42571b09 : fffff803`42451c0a 00000000`00000001 00000000`00000000 00000000`0037131f : nt!KiBreakpointTrap+0xea
ffff8800`0766f618 fffff803`42451c0a : 00000000`00000001 00000000`00000000 00000000`0037131f 00004a19`21e6181c : nt!memset+0x89
ffff8800`0766f620 fffff803`42451250 : 00000000`00000003 00000000`00000002 00000000`00000000 00000000`00000000 : nt!PpmIdleExecuteTransition+0x82a
ffff8800`0766fa00 fffff803`4256820c : ffffffff`00000000 ffff8b01`2c079180 ffff8b01`2c085dc0 ffffbc05`bd135700 : nt!PoIdle+0x340
ffff8800`0766fb60 00000000`00000000 : ffff8800`07670000 ffff8800`07669000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


THREAD_SHA1_HASH_MOD_FUNC: ce05a7c293c61d21f9c766dc27b141bb12fd5060

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 444be1fbf5ee905615c289bd80a476144b77c82c

THREAD_SHA1_HASH_MOD: b28610981796779b4ac02f58898fde25728a775c

FOLLOWUP_IP:
nt!KiFatalExceptionHandler+22
fffff803`425fe24e cc int 3

FAULT_INSTR_CODE: cccccccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiFatalExceptionHandler+22

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5a29b8d4

IMAGE_VERSION: 10.0.16299.125

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 22

FAILURE_BUCKET_ID: 0x1E_80000003_nt!KiFatalExceptionHandler

BUCKET_ID: 0x1E_80000003_nt!KiFatalExceptionHandler

PRIMARY_PROBLEM_CLASS: 0x1E_80000003_nt!KiFatalExceptionHandler

TARGET_TIME: 2018-01-11T21:11:04.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-12-07 22:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: 87c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_80000003_nt!kifatalexceptionhandler

FAILURE_ID_HASH: {607caa00-6792-b827-2de6-fa2add1f41dc}

Followup: MachineOwner

Da ich ein noob bin, kann ich nix damit anfangen, auch nach mittlerweile locker 5 Stunden Recherche. Angeblich soll das ein Treiberproblem sein. Meine Treiber sind aber aktuell. Ich bitte um Hilfe!


MFG Mathias

Weiterlesen...