NVIDIA GeForce 304.79 Beta Download & Discussion

[ManuelG]

Originally Posted by PowerK

Hi ManuelG.

The sudden hard reboot occurred again while playing Diablo III. The same behavior - screen froze and my monitor (U3011) displayed "no signal" and then 1~2 seconds later my PC rebooted. This seems to happen once a day while playing Diablo III.

My GTX690s are @ stock. This sudden reboot has never happened with my system before. (301.42 WHQL, 304.48 BETA were all fine in terms of stability). This hard reboot only happens with 304.79

Here is a screenshot of Diablo III profile in nVIDIA Inspector I was using.
http://i.minus.com/ibasotGDumXZkB.JPG

Background program/application while I was playing Diablo III were
- MSI AfterBurner v2.2.2
- RealTemp v3.70
- Fraps v3.5.0
- Microsoft Security Essentials v4.0
That's it. Nothing else. Processes in Task Manager under Processes tab are all standard processes in Windows 7 x64 SP1.
This main PC is for PC gaming only. I have a second desktop (2600K with 560Ti) I use for other stuff.

Device drivers I currently have installed are as follows.
- Intel INF Update v9.​3.​0.​1019
- Intel Management Engine Interface v8.0.3.1427
- Intel RST v11.1.0.1006
- Realtek HD Audio R2.68
- Broadcom BCM57781 Ethernet v14.8.4.1

Intel iGPU is disabled.

If you need further information, please let me know.
I'm going to revert back to 304.48
Thank you for your attention.

Thanks. Unfortunately most image hosting sights are blocked by NVIDIA IT. I'll check the image when I get home. The settings you are using inside of NVIDIA Inspector, if you revert back to default, does the Diablo III issue go away?

[Darren Hodgson]

Originally Posted by ManuelG

Most likely Tuesday

Thanks.

[PowerK]

Originally Posted by SirPauly

The response gets noticed, too PowerK!

Good to see you here as well, Pauly!

[PowerK]

Originally Posted by PowerK

After updating my driver from v304.48 to v304.79, I had a sudden reboot while playing Diablo III yesterday. (This is the first time ever happened with my system).
Screen froze and my monitor (U3011) displayed "no signal" and then 1~2 seconds after my PC rebooted.

I don't think this is a Diablo III problem as it's my understanding that application cannot cause BSOD nor reboot in Windows 7. I'm thinking perhaps it's the driver v304.79
I was playing Diablo III with adaptive v-sync on, 4xMSAA + 4xSGSSAA forced through nVIDIA Inspector (in-game AA off).

Originally Posted by ManuelG

Please let me know if it occurs again. Also, are you overclocking your GTX 690 graphics cards? If you can reproduce this problem, does the problem go away when returning the clock speeds to stock speeds?

Originally Posted by PowerK

Hi ManuelG,
Thanks for the response. Greatly appreciated.

No, my 690s are at stock speed.
I'll definitely let you know if it occurs again.

Originally Posted by PowerK

Hi ManuelG.

The sudden hard reboot occurred again while playing Diablo III. The same behavior - screen froze and my monitor (U3011) displayed "no signal" and then 1~2 seconds later my PC rebooted. This seems to happen once a day while playing Diablo III.

My GTX690s are @ stock. This sudden reboot has never happened with my system before. (301.42 WHQL, 304.48 BETA were all fine in terms of stability). This hard reboot only happens with 304.79

Here is a screenshot of Diablo III profile in nVIDIA Inspector I was using.
http://i.minus.com/ibasotGDumXZkB.JPG

Background program/application while I was playing Diablo III were
- MSI AfterBurner v2.2.2
- RealTemp v3.70
- Fraps v3.5.0
- Microsoft Security Essentials v4.0
That's it. Nothing else. Processes in Task Manager under Processes tab are all standard processes in Windows 7 x64 SP1.
This main PC is for PC gaming only. I have a second desktop (2600K with 560Ti) I use for other stuff.

Device drivers I currently have installed are as follows.
- Intel INF Update v9.​3.​0.​1019
- Intel Management Engine Interface v8.0.3.1427
- Intel RST v11.1.0.1006
- Realtek HD Audio R2.68
- Broadcom BCM57781 Ethernet v14.8.4.1

Intel iGPU is disabled.

If you need further information, please let me know.
I'm going to revert back to 304.48
Thank you for your attention.

Originally Posted by ManuelG

Thanks. Unfortunately most image hosting sights are blocked by NVIDIA IT. I'll check the image when I get home. The settings you are using inside of NVIDIA Inspector, if you revert back to default, does the Diablo III issue go away?

ManuelG,

Ok.

I think the problem is related to forced anti-aliasing.

I've tried AA compatibility of 0x004412C1 and 0x00400080 for Diablo III. Both resulted in random reboot during playing. (4xMSAA + 4xSGSSAA + adaptive v-sync forced through nVIDIA Inspector).

After disabling AA in nVIDIA Inspector (default NVCP settings), the reboot problem goes away. This is on 3770K + 690 Quad-SLI @ 2560x1600.

This only happens with Diablo III for me. Other games I've tried recently such as Crysis, Mafia II, Just Cause 2 and Skyrim all ran ok with 4xMSAA + 4xSGSSAA @ 2560x1600.

I've tried it on my second PC with 2600K + 560Ti as well. With 560Ti (v304.79), I can force 2xMSAA + 2xSGSSAA + adaptive v-sync and Diablo III runs ok without any reboot issue. Although 560Ti does not provide smooth frame rate at 1080p with 2xMSAA + 2xSGSSAA at 1080p, it does not exhibit stability problem.

So, I'm guessing.. it's forced anti-aliasing problem with multi-GPU setups. (2-way, 3-way and/or 4-way/Quad)

I sincerely hope this gets fixed in the future driver release as FXAA implementation in Diablo III isn't very good, IMHO. (Also, any chance we can get SLI AA working with Diablo III in the future?)

EDIT : Oh, and as for the Diablo III profile in nVIDIA Inspector I was using, let me type them out here for you.

Ambient Occlusion compatibility = 0x0000002A (Diablo III)
Antialiasing compatibility = 0x004412C1 (Diablo III)
SLI compatibility bits = 0x02400005

Antialiasing - Behavior Flags = None
Antialiasing - Mode = Override any application setting
Antialiasing - Setting = 4x [4x Multisampling]
Antialiasing - Transparency Multisampling = Disabled
Antialiasing - Transparency Supersampling = 4x Sparse Grid Supersampling

Texture filtering - LOD bias (DX9) = -1.000

Ambient Occlusion setting = Quality
Ambient Occlusion usage = Enabled
Vertical Sync Tear Control = Adaptive
Vertical Sync = Forced on

[wsgroves]

Going to try these out when I get home.
ManuelG, is there a Tera SLI profile update coming?
Mine runs ok but not like it should with 670 sli.

[GhostXL]

Originally Posted by wsgroves

Going to try these out when I get home.
ManuelG, is there a Tera SLI profile update coming?
Mine runs ok but not like it should with 670 sli.

The developers of TERA are not interested in Official Multi-GPU support sadly. Let's hope this changes.

[ManuelG]

Originally Posted by jez_uk1

Does this fix the problem with 304.48 where World of Warcraft randomly closes without error?

We are not tracking that issue. Just the error where it crashes with "nvlddmkm" error. More details?

[ManuelG]

Originally Posted by -Tj-

Fear 1 multiplayer DM (2xaa, no shadows, rest high) @ 1920x1080 Windows 7 64bit, Geforce 460gtx 1gb, i7 2600k, 8gb ddr3 1600mhz,

Slower performance compared to 304.48, any map. Slowdowns happen after few moments when in heavy combat (10+ players).



And 570gtx has slight stutters when entering new areas with high fps fluctuations - 150fps to 300fps. Mostly in Evacuation and Construction map.

I need to know the before/after difference. 10%? 25%? 50% slower?

[RedPyramid]

Originally Posted by ManuelG

Most likely Tuesday

Does part of your "maintenance" work involve translating the Dead Sea Scrolls into binary code? holy sheeite

[ManuelG]

Originally Posted by mantismu

I'm experiencing audio drop outs, pops and clicks after updating from 304.48

This is occurring on two different external USB audio devices.

LatencyMon reports the nvlddmkm.sys as the culprit with an execution latency of over 5ms. Every other driver is under 1ms latency.

Can you repro this on onboard audio controller?

[-Tj-]

Originally Posted by ManuelG

I need to know the before/after difference. 10%? 25%? 50% slower?

Hi,

Im not sure, but he's a long time player so im pretty sure he is accurate.

Judging by his reaction i would say 30-50%.


Im gonna re-edit this post when i know more.

EDIT: he said ~ 25%.

---
Also can you check my side problem with FEAR1, i suffer from occasional micro stutters when i get max fps or the other way around. I somehow "eliminated" most of it by limiting the game to 2 cores and threaded optimization - off..

[ESlik]

Originally Posted by ManuelG

Most likely Tuesday

Who needs the Nvidia support forum? We have "The MAN" right here!! Welcome ManuelG.

[rewt]

Originally Posted by Cyberdyne

No it aint.

For me this is the first driver where adaptive vsync options are visible in the control panel.

Originally Posted by ManuelG

Thank you very much for your kind words and for choosing NVIDIA. Our company is constantly looking for new ways to reach out to our customers so you will continue to see more and more of us on the internet interacting with our users.

Thanks for your support!

[wsgroves]

Originally Posted by GhostXL

The developers of TERA are not interested in Official Multi-GPU support sadly. Let's hope this changes.

Aye, I figured that to be the case. Thanks for the heads up.

[rognarok]

I've noticed with World of Warcraft with 304.79 my CPU temps are about 10c higher and there is more CPU usage then release drivers. Roughly about 20-30% more then usual. The unusual thing is the temps stay roughly the same if I'm in a deserted area with little going, or in a 25 man raid. I only did the first boss in raid finder, and I'm not sure this is affecting performance, but it's a bit weird seeing so much of my CPU being used

[psyside]

Originally Posted by ManuelG

Most likely Tuesday

Hello ManuelG and first of all thanks for the great support, to have an Nvidia employ and help us directly is simply great! please report back to your HQ that we really really like this, and that you should extend the number of members to other forums as well, just like hardware companies with their hardware rep members.

Now, slightly offtopic, can you report that we would really love to see Metro 2033 improvements, seems like Nvidia cards are not doing so great in this title, and i would love to play this game in its whole glory when my GTX680 DCII arrive in 1 week from now. In the past Nvidia has produced some stunning resluts regarding performance improvements just by drivers updgrades, so i think it should not be problem for you guys

Thanks in advance.

[Bentez]

So I've lost 400 P score points and 1000 graphics score points in 3D11 after installing 304.79 over 304.48. Has anyone experienced this? I tried reinstalling but got the same scores.. I may rollback to .48s

[Cyberdyne]

Unless you are only using the PC for competition or something, what is the point of ditching a driver set over a single benchmark?
Did you lose similar performance in other games? I know I didn't lose any.

[D4rKy21]

I got some weird sound cracking in games with these drivers, sort of lag spikes :S

This is the first driver that cause me this problem rolling back to 304.48

[Bentez]

Originally Posted by Cyberdyne

Unless you are only using the PC for competition or something, what is the point of ditching a driver set over a single benchmark?
Did you lose similar performance in other games? I know I didn't lose any.

I'm testing games at the minute. benchmarks only matter to give an indication of performance, though generally 3D11 is a pretty good yard stick of how good a driver is..

[jez_uk1]

We are not tracking that issue. Just the error where it crashes with "nvlddmkm" error. More details?

Hi ManuelG,

When installing 304.48 myself and a friend both noticed that World of Warcraft would occasionally and randomly terminate without any error or message. The window would just vanish as if ALT+F4 was pressed. I reverted back to 301 to fix the problem.

I've also noticed that is World of Warcraft is blurred when run in DX11 fullscreen mode on my Surround setup but only when the game is run on the center screen. i.e. Surround desktop is 5760x1080. If i run WoW in 1920x1080 it is correctly scaled on the center screen but everything is blurry. This only seems to affect DX11 mode, it's fine in DX9. I've had this problem with all drivers I've tried since purchasing the two GTX 680's.

[D4rKy21]

@ Manuel G i have some kind of sound interruption with these drivers crackling sound effect, its like tik tik tik, in every game i just tested it with Call of Pripyat Max Payne 3 and games like Metr0 2033 Serious Sam BFE, i didnt had this problem before with beta 304.48.

[ipredator]

@ManuelG, do you know when the first official 680M driver is up on the nvidia site?

[NeoandGeo]

I still seem to be crashing with these after about 45 minutes to an hour of Battlefield. Same with the 304.48. The crash is weird too, it just freezes and kicks me to the desktop with the app still running. I have to alt-tab and then close it through task manager.

[skippy_watford]

Just bought a new 680 to replace one of my 570s. Now have a KFA2 4GB 680 EX OC (68NQH6DN6DXZ manufacturers code) and I've left one of the 570s as a physx card (MSI Twin Frozr III 1280Mb).

I've been having a huge amount of crashes. Around about one per day. I think I've determined it's the beta drivers since although they were stable when I had the 570s in SLI, after going back to 301.42 the only game that's crashed has been Crysis 2 which is notorious for being unstable. I'll give it a few more days to be sure though. With the Beta drivers basically all my DX10/11 games are crashing - DX9 games seem stable although I haven't played them too much to be sure.

The games are freezing at random points for a second or two and then the screen goes black as the 680 resets itself and I have to ctrl-alt-del to get the task manager and close whichever game it is.

Sometimes get an apphang windows message, although not always. But when looking in windows reliability I get the following....

Source
Windows

Summary
Video hardware error

Date
‎07/‎07/‎2012 02:42

Status
Not reported

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Files that help describe the problem
WD-20120707-0242.dmp
sysdata.xml
WERInternalMetadata.xml

Extra information about the problem
BCCode: 117
BCP1: FFFFFA80078734E0
BCP2: FFFFF8800F55BAC4
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


This happens in all the DX10/11 games I've played within a short while using either of the beta drivers

Battlefield3/Batman AC/Metro 2033 and Crysis 2 (although that still crashes with 301.42 and is notorious for crashes so may be the game)

Are you aware of other people having these crashes, as I'm also liasing with the company I bought the 680 from as it could, of course, be an issue with my card although the temperatures etc. are all fine with the card never getting higher than 75.

Edit:The crash with Crysis 2(using 301.42) I've just noticed was slightly different in the windows reliability utility.....
Source
Windows

Summary
Video hardware error

Date
‎06/‎07/‎2012 20:40

Status
Report sent

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Extra information about the problem
BCCode: 117
BCP1: FFFFFA800E889010
BCP2: FFFFF8800F5C84D4
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys
Server information: 669632d9-86ae-4f0f-9416-4db15cea15cb


As I said any advice would be appreciated.