GeForce HotFix driver 398.46

I don't know, you seem to have multiple issues all the time.

I don't have any issues on several systems.

Might be worth doing that and/or stock bios.

 

Oh please.., only nvcontainer crap that Nvidia fixed for others.

And fyi I bet it's something with that nvidia quick launch notification icon, forgot to disable that and saw it later when I tired to turn off pc and got greeted with this shitty error.

 

Mines not disabled; never had nv container on 1060m system, the 1080ti, 980ti etc

Most likely unstable system or software conflict

 

You waste more time talking about it on forums, instead of actually trying to find the cause. I'm done.

 

Really I don't know what happens with Nvidia... wait wait the launch of Volta is approaching, that's why all old should be worse !!!!

 

I'm blaming Windows
But seriously
I needed to set App Detection Level to High in RTSS with Stealth Mode On, in order to solve the stutter issue I was having, using Nvcpl, vsync on, cap at 60fps, 144 refresh, Dsr 4K...16AF, Quality T.Filtering (default).
Usual games WD2, Witcher3..running excellent since then, that was Sunday.
But I'm bottlenecked with this platform as is, so the more I put on the gpu the better.
Also, since then, I haven't seen the message pop up at shutdown or reboot.
Maybe RTSS hooking mechanism "fixed" whatever compatibility issue was present and somehow I benefitted?
Only conclusion I have at this point.

 

Agent101

No.

I didn't ask you anything.

I posted a issue, end of story.

 

I posted a potential solution to your issue. Don't want to fix it, enjoy it then.

 

mm, only real issue i've had at all is that kmode bsod when monitoring tools are open,

HeavyHemi had it too, others still reporting it.

 

lol don't get me started with such responses.
You can enjoy yourself too.



Besides I tested so much to the point, nvidia fixed it with 398.36 (only driver from R396), now its back. And this started after R391 when nv fixed it for some Pascal users, I NEVER had that before! Get it?


And now when I returned back to 389.36, I had one as well.. Priceless.


//Guess I will report directly to nvidia next time, don't need such replies here.

 

Il start such responses as apparently, I'm talking with Aries here (which is pointless).

In our office one of my (many) responsibilities is to maintain the latest driver support/software support on more than 25 pc's. At home I have two pc's and a laptop. My gf has laptop, same goes for my parents. All of those pc's has a mix of video cards, from ancient to top of the line as right now.

Nearly all (except 3 office pc's with GT 210 ) have the latest drivers. None of those has issues you mention.

And instead of quickly installing windows on a test partition, you argue against everyone that your OS is Fine because you know it. Where's the logic? It's the easiest thing to check.

Anyways do what you want.

 

The negative energy flowing through this thread nourishes my soul.

 

Description
Faulting application name: NVDisplay.Container.exe, version: 1.11.2431.7967, time stamp: 0x5b1e2b17
Faulting module name: NVDisplay.Container.exe, version: 1.11.2431.7967, time stamp: 0x5b1e2b17
Exception code: 0xc0000409
Fault offset: 0x000000000004c915
Faulting process id: 0x1854
Faulting application start time: 0x01d4186aaa7ee7a1
Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe
Faulting module path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe
Report Id: 69354a11-4389-4ffe-b36c-c263311acd35
Faulting package full name:
Faulting package-relative application ID:

.............................

Description
Faulting Application Path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe

Problem signature
Problem Event Name: BEX64
Application Name: NVDisplay.Container.exe
Application Version: 1.11.2431.7967
Application Timestamp: 5b1e2b17
Fault Module Name: NVDisplay.Container.exe
Fault Module Version: 1.11.2431.7967
Fault Module Timestamp: 5b1e2b17
Exception Offset: 000000000004c915
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.17134.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 08c6
Additional Information 2: 08c61db67294d26684816250d20f7c7c
Additional Information 3: 0283
Additional Information 4: 0283ae959979cb917bfff493288ee0c9

...................


and now it manifested into 398.36.. Thanks!

 

Which means its not a driver issue.

 

Yes it is, just like stutter by some games. Seen it before in the past.

Btw there was no need for this nvcontainer in the past., Not few driver branches ago its all the sudden mandatory to work properly, right.

 

The nvcontainer is just a wrapper for the display driver service in order to sandbox it and prevent exploits.

 

What year is this???

 

Spoiler: offtopic

Feels like 2016. It's going to be 2015 again, soon. I feel it in my bones. The world is trying to live in the past as a desperate attempt of facing the consequences of the last decade.

 

Do you mean what month ?

 

Latest official windows,

What does oc have to do with it? I dont oc in msi ab, mild bios flash, no vram oc, gpu is still in safe zone no voltage tweak

Btw Its in idle mode, right before windows shuts down this error prevents it from closing and hangs, I have to press close them it shuts down or restarts, not always but frequent enough.