Thread: Video Loss After Post and Windows Splash Screen Xenarc and EN15000

Do you get this problem after installing the Unichrome drivers? I've been using the generic drivers because of this issue. I have the VIA CN1300 and a Liliput.

Everytime I try to install the Unichrome drivers this problem comes back up. I can get the driver to work if I set the S3 tray utility to use both LCD and CRT, but that seems to work only for a short time. I also noticed only 640x480 is avalible (you can get other options by making the control list other modes). My BIOS is set to CRT, CRT+LCD did not work for me.

I'm wondering if it is switching to TV or LCD which the monitor can't output. It's obviously changing something in the BIOS, because I have to reset when it happens.

I've contacted VIA but they are not much help here. I'm sure the VIA drivers are faster than the generic ones.

I have my setup on the bench right now, so I'm looking into this again.

I've had the same problem after disconnecting my VGA plug without turning off the PC (don't ask me why it reacted like this)

I solved it by putting LCD+CRT in the BIOS

Try also to boot up in VGA mode....

Originally Posted by chrisyoon

Okay. First of all. It's a love hate relationship. I love the smallness of the Mini-ITX, but the lack of all aroudn support due to it's proprietary drivers and bios drives me nuts. Like I said, I feel as though I"m pretty adept to the whole computer scene, but this problem left me clueless.

I fixed it.

I don't understand it.

BUT.

It's fixed. For some reason, the Bios did NOT like the setting of "LCD" or "CRT" as a display setting. Go under the Bios, and you'll see what i'm seeing. if you get this problem, set it to "LCD + CRT". I have NO idea why this works, but it does. I tried an external monitor to no avail. every other setting, nada. Finally, after putting it back in the car, seraching every video setting available, the "LCD + CRT" settign on this motherboard solved the issue. It starts up, I get video, and no problems after numerous restarts.

Case solved.

If you have a CN700 video chipset and are not getting video after the windows splash screen, check to make sure your BIOS setting is set to "LCD + CRT". Don't ask, just accept. I now can enjoy my completely stealth mini-itx install finally.

Just so a good thread doesn't die...

I had the same problem after fiddling with the pc today. Was in the car and it seemed like the BIOS settings wouldn't stick, almost like a CMOS battery problem. Then just noticed it was just the video setting. Was about to reinstall windows but found this thread. Although it doesn't allow for the nicest boot up (my screen is shifted a little to the left during the bios loading) it does fix it past that. Good advice!

I actually just had this happen to me last night. I am still having a great deal of problems as changing the BIOS settings did not work. I also tried it with a different monitor and I had the same issue.

However, I was able to get it past the boot screen and use the system if I booted in safe mode. However, I am having trouble with the image being shifted quite severely horizontally to the point that I can't read much of the stuff during boot or in Windows.

I am spending the rest of the day researching this but would be grateful for anyone who could offer some advice.

It looks like I was having a problem with my video driver (EN1500G). I logged in through safe mode, uninstalled the video drivers and installed the stock ones from Windows and it worked.

I am however, still having trouble with the picture being severely shifted to the left horizontally right from the BIOS screen into Windows and CF. I will have to keep seeing if I can find something.

Okay I finally got this resolved. For me it was a messed up BIOS I guess. All I did was click on the reset to optimized defaults and everything is fixed. It now boots into Windows and the image is centred.

Just checking in on the threads that I reported the problems I had.

I swapped the MB from a Jetway to an MSI (fuzzy gm1) and just about everything went away. Its working as it should now.