Frequent BSOD with BAD_POOL_CALLER and 1080 TI GPU

[4k_pc_newbie]

# Error Description

BSOD three times while playing the Witcher 3 on very high graphics settings. It's not predictable when it will occur. Could be within 10 minutes, other times I'll play for 3 hours without incident. Have not seen any issues running other games so far. Screen will freeze, audio keeps playing, after a few moments it crashes to the BSOD with the below error. I did not appear to have this issue until the latest NVIDIA driver update, but this is admittedly subjective.

# WhoCrashed Info

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xDDDA6)
Bugcheck code: 0xC2 (0x7, 0x4D52564E, 0x4050021, 0xFFFFAB8ED15CF220)
Error: BAD_POOL_CALLER
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f4187dc256a67a6b\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 416.34
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 416.34
Bug check description: This indicates that the current thread is making a bad pool request.

# Specs

## CPU

Model: Intel i7-8700k @ 3.70 GHz
Clock: 3700 MHz
Voltage: 1.024 V
Temps: 35 C idle, 63 C load
Cooler: Corsair H115i

## Motherboard

Model: ASUS Maximus X Hero WI-FI AC
BIOS: Just updated to version 1704
Target CPU Turbo-Mode Frequency: 4700 MHz
Target CPU @ AVX Frequency: 4700 MHz
Target Cache Frequency: 4400 MHz
Target DRAM Frequency: 2133 MHz
Overclocking Presets: AUTO

I think this motherboard places a slight overclock on the CPU by default but I'm not 100% sure.

## GPU

Model: ASUS GeForce GTX 1080 TI 11GB STRIX GAMING
Clock: No overclock, so whatever the default is
Driver: GeForce Game Ready Driver v 416.34
Temps: 50 C idle, 73 C load

## RAM

Model: Corsair Vengeance LPX 32GB (2x16GB)
Clock: 2133 MHz
Voltage: 1.200 V

## Other Info

Power Supply: EVGA 1000W 80+ Platinum Certified Fully-Modular ATX Power Supply
SSD: Samsung 970 Evo 1.0TB M.2-2280
Case: Corsair Obsidian 500D ATX Mid Tower Case
OS: Windows 10 Home 64-bit, Build 17134
Monitor: Asus PG279Q ROG Swift 27.0" 2560x1440 165Hz
GSYNC: Enabled for full screen (not windowed)
Refresh Rate: Set to 144hz in NVIDIA Control Panel

## Full Parts List for Reference

https://pcpartpicker.com/user/no_decaf/saved/#view=8n4sZL

# Stress Tests

Prime95: 8 hours runtime, 0 errors, 0 warnings (all threads)
FurMark: 10 hours runtime, no apparent errors, max GPU temp 73 C
MemTest86: 5 passes w/ all tests (1-13), 7:56 test duration, 100% tests passed, 0 cumulative/contiguous errors
3DMark: Fire Strike 22,388; Fire Strike Extreme 13,054; Fire Strike Ultra 6,916; Time Spy 9,251; Time Spy Extreme 4,302
Valley: 2560x1440, 8X AA, Ultra quality => 94.9 FPS; 3,972 score

 

[johnbl]

pool is a memory data structure shared by device drivers. generally, a bad pool call is a driver messing up by freeing a the memory twice. the first time it works, the second time it fails since the driver no longer is the owner of that memory.

so, you would remove any overclock for the GPU and cpu. update the GPU drivers including the GPU sound driver. Then go to the motherboard vendors website and update the motherboards sound driver (since it is a very common source of GPU problems)

the problem can be debugged but requires a kernel memory dump.
best to update the drivers and remove the overclock and see if you still have the problem.

 

[hiredranger2014]

Having the same issue in the last week or so. But only in ARK Evolved.

Model: ASUS Maximus X Code
Intel i7 8700K (Delidded, liquid metal). 5 GHZ - ( tried reverting to stock, same problem )
Target Cache Frequency: 4400 MHz
Target DRAM Frequency: 3200 MHz
2 X 1080Ti EVGA. (SLI disabled for UE4 games).
Windows 10.

Whole system has pretty extreme watercooling. It doesnt get warm (outside of long benches and BF1) with ultra and 150/200% oversampled resolution.

I do not use/install NVidia experience and microsoft and nvidia telemetry is disabled/blocked on our network and on the PC.

A lot of people were going crazy in servers that they couldnt play using 2080s. Same error. For some stupid reason, I remembered I hadnt update driver and did so after seeing that. Started around the same time.

Mainly play on a private professionally hosted server owned by myself.