- Joined
- Mar 18, 2008
- Messages
- 5,717 (0.97/day)
| System Name | Virtual Reality / Bioinformatics |
|---|---|
| Processor | Undead CPU |
| Motherboard | Undead TUF X99 |
| Cooling | Noctua NH-D15 |
| Memory | GSkill 128GB DDR4-3000 |
| Video Card(s) | EVGA RTX 3090 FTW3 Ultra |
| Storage | Samsung 960 Pro 1TB + 860 EVO 2TB + WD Black 5TB |
| Display(s) | 32'' 4K Dell |
| Case | Fractal Design R5 |
| Audio Device(s) | BOSE 2.0 |
| Power Supply | Seasonic 850watt |
| Mouse | Logitech Master MX |
| Keyboard | Corsair K70 Cherry MX Blue |
| VR HMD | HTC Vive + Oculus Quest 2 |
| Software | Windows 10 P |
Came home to another random BSOD, due to my recent experience with dying processors and motherboards I was scared as f*uck. It took me a good 30 seconds to read the actual BSOD message was video scheduler error or something. Upon restart the Crimson driver mentioned it has been reset. Well I did not even touch that thing after getting system ready, and I did not even game/work on the rig.
So tried a few graphic benchmarks. Yep, getting BSOD left and right. DDU uninstalled the 17.10.1 and tried several recent betas. Nope, all of them are unstable. Finally revert back to 17.7.2 driver and the stability problem is finally solved.
Seems the Crimson driver after Vega launch has gone completely nuts for the Fury/X. Locking up HBM overlocking and bugging out freesync. RTG needs some serious kicking in the nuts to smart up.
So tried a few graphic benchmarks. Yep, getting BSOD left and right. DDU uninstalled the 17.10.1 and tried several recent betas. Nope, all of them are unstable. Finally revert back to 17.7.2 driver and the stability problem is finally solved.
Seems the Crimson driver after Vega launch has gone completely nuts for the Fury/X. Locking up HBM overlocking and bugging out freesync. RTG needs some serious kicking in the nuts to smart up.