My monitor used to be 1680x1050 & 60Hz, now it is 1024x768 60Hz and i can't change it

[Dara Leonard]

One day my screen suddenly went black for a moment and then came back with the lower resolution. Then after a while my monitor would show a "no signal input" message and turn to standby mode. I had to turn it off and on to have the screen visible with the lower resolution before the "no signal input" message came back.

I have installed the newest nvidia drivers and drivers for everything else that needed updates, but i still can't change the resolution to higher than 1024x768.

I did remove the DVI-D cable and insert it in my monitor and that changed the resolution back to 1680x1050 for a few seconds before changing back to 1024x768.

I have also done a system restore to a point earlier when my resolution was fine. That didnt change anything.

I have also tried moving the cableinput on my computer to another output. After that i was able to change resolution to up to 1980x1080, which i wasnt before. However i changed my resolution to 1680x1050 and applied the changes, but then my monitor went in standby and the "no signal input" message came up. When i reset the monitor it was again in 1024x768 and the same problem occured.

These are my specs:

Operating System: Windows 10 Pro 64-bit
BIOS: BIOS Date: 07/11/13 16:53:06 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~3.3GHz
Memory: 12288MB RAM
Available OS Memory: 12170MB RAM
Card name: NVIDIA GeForce GTX 760
Display Memory: 8074 MB
Dedicated Memory: 1989 MB
Shared Memory: 6084 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor Name: Generic Non-PnP Monitor
Output Type: DVI

Although it say Generic Non-PnP Monitor, it is a Chimei CMV223D

The output is a DVI-D duallink, but my cable is a DVI-D singlelink. It has never given me any
problems before, but that may have changed.

I did go out and buy a new DVI-D duallink cable today, but nothing changed.

I would appreciate any help

 

[woj666]

I have had this problem twice. I think it was a result of Windows 10 going into sleep mode and confusing the monitor. I tried everything but I think what fixed it was unplugging the monitor from the power bar and letting it reset itself. Give that a try but I've had the same thing and it eventually fixes itself.

 

[Dara Leonard]

I have had this problem twice. I think it was a result of Windows 10 going into sleep mode and confusing the monitor. I tried everything but I think what fixed it was unplugging the monitor from the power bar and letting it reset itself. Give that a try but I've had the same thing and it eventually fixes itself.

That worked and I don't know why. i'll remember this.