New build was working just fine until last night, "DVI No Signal"

antoinetta67

Reputable
Feb 5, 2016
2
0
4,510
I built this computer about a week ago and upon its first test run I ran into the problem of the monitor displaying the message "DVI No Signal" which I fixed by reinserting the RAM sticks since they weren't in all the way. I finished up building the system and everything worked fine after that and I've been using it since then, except last night the screen went black. I could still hear my music playing in my headphones, so I restarted the computer and everything seemed fine again. A few minutes later, the same thing happened and restarting didn't help. Now the power button on the monitor goes orange instead of blue and the "DVI No Signal" message shows again. I tried removing and putting the RAM sticks back in since that fixed it the last time but nothing changed. I haven't touched anything inside the case since I closed it the first time and started using it.

Any help is appreciated.
 
Solution
Hi Alex,

I dunno if it will be of any help, but my mom had the same problem with her pc. After a little troubleshooting, it turned out that it was windows update that installed some new patch. That problem happened a couple of time. Only solution is to boot in safe mode, deactivate auto update, and uninstall the updates. Then reinstall updates one at a time (if many) with a reboot between each to see which one exactly causes the problem. Once identified, you simply block that update. Leave auto update of, and once a week, check it out manually.

She has an HP pavillon something.

niavlys

Reputable
Apr 3, 2016
10
0
4,520
Hi Alex,

I dunno if it will be of any help, but my mom had the same problem with her pc. After a little troubleshooting, it turned out that it was windows update that installed some new patch. That problem happened a couple of time. Only solution is to boot in safe mode, deactivate auto update, and uninstall the updates. Then reinstall updates one at a time (if many) with a reboot between each to see which one exactly causes the problem. Once identified, you simply block that update. Leave auto update of, and once a week, check it out manually.

She has an HP pavillon something.
 
Solution