Random BSODs, last one -- IRQL_NOT_LESS_OR_EQUAL

[sevenfourk]

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:

Spoiler

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:

Spoiler

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

 

[mondiaraphael]

Hello

excuse me if i am not to the right place but i have some issues with my pc and it looks the same ... Can someone help me ? i have the report from WhoCrashed if it can help... and my pc is a MSI GS70 2QE .. it is about the wifi i saw it but on the msi site they are two drivers for wifi but i don't know which one i should use and what are the step ...

thx for your help

System Information (local)
--------------------------------------------------------------------------------

Computer name: RAPHI
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: GS70 2QE, Micro-Star International Co., Ltd., MS-1773
CPU: GenuineIntel Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8503701504 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 15/10/2017 15:41:31 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101517-9296-01.dmp
This was probably caused by the following module: nwifi.sys (0xFFFFF80F9418F039)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF80F9418F039)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 15/10/2017 15:09:16 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101517-7703-01.dmp
This was probably caused by the following module: bwcw10x64.sys (0xFFFFF809F3C5CB73)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF809F3C5CB73)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bwcw10x64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bwcw10x64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 13/10/2017 15:48:50 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-7515-01.dmp
This was probably caused by the following module: nwifi.sys (0xFFFFF8002A02F039)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF8002A02F039)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 11/10/2017 20:13:24 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101117-13046-01.dmp
This was probably caused by the following module: bwcw10x64.sys (0xFFFFF80ADF6402BB)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF80ADF6402BB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bwcw10x64.sys
product: Killer Bandwidth Control
company: Rivet Networks, LLC.
description: Killer Bandwidth Control Filter Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bwcw10x64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.).
Google query: Rivet Networks, LLC. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 11/10/2017 20:03:33 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101117-10578-01.dmp
This was probably caused by the following module: nwifi.sys (0xFFFFF8025FE8F039)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF8025FE8F039)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

10 crash dumps have been found and analyzed. Only 5 are included in this report. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation)
qcamain10x64.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros, Inc.)
bwcw10x64.sys (Killer Bandwidth Control Filter Driver, Rivet Networks, LLC.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[axe0axe0]

Update your network drivers from your motherboard manufacturer.

 

[mondiaraphael]

but windows tell me everything is updated so i am not sure what you are asking ^^"

 

[axe0axe0]

Windows doesn't update everything, sometimes it includes drivers like chipset, gpu, audio and network drivers with the updates but not often.

Go to the support page of your motherboard manufacturer, download the newest network drivers for your OS and install them.

 

[mondiaraphael]

Ok i will try thanks a lot for your help !

 

[sevenfourk]

instead Windows 10 LTSB, I have tried Windows 10 Enterprise. 3 days no any Blue Screen, no nothing, but happened again:

while I was gaming World of Tanks game.

WhoCrashed

Spoiler

On Mon 16.10.2017 10:16:18 your computer crashed
crash dump file: C:\Windows\Minidump\101617-4781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x139 (0x3, 0xFFFF82818ED64D60, 0xFFFF82818ED64CB8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 16.10.2017 10:16:18 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x1DF5)
Bugcheck code: 0x139 (0x3, 0xFFFF82818ED64D60, 0xFFFF82818ED64CB8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

windbg says this somehow:

Spoiler

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


Loading Dump File [D:\Downloads\101617-4781-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 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff802`13e17000 PsLoadedModuleList = 0xfffff802`141635c0
Debug session time: Mon Oct 16 10:16:18.193 2017 (UTC + 3:00)
System Uptime: 0 days 12:58:31.827
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
..............
GetContextState failed, 0x8007001E
CS descriptor lookup failed
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get program counter
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffff82818ed64d60, ffff82818ed64cb8, 0}

GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E

c:\windows\memory.dmp analysis with windbg:

Spoiler

Loading Dump File [D:\Downloads\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 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff802`13e17000 PsLoadedModuleList = 0xfffff802`141635c0
Debug session time: Mon Oct 16 10:16:18.193 2017 (UTC + 3:00)
System Uptime: 0 days 12:58:31.827
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`003b6018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffff82818ed64d60, ffff82818ed64cb8, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+22d4 )

Followup: Pool_corruption
---------

4: 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: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff82818ed64d60, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff82818ed64cb8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

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

BUGCHECK_P1: 3

BUGCHECK_P2: ffff82818ed64d60

BUGCHECK_P3: ffff82818ed64cb8

BUGCHECK_P4: 0

TRAP_FRAME: ffff82818ed64d60 -- (.trap 0xffff82818ed64d60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9e0f277b6540 rbx=0000000000000000 rcx=0000000000000003
rdx=ffff9e0f27a2cc00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802140982f4 rsp=ffff82818ed64ef0 rbp=0000000000000000
r8=ffff9e0f277b6570 r9=ffff9e0f2807fc00 r10=0000000000000001
r11=ffff9e0f23213100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!ExDeferredFreePool+0x22d4:
fffff802`140982f4 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffff82818ed64cb8 -- (.exr 0xffff82818ed64cb8)
ExceptionAddress: fffff802140982f4 (nt!ExDeferredFreePool+0x00000000000022d4)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 8

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

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

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-443TSOF

ANALYSIS_SESSION_TIME: 10-16-2017 10:40:20.0149

ANALYSIS_VERSION: 10.0.15063.468 x86fre

LAST_CONTROL_TRANSFER: from fffff80213f8e8a9 to fffff80213f83580

STACK_TEXT:
ffff8281`8ed64a38 fffff802`13f8e8a9 : 00000000`00000139 00000000`00000003 ffff8281`8ed64d60 ffff8281`8ed64cb8 : nt!KeBugCheckEx
ffff8281`8ed64a40 fffff802`13f8ec10 : ffffb48d`619697c0 ffffb48d`5d1f2a68 00000000`00000001 ffff8281`8eadf180 : nt!KiBugCheckDispatch+0x69
ffff8281`8ed64b80 fffff802`13f8dbf7 : ffff8281`00000000 fffff802`1420f200 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffff8281`8ed64d60 fffff802`140982f4 : ffffb48d`5aa42500 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf7
ffff8281`8ed64ef0 fffff802`14097801 : ffff9e0f`277b6580 ffffb48d`5aa42500 ffff8281`8ed65009 ffff9e0f`276dc8e0 : nt!ExDeferredFreePool+0x22d4
ffff8281`8ed64f70 fffff808`c6d61df5 : ffffb48d`5f5aa001 ffff9e0f`235018b0 ffffb48d`5f5aa000 00000000`00000001 : nt!ExFreePoolWithTag+0x7e1
ffff8281`8ed65070 fffff808`c6dbfa61 : ffff9e0f`276dc8f0 00000000`00000000 ffffb48d`00000004 ffffb48d`5f5aa000 : dxgmms2!operator delete+0x11
ffff8281`8ed650a0 fffff808`c5ee165e : ffffb48d`5f277d60 ffff8281`00000000 00000000`00000003 ffffb48d`00000001 : dxgmms2!VIDMM_GLOBAL:estroyOneAllocation+0x221
ffff8281`8ed652d0 fffff808`c5eda43e : ffff9e0f`235018b0 fffff808`c5eda3b4 ffff9e0f`235018b0 ffff8281`8ed65670 : dxgkrnl!DXGDEVICE:estroyAllocations+0x372
ffff8281`8ed65460 fffff808`c5ee2bca : ffff9e0f`235018b0 ffff9e0f`235018b0 00000000`00000000 fffff808`c5e2a000 : dxgkrnl!DXGDEVICE:rainAllocations+0x4a
ffff8281`8ed654c0 fffff808`c5ec2aff : ffffffff`ffb3b4c0 ffffffff`ffb3b4c0 ffff9e0f`235018b0 00000000`00000000 : dxgkrnl!DXGDEVICE:estroyAllDeviceState+0x1c2
ffff8281`8ed65540 fffff808`c5ed56fd : ffff8281`8ed65770 ffff9e0f`235018b0 ffff9e0f`00000001 ffff9e0f`235018b0 : dxgkrnl!ADAPTER_RENDER:estroyDevice+0xa7
ffff8281`8ed65570 fffff808`c5ed3c16 : 00000000`000001c5 00000000`000001c5 00000000`00000000 ffff9e0f`20ccb7c0 : dxgkrnl!DXGPROCESS:estroy+0x41d
ffff8281`8ed65730 fffff808`c5e24bb7 : ffffb48d`61f2e7c0 00000000`00000000 ffffb48d`61f2e7c0 00000000`00000005 : dxgkrnl!DXGPROCESS:estroyDxgProcess+0xb6
ffff8281`8ed657e0 fffff802`14255189 : 00000000`00000000 00000000`00000000 00000000`0000ff00 ffffb48d`5aeddc30 : dxgkrnl!DxgkProcessNotify+0x17
ffff8281`8ed65810 fffff802`142dcd9c : ffffb48d`61f2e700 ffffb48d`61f2e7c0 ffffb48d`61f2e700 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x1f1
ffff8281`8ed658d0 fffff802`142515fe : ffffb48d`61969db0 ffffb48d`00000000 ffffb48d`61f2e7c0 ffff8281`8ee58180 : nt!PspExitProcess+0x78
ffff8281`8ed65910 fffff802`14310ff9 : 00000000`00000003 ffffb48d`61f2e701 00000000`003b8000 ffffb48d`619697c0 : nt!PspExitThread+0x53a
ffff8281`8ed65a10 fffff802`13f8e413 : ffffb48d`61f2e7c0 ffffb48d`619697c0 ffff8281`8ed65b00 00000000`00000003 : nt!NtTerminateProcess+0xe9
ffff8281`8ed65a80 00000000`5b7d21cc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009ef08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5b7d21cc


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 8e8b63aeeeae81afaab9eb761b8934bf67f49bcb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ccc14d6ea5cc1bf33d000920100501f6e50631c0

THREAD_SHA1_HASH_MOD: 799f075ab15bb6057e77973c8d31a5cdacdfb332

FOLLOWUP_IP:
nt!ExDeferredFreePool+22d4
fffff802`140982f4 cd29 int 29h

FAULT_INSTR_CODE: 3b929cd

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!ExDeferredFreePool+22d4

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

BUCKET_ID_FUNC_OFFSET: 22d4

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExDeferredFreePool

BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExDeferredFreePool

PRIMARY_PROBLEM_CLASS: 0x139_3_CORRUPT_LIST_ENTRY_nt!ExDeferredFreePool

TARGET_TIME: 2017-10-16T07:16:18.000Z

OSBUILD: 15063

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: 2017-09-29 10:20:26

BUILDDATESTAMP_STR: 170317-1834

BUILDLAB_STR: rs2_release

BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME: 26ca

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_3_corrupt_list_entry_nt!exdeferredfreepool

FAILURE_ID_HASH: {7ef5a43a-ed8f-4a4a-f936-b37f9eaa1b29}

Followup: Pool_corruption
---------

that seems like a ****up directX drivers or something, and someone here saying about great job being done by Microsoft, that makes me cry

have latest driver for every peace of hardware

all apps installed:
https://imgur.com/a/bpC2O

currently mobo runs default BIOS, my memory runs at it's default 2133Mhz

 

[axe0axe0]

You have a version of Windbg that is known to give those errors.

DirectX points to the graphics driver, ie AMD, NVIDIA or Intel, not Microsoft!

 

[sevenfourk]

Guys, so I came to the point, where I started to test my RAM, 2 sticks of 8G 2133/2400 XMP. Did memtest86 tests of two beeing in both slots. But not one by one. So I just ejected one of them, and started using computer as a normal use, no BSODs for two days straight. Then insterted the one RAM stick that was waiting for it's star time, and here were go -- got BSOD. Change the slots of this RAM stick -- again BSOD.

The issue could be different of course, CPU memory controller issues, dual channel issue on the motherboard. But if RAM stick got issues in both slots, I suspect this is most probably it.

Will hand it over for the warranty, will see what they say.

 

[Colif]

Shame none of us ever suggested running memtest86.

Bad ram will cause random errors, I should have suggested it...

Glad you worked it out.

 

[sevenfourk]

Thing is, sorry didn't mention in prev post, that while testing both rams in memtest86 that didn't show any errors at all. I have tested it even before all this fuzz I have started in this thread. So I thought, oh, ok, RAM probably not to blame. But I didn't test it one by one. I will let to test that the store where I purchased it.