This post is more than 5 years old
6 Posts
0
4441
February 26th, 2017 00:00
Alienware X51 R3 no boot when connected to 4k TV via HDMI
I have an issue with booting my X51 R3 when connected to my new 4k TV via HDMI. The System does not boot up, no matter if TV ist turned on or off. I have to disconnect the HDMI cable (tried DVI to HDMI as well - same issue) - wait until the System booted to Windows 10 , then connect it and after this Point all works as usual.
Given this fact, i can't get into BIOS - except connecting another TV - i found some Post here concerning the same Problem, but not found a common solution.
I have actual Bios 1.2.8 as well as actual Nvidia Drivers (genuine GTX 970).
Very rarely the System managed to boot into Windows - but no TV Signal present, but it was able to connect to my PC via TeamViewer - and could see inside the Device Manager that the Geforce has been turned off due to "the device reported Problems and was disabled" - after rebooting without hdmi cable - worked again normally.
I connected a Dell Vostro 460 to the 4kTV via HDMI - boots fine - no issues.
So i can only guess it's a BIOS related Problem - but no Change since 1.2.4 what i could read here :/
will be grateful for any advice!!
gertsch
6 Posts
0
February 28th, 2017 12:00
Seems like i was lucky, and stumbled over a solution on another Forum.
Long Story short, switching the "Output Color Format" inside the Nvidia Control Panel from RGB to YCbCR444 did the trick. After the next complete shutdown i could see my whole boot process again and entered Windows with HDMI connected all the time :) (did 2-3 cold and warm boots to be completely sure)
it was mentioned in the guide Tesla posted, that RGB did not work properly on Samsung TVs earlier, only after a Firmware upgrade... so maybe LG are on their way there too :/
thank you all!
Tesla1856
8 Wizard
•
17K Posts
0
February 26th, 2017 11:00
Research EDID problems over HDMI. Could also be HDCP over HDMI problem, but I don't really think so since you are not even getting to playing any HDCP Protected Content.
Not being able to see BIOS over HDMI is a common problem with any video card.
Do you have a proper .INF file installed for that HDTV display?
gertsch
6 Posts
0
February 26th, 2017 12:00
Thank you for your Reply! I still have the generic Plug & Play Monitor .inf installed... TV is LG OLED55B6V - actual FW, no further Drivers availabe from LG. Never had an issue like this before on predecessor TV and PC, always using HDMI Connection.
i came accross some Posts from People blaming UEFI secure boot - what do you think?
Tesla1856
8 Wizard
•
17K Posts
0
February 26th, 2017 13:00
1. Unfortunate. If Windows-10 can't Plug-and-Play the LG OLED55B6V ... and download a INF (sort of like a driver) from Windows Update, then LG is your only hope.
2. That's nice. Yes, I use HDMI with various computers with no problems also, but usually only "Home Theater" related. For desktops I would rather use DVI or DisplayPort.
3. Doubtful, but possible. I don't own your LG-HDTV or a x51-R3 to test it. I can tell you I have a Lenovo X1-Carbon here with UEFI and SecureBoot active. It's HDMI output works fine with my Onkyo-607 AVR/Amp (which has both a HDMI 1080p plasma and projector connected). Also, works connected directly to Epson projector via HDMI.
Tesla1856
8 Wizard
•
17K Posts
0
February 26th, 2017 15:00
Here is a guide I Googled.
Actual menus might be a bit different on your model TV, but basically the same steps.
hardforum.com/.../
89fordprobee
1.2K Posts
0
February 26th, 2017 15:00
well sitting here on a X51 R3 .. on a Samsung UN55HU8550 4k of course and have no issues but I have a high priced hdmi cable , but even sending via wireless connection to the tv I have no issues with the 4k (after booted of course) and I run my Ark Survival on it.. my daughter loves watching the dino's lol
so as said its possible tv is issue as I have heard of it before ..
89fordprobee
1.2K Posts
0
February 26th, 2017 16:00
even sending via wireless connection to the tv I have no issues with the 4k (after booted of course)
when using the wireless intel ...
with hdmi I boot no issues never have but it is an older tv like the OP's original tv but windows does see it as a proper Samsung tv with model # ..
Tesla1856
8 Wizard
•
17K Posts
0
February 26th, 2017 16:00
People think that all HDMI cables are the same, but it's simply not the case. I like heavy gauge ones, short as possible, and non-Redmere or anything tricky. They should be spec-ed to handle highest version HDMI port on component in system (v1.4, v2.0, etc.) as well as associated higher bandwidths.
Tesla1856
8 Wizard
•
17K Posts
0
February 26th, 2017 16:00
1. OK
2. While not a true solution, sounds like a simple HDMI Switch might be an acceptable work-around. It might needed to be spec-ed to handle HDMI v2.0.
Tesla1856
8 Wizard
•
17K Posts
0
February 26th, 2017 16:00
Can you elaborate? Sounds like it works for OP also "after booted".
Tesla1856
8 Wizard
•
17K Posts
0
February 26th, 2017 19:00
Pretty sure that requires a proper INF file. So, they are available for some HDTVs.
gertsch
6 Posts
0
February 26th, 2017 23:00
thank you for yor Inputs so far !
i googled EIDI - couldnt find anything, but i think you meant EDID? as far i could understand this handles some Kind of handshaking protocol between PC and TV - so it seems the TV can't negotiate with the BIOS, but later on with the Nvidia Driver?
1. Installing a proper INF file for the TV - wouldn't that only affect handling when Windows has already started? Last Samsung TV worked only on Plug&Play Monitor.
2. HDMI cable is an actual 2.0 - was my first thought when expericencing this issue, but no Change... even tried with a DVI cable - same there....
When trying with an elder Dell Vostro (GTX 750 ti) on the same TV - everything from boot on was visible - so i kinda checked off TV Settings and cable being responsible.
I planned for my next Weekend:
1. Routing HDMI cable through my soundbar (has HDMI in and out)
2. switching the GTX 970 into another Desktop (w/o UEFi) and see what happens there
thanks so far!
Tesla1856
8 Wizard
•
17K Posts
0
February 28th, 2017 12:00
Thanks for posting the solution.
Yes, that link had lots of info for anyone who cared to read it. As you can see, it can be any number of things.
Basically, I think it was failing the initial HDMI negotiation, due to what the HDMI devices considered incompatible capabilities or even just settings.