At first I thought my new monitor may be causing the problem because it started as soon as I got it, but after some messing around I managed to make my pc crash in all of the following circumstances:
1. With just the new monitor plugged in, running something in fullscreen.
2. With just the old monitor plugged in, running something in fullscreen.
3. With both monitors plugged in, running something in fullscreen on the new one.
4. With both monitors plugged in, running something in fullscreen on the old one.
These are the monitors:
Old one: PHILIPS 170s7fs/00, 4x3, plugged into my pc with a VGA cord, through a VGA - DVI-I adapter.
New one: ASUS VP228HE, 16x9, plugged into my pc with an HDMI cord, through a HDMI - DVI-D adapter.
Things it crashed with:
Warframe, The Witcher 3, Hearthstone and YouTube videos on fullscreen.
Note: I played Hearthstone in windowed mode for an hour and a bit to check my theory and it didn't crash. It usually takes way less time than that.
My system:
1. Motherboard: ASrock Z97 PRO4
2. Graphics card: AMD Radeon R9 270X OC DirectCU II, 2GB, GDDR5, 256bit, HDMI, 2xDVI
3. CPU: Intel Core i7-4790K, 40.GHz, Haswell, 8MB
4. Memory: Kingston HyperX PnP 8GB (2x4GB), DDR3, 1600MHz, CL9, 1.5V
5. Hard disk: HDD WD Blue 1TB, 7200rpm, 64MB, SATA 3
6. Power: Inter-Tech SL-700, 700W
I'm running Windows 10 64bit.
I have tried updating my graphics card and monitor drivers already.
Most of the time when it happens, the game freezes, then the monitor shows the "No VGA(or HDMI) input." message and then it just goes black and turns off. After this, sounds still play for a few seconds before they stop too. The pc keeps running, but I can't do anything and I have to restart it manually.
Very rarely it just shows a bluescreen of death instead.
I would appreciate any advice on how I could fix this.
EDIT:
It started crashing without even going fullscreen now, so I disconnected the ASUS monitor completely and restarted my computer. With just the PHILIPS monitor it doesn't seem to restart anymore - in fullscreen or not.
The new monitor seems to cause the problem. I read somewhere that it might be a problem with the voltage being sent back to the pc by the monitor.
1. With just the new monitor plugged in, running something in fullscreen.
2. With just the old monitor plugged in, running something in fullscreen.
3. With both monitors plugged in, running something in fullscreen on the new one.
4. With both monitors plugged in, running something in fullscreen on the old one.
These are the monitors:
Old one: PHILIPS 170s7fs/00, 4x3, plugged into my pc with a VGA cord, through a VGA - DVI-I adapter.
New one: ASUS VP228HE, 16x9, plugged into my pc with an HDMI cord, through a HDMI - DVI-D adapter.
Things it crashed with:
Warframe, The Witcher 3, Hearthstone and YouTube videos on fullscreen.
Note: I played Hearthstone in windowed mode for an hour and a bit to check my theory and it didn't crash. It usually takes way less time than that.
My system:
1. Motherboard: ASrock Z97 PRO4
2. Graphics card: AMD Radeon R9 270X OC DirectCU II, 2GB, GDDR5, 256bit, HDMI, 2xDVI
3. CPU: Intel Core i7-4790K, 40.GHz, Haswell, 8MB
4. Memory: Kingston HyperX PnP 8GB (2x4GB), DDR3, 1600MHz, CL9, 1.5V
5. Hard disk: HDD WD Blue 1TB, 7200rpm, 64MB, SATA 3
6. Power: Inter-Tech SL-700, 700W
I'm running Windows 10 64bit.
I have tried updating my graphics card and monitor drivers already.
Most of the time when it happens, the game freezes, then the monitor shows the "No VGA(or HDMI) input." message and then it just goes black and turns off. After this, sounds still play for a few seconds before they stop too. The pc keeps running, but I can't do anything and I have to restart it manually.
Very rarely it just shows a bluescreen of death instead.
I would appreciate any advice on how I could fix this.
EDIT:
It started crashing without even going fullscreen now, so I disconnected the ASUS monitor completely and restarted my computer. With just the PHILIPS monitor it doesn't seem to restart anymore - in fullscreen or not.
The new monitor seems to cause the problem. I read somewhere that it might be a problem with the voltage being sent back to the pc by the monitor.