- Joined
- Sep 17, 2014
- Messages
- 22,438 (6.03/day)
- Location
- The Washing Machine
Processor | 7800X3D |
---|---|
Motherboard | MSI MAG Mortar b650m wifi |
Cooling | Thermalright Peerless Assassin |
Memory | 32GB Corsair Vengeance 30CL6000 |
Video Card(s) | ASRock RX7900XT Phantom Gaming |
Storage | Lexar NM790 4TB + Samsung 850 EVO 1TB + Samsung 980 1TB + Crucial BX100 250GB |
Display(s) | Gigabyte G34QWC (3440x1440) |
Case | Lian Li A3 mATX White |
Audio Device(s) | Harman Kardon AVR137 + 2.1 |
Power Supply | EVGA Supernova G2 750W |
Mouse | Steelseries Aerox 5 |
Keyboard | Lenovo Thinkpad Trackpoint II |
Software | W11 IoT Enterprise LTSC |
Benchmark Scores | Over 9000 |
How the heck did that happen? Was the OS installing updates when the TDR happened and you didn't give it time to recover and turned the system off?
In the early Vista days nVidia wasn't the only one with poor drivers, pretty much all the hardware manufacturers got caught with the pants down. Even Intel's drivers caused shitloads of BSODs back in the day, their storage drivers for Vista were pretty bad in the beginning.
It is always funny when someone is commenting on something, trying to make a big deal about a problem they've never even experienced. When the crash happens you don't loose anything. The browser doesn't crash, the computer doesn't need to be rebooted. You can't be right in the middle of writing a long post, chrome just freezes for a second, then the monitor goes black, and 10-15 seconds later it comes back on and your right back where you left off with a message saying the nVidia driver crashed and recovered. The crash is a driver crash, not a browser crash or a system crash. The driver recovers and you keep on typing.
I've been dealing with it on my main system for about a month since they put out the first driver with the problem, it has happened 100s of times, and not once has it failed to recover.
Not entirely true, the Chrome bug also manifests itself as a reboot loop where you need a hard shut down / power down up to your PSU switch. I have had this one and it was gone one driver iteration later (the second release after 350.12). I also see others who have seen this bug crash their system or hard freeze. And this was on Kepler (!) not Maxwell. As far as I could distill, for Kepler it's now gone, has been smooth sailing for about a month now.