Windows 10: Bsod video_memory_management_internal

Hello all,

I just saw this BSOD for the first time today. I was doing a stress test to get max temps that I would get on my CPU. The point of this was I was helping someone else who was seeming to get unusually high temps on a very similar machine while also doing stress tests. I wanted to see if mine would be similar. Mine ran about 6C cooler (got up to 91C on one core.)

Anyway, this BSOD popped up after a couple minutes into the stress test. What is odd is there are also two minidumps along with the kernel memory dump that was generated. I only recall seeing one BSOD. For whatever reason my machine was configured to do kernel memory dumps, but I have since changed it to minidumps. Because of the size of the kernel dump I had to share the zip from my OneDrive.

CHRIS-PMW-09_19_2017_Tue__93815_99.7z

Hopefully this will be just a one time thing. Im not overly concerned about it, however I still wanted to see what others here thought.

EDIT: Sorry, I should include the specs of the machine. This is the machine listed under my second system specs.

:)

 

BSOD: VIDEO_MEMORY_MANAGEMENT_INTERNAL

Motherboard is listed in the speccy text file that I had already uploaded to OneDrive -- ASRock P67 Extreme4 Gen3.

I added the results of DriverView to the same folder from the original post.

 

BSOD: VIDEO_MEMORY_MANAGEMENT_INTERNAL

What is your computer make and model? If not a branded computer what is your motherboard make and model?



Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please, HTML files are less easy
to work with.

DriverView: Loaded Windows Drivers List

 

I looked at the crashdumps, the 10E bugcheck is generally caused by the video driver, and I saw that both your nvidia and intel drivers were shown in the thread stack.

The other minidump was a 9F (DRIVER_POWER_STATE_FAILURE), the blocked IRP pointed to Netwbw02.sys, your Intel AC 7260's driver, as the culprit.

General advice is to make sure you are running the latest drivers for graphics and networking.

However given that you are running an insider build of windows, it may have some yet-to-be-fixed bugs in the graphics and networking stacks, and there also is the fact that most drivers are not fully tested against preview builds. If you aren't able to reproduce these crashes on the creator's update or when the fall creator's update comes out, these may be temporary bugs.

 

Alright. Thank you for the info. Honestly, I thought it may have to do with the latest insider build (fast ring) because I never saw this until I updated to the latest build.

 

Before stress testing hardware it should be verified that there are no driver issues (or missing drivers). And u have many driver issues.

Problem devices from msinfo:
Code: Broadcom USH USB\VID_0A5C&PID_5800&MI_00\7&66DE6C9&0&0000 The drivers for this device are not installed. Intel(R) Display Audio HDAUDIO\FUNC_01&VEN_8086&DEV_2807&SUBSYS_80860101&REV_1000\4&32DF08F8&1&0001 39[/quote]
eventlog:
Code: 2017-09-19 08:50:05 Warning: The driver \Driver\IntcDAud failed to load for the device HDAUDIO\FUNC_01&VEN_8086&DEV_2807&SUBSYS_80860101&REV_1000\4&32df08f8&1&0001. 2017-09-19 08:50:05 Warning: The driver \Driver\IntcDAud failed to load for the device HDAUDIO\FUNC_01&VEN_8086&DEV_2807&SUBSYS_80860101&REV_1000\4&32df08f8&1&0001. 2017-09-19 09:36:49 Warning: Display driver nvlddmkm stopped responding and has successfully recovered. 2017-09-19 09:36:53 Warning: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[737]: Log Name: System Source: NetBT Date: 2017-09-17T20:35:39.996 Event ID: 4311 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: CHRIS-PMW Description: Initialization failed because the driver device could not be created. Use the string "ACFDCEE70C62" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.[/quote]

 

Sorry for taking so long to get back to this. Been stupidly busy the last few days. Anyway....

I have updated all the drivers on my system to their latest versions. I have yet to see any more issues after updating the drivers and to Insider Build 16296. Ill leave this open a bit more before I close it as solved.