BSOD in nv4_disp.sys, v81.85

[SunnyD]

Well, it happened, and I'm not too sure why. I finally got my first BSOD since uninstalling that stupid NAM software... but this time the culprit was nv4_disp.sys.

Running v81.85 drivers, doing nothing out of the ordinary, I was in WoW just walking around in Ironforge when the whole thing just locked up. I knew it wasn't totally locked because after about a minute the screen switch to desktop gamma mode. So I figured WoW crashed and I would be on my merry way...

About 2 minutes later WoW finally came down and up popped a BSOD. The error, as mention, was in nv4_disp.sys. The issue itself was that the driver got stuck in an infinite loop.

Windows kindly suggested it was either a bad driver or a hardware problem.

Anyone else getting this with 81.85?

 

[grimlykindo]

79.11 is all you need to know. I ditched the 81.85 within hours of installing. I even get better frames with the 79.11

Google "79.11 forceware" and you will find it

 

[imported_ST]

Originally posted by: SunnyD
Well, it happened, and I'm not too sure why. I finally got my first BSOD since uninstalling that stupid NAM software... but this time the culprit was nv4_disp.sys.

Running v81.85 drivers, doing nothing out of the ordinary, I was in WoW just walking around in Ironforge when the whole thing just locked up. I knew it wasn't totally locked because after about a minute the screen switch to desktop gamma mode. So I figured WoW crashed and I would be on my merry way...

About 2 minutes later WoW finally came down and up popped a BSOD. The error, as mention, was in nv4_disp.sys. The issue itself was that the driver got stuck in an infinite loop.

Windows kindly suggested it was either a bad driver or a hardware problem.

Anyone else getting this with 81.85?

i get the same thing with WoW constantly now on 81.85. Are you running AMD X2 per chance?

 

[SunnyD]

Originally posted by: ST

Originally posted by: SunnyD
Well, it happened, and I'm not too sure why. I finally got my first BSOD since uninstalling that stupid NAM software... but this time the culprit was nv4_disp.sys.

Running v81.85 drivers, doing nothing out of the ordinary, I was in WoW just walking around in Ironforge when the whole thing just locked up. I knew it wasn't totally locked because after about a minute the screen switch to desktop gamma mode. So I figured WoW crashed and I would be on my merry way...

About 2 minutes later WoW finally came down and up popped a BSOD. The error, as mention, was in nv4_disp.sys. The issue itself was that the driver got stuck in an infinite loop.

Windows kindly suggested it was either a bad driver or a hardware problem.

Anyone else getting this with 81.85?

i get the same thing with WoW constantly now on 81.85. Are you running AMD X2 per chance?

Nope, Sempron 64

 

[imported_BikeDude]

FWIW: I got a BSOD under x64 when trying to launch FarCry. BSOD as soon as the level had loaded. And yes, the BSOD pointed the finger at nv4_disp.sys.

Question is... Where do we submit the memory dumps?

(and yeah, 79.11 is nice)

 

[imported_ST]

Originally posted by: BikeDude
FWIW: I got a BSOD under x64 when trying to launch FarCry. BSOD as soon as the level had loaded. And yes, the BSOD pointed the finger at nv4_disp.sys.

Question is... Where do we submit the memory dumps?

(and yeah, 79.11 is nice)

only 80 series has dual core support

 

[imported_BikeDude]

Originally posted by: ST
only 80 series has dual core support

You mean: Only the 80-series attempts to benefit from multiple processors and/or cores.

I have two Opteron 244 CPUs myself and the 7x.xx series work fine (stabilitywise), whereas 81.85 flat out fails.

I too am looking forward to a more multithreaded device driver from nVidia, but it would be nice to be able to submit bug reports to them. (Gainward have simply stopped replying to my e-mails, beyond their "81.85 is only for the game F.E.A.R. - use the old drivers instead!" response)