Random BSODs, last one -- IRQL_NOT_LESS_OR_EQUAL

sevenfourk · Oct 7, 2017

I've built a PC this September. And was getting random BSODs staring that time. Till that time I've reinstalled my Windows a couple of times. Nothing changed. I'm getting these BSODs from time to time.

I currently use my PC only for gaming or random browsing, leisure stuff, not mission critical. But it really started to bug me.

I was able to analyze last dump with windbg, but I could only guess what could go wrong. If anyone are more proficient in this, that would very cool, to help me out here.

my pc parts:

CPU: Intel - Core i7-7700 3.6GHz Quad-Core Processor
CPU Cooler: Noctua - NH-U14S 55.0 CFM CPU Cooler
Motherboard: Asus - STRIX B250I GAMING Mini ITX LGA1151 Motherboard
Memory: G.Skill - NT Series 16GB (2 x 8GB) DDR4-2400 Memory
Storage: Western Digital - Blue 500GB M.2-2280 Solid State Drive
Storage: Western Digital - Black 512GB M.2-2280 Solid State Drive
Video Card: MSI - GeForce GTX 1080 8GB GAMING X 8G Video Card
Case: Fractal Design - Node 304 Mini ITX Tower Case
Power Supply: SeaSonic - FOCUS Plus Gold 550W 80+ Gold Certified Fully-Modular ATX Power Supply
Mouse: Logitech - MX Master Bluetooth Wireless Laser Mouse

My OS: Windows 10 LTSB

Previously I installed all drivers from ASUS site, and I think it messed up my bluetooth driver, and I was getting BSODs back then every time I want to restart or just power off my computer.

So this time I just didn't install any of drivers, just keep checking on updated in Device Manager.

I'm looking at this in Device Manager, the questions mark under some devices, is that okay?

I'm thinking here, if everything works, why should I update any drivers.

my current list of BSODs:

anazyle -v output:

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

Loading Dump File [C:\Windows\Minidump\100717-5265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1715.amd64fre.rs1_release_inmarket.170906-1810
Machine Name:
Kernel base = 0xfffff802`65c0b000 PsLoadedModuleList = 0xfffff802`65f09040
Debug session time: Sat Oct 7 19:52:57.061 2017 (UTC + 3:00)
System Uptime: 0 days 2:16:18.713
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffed99c6b12208, 2, 1, fffff80265c84a3c}

*** ERROR: Module load completed but symbols could not be loaded for NTFS.sys
Probably caused by : ntkrnlmp.exe ( nt!RemoveListHeadPte+a0 )

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

5: 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: ffffed99c6b12208, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80265c84a3c, address which referenced memory

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.1715 (rs1_release_inmarket.170906-1810)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0809

BIOS_DATE: 07/07/2017

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: STRIX B250I GAMING

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffed99c6b12208

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80265c84a3c

WRITE_ADDRESS: fffff80265faa338: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffed99c6b12208

CURRENT_IRQL: 2

FAULTING_IP:
nt!RemoveListHeadPte+a0
fffff802`65c84a3c 4a8944d308 mov qword ptr [rbx+r10*8+8],rax

CPU_COUNT: 8

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: WerFault.exe

ANALYSIS_SESSION_HOST: PC

ANALYSIS_SESSION_TIME: 10-07-2017 20:54:48.0728

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

TRAP_FRAME: ffff8001c9e9ac70 -- (.trap 0xffff8001c9e9ac70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=780265f250000000 rbx=0000000000000000 rcx=b38d624400000000
rdx=ffffed0000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80265c84a3c rsp=ffff8001c9e9ae00 rbp=ffff8001c9e9af40
r8=ffffed55c6c69400 r9=000000000fffffff r10=0000000b38d62440
r11=fffff80265f25ea0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!RemoveListHeadPte+0xa0:
fffff802`65c84a3c 4a8944d308 mov qword ptr [rbx+r10*8+8],rax ds:00000059`c6b12208=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80265d65a29 to fffff80265d5a8b0

STACK_TEXT:
ffff8001`c9e9ab28 fffff802`65d65a29 : 00000000`0000000a ffffed99`c6b12208 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff8001`c9e9ab30 fffff802`65d64007 : ffffd985`88575f00 fffff802`65cdab82 ffff8001`00000002 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff8001`c9e9ac70 fffff802`65c84a3c : 00000000`00000000 ffff8001`c9e9b0d0 ffff8001`c9e9b190 ffffd985`89bc06c0 : nt!KiPageFault+0x247
ffff8001`c9e9ae00 fffff802`65c82a4c : ffffed00`00000000 fffff802`65f28080 ffff8001`c9e9af40 00000000`00000040 : nt!RemoveListHeadPte+0xa0
ffff8001`c9e9ae40 fffff802`65c81bea : ffffd985`89bc06c0 00000000`00000040 ffffd985`863ef728 ffffd985`89bc06c0 : nt!MiObtainSystemCacheView+0x11c
ffff8001`c9e9b000 fffff802`65c85690 : ffffd985`89bc0640 ffffc287`cbbdf540 ffffffd8`00000000 ffffd985`89bc0678 : nt!MmMapViewInSystemCache+0xda
ffff8001`c9e9b160 fffff802`65c57810 : ffffd985`8722bcb8 ffffd985`8722bcb8 ffffd985`00000000 00000000`00000000 : nt!CcGetVacbMiss+0xb8
ffff8001`c9e9b1e0 fffff802`65c38200 : ffffd985`00000000 00000000`00000000 ffff8001`c9e9b2e8 ffff8001`c9e9b2dc : nt!CcGetVirtualAddress+0x330
ffff8001`c9e9b290 fffff802`65c35187 : ffffd985`8722bc50 000000a5`380c9728 ffff8001`c9e9b400 ffffd985`00000002 : nt!CcMapAndCopyInToCache+0x4a0
ffff8001`c9e9b3a0 fffff804`1e5fa427 : ffffd985`8733f658 ffffc287`d1a9e150 ffffd985`8c3368d0 ffffc287`d1a9e150 : nt!CcCopyWriteEx+0xe7
ffff8001`c9e9b420 fffff804`1e5f6388 : ffffd985`8733f658 00000000`00000000 00000000`00000000 ffffd985`8733f658 : NTFS+0x1a427
ffff8001`c9e9b6a0 fffff804`1dc05206 : ffffd985`8c46a400 ffffd985`8725db80 ffffd985`8725db80 ffffd985`8725df68 : NTFS+0x16388
ffff8001`c9e9b760 fffff804`1dc03146 : 00000000`00000000 00000000`00000000 00000000`ffff8001 ffffd985`8b969080 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a6
ffff8001`c9e9b7f0 fffff802`66020dd0 : ffffd985`8c3368d0 ffffd985`8725db80 00000000`00000002 ffffd985`8c3368d0 : FLTMGR!FltpDispatch+0xb6
ffff8001`c9e9b850 fffff802`660217dd : 00000000`00000001 00000000`00000004 ffffd985`8c336920 ffff8001`c9e9bb00 : nt!IopSynchronousServiceTail+0x1a0
ffff8001`c9e9b910 fffff802`65d65593 : 00000000`00000240 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x66d
ffff8001`c9e9ba10 00007ffc`710261a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000a5`380c9608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`710261a4

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: cd06802cf3339439210a3ab6cb920e5d61c97c89

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dc905217f32d8d3a729f5b3e041aa96a75c52728

THREAD_SHA1_HASH_MOD: 3ac2c0f5433a12278e529a8539a883f6a8a3028d

FOLLOWUP_IP:
nt!RemoveListHeadPte+a0
fffff802`65c84a3c 4a8944d308 mov qword ptr [rbx+r10*8+8],rax

FAULT_INSTR_CODE: d344894a

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!RemoveListHeadPte+a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 59b0d121

IMAGE_VERSION: 10.0.14393.1715

BUCKET_ID_FUNC_OFFSET: a0

FAILURE_BUCKET_ID: AV_nt!RemoveListHeadPte

BUCKET_ID: AV_nt!RemoveListHeadPte

PRIMARY_PROBLEM_CLASS: AV_nt!RemoveListHeadPte

TARGET_TIME: 2017-10-07T16:52:57.000Z

OSBUILD: 14393

OSSERVICEPACK: 1715

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: 2017-09-07 07:54:57

BUILDDATESTAMP_STR: 170906-1810

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.1715

ANALYSIS_SESSION_ELAPSED_TIME: 812

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!removelistheadpte

FAILURE_ID_HASH: {45295d5a-ec7e-df5c-2592-394617d6bb64}

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

uploaded a bunch of minidumps starting from 09/20, when installed windows 10:
https://drive.google.com/drive/folders/0B07lGQ9a3UWVNGtaWUFzMVRHbTg?usp=sharing

Colif · Oct 7, 2017

The Direct X errors are going to be caused by Nvidia drivers. Try doing this and depending where you got drivers from before, either update them via Nvidia web site or use Windows Update to get new ones - http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

the others are less obvious so can you look in c:\windows\minidump. Copy all the files here to another location and then upload the copies from that location to a file sharing site and show a link here. Someone will help you figure out the rest.

sevenfourk · Oct 8, 2017

Colif :

@Colif, thanks. will follow that doc. Windows 10 got the drivers itself, I didn't install anything. Thus, when I first run Windows 10 session, I already got my nvidia drivers installed, though version comparing to nvidia site was a bit lower. I decided not to mess with drivers, and to updated further using Device Manager.

upd: ok, just installed last driver from nvidia site: 385.69 using Device Manager, much cleaner than installing the whole bunch of stuff it will install when invoking the installer itself, plus, I can revert back if needed.

Colif · Oct 8, 2017

that question mark in a blue circle seems to show devices aren't working - its unclear as even Microsoft aren't giving me a full clear answer as to what it means. Did you try clicking on question mark? It seems to show on network devices a lot

don't forget to upload the minidumps

sevenfourk · Oct 8, 2017

@Colif, yeah, I've added minidump section to my question.

but, let me add that here in new reply as well:

uploaded a bunch of minidumps starting from 09/20, when installed windows 10:
https://drive.google.com/drive/folders/0B07lGQ9a3UWVNGtaWUFzMVRHbTg?usp=sharing

as of now, I just disable that devices with question marks.

does not show any informative stuff:

gardenman · Oct 8, 2017

Hi, I ran the dump file(s) through the debugger and got the following information: https://pste.eu/p/icqH.html

File: 100717-5265-01.dmp (Oct 7 2017 - 12:52:57)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: WerFault.exe)
Uptime: 0 Day(s), 2 Hour(s), 16 Min(s), and 18 Sec(s)

File: 100717-4812-01.dmp (Oct 7 2017 - 10:36:09)
BugCheck: [VIDEO_TDR_ERROR (116)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: nvlddmkm.sys (Process: System)
Uptime: 0 Day(s), 8 Hour(s), 06 Min(s), and 17 Sec(s)

File: 100317-4593-01.dmp (Oct 3 2017 - 09:49:11)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: dxgkrnl.sys (Process: WorldOfTanks.e)
Uptime: 1 Day(s), 20 Hour(s), 54 Min(s), and 21 Sec(s)

File: 092917-4687-01.dmp (Sep 29 2017 - 03:09:47)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: chrome.exe)
Uptime: 0 Day(s), 13 Hour(s), 25 Min(s), and 57 Sec(s)

File: 092617-6265-01.dmp (Sep 26 2017 - 10:05:24)
BugCheck: [BAD_POOL_HEADER (19)]
Probably caused by: ntkrnlmp.exe (Process: WerFault.exe)
Uptime: 2 Day(s), 4 Hour(s), 25 Min(s), and 51 Sec(s)

File: 092017-6640-01.dmp (Sep 20 2017 - 11:08:18)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: NTFS.sys (Process: Steam.exe)
Uptime: 0 Day(s), 1 Hour(s), 21 Min(s), and 53 Sec(s)

One of the 6 crashes was caused by the nvlddmkm.sys file. This file is part of a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/

I can't help you with this. Wait for someone else to reply. Good luck.

sevenfourk · Oct 8, 2017

@gardenman, thanks for your help.

already updated nvidia drivers to be the latest. another BSOD happened again, posted as another question, not to confuse anybody. -- http://www.tomshardware.co.uk/forum/id-3538397/bsod-special-pool-detected-memory-corruption-reboot-bluetooth-working.html

axe0axe0 · Oct 8, 2017

MERGED QUESTION
Question from sevenfourk : "BSOD -- SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION -- after reboot bluetooth not working"

sevenfourk :

I've built a PC this September. I'm getting these randoms BSODs. After some of them, after reboot to be precise, my bluetooth adapter stops working. I don't know what exactly makes him work again. But one time I powered off and then power on again my PSU. Sometime I've disassembled and then assembled again my Wifi adapter connectors on the back of my PC. Currently I've tried turning off my PSU. That didn't help. Writing from my mac now.

I've updated my nvidia drivers to be the latest ones. This is my third time installing this windows 10. Before, I have installed all of the drivers from asus drivers and support page. Back then when bluetooth drivers was installed from official site I was having BSOD after every reboot or shutdown.

So last time I've installed Windows 10 and let it install drivers by itself. The only driver I updated is nvidia one. I've unpacked it and installed using Device Manager.

my pc parts:

CPU: Intel - Core i7-7700 3.6GHz Quad-Core Processor
CPU Cooler: Noctua - NH-U14S 55.0 CFM CPU Cooler
Motherboard: Asus - STRIX B250I GAMING Mini ITX LGA1151 Motherboard
Memory: G.Skill - NT Series 16GB (2 x 8GB) DDR4-2400 Memory
Storage: Western Digital - Blue 500GB M.2-2280 Solid State Drive
Storage: Western Digital - Black 512GB M.2-2280 Solid State Drive
Video Card: MSI - GeForce GTX 1080 8GB GAMING X 8G Video Card
Case: Fractal Design - Node 304 Mini ITX Tower Case
Power Supply: SeaSonic - FOCUS Plus Gold 550W 80+ Gold Certified Fully-Modular ATX Power Supply
Mouse: Logitech - MX Master Bluetooth Wireless Laser Mouse

My OS: Windows 10 LTSB

also ran memtest86 before, no problems found.

I've got the latest BIOS updated for my asus b250i gaming pro

anazyle -v output:

Loading Dump File [D:\Downloads\100817-7843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1715.amd64fre.rs1_release_inmarket.170906-1810
Machine Name:
Kernel base = 0xfffff800`f9c75000 PsLoadedModuleList = 0xfffff800`f9f73040
Debug session time: Sun Oct 8 18:49:07.725 2017 (UTC + 3:00)
System Uptime: 0 days 2:06:44.415
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck C1, {ffffc684a9dbcfe0, ffffc684a9dbc107, 5fc018, 23}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+c9282 )

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

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: ffffc684a9dbcfe0, address trying to free
Arg2: ffffc684a9dbc107, address where bits are corrupted
Arg3: 00000000005fc018, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.1715 (rs1_release_inmarket.170906-1810)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0809

BIOS_DATE: 07/07/2017

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: STRIX B250I GAMING

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: ffffc684a9dbcfe0

BUGCHECK_P2: ffffc684a9dbc107

BUGCHECK_P3: 5fc018

BUGCHECK_P4: 23

BUGCHECK_STR: 0xC1_23

SPECIAL_POOL_CORRUPTION_TYPE: 23

CPU_COUNT: 8

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: PC

ANALYSIS_SESSION_TIME: 10-08-2017 18:58:12.0368

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from fffff800f9e58e59 to fffff800f9dc48b0

STACK_TEXT:
ffffcb80`4b931ba8 fffff800`f9e58e59 : 00000000`000000c1 ffffc684`a9dbcfe0 ffffc684`a9dbc107 00000000`005fc018 : nt!KeBugCheckEx
ffffcb80`4b931bb0 fffff800`f9e59a43 : 00000000`00000fff ffffc684`a9dbc000 ffffc684`a9dbcfe0 ffff970b`0337cb70 : nt!MiCheckSpecialPoolSlop+0xa1
ffffcb80`4b931bf0 fffff800`f9ebdc7f : ffffc684`a9dbcfe0 ffffffff`fffff6e8 00000000`00000001 00000000`614c764e : nt!MmFreeSpecialPool+0x137
ffffcb80`4b931d50 fffff80e`2e1e8de0 : ffffc684`a9dbcfe0 00000000`00000000 ffff970b`00c7b000 00000000`00000000 : nt!ExFreePoolWithTag+0x1c7f
ffffcb80`4b931e30 fffff800`fa36e434 : ffffc684`a9dbcfe0 00000000`00000200 ffffcb80`4b931e88 00000000`00000018 : VerifierExt!ExFreePoolWithTag_wrapper+0x10
ffffcb80`4b931e60 fffff80e`31be9282 : ffffc684`a9dbcfe0 00000000`00000000 ffffaa03`84564748 00000000`00000000 : nt!VerifierExFreePoolWithTag+0x44
ffffcb80`4b931e90 ffffc684`a9dbcfe0 : 00000000`00000000 ffffaa03`84564748 00000000`00000000 00000000`caf12028 : nvlddmkm+0xc9282
ffffcb80`4b931e98 00000000`00000000 : ffffaa03`84564748 00000000`00000000 00000000`caf12028 fffff80e`32505381 : 0xffffc684`a9dbcfe0

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: d81d571b063d6012781b28fdaf153e8bffd659a8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d23ef91a8ff83f33edfd895ca1fdb90b64fb3203

THREAD_SHA1_HASH_MOD: fb34d4f16a20e13deb8856488d981bf22c9fccd2

FOLLOWUP_IP:
nvlddmkm+c9282
fffff80e`31be9282 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: nvlddmkm+c9282

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 59bd5729

BUCKET_ID_FUNC_OFFSET: c9282

FAILURE_BUCKET_ID: 0xC1_23_nvlddmkm!unknown_function

BUCKET_ID: 0xC1_23_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS: 0xC1_23_nvlddmkm!unknown_function

TARGET_TIME: 2017-10-08T15:49:07.000Z

OSBUILD: 14393

OSSERVICEPACK: 1715

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: 2017-09-07 07:54:57

BUILDDATESTAMP_STR: 170906-1810

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.1715

ANALYSIS_SESSION_ELAPSED_TIME: 34b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc1_23_nvlddmkm!unknown_function

FAILURE_ID_HASH: {fa539a3c-c776-f1d8-9106-51618b00d0db}

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

UPDATE
just powered on my PC, and bluetooth is working again somehow. well, maybe that's not related with BSOD

UPDATE2
just checked my memory sticks, if my mobo supports them, and it seems like my 2x8G G.Skill (F4-2400C15D-16GNT) are not here supported http://dlcdnet.asus.com/pub/ASUS/mb/LGA1151/STRIX_B250I_GAMING/STRIX_B250I_GAMING_KabylakeCPUDDR4-DRAM_Test_Report.pdf?_ga=2.92610718.2004010656.1507482635-1812290983.1506001588.

not sure if this is really big deal.

Have you tried reseating the card, trying the card in a different system or trying a different card?

Colif · Oct 9, 2017

You might also want to update your network drivers, only as you are using Killer internet and they are well known for causing bsod - http://www.killernetworking.com/driver-downloads

I am going to merge that thread into this one since they likely related still

sevenfourk · Oct 9, 2017

axe0axe0 :

previously I had Palit GTX 1060 SJS 6G. but then I have to replace it, since it was to high for my case, node 304. I went with msi gtx 1080 gaming x+. I don't recall for sure, but it seems it to me that I haven't had any bsods back then, when I had palit gtx 1060 sjs.

I have replaced stock CPU cooler, setup m.2 ssd's, so I have reseated a card a couple of times definitely.

sevenfourk · Oct 9, 2017

Colif :

I see that my wifi card manufacturer is: Qualcomm Atheros Communications Inc.

Colif · Oct 9, 2017

from the dumps Gardenman looked at:

Feb 24 2016 Qcamain10x64.sys Qualcomm Atheros Network Adapter driver http://www.killernetworking.com/

Qualcomm make the hardware, killer was started by 2 people who were involved in the hardware being made better for users.

It’s been an exciting 12 months. As you know, Qualcomm Atheros acquired Bigfoot Networks in 2011. Before the acquisition, Bigfoot had the Killer line of networking products and was developing an advanced traffic shaping technology for routers. During our time at Qualcomm we spent a lot of effort improving the Killer products by moving them to a simpler, better, and more cost effective solution as well as dramatically increasing the OEM and ODM customer base.

Last December, we started a new company called Rivet Networks to focus on Killer and take advantage of what we think is a great opportunity in gaming/performance networking. This was a big move for a lot of reasons, but we felt that there was a lot more that we could do to enhance the networking experience of gamers.

We have already tripled the investment into the product line. We also brought the critical talent from Bigfoot and Qualcomm along with us, including Wayne Dunlap who was the CTO of Bigfoot prior to the acquisition and managed the Killer line of products with me at Qualcomm. He and I created Rivet Networks, then hired Bob Grim, who left AMD to rejoin the technology he helped found with me years ago. We have a lot of momentum right now with our new products and company, and are really excited about it.

https://hothardware.com/reviews/rivet-networks-qa-from-the-bigfoot-killer-nic-to-qualcomm-and-back

Qualcomm don't make the drivers, Killer do.

sevenfourk · Oct 9, 2017

Colif :

ah, sorry, it's clear now. thanks.

sevenfourk · Oct 9, 2017

I guess I should install here: http://www.killernetworking.com/driver-downloads:

* Killer Control Center 64-bit -- (says not compatible hardware has been found)
* Bluetooth for Killer 1535/1525/1435 - Windows 10

Colif · Oct 9, 2017

is the WiFi you are using the on board one? You don't need control panel

did you try the latest driver on Asus web site?

I never realised that Asus used killer WiFi. Now I am side tracked looking to see what my PC has in it

axe0axe0 · Oct 9, 2017

sevenfourk :

axe0axe0 :

previously I had Palit GTX 1060 SJS 6G. but then I have to replace it, since it was to high for my case, node 304. I went with msi gtx 1080 gaming x+. I don't recall for sure, but it seems it to me that I haven't had any bsods back then, when I had palit gtx 1060 sjs.

I have replaced stock CPU cooler, setup m.2 ssd's, so I have reseated a card a couple of times definitely.

You may have a bad GPU card.

sevenfourk · Oct 9, 2017

Colif :

the only one, that came with ROG STRIX B250I GAMING.

just checked with ubuntu to be sure which firmware do I have for wifi:

Colif :

previously, yes. and I think that may have lead to even more BSODs and every time I got my pc rebooted or shutdown. I'm afraid to do that again :-D

sevenfourk · Oct 9, 2017

axe0axe0 :

well, probably, but I don't have enough facts to prove that only gpu is to blame here.

axe0axe0 · Oct 9, 2017

It's definitely not the sole cause, testing is required to identify other possible causes.

Please follow these suggestions in order:
- Update Windows 10 to the Creators Update, if possible.
- Run chkdsk /r on all partitions in an admin command prompt or admin powershell.
- Run driver verifier: https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html

Colif · Oct 9, 2017

Qualcomm Atheros QCA6174 802.11AC
see here under rome: https://wikidevi.com/wiki/Qualcomm_Atheros. If you click on the 6 devices link you will get this page which shows https://wikidevi.com/wiki/Rivet_Networks_Killer_Wireless-AC_1525 as one of the 6 links.

So the drivers should have worked, you can try the link here that is just the drivers: http://www.killernetworking.com/driver-downloads/category/other-downloads but a slightly older driver version.

sevenfourk · Oct 10, 2017

guys, thanks for your help here. let me get back in couple of days and proceed with instructions.

(this is rhetorical) just don't see a reason why to update drivers, when it works normally most of the time. it is so confusing and frustrated on windows, rather than on mac/linux. damn, so painful, and I just wanted to build a PC to play some casual games :-D

axe0axe0 · Oct 10, 2017

Reasons for updating drivers:
- bugfixes and improvements
- stability
- compatibility with Windows

sevenfourk · Oct 10, 2017

axe0axe0 :

totally agree, it's just frustrating comparing to UNIX systems I have used mostly.

GizmoMKD · Oct 10, 2017

sevenfourk :

unix systems are joke dude but that's a different story.

your problem is caused by your drivers, so the manufacturer must update their drivers so they will be compatible with win10.

axe0axe0 · Oct 10, 2017

sevenfourk :

With no disrespect to Microsoft, Windows is designed to support a wide range of hardware. Thanks to researchers and new features Windows needs updates and drivers that control hardware need to be updated too. IMHO Microsoft is doing an amazing job with Windows even though many are complaining because they don't know (or don't want to) that they need to update software.

Random BSODs, last one -- IRQL_NOT_LESS_OR_EQUAL

Commendable

Win 11 Master

Commendable

Win 11 Master

Commendable

Splendid

Commendable

Honorable

Win 11 Master

Commendable

Commendable

Win 11 Master

Commendable

Commendable

Win 11 Master

Honorable

Commendable

Commendable

Honorable

Win 11 Master

Commendable

Honorable

Commendable

Distinguished

Honorable

Share this page