Hi,my pc. 9900K turbo on 2x16GB DDR4 GSKILL 3000 XMP Corsair 850 RmX Asus Prime Z390-A Aorus Rtx 2080 Ti ( stock ) Using 417.35 or 416.94 gpu drivers, looped Timespy graphic test 2 crashing display driver or making BSOD on Aorus 2080 ti stock. No oc,stock. Also using 417.71 the newest no crashing. Games are stable. Also no bsod, no crashing nothing on 417.71. Could 417.35 or 416.94 merely be exposing a hardware defect in my new card or is the driver just bugged? Today using 416.94 drivers, when looping timespy Gpu test 2 it crashed display driver after 5 hours.
So event said: Display driver succesfuly recovered............. 2 the same events in the same second.
That`s not detailed info. What was the bugcheck code, faulty module? PS In case you don`t know where/how to view, you can use these apps https://www.nirsoft.net/utils/blue_screen_view.html https://www.resplendence.com/whocrashed
Could be that your gpu is slowly going to die, did u had this problem before with another gpu ? [before the rtx 2080ti]
Aorus 2080 ti became available a few weeks ago in one well known online store in my country. I rembember 1080ti Aorus having great reviews, but on this one, out of 10 comments from buyers 4 had to send it back, 3 beacause of artifacts/crashes, one for extreme overheating. I was thinking about it, as the beginning of the year has been good on the money and at 3440x1440 I'm in a weird spot with my 1070ti. It might be coincidence, or people mostly posting on store comments or threads like this only when there's a problems, so info is biased, but still not convinced to pull the trigger on it It might be a bad batch of cadrs giving problems
So i tested on 411.70 10 hours and no crash. Also 417.71 the newest its fine too. After 3 hours looping , Bsod was: DPC Watchdog Violation 416.94 So what now ?
If you can't reproduce the crash in newest drivers you're fine. And if drivers that give you problems are not even latest ones it's even less of a problem. Probably someting bugged in 416.94
Also ...............its weird because it was crashing in the same hour and minute after 2 hours 30 minutes BSOD : ). Anyway on 417.71 and 411.70 looped 14 hours and no BSOD so no reason to rma? yes temps 72C on load
If you can't avoid the crash in some drivers and can't reproduce in other ones it's hard to blame the hardware. Not impossible, but unlikely, it is much more likely that it's a driver problem.
there's the latest bios dated : 11 January 2019 ------------------------------------ + Install: ------------------------------------ Also check: Run the test when XMP enabled OR disabled (check both one at a time) ------------------------------------
@jmmy23 DPC Watchdog Timer is "utility" in Windows which raises BSOD when it decides that DPC (Deferred Procedure Call - a mechanism utilized for the second stage of interrupt handling) tooks too much time. So we can guess that some drivers you tried are badly coded. https://docs.microsoft.com/en-us/wi...bugger/bug-check-0x133-dpc-watchdog-violation
hey guys. I updated uefi bios to newest and testing on 416 .94 that was crashing previous and now on 3 hour its not crashing. So its possible that updated bios helped?