BSOD BAD_POOL_CALLER (nvlddmkm.sys ( nvlddmkm+ddda6 ))

Toggle sidebar Toggle sidebar
K

_kaede

Oct 29, 2018
2
0
10
So far I haven't been able to track down the conditions to generate this BSOD, it happens at a random time only while playing ARK: Survival Evolved, mostly after several hours of playtime.

I have been stress-testing my video card with FurMark v 1.20.1.0 and MSI Kombustor v 3.5.2.1 (the latter for VRAM load tests mostly, only reliable tool I've found for that purpose) for around 10 minutes straight several times without issues.

I already tried a clean install of Win 10, installing the 416.34 drivers on top of those already installed by windows as soon as the OS finished installing itself, without removing them beforehand with DDU, I have also updated the motherboard's BIOS to the latest version.

**EDIT**
The BSOD does not happen outright, but as soon as I try to kill the game process through task manager, right after the game froze without recovering.

Specs:

Motherboard ASUS Z170 PRO GAMING
CPU i7 6700k
RAM 2x8 GB DDR4 3200 MHz Corsair Vengeance LPX
GPU GTX 1070 Zotac AMP! Extreme
PSU Corsair CS750M 750 W 80 Plus Gold


WinDbg dump reading:

Code: 
Microsoft (R) Windows Debugger Version 10.0.18239.1000 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.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`49c14000 PsLoadedModuleList = 0xfffff801`49fc2150
Debug session time: Mon Oct 29 16:57:41.750 2018 (UTC + 1:00)
System Uptime: 0 days 12:56:40.440
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000009e`7617d018).  Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 53646156, 4050005, ffffd2847428d920}

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
unable to get nt!ExpHeapBackedPoolEnabledState
Probably caused by : nvlddmkm.sys ( nvlddmkm+ddda6 )

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

nt!KeBugCheckEx:
fffff801`49dbd490 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff838b`ffaeeaf0=00000000000000c2
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000053646156, Pool tag value from the pool header
Arg3: 0000000004050005, Contents of the first 4 bytes of the pool header
Arg4: ffffd2847428d920, Address of the block of pool being deallocated

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:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  3805

BIOS_DATE:  05/16/2018

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  Z170 PRO GAMING

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  1

BUGCHECK_P1: 7

BUGCHECK_P2: 53646156

BUGCHECK_P3: 4050005

BUGCHECK_P4: ffffd2847428d920

POOL_ADDRESS:  ffffd2847428d920 Nonpaged pool

FREED_POOL_TAG:  VadS

BUGCHECK_STR:  0xc2_7_VadS

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  ShooterGame.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-M1H83QU

ANALYSIS_SESSION_TIME:  10-29-2018 17:06:04.0423

ANALYSIS_VERSION: 10.0.18239.1000 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80149f0003c to fffff80149dbd490

STACK_TEXT:  
ffff838b`ffaeeae8 fffff801`49f0003c : 00000000`000000c2 00000000`00000007 00000000`53646156 00000000`04050005 : nt!KeBugCheckEx
ffff838b`ffaeeaf0 fffff805`41f7dda6 : ffffd284`7428d920 fffff801`49c18720 ffffc201`24b56180 ffffd284`6bda8080 : nt!ExFreePoolWithTag+0xfdc
ffff838b`ffaeebd0 fffff805`420774a3 : ffffd284`6598a010 ffff838b`ffaeed90 ffffd284`6c6ec010 fffff801`49c1803f : nvlddmkm+0xddda6
ffff838b`ffaeec00 fffff805`42095dcf : 00000000`00000000 ffff838b`ffaeed70 00000000`00000000 00000000`00000000 : nvlddmkm+0x1d74a3
ffff838b`ffaeec30 fffff805`42095fd4 : ffff9525`b55062f9 00000000`00000000 00000000`00000003 00000000`00000004 : nvlddmkm+0x1f5dcf
ffff838b`ffaeec60 fffff805`424b06a1 : 00000000`00000000 ffff838b`ffaeeda9 ffffd284`69bc6000 fffff801`49cec8bc : nvlddmkm+0x1f5fd4
ffff838b`ffaeec90 fffff805`41f9dd3a : ffffd284`6598a010 fffff805`00000000 ffffd284`6598a010 00000000`00000000 : nvlddmkm+0x6106a1
ffff838b`ffaeedf0 fffff805`429f3e81 : ffffd284`6c6ec010 ffff838b`ffaeefa0 ffffd284`6c6ec010 ffffd284`6a52e000 : nvlddmkm+0xfdd3a
ffff838b`ffaeee30 fffff805`41fc03bd : ffffd284`6c6ec010 ffff838b`ffaeefa0 ffffd284`6a52e000 00000000`00000000 : nvlddmkm+0xb53e81
ffff838b`ffaeee70 fffff805`429cd05a : ffffd284`6c6ec010 00000000`00000000 00000000`00000082 00000000`00000082 : nvlddmkm+0x1203bd
ffff838b`ffaeeea0 fffff805`429ccea6 : ffffd284`6c6ec010 ffff838b`00000000 ffffd284`6c6ec010 00000000`00000000 : nvlddmkm+0xb2d05a
ffff838b`ffaeef20 fffff805`429ae806 : ffffd284`6a52e000 ffffd284`6a52e000 ffffd284`6cf8a1c0 ffffd284`6c6ec010 : nvlddmkm+0xb2cea6
ffff838b`ffaeefc0 fffff805`3eec0ffc : fffff805`429ae792 00000000`00000000 ffff838b`ffaef189 ffffac05`b3e0b600 : nvlddmkm+0xb0e806
ffff838b`ffaef060 fffff805`3eedcb82 : ffffac05`b3e0b530 00000000`00000008 ffffac05`b3e0b530 ffffd284`6a2ce2d8 : dxgkrnl!ADAPTER_RENDER::DdiDestroyContext+0x114
ffff838b`ffaef120 fffff805`3eed6a99 : ffffac05`b3e0b530 ffffac05`af46aa88 ffffac05`af46a920 00000000`00000001 : dxgkrnl!DXGCONTEXT::DestroyContext+0x2aa
ffff838b`ffaef1f0 fffff805`3eed45bf : ffffac05`af46a920 ffffac05`af46a920 00000000`00000000 fffff805`3ee10000 : dxgkrnl!DXGDEVICE::DestroyDevice+0x209
ffff838b`ffaef280 fffff805`3eec2e04 : ffffffff`ffb3b4c0 ffffffff`ffb3b4c0 ffffac05`af46a920 ffffac05`ac77f240 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState+0x1c3
ffff838b`ffaef300 fffff805`3eed9340 : 00000000`00000000 ffff838b`ffaef409 ffffac05`af46a920 ffffac05`af46a920 : dxgkrnl!ADAPTER_RENDER::DestroyDevice+0xe0
ffff838b`ffaef330 fffff805`3eeee400 : ffffac05`ac8e0130 ffffac05`ac8e2e30 00000000`00001800 00000000`00000000 : dxgkrnl!DXGPROCESS::Destroy+0x394
ffff838b`ffaef470 fffff805`3ee125f4 : ffffd284`6bf06580 ffffac05`ac8e2e30 00000000`00000007 ffffd284`6bf06580 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0xd4
ffff838b`ffaef5b0 fffff801`4a1a45f2 : 00000000`00000000 00000000`00000000 ffff838b`ffaeff00 ffffd284`6c0e84e0 : dxgkrnl!DxgkProcessNotify+0x84
ffff838b`ffaef5f0 fffff801`4a1846b4 : ffffd284`6bf06500 ffffd284`6bf06580 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x206
ffff838b`ffaef6c0 fffff801`4a0b8ae0 : ffffd284`6bda8678 00000000`00000000 00000000`00000000 ffffd284`6bda8080 : nt!PspExitProcess+0x70
ffff838b`ffaef6f0 fffff801`4a0bace3 : 00000000`00000001 ffffc201`24ac0101 0000009e`761c4000 fffff801`49c4cdcb : nt!PspExitThread+0x568
ffff838b`ffaef7f0 fffff801`49c4f810 : ffffd284`655b3ce8 fffff801`4a56a4e6 ffff9525`00000000 00000000`001f0003 : nt!KiSchedulerApcTerminate+0x33
ffff838b`ffaef830 fffff801`49dc1540 : 00000000`000008a0 ffff838b`ffaef8c0 00000000`ffaefa00 fffff801`00000000 : nt!KiDeliverApc+0x3a0
ffff838b`ffaef8c0 fffff801`49dcdbea : ffffd284`6bda8080 00000000`00000000 00000000`00000000 ffffd284`65d87140 : nt!KiInitiateUserApc+0x70
ffff838b`ffaefa00 00007ffc`f4cb9f84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
0000009e`7a5af928 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`f4cb9f84


THREAD_SHA1_HASH_MOD_FUNC:  f4c8e71bcb79ef7ee563ae95bf707cea2049d92c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  755e12da413c03b6858f76b5d08498385d878136

THREAD_SHA1_HASH_MOD:  a0c0d34369f06c13ec307cba1386f9d77c01a036

FOLLOWUP_IP: 
nvlddmkm+ddda6
fffff805`41f7dda6 f048ff8fa8000000 lock dec qword ptr [rdi+0A8h]

FAULT_INSTR_CODE:  8fff48f0

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nvlddmkm+ddda6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5bbe7e34

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ddda6

FAILURE_BUCKET_ID:  0xc2_7_VadS_nvlddmkm!unknown_function

BUCKET_ID:  0xc2_7_VadS_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  0xc2_7_VadS_nvlddmkm!unknown_function

TARGET_TIME:  2018-10-29T15:57:41.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-10-21 09:17:29

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  1a41

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc2_7_vads_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {649bfaf9-9289-80ca-68c5-a5bc4482655d}

Followup:     MachineOwner
---------
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
pool tag = VadS = Mm virtual address descriptors
virtual address descriptor deleted twice.

maybe update the bios and sata drivers. make sure there is free space on the drive to create more virtual memory.
ie enlarge c:\pagefile.sys
I would also check the drive to see if it is having errors, run crystaldiskinfo.exe to see if it is reporting errors.

make sure you are not running any third party caching programs.

normally, you should change the memory dump type to kernel and provide the kernel memory dump file so it can be looked at with the windows debugger. the automated script does not show the proper info.
 
Upvote 0 Downvote
K

_kaede

Oct 29, 2018
2
0
10
BIOS and SATA drivers are up to date already, and the HDD on which the game is installed has 142 free GBs out of 931, the only thing is that that's the D: drive, while I have formatted the C: drive with the OS on and simply reinstalled steam on the old installation in D:, my guessing is that some registry key is missing.

How am I able to change the memory dump type? And will that need me to repeat the BSOD?

I'm using WinDbg Preview to view the dump files.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom