Windows 10: kmode_exception_not_handled netio.sys windows 10

Hallo Community,


ich Keep on getting blue screens with kmode_exception_not_handled netio.sys. I just bought a new pc and freshly installed Windows 10. They occur every 10-15 Minutes or so.


Used Memtest86 with 3 Passes (the whole night) with no result.


I used sfc /scannow with no result.


Driver verifier enabeld (with no Windows Drivers) keeps on crashing, this is the crash Dump.


Really dont know what to do.


Microsoft (R) Windows Debugger Version 10.0.17763.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\frank\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`1a8a6000 PsLoadedModuleList = 0xfffff801`1ac54150
Debug session time: Sat Dec 8 11:27:22.272 2018 (UTC + 1:00)
System Uptime: 0 days 0:00:12.081
Loading Kernel Symbols
...............................................................
..........Page 80409f not present in the dump file. Type ".hh dbgerr004" for details
........Page 804d50 not present in the dump file. Type ".hh dbgerr004" for details
..............................................
.................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {2000, fffff803177c2586, 0, 65447a52}

*** ERROR: Module load completed but symbols could not be loaded for RzDev_006c.sys
Probably caused by : RzDev_006c.sys ( RzDev_006c+2586 )

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

10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff803177c2586, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000065447a52, Pool Tag (if provided).

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: B450 I AORUS PRO WIFI

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F1

BIOS_DATE: 07/23/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: B450 I AORUS PRO WIFI-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff803177c2586

BUGCHECK_P3: 0

BUGCHECK_P4: 65447a52

BUGCHECK_STR: 0xc4_2000

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-TO698O7

ANALYSIS_SESSION_TIME: 12-08-2018 11:43:27.0616

ANALYSIS_VERSION: 10.0.17763.1 amd64fre

LOCK_ADDRESS: fffff8011ac6e3e0 -- (!locks fffff8011ac6e3e0)

Resource @ nt!PiEngineLock (0xfffff8011ac6e3e0) Exclusively owned
Contention Count = 1
NumberOfExclusiveWaiters = 1
Threads: ffffbf8bd81cf040-01<*>

Threads Waiting On Exclusive Access:
ffffbf8bd80c6700
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff8011ac6e3e0
Thread Count : 1
Thread address: 0xffffbf8bd81cf040
Thread wait : 0x305

LAST_CONTROL_TRANSFER: from fffff8011b0c4443 to fffff8011aa4f690

STACK_TEXT:
ffffd188`8f54ead8 fffff801`1b0c4443 : 00000000`000000c4 00000000`00002000 fffff803`177c2586 00000000`00000000 : nt!KeBugCheckEx
ffffd188`8f54eae0 fffff801`1ab511db : fffff801`1ac44184 00000000`00002000 fffff803`177c2586 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xdf
ffffd188`8f54eb20 fffff801`1b0bc3fc : 00000000`65447a52 fffff801`1ac44184 fffff803`177c2586 ffffd188`8f54ed20 : nt!VfReportIssueWithOptions+0x103
ffffd188`8f54eb70 fffff801`1ab4feb2 : ffffbf8b`da25aa60 00000000`00000001 00004074`25d9bb38 ffffbf8b`da25ce40 : nt!VfCheckPoolType+0x90
ffffd188`8f54ebb0 fffff803`12f61f0d : 00000000`00000000 00004074`25d9bb38 ffff42df`5efa66ac 00000000`00000011 : nt!VfCheckNxPoolType+0x12
ffffd188`8f54ebe0 fffff803`177c2586 : ffffbf8b`da2644c0 00000000`00000000 ffffd188`8f54ed40 00000000`00000001 : Wdf01000!imp_WdfDeviceAllocAndQueryProperty+0x29e8d [minkernel\wdf\framework\shared\core\fxdeviceapi.cpp @ 1169]
ffffd188`8f54ec40 fffff803`177c44b0 : ffffbf8b`da2644c0 ffffbf8b`da2647b0 ffffd188`8f54f0a0 00000000`00000000 : RzDev_006c+0x2586
ffffd188`8f54f020 fffff803`12f1e930 : 00004074`25da31b8 00000000`00000000 00004074`25d9bb38 ffffbf8b`da25ce40 : RzDev_006c+0x44b0
ffffd188`8f54f0b0 fffff803`12f21c96 : ffffbf8b`d96158d0 ffffbf8b`d803ffa0 ffffbf8b`d96158d0 ffffbf8b`da25acd0 : Wdf01000!FxDriver::AddDevice+0xac [minkernel\wdf\framework\shared\core\km\fxdriverkm.cpp @ 72]
ffffd188`8f54f4d0 fffff803`127f8524 : 00000000`00000000 ffffbf8b`da25acd0 ffffbf8b`d96158d0 fffff803`12f21c70 : Wdf01000!FxDriver::AddDevice+0x26 [minkernel\wdf\framework\shared\core\km\fxdriverkm.cpp @ 51]
ffffd188`8f54f500 fffff801`1b0d68d1 : fffff801`1b0d68a0 00000000`00000002 ffffbf8b`d803ffa0 ffffbf8b`d96158d0 : VerifierExt!xdv_AddDevice_wrapper+0x74
ffffd188`8f54f530 fffff801`1aab9715 : fffff801`1b0d68a0 00000000`00000000 00000000`00000000 fffff801`1ab9bd38 : nt!ViGenericAddDevice+0x31
ffffd188`8f54f570 fffff801`1aea5739 : 00000000`00000000 00000000`00000001 ffffbf8b`d9619590 ffffd188`8f54f738 : nt!PpvUtilCallAddDevice+0xb114d
ffffd188`8f54f5b0 fffff801`1ae77587 : 00000000`00000000 00000000`40000000 ffffd188`8f54f740 00000000`40000000 : nt!PnpCallAddDevice+0x59
ffffd188`8f54f640 fffff801`1ae767c9 : ffffbf8b`d9619590 ffffd188`8f54f8f0 ffffbf8b`d9619590 00000000`00000000 : nt!PipCallDriverAddDevice+0x813
ffffd188`8f54f7f0 fffff801`1ae7e2da : ffffbf8b`d897a640 fffff801`1a8dc7f7 ffffbf8b`d81cf040 ffffbf8b`d897a690 : nt!PipProcessDevNodeTree+0x1f1
ffffd188`8f54fa70 fffff801`1a9eff0b : ffffbf01`00000003 ffffbf8b`d5d38a40 ffffbf8b`d897a640 00000000`00000000 : nt!PiProcessReenumeration+0x82
ffffd188`8f54fac0 fffff801`1a8fce35 : ffffbf8b`d81cf040 ffffbf8b`d248a650 fffff801`1ac6cc80 ffffbf8b`d248a650 : nt!PnpDeviceActionWorker+0x1eb
ffffd188`8f54fb80 fffff801`1a9194f7 : ffffbf8b`d81cf040 00000000`00000080 ffffbf8b`d249e040 ffffbf8b`d81cf040 : nt!ExpWorkerThread+0xf5
ffffd188`8f54fc10 fffff801`1aa56b06 : ffffd281`61a45180 ffffbf8b`d81cf040 fffff801`1a9194b0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffd188`8f54fc60 00000000`00000000 : ffffd188`8f550000 ffffd188`8f54a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 113979dcaaa46318fb4b87db68eb02fc9dfa2a66

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 48deb17c0f0fccfe990d9ea74ec821d2a5ea2f40

THREAD_SHA1_HASH_MOD: 33a27f6c2f6315c55e771c521ac34b99e0466be8

FOLLOWUP_IP:
RzDev_006c+2586
fffff803`177c2586 85c0 test eax,eax

FAULT_INSTR_CODE: 880fc085

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: RzDev_006c+2586

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RzDev_006c

IMAGE_NAME: RzDev_006c.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5add4574

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2586

FAILURE_BUCKET_ID: 0xc4_2000_VRF_RzDev_006c!unknown_function

BUCKET_ID: 0xc4_2000_VRF_RzDev_006c!unknown_function

PRIMARY_PROBLEM_CLASS: 0xc4_2000_VRF_RzDev_006c!unknown_function

TARGET_TIME: 2018-12-08T10:27:22.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

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-11-01 07:56:19

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: d2f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc4_2000_vrf_rzdev_006c!unknown_function

FAILURE_ID_HASH: {3f8abeac-2ef6-7494-d01b-03d0fd756dfe}

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

:)

 

KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys)


Please run driver verifier again using the settings from the driver verifier tutorial in post KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys) - Windows 10 Forums

 

KMODE_EXCEPTION_NOT_HANDLED on igdkmd64.sys

My computer keeps giving me the blue screen of death and giving me error code

KMODE_EXCEPTION_NOT_HANDLED on igdkmd64.sys

How can this be fixed?

 

KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys)


Here's the BIOS values