- Joined
- Dec 7, 2014
- Messages
- 181 (0.05/day)
- Location
- Tokyo, Japan
| System Name | Workstation |
|---|---|
| Processor | Intel Core-i9 9960x |
| Motherboard | Asus WS X299 SAGE |
| Cooling | Custom |
| Memory | Crucial Ballistix 128 GB (8 x BL2K16G36C16U4B) |
| Video Card(s) | NVIDIA RTX 4080 Super |
| Storage | Intel Optane 905P (SSDPED1D015TAX1), Nextorage NE1N4TB, 4 x DC HC570 |
| Display(s) | NEC PA272W-BK-SV, Eizo CG2700S-BK |
| Case | Fractal Design Define 7 XL |
| Audio Device(s) | Asus Essence STX II, Sony WH-1000XM, Audio-Technica ATH-M50x |
| Power Supply | Seasonic PRIME TX-1300 |
| Mouse | Logicool G502 X |
| Keyboard | Logicool G810 |
| Software | Windows 10 Pro 64-bit 22H2, several Adobe software, RawTherapee |
I did. I haven't seen anything wrong about 466.11 yet, other than a very few crashes with Cyberpunk 2077 (v1.21 Hotfix), but that was something I expected.Someone else can test these with a 1080 Ti, I'm too lazy to test every driver version.
My result with 466.11 after 2 days:
- Fixed raw images showing up as black (blank?) images in Bridge and Lightroom for me. Not Adobe's fault. This issue was from the Re-Bar driver (465.89), which I uninstalled immediately. I have no idea when this issue started or from which driver or branch, but 441.66 and 456.71 (Studio driver) didn't have it.
- Cyberpunk 2077 ran fine, but with a very few crashes. Something I always expected from Cyberpunk 2077. Probably memory leak like some people reported in CDPR forums, Steam forums and Reddit, because the crashes seemed related to opening map or trying to hack objects (cameras, turrets, etc.). Free roaming and other things didn't crash the game.
- Didn't have problem running and playing Nioh 2, and so did 441.66 and 456.71.
- This is not a studio driver, but I didn't have problem with Photoshop at all. Re-Bar driver sometimes caused Photoshop not detecting and using my GPU. Restarting Photoshop fixed it.
- Yakuza 6 crashed a lot, but I'm sure it didn't have nothing to do with the new driver. QLOC being the studio porting the game does have something to do with the game's problems (SEGA, please stop using them!).
- Didn't have problem with Firefox (browsing, watching videos, etc.). I don't have Chrome and would rather not have one so I couldn't test the driver with it. Didn't test the driver with Edge either.
I came a long way from 441.66 and 456.71. From what I read, many other Pascal users have been using 456.71 too although they're using the Game-Ready driver, not the studio one I had. But I'm confident to replace my 441.66 and 456.71 with this driver. Hopefully nothing will go wrong or bad in many days to come. Seems a very good and stable driver for me, but keep in mind that I don't play games a lot and often (always have a lot of projects to work in) so I have no idea if this driver works great with many games.
Your result may be different from mine. I say it doesn't hurt to try. You can always go back to 456.71 or whatever driver works for you if 466.11 gives you problem.
@qubit is our resident “throw all caution to the wind” driver tester.
I always have a feeling of admiration towards those who always take one for the team.
