Timeline for Second monitor failure after crash
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2017 at 21:08 | vote | accept | Adriaan | ||
| Dec 8, 2017 at 13:39 | answer | added | Adriaan | timeline score: 1 | |
| Dec 7, 2017 at 10:31 | history | edited | Adriaan | CC BY-SA 3.0 |
added 369 characters in body
|
| Dec 6, 2017 at 23:20 | history | edited | Adriaan | CC BY-SA 3.0 |
Tweaked language
|
| Dec 6, 2017 at 20:47 | history | edited | Adriaan | CC BY-SA 3.0 |
added 101 characters in body
|
| Dec 6, 2017 at 20:47 | comment | added | Adriaan | @Ramhound yes, and I can even run my miner normally, with default settings, and it runs fine again. Also, I launched my ubuntu 16.04 build now, and I have a regular dual-monitor set-up with extended display working like a charm. | |
| Dec 6, 2017 at 20:43 | comment | added | Ramhound | You have verified the frequency of the clock is back to its default value? | |
| Dec 6, 2017 at 20:41 | comment | added | Adriaan | @Ramhound this was in the miner settings itself, so after closing the miner, there no longer was an overclock. | |
| Dec 6, 2017 at 20:39 | comment | added | Ramhound | The first step will be to reverse your overclocking. A 25 Mhz increase in clock frequency will not increase your computational hashing performance in the slightest. It, however, could be causing the behavior you have experienced, due to a variety of reasons. The fact it works within the BIOS/UEFI shell doesn't really indicate much honestly. What has to happen to display that vs the Windows desktop is completely different. | |
| Dec 6, 2017 at 20:33 | review | First posts | |||
| Dec 6, 2017 at 23:13 | |||||
| Dec 6, 2017 at 20:31 | history | asked | Adriaan | CC BY-SA 3.0 |