Requesting help, video_memory_management_internal BSOD

JulesRuby

Honorable
Sep 11, 2012
9
0
10,510
Laptop specs:

i7-7700HQ CPU @ 2.80GHz
16 GB RAM
NVIDIA Geforce GTX 1050
Windows 10 64-bit

I purchased Hunt: Showdown about a week ago, and I installed it. I managed to play the game for several rounds without any real issues, and I was having a blast. However, from the next day on, I have not been able to play the game since. What happens is that I log in to the game, I click on 'Play', I get matched with another player, I Ready up, the match begins filling the roster with players. Once a match is found, the game informs me that it's going to load the map. The loading wheel appears, though it almost immediately fails to have any animation to it. After about half a minute, my computer just crashes. The most common error seems to be video_memory_management_internal, though I have seen errors for video_scheduler_internal_error and video_tdr_error throughout my attempts to tweak my laptop settings and drivers.

I've tried clean installing all of my video drivers using DDU and Nvidia Experience, I've uninstalled and reinstalled Hunt, I've put all the graphics settings to low, increased my page file RAM (if that makes a difference here?), deleted the user folder... I feel like there were a few other things I tried, but I've staggered my attempts throughout the week in between my work shifts, so I may be forgetting a few.

Earlier I sought out help on their discord, and they suggested that it may be a temperature problem also. Which I understand is a possibility, and I will invest in a quality cooling pad. However the error message I am receiving upon duplicating the crash makes me feel like it's perhaps not.

I ran a WhoCrashed and I will post what the log has stated. I'm not entirely sure how to use the information though, so if anyone could offer me some advice, I would be grateful.



Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 2018-10-21 7:07:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102118-29953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0x10E (0x1D, 0xFFFF8189F8C37290, 0x0, 0x0)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2018-10-21 7:07:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!MmBuildMdlForNonPagedPool+0x3777)
Bugcheck code: 0x10E (0x1D, 0xFFFF8189F8C37290, 0x0, 0x0)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2018-10-21 4:09:32 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102118-28437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFC980DD4C2860, 0xFFFFE20F9EB45B30)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2018-10-21 2:49:45 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102118-28484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0x10E (0x1D, 0xFFFFD9075AB55340, 0x0, 0x0)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2018-10-20 5:55:44 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102018-36109-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF805325B4650)
Bugcheck code: 0x116 (0xFFFF80030D12A4A0, 0xFFFFF805325B4650, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvami.inf_amd64_eb18ef0e5d636f6f\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 an attempt to reset the display driver and recover from a timeout failed.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 416.34 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR
 
bugcheck 0x10e with parameter 1= 0x1d is not documented.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x10e---video-memory-management-internal

the error:
0: kd> !error 0xC000000D
Error code: (NTSTATUS) 0xc000000d (3221225485) - An invalid parameter was passed to a service or function.
could mean you have a mixed build of gpu drivers. ie one driver from windows update, and another part of the gpu driver from a old build of a gpu driver. tends to happen when windows pushes out a graphics driver update and the machine is not rebooted at the correct time.


i would remove all overclock drivers.
i would update the motherboard sound driver

I would use windows control panel device manager and disable any sound sources that do not have a speaker attached to them.