Question IQRL BSOD & Other BSODs & Can't Find A Fix

[loagnbones]

->Occasionally nowadays I am running into BSODS most recently I'm dealing with IQRL which seem to be most common I don't think I can attach a dump file as I'm new to the forums and I don't think I can put one available without putting up a download link but if it helps I've copied and pasted the analysis from WinDbg below:
->I've tried sfc /scannow and it turned up nothing and memory stress testing by opening up tabs of chrome and games to bring up memory usuage to ~%90 and the system didn't crash. I also remember trying windows memory diagnostic tool and that turned up nothing and my drivers are fully updated using driver easy.
->As far as using my computer sometimes it just blue screens out of the blue and sometimes when I leave my computer on and idle and come back to a blue screen with the 0% collecting info and I have to manually restart.
->In terms of other BSOD's in the past that I don't have dump files for but I have taken a picture of the stop codes are these: KMODE_EXCEPTION_NOT_HANDLED, MEMORY_MANAGEMENT What Failed: partmgr.sys, SYSTEM_SERVICE_EXCEPTION
->Like 10 or so minutes ago I was looking at an analysis of a stop code: DRIVER_IRQL_NOT_LESS_OR_EQUAL What Failed: NETIO.SYS-> when my computer blue screened the analysis below.
->Any questions feel free and I'll try my best to answer.

|ANALYSIS|
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\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 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff8040c200000 PsLoadedModuleList = 0xfffff8040c643370
Debug session time: Sun Jun 30 21:33:56.913 2019 (UTC - 7:00)
System Uptime: 0 days 0:13:36.608
Loading Kernel Symbols
...............................................................
................................................................
.............Page 167acb not present in the dump file. Type ".hh dbgerr004" for details
.Page 110258 not present in the dump file. Type ".hh dbgerr004" for details
............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000c8cce5e018). Type ".hh dbgerr001" for details Loading unloaded module list ........... For analysis of this file, run !analyze -v 10: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* 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: 0000000000000010, memory referenced Arg2: 0000000000000002, 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: fffff8040c21994f, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202 SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd. SYSTEM_PRODUCT_NAME: MS-7B79 SYSTEM_SKU: To be filled by O.E.M. SYSTEM_VERSION: 2.0 BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: A.90 BIOS_DATE: 03/07/2019 BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd. BASEBOARD_PRODUCT: X470 GAMING PLUS (MS-7B79) BASEBOARD_VERSION: 2.0 DUMP_TYPE: 1 BUGCHECK_P1: 10 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8040c21994f READ_ADDRESS: 0000000000000010 CURRENT_IRQL: 2 FAULTING_IP: nt!MiInsertPageInFreeOrZeroedList+19f fffff8040c21994f 49034710 add rax,qword ptr [r15+10h]

CPU_COUNT: 10

CPU_MHZ: e74

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: chrome.exe

ANALYSIS_SESSION_HOST: DESKTOP-LD32LC6

ANALYSIS_SESSION_TIME: 06-30-2019 21:35:49.0015

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME: fffffd099b7cc890 -- (.trap 0xfffffd099b7cc890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000008
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8040c21994f rsp=fffffd099b7cca20 rbp=fffffd099b7cca99
r8=00000000000000aa r9=00000000000000aa r10=0000000000000000
r11=fffffd099b7ccaf8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr ac po nc
nt!MiInsertPageInFreeOrZeroedList+0x19f:
fffff8040c21994f 49034710 add rax,qword ptr [r15+10h] ds:0000000000000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8040c3ce569 to fffff8040c3bc8a0

STACK_TEXT:
fffffd099b7cc748 fffff8040c3ce569 : 000000000000000a 0000000000000010 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffffd099b7cc750 fffff8040c3ca8a5 : 0000000000000000 ffff9c0a486c3980 ffff4bd56a80355a 0000000000000000 : nt!KiBugCheckDispatch+0x69
fffffd099b7cc890 fffff8040c21994f : 0000000000000000 ffff890100000001 0000000000000000 fffff8040c2b8b95 : nt!KiPageFault+0x465
fffffd099b7cca20 fffff8040c215adf : 00000000001767aa 0200000000000000 0000000000000001 0000000000000000 : nt!MiInsertPageInFreeOrZeroedList+0x19f
fffffd099b7ccb00 fffff8040c2c3770 : fffffd099b7ccd90 ffff9c0a58fef080 0000000000000001 fffffd099b7cd7c0 : nt!MiDeletePteList+0x28f
fffffd099b7ccbe0 fffff8040c85863d : 0000000000000002 ffff9c0a58fef080 00000227539b3000 ffff9c0a52f20b00 : nt!MiDecommitPages+0x1510
fffffd099b7cd780 fffff8040c858b8b : 0000000000086000 0000000000000000 fffffd099b7cda60 ffffffffffffffff : nt!MiDecommitRegion+0xbd
fffffd099b7cd960 fffff8040c85887b : fffffd0900000002 fffffd099b7cda00 0000000000000000 ffffad83df7d8b40 : nt!MmFreeVirtualMemory+0x2db
fffffd099b7cdaa0 fffff8040c3cdf98 : ffff9c0a58fed080 000000c8cf1ff828 fffffd099b7cdb18 ffffffffec549980 : nt!NtFreeVirtualMemory+0x8b
fffffd099b7cdb00 00007ff93eb5c424 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000c8cf1feb68 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff93eb5c424 THREAD_SHA1_HASH_MOD_FUNC: d4a10c44704b334d3e5994fb33c7c64180e621a5 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ec6c10477ca6d7d4bc88138b303e5fb121cf3013 THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406 FOLLOWUP_IP: nt!MiInsertPageInFreeOrZeroedList+19f fffff8040c21994f 49034710 add rax,qword ptr [r15+10h]

FAULT_INSTR_CODE: 10470349

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiInsertPageInFreeOrZeroedList+19f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 19f

FAILURE_BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList

BUCKET_ID: AV_nt!MiInsertPageInFreeOrZeroedList

PRIMARY_PROBLEM_CLASS: AV_nt!MiInsertPageInFreeOrZeroedList

TARGET_TIME: 2019-07-01T04:33:56.000Z

OSBUILD: 18362

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: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 183d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!miinsertpageinfreeorzeroedlist

FAILURE_ID_HASH: {779c7427-9286-2607-95ab-7b33d42c5f3a}

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

 

[Colif]

can you do both steps in 1st post here (don't do 2nd post yet) - https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/

netio.sys is Windows Network Input output driver, its used for internet access, so I would look at your LAN drivers
Can't say I seen partmgr.sys before, though its part of windows.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

 

[loagnbones]

Sorry I was at work. Ok question does memtest86 have an option to test 1 stick at a time or should I uninstall one to test the other? I've also did the test with both sticks in at default settings and there were no errors.

 

[loagnbones]

I will also like to apologize for not having my specs listed here they are:
Ryzen 7 2700x
2x 8gb memory
GTX 1060
Air Cooler-Scythe Mugen Rev. B
3x Thermaltake Fan kit
Full ATX x470 MSI Gaming Plus
1x 1tb HDD At 7200rpm
1x 1tb SSD
EVGA 500B 500w Bronze+ Certified

 

[loagnbones]

Additionally I went ahead and made a share link up for download for my minidump file: https://www.dropbox.com/s/oyu1l793u69h2pg/Minidump.zip?dl=0

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pastebin.com/ecjx2Qjn

Spoiler

File information:	063019-9468-01.dmp (Jul 1 2019 - 00:33:56)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Uptime:	0 Day(s), 0 Hour(s), 13 Min(s), and 36 Sec(s)

File information:	070119-9812-01.dmp (Jul 1 2019 - 19:04:17)
Bugcheck:	BAD_POOL_HEADER (19)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 20 Sec(s)

File information:	062919-9593-01.dmp (Jun 29 2019 - 19:25:23)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Uptime:	0 Day(s), 0 Hour(s), 05 Min(s), and 44 Sec(s)

File information:	062919-9562-01.dmp (Jun 29 2019 - 19:27:45)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 33 Sec(s)

File information:	062519-9046-01.dmp (Jun 26 2019 - 01:12:43)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Uptime:	0 Day(s), 0 Hour(s), 29 Min(s), and 42 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/X470-GAMING-PLUS
There is a BIOS update available for your system (version A.A) You are using version A.9. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[loagnbones]

Hi, I ran the dump files through the debugger and got the following information: https://pastebin.com/ecjx2Qjn

Spoiler

File information:	063019-9468-01.dmp (Jul 1 2019 - 00:33:56)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Uptime:	0 Day(s), 0 Hour(s), 13 Min(s), and 36 Sec(s)

File information:	070119-9812-01.dmp (Jul 1 2019 - 19:04:17)
Bugcheck:	BAD_POOL_HEADER (19)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 20 Sec(s)

File information:	062919-9593-01.dmp (Jun 29 2019 - 19:25:23)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Uptime:	0 Day(s), 0 Hour(s), 05 Min(s), and 44 Sec(s)

File information:	062919-9562-01.dmp (Jun 29 2019 - 19:27:45)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 33 Sec(s)

File information:	062519-9046-01.dmp (Jun 26 2019 - 01:12:43)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Uptime:	0 Day(s), 0 Hour(s), 29 Min(s), and 42 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/X470-GAMING-PLUS
There is a BIOS update available for your system (version A.A) You are using version A.9. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

I can confirm this is the correct motherboard and have installed a bios update already in the past. Currently I'm testing 1 memory stick at a time on memtest86 and 1 ram stick already I can confirm turned up no errors. I'm almost finished with pass 2 out 4 with the other ram stick.

 

[loagnbones]

Update: Used memtest86 default settings including 4 passes on each memory stick separately and no errors were found.