Board won't let me keep IGP enabled with GPU?

[pantsaregood]

I have an ASRock Z77 Extreme4 with an i5-2500K. Any time a GPU is in my PC, the IGP is completely disabled. I've attempted to enable "Multi-monitor support" in the BIOS, as well as setting the BIOS to default to the IGP, but neither appears to work. It seems the IGP is completely inactive whenever a GPU is installed, but it works fine otherwise.

Is this supposed to be the case? It's kind of annoying.

 

[jkauff]

I assume when you say "multi-monitor support" you mean "multi-GPU support".

I ran into the same problem when I upgraded my GTX 660 to a GTX 770, both Asus boards. Worked fine with the old card, and not at all with the new one. I have two monitors, and the only way I could get it working was to physically attach the IGP to my secondary monitor, set the IGP as default in the BIOS, and then in Windows set the displays so that my primary monitor (connected to the GPU) is the active display. System boots on the secondary monitor, then switches to the primary monitor when Windows loads. Stupid, but at least it works.

 

[javier_machuk]

i think what the OP meant is that he wants to use a discrete gpu alongside the igp.
OP: it is strange, it used to work in my pc, i5 2500k and asus p8z68-v mobo, i certainly had to enable some settings in the bios, but it was pretty straightforward. Have you searched if it is supported on your particular mobo?
Pd: i ended dropping it and using only the discrete gpu because of some driver conflicts between Intel and amd drivers, the downside is that the dGPU doesnt idle as well as with only one monitor connected to it

 

[piasabird]

At one point they were doing this with Virtu Software. With Sandybridge it use to come with the Motherboard.

 

[Phanuel]

At one point they were doing this with Virtu Software. With Sandybridge it use to come with the Motherboard.

Even with the Virtu software, to get the software to run it had to see the chipset enabled and to get the chipset to enable I had to do what jkauff did and it was a giant pain in the ass.

And all so I could do encoding which promptly crashed the system within 5 minutes of encoding, twice.

So I also gave up and just went back to dGPU only and longer encode times.

 

[jkauff]

Even with the Virtu software, to get the software to run it had to see the chipset enabled and to get the chipset to enable I had to do what jkauff did and it was a giant pain in the ass.

And all so I could do encoding which promptly crashed the system within 5 minutes of encoding, twice.

So I also gave up and just went back to dGPU only and longer encode times.

Sorry to hear that. QuickSync encoding with Handbrake works fine for me--assuming you're using Handbrake, are you using the latest nightly builds and the latest Intel drivers?

Although the QS video quality continues to improve, I only use it to quickly put a movie on my phone. x264 is still the quality king for archiving.