Nvidia GeForce 327.23 WHQL - Download & Discussion

nah its not that, this happened to me too in Win8.. It can be caused by "damaged" WMI

http://technet.microsoft.com/en-us/library/ff404265.aspx

or run CMD as admin and type in DISM /Online /Cleanup-Image /RestoreHealth

and later
sfc /scannow

then reboot and test again if it works ok.

 

Back to 326.80 after watching video\browsing freeze with this 327.23 WTFLOL crap :bang:

 

EDIT: Confirmed, it's not the 327.23 driver causing this. Just had it happen again after installing 314.22. Joy, some new random problem to find and fix now...

Thanks. I will keep that in mind if this continues. I just re-installed a fresh copy of Windows x2 (Win7 on one drive, WinXP and two other partitions on the other) yesterday, and decided to go with the 327.23 drivers from the start. The XP install seems fine, but it has 314.22. The Win7 install is/was wonky.

I already removed 327.23 and put 314.22 back as my first "test" and so far have not had a lock up...so far...it is back to working fine.

Anyway, yeah, I really didn't think it was the nvidia drivers causing it. But it is the only thing I changed from my usual rock solid install ritual that I could think of. All the obvious first tests, like "chkdsk /f" reports all partitions as good to go.

 

It can be your right menu has some dll causing it, just using Autoruns and check your Explorer dll.
---
So it might be other software that adding some dll into the right menu causing it, as you don't has any issues now.

 

This too,

handy app for that is shexview-x64
http://www.nirsoft.net/utils/shexview.html

 

Thanks for that too...had not thought of that! Will also keep that in mind. WinRAR and 7zip have added right click entries. I doubt, it's them, but...

EDIT: Sorry for the unintended thread hijack, but wanted to post the results of this little investigation in case anyone else stumbles upon this (from googling their problem). Using Shellxview to disable right click context menus while this problem was occurring.

1. It only seems to occur after Windows Search/Indexing is removed/disabled from "Turn Windows features on or off" (I know, I know...but I find it useless and like it OFF!).
2. It stopped when Alcohol 120's shell items were disabled with Shellxview.

 

So it's not just me getting the Chrome freezing then kernel crash to black screen having to wait for it to recover?

 

Display driver nvlddmkm stopped responding and has successfully recovered. This is the first time i ever got a driver crash and this was while playing Leage of Legends. Happened once last night but hasn't done it since.

 

Been experiencing a weird issue lately and don't know if it's these drivers or not. Basically, i have my pc connected to an AVR, connected to a TV and if i switch inputs on the tv, when i switch back, the PC display will not come back on. ATI cards used to be a nightmare for that, but it's never been a problem with Nvidia for me until now.

 

Anyone else getting Driver IRQ Not less or equal BSODs with this driver and leaving your PC on for more than a day?

 

Just a note -- I've removed 327.23 and reverted to 320.49 as I was seeing power level spikes up around 260% according to Nvidia Inspector. After reverting to 320.49, I'm not seeing these power spikes anymore. I also didn't see them with 314.22.

Card is GTX680 4GB, if it matters. Apart from this the drivers performed fine, and I don't know whether Power Level as Inspector reports it is related to raw juice going into the chip, but I'd rather be safe than sorry!

Will be looking forward to next WHQL to see if this is fixed.

 

327.23 with windows 8.1 pro

Since i installed windows 8.1 pro the driver work perfectly well but benchmark scores are lower.

 

En...
GPU or CPU performance loss?
And how about the lowest FPS?

 

No but I've been getting random driver crash/resets and strange flashing from occlusion culling in FFXIV when I've had it running for 8+ hours.

At this point I can't determine if it is the driver or my overclock because it is so hard to reproduce and nothing else seems to trigger this.

 

GPU loss.

Fire strike 4782 327.23 windows 8
with NVIDIA GeForce GTX 780(1x) and Intel Core i7-3770K Processor
Graphics Score
4945
Physics Score
11444
Combined Score
2256
Fire strike 4663 327.23 windows 8.1
with NVIDIA GeForce GTX 780(1x) and Intel Core i7-3770K Processor
Graphics Score
4814
Physics Score
10682
Combined Score
2242

Unigine Valley 60.4 windows 8
Unigine Valley 59.9 windows 8.1

 

I can't get Windows 8.1 to install it stops with 0xc190010 0x40017 and a message saying it couldn't install the Windows update and rolls back to Windows 8. I've googled everything nobody is very knowledgeable on this issue, nobody had a resolution on google, anyone else encountered this?

 

Thank for the information, so most graphic card driver don't "ready" for WDDM 1.3.

I hope it is not some feature that adding in WDDM 1.3 and causing this issues.