Question Video Memory Management Internal BSOD

I am getting video memory management internal BSOD, it happens randomly, I might be working on something and suddenly I get the BSOD. Sometimes, there are weird errors in the console regarding "GUI". I am not able to copy these errors because I get the BSOD within seconds after that. I am using GTX 1050 4GB latest updated driver, I have tried reinstalling Unity as well as the driver. Still getting the BSOD. Help!

 

I have had the same problem with a GTX 1050Ti, 4GB.
Do you mind sharing which version of Unity were you using? I am using Unity 2019.4.13f1 (64-bit).

 

A BSOD generally points to driver or hardware issues. They are highly unlikely to be caused by Unity, even if you have only experienced them while using Unity.

 

I am using Unity 2020.1.11f.
Joe-Censored you might be correct, but I am user of Unreal too and its working perfectly fine. The games I play including latest Watch Dogs Legion work fine. Why just Unity then?

 

I do agree it is highly unlikely, but it seems a weird coincindence they won't happen while I'm doing anything else.
Just got the third one in four days, and they only happened while using Unity for more than half an hour.

EDIT: Two times in a morning, the second one while using Unity for about 40 minutes. I had more than two hour of other stuff (gaming, coding, videos) before starting Unity and it was fine.

 

And it's very random too. Sometimes, it doesn't happen at all and sometimes it happens while editing particle systems.

 

I have tried again, clean install with Unity 2019.4.6, and the same problem was there. About 30-40 minutes of editing code in Visual Studio and entering/exiting Play Mode in the Unity Editor, and the BSOD was there.
The last tries I could make are formatting and trying to install Unity again, hopefully without this problem.

 

I've gone further than trying to use the Event Viewer. I tried extracting more info than that from the .dmp file that was generated, using Windows Debugging Tools (WinDbg and KD, specifically.
It seems the process originating the BSOD is "System" (as generic as it can be) and the module is "dxgmms2"; it happens when calling "UpdatePageTable", which seems coherent with the description of the BSOD:

"VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition."

I definitely agree with you about it probably being "some aspect of Unity specifically that is pinging hardware to do some work". My next test is trying do a clean install of nVidia's drivers and seeing if it crashes again.
It still seems Unity-related since other applications don't seem to interact in the same way with the drivers - assuming it is a driver problem, of course.

 

It only sounds like that, though! I think I'm actually under it!
I'll probably post again if I get any more precise solution, since I may have stopped it from happening again. I've not tested it enough and I don't want to call it a victory too early.

 

So that means, I gotta just format my PC..?

 

I am not sure I got some time to test extensively if any BSOD will happen again after yesterday's tentative changes, but...

What I tried to do is uninstall my GPU card from Windows' Device manager and install drivers cleanly; moreover, I chose to use the SD version (instead of GRD one) which sould guarantee stability.
I wouldn't want to jinx it - yeah, going into luck and magic at this point lol! - but it seemed to work after that.
I'll report any improvements, if I see this method works on the long run. Please let me know if that fixes the problem for you too. (It would make me sleep much more serene tonight )
If that seems to be a weird interaction between the last nVidia drivers and Unity 2017.4, we can try and report this to both Unity and nVidia and wait for a fix, maybe.

 

So, could you please explain how to do this GRD and SD thingies...? If you cannot, can you share a YouTube video or something like that for the same?

 

Just search for "nvidia drivers", on their site. When you are on their site, you will be asked to select which product you want to download drivers for, which OS and stuff like that. In my case (GTX 1050Ti) you could select a "download type" too.
I picked Studio Drivers (SD) since NVIDIA writes that they're to be preferred if you need "stability and quality" instead of the latest drivers for gaming (which you would get with Game Ready Drivers, or GRD).

Please let me know if that works for you!

EDIT 13/11/2020 (so I don't double-post): I feel like I can confirm that, in my case, the clean install of NVIDIA drivers solved the problem.
In order to be sure it won't happen again while working, I'm staying with these drivers for a while, at least until I can go ahead and start experimenting more without the pressure of my working machine going KO.

EDIT 13/11/2020, later on: Or maybe not. It seems I called it too early. It could be due to some mistake in the project, or maybe anything else, but the BSOD problem came back.

Repeating the process seems to make it disappear for a while. Could Windows Updates have updated my drivers to more recent, unstable ones last night?
Is there any known issue for which Unity Editor may be overwriting something in memory? Is there any occurence of Unity Project staying corrupted after some errors?
When this problem occurred to me for the first time, I just had got a stack overflow issue within Unity; could this be relevant?

Anyway, and again, the problem seems specific and related to Unity. It didn't happen while using any other program which uses my GPU.

 

Same BSOD here, also on a GTX 1050 (in a Dell XPS 15). I reinstalled he latest studio drivers, also no change. after ~20-40 minutes in Unity I get the bluescreen.
1) I did a bios update before encountering this BSOD
2) I changed the Unity Version from 2019.4.11 to 2019.4.14

 

I thought I solved this by simply switching project, literally by copying my Assets in a new one. While this seemed to give me half a week of undisturbed work, it started crashing again.

I tried keeping Unity open for more than 50 minutes, without using anything else in the meanwhile. Once I tried closing it, I got a BSOD again, with the minidump explicitly saying Unity.exe was the process causing it.

As far as I am concerned, I am almost done with my current project and I'd be planning to try a clean install of Unity later on.
To be completely honest, though, the whole situation scared me so much I'm not too serene at the thought of trying again. Not being able to pin down the problem to something more specific doesn't help and working "scared of the program you're using" is pretty disheartening.

 

it happens to on 2020.3.36 and above
It didn't happen in 2021.3.5f1