- Aug 10, 2009
I'm immediately blaming the drivers in this case because it *is the drivers*.
No, i'm not using displayport, i'm using DVI. I also spent near on three months troubleshooting this issue when I first built the PC when it was a known issue with the drivers at the time. The same thing happened on three different cards (two entirely separate MSI 7870 HAWK and a Gigabyte 7950), persisted through *three* complete format/reinstalls of windows, and went away completely the minute I installed 12.10. Yes, I tried the monitor with another PC, and it didn't do it. Yes, I tried another video card (a 5870) in the PC, and it didn't do it, nor does it do it using the ivy bridge I7's integrated graphics. Even the keyboard locks up, can't change the lights or the macro bays on my Sidewinder x4, but I *can* access shared folders over the network while its locked up. Yes, it still does it even if I use HDMI or VGA. Yes, it does it with two separate, known good PSUs. No, it's not easily reproducible, it'll hard lock one out of maybe 10 times the monitor turns itself off. System Sleep/Hibernate are both totally disabled, it is strictly the monitor "turn off after 15 minutes" setting in windows. Occasionally if I leave it sitting frozen long enough, it will throw a DRIVER_POWER_STATE_FAILURE BSOD with error codes pointing to, you guessed it, the video card drivers.
I've been without this issue for months and months since installing 12.10. Not an hour after installing 13.1, it's back.
So yeah, maybe i'm not the one making unfounded assumptions about people here
Relax! I wasn't talking about you in particular. I was only commenting on the post I quoted.