NVIDIA crashing KERNEL driver on WIN10

Hi everyone, NEW UPDATE -***

Problem with KERNEL CRASHING HAS GONE FOREVER BY REPLACING OR CLEANING MEMMORY STICKS WITH ALCOHOL !!!

IT WAS JUST FAULTY RAM INSIDE COMPUTER CAUSING THIS … NOT GPU

Original post:

Hi everyone,

I had a couple of problems with NVIDIA drivers crashing.,trying to solve with support & one day I have found This — > (" I hope It would be same issue for AMD cards ") It was really because I have found that earlier builds of Windows 10 than 10586 cant use d3d11.3 and later… It will be sitting on d3d11.2 forever. UE 4.14 just recommend using d3d11.3 as I have found in my forever crash reports.

So , anybody who has same issue , just get later or latest build of Windows 10 as I did and forget that issues.

I had disabled updates throught my registry files because I hate that time and network usage of updates.

I hope it will help.!!

Hey Ralph_El Moon,

Thanks for posting the information. I’m going to mark this topic as resolved, as it’s just containing additional information regarding a fix. Let me know if you require additional assistance.

Have a great day

Win10 should always be updated in combination with UE. Endusers will get into trouble with the redists, too - if they’re on a not up to date Win10. (At least in combination with steam)

not totally,!! now i am unable to use particles ,
crashes fd3ddynamicRHI again… … I AM SURE due to st***id windows 10 updates

could u please tell me if theese issues are reported only for windows 10 ?

i am finally gonna try windows 7 sp1 if it will solve this because ,as i’ve been searching , googling, ----> i did’nt found any bugreport simmilar to this issues on win7

As far as I’ve seen, these particular issues have been isolated to windows 10. Let me know what results you see on Windows 7.

So, i’m run my project on windows 8.1 and it’s ok, no error. I think that this problem in Directx 11.3/12 on old videocard that don’t support 11.3/12

what card you own ? i have NVIDIA Asus gtx570 directCU2 (400euro few years ago), which I believe that it is not that old dying grandgrandpa gpu. Or , is it ?

so, i’have installed windows 7 sp1, and ---- >

when i did run ue4.14 on fresh windows 7 installation — > i was unable to edit particle systems, == kernel crash every minute.

After I have downloaded recommended updates like windows 7 sp1 platform update from year 2016 and Kernel Driver NetFramework :

"“S O M E T I M E S” ( now, word “sometimes” consider like almost stable,) it crashes kernel when i have for example model of car with 8 different materials exported from 3ds max, and i am trying to change them in static mesh editor table, it randomly crash that kernel , (fd3ddynamicRHI.cpp device HUNG error or d3dviewport.cpp:266) – > then, blackscreen – > editor crash – > launcher crash → reinitialize GPU – > run project again. === → PERPETUM ORBITAL RANDOMLINEAR CRASHING MACHINE :smiley: lol

so, there is something which is “HUNGïng” my device maybe when engine is compiling that shader before applying on model in background process.
I know NVIDIA & Microsoft has some trouble to troubleshot simmilar issues & also found there was simillar problems also in earlier versions of UE4, I believe there will be some HOTFIX for this soon.

I gave my GPU stress test for latest games and renderings and there was no problem or kernel crashes & UE4.13 works like hell.

There would be great to inform us about some DirectX dependencies between 4.13 and 4.14 ,if there are some.
DX 11.xx versions should be supported by all dx11 gpus

i dont know

I use gt440. I think the earlier model 600 NVIDIA video does not fully support DX12.11.3.

as u said – > u use gt440 with no error problem, so , there isn’t maybe problem with DX itself , but maybe something using DX (shaders, texture binding or video memmory ) that is causing DX crash. It can be just one thing in between dx11 – dx 12 world,and if it is used not propperly it can cause gpu crash,… I had simmilar problem when I was programming WEBGL, there was webgl 1.0 with some experimental features of webgl 2.0. That’s the same as for example using DX 11.3 → its bridge between DX 11 & new standard which will be DX 12 … i think.
It is still in development & as I saw there was huge changes in rendering with ue 4.14

i am sending u crash report

link text

it happen exactly when trying to change material in material slot in static mesh
its new blank project

issue is same as was in WIN10

as u can read in this file , i have – > feature level 11 & if I use -d3ddebug flag , ---- > it says dx11 feature level 10 required to run engine… so what’s going on ?

OK, forget what I wrote above !!!

now I have found FINAL solution maybe for me & maybe also for some users having headaches like me should try this (read).

THAT WAS FINALLY MY GPU. ---- > why ?

i dont know what NVIDIA did last years, but did something wrong,pretty wrong way runs in engineering…

I’ve been surfing , searching, digging, swimming , running, jumping, rotating,acceleraing, hanging, flying, observing, having centripetal forces skewing my face while googling on internet , and FOUND !!!
THAT MY expensive gpu was made with bad voltage setup… earlier version had bios update, but mine ? they forgot to do that for EUROPE distributed version . So what FINALY SOLVED my “PAIN” was downloading MSI Afterburner & Enabling ---- ’ FORCE CONSTANT VOLTAGE ', because dynamic voltage was programmed when some of NVIDI|A employes spilt one’s tea on his keyboard and forgot what he had to finish. lol ? or he won millions in lottery and fired himself from his job in that moment to get lifetime holydays.

Be carefull to not fry your gpu like a pizza when enabling constant volts ,
GTX570 DCii is built to make almost double power overclock while in warranty, thats why its that big like a horse

So, now , after 30 min of materials changing, hacking, cracking, slowly kicking into computer, cracking the newtons laws(believe me,“binaries almost flew”) , when trying to crash UE 4.14, boooioom ---- > no crash ? what da hell ?

117622-agent-smith-evil-laugh-smile-gif.gif

CONSIDER SOLVED FOR MY THREAD back in WINDOWS 10. :smiley: (but dont forget to make sure to check if it is still not something in code)
Also as i wrote on TOP > u will need WIN10 build:10586 or later which is dx11.3 capable to avoid landscape layers crashes)

I have found out how to fix the problem with the “LowLevelFatalError GPU crashed” or found a workaround that no longer causes this error.

LowLevelFatalError [File:D:\build\PC\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: ***]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - ‘HUNG’)

Please support me to spread this in other forums as there are a lot of people with this problem.
I’ve been busy for a week now and read a lot, which did not help!
(At least 7x 3 hrs. Ie 21 hrs.)

Please also help by writing to the devs that fix this bug, as I do not know exactly who is to blame for this bug.
Maybe the Unreal Engine Devs or graphics cards Devs.
(Graphics card manufacturer or driver creator)

Long story short, it is related to the Nvidia Garfikkarten that are already overclocked from house !!!
The so-called Nvidia OC graphic cards!

The overclocked Nvidia graphics cards have a problem with the Unreal Engine or its programming or vice versa!
That’s what I found out after days of testing!

Now for the help of me:

It now depends on the graphics card manufacturer, whether he provides an overclocking OC software on his website.
In my case I have a Zotac Geforce GTX 1080 AMP! Extreme and Zotac I had to download the overclocking tool “Firestorm” which is only intended for the Zotac OC graphics cards.

The point here is that with this tool we need to lower our graphics card back to normal, so that we can play the Unreal Engine games that get this low-level FatalError / GPU crashed.
So you download this tool, like Firestorm, MSI it is the Afterburner etc. down and changes the GPU clock down -200 / -400 MHz it was with me and saves! (do not forget!)
I have to leave the tool open, or in the background, if you can close it, I do not know.

(Before: It’s best to save the default settings so that you can use your OC Garfikkarten Power games that do not have this problem.
Some have but a standard setting button “default” which you can reset the back in auszusungszsutand with OC Pwoer.)

That’s it already!
Your Unreal Engine game should now work without this bug!

PS:
For me it was 3 games that had this error.
I do not list these now because I will copy and paste this text to spread it and I do not want it to be deleted for advertising another game.

By the way, game developers are welcome to help inform Nvidia and Unreal Devs about this issue and have it resolved in collaboration.
After all, it also saves you a lot of time, trouble and above all money, as there are many players who will return the game due to this error.

Since I am a German, I have this text translated by Google Translator, I hope you can handle the English translation.
If not just comment or answer.

Thank you!

Hi everyone, NEW UPDATE -***

Problem with KERNEL CRASHING HAS GONE FOREVER BY REPLACING OR CLEANING MEMMORY STICKS WITH ALCOHOL !!!

IT WAS JUST FAULTY RAM IN COMPUTER CAUSING THIS>> NOT GPU