ASUS VG248QE Not Detected

DeluxeEditon

Reputable
Jun 9, 2014
4
0
4,510
I just got my VG248QE monitor in and it is saying DVI not detected as soon as Windows 10 loads. The monitor starts up and works fine while I'm in the BIOS. My second monitor loads up and becomes my main (what i'm typing this on now). The ASUS VG248QE is not detected at all by windows, I don't see it when I go into my display options.

Can anyone help me, it would make my day! :)

Setup:
R9 290
Asrock 990FX Extreme 2
AMD 8350
16 gig ram
800 Watt PSU 80%
 
Make sure your bios is set to use PCIE graphics.
It really sounds like a driver issue with windows. New graphics card/drivers recently?

Boot to safe mode and uninstall all graphic drivers, then install fresh drivers from AMD. You might need to disabled anything intel under display adapters in device manager. My amd drivers didn't like when windows saw the integrated intel gpu and windows kept loading generic drivers for it.
 
It doesn't even show the monitor in Catalyst. My 290 does not have an HDMI out, however i did try it with my active display port adapter i used with eyeinfinity, but same issue. I used CRU and DDU uninstalling and reinstalling the drivers in safe mode.

Interesting note. The monitor worked fine and was detected in safe mode, and out of it while Catalyst was uninstalled. As soon as I reinstalled the drivers the issue returned.
 


I got mine last week and didnt have any problems. Did you try the default windows detect/ identify monitor option?
 


lol what the heck!!! im literally using my monitor on Win 10. ! Are you sure your windows recognizes it?
 
That's a crock. You can run Windows 10 on a 20yr old CRT. It's a display, has absolutely nothing to do with what picture is on the screen as long as the picture is in a verified resolution at the correct frequency. It's not the monitor that has anything to do with win 10,its the adapter powering it. Basically she had absolutely no idea what your issue could have been so fell back to a 'form message'.

Go to amd and dl an older set of drivers, one from 6 months ago or so and try that. Sometimes new drivers do buggy things to older cards.