Topic: Driver keeps crashing - Crimson 17.6.1 (Read 288 times)
Then you probably should use DDU in safe mode, you know that right? Incomplete uninstallation may cause a lot of issues. It doesn't take much time. You should give it a go once and see if it works for you.
Give Crimson 17.5.2 a try. It's way stable than anything out there for 6+ AMD rigs. I've had an uptime of more than weeks with this driver and Windows 10 OS. You remember of uninstalling display drivers in safe mode with DDU, right?
I never do it via safe mode just launch it in normal mode. I got caught out going into safe mode previously and took ages to fix it.
Give Crimson 17.5.2 a try. It's way stable than anything out there for 6+ AMD rigs. I've had an uptime of more than weeks with this driver and Windows 10 OS. You remember of uninstalling display drivers in safe mode with DDU, right?
I was running a 4 GPU rig fine and upgraded the mobo to support another 2 cards.
Reinstalled Windows, installed drivers 17.6.1(same version I was using on 4 GPU rig) and ran the driver patch. Now after about 5 - 10 minutes a GPU will fail in Claymore, i get a warning advising the display driver has stopped responding and sometimes the machine will hang. I tried updating to 17.6.2 but hash rate dropped down to 14mh/s.
Any suggestions?
Windows 10 Pro
Crimson 17.6.1
8GB ram
16gb virtual memory
I'm taking the risk and updating Windows to apply all teh current updates. I used a version 1511 installer so perhaps 1703 might resolve the issue
Reinstalled Windows, installed drivers 17.6.1(same version I was using on 4 GPU rig) and ran the driver patch. Now after about 5 - 10 minutes a GPU will fail in Claymore, i get a warning advising the display driver has stopped responding and sometimes the machine will hang. I tried updating to 17.6.2 but hash rate dropped down to 14mh/s.
Any suggestions?
Windows 10 Pro
Crimson 17.6.1
8GB ram
16gb virtual memory
I'm taking the risk and updating Windows to apply all teh current updates. I used a version 1511 installer so perhaps 1703 might resolve the issue
Jump to: