Hosting Parsec On A Laptop With Both Nvidia and Intel GPU's




  • Avatar
    Captain Clay

    Doesn't work for me, after doing this i get error -13008

  • Avatar
    Farya Wolyo

    Same for me, I'm on an Alienware M14x with discrete and integrated graphics, I disabled my Intel graphics on the device manager, though my friend received the same error as prior upon attempting to join my session.

  • Avatar
    Benjy Boxer

    Can you check your Nvidia settings to make sure it's outputting to your monitor at 1080p 60FPS?



  • Avatar
    Brett S

    I had to do the opposite on mine, disable the Nvidia GPU and use the Intel one.  The Intel GPU is directly connected to the HDMI port on the laptop so the HDMI port does not function if you disable the integrated graphics.  The intel IGPU acts as a frame buffer for the Nvidia GPU and sends the frame to the HDMI port.  This is a problem for people that use their laptop as a desktop and also the reason why nvidia 3d vision does not work even though the GPU supports it (PITA). 

  • Avatar
    Duncan Armstrong

    Edited - Found a very simple workaround.

    1. Attach a display or display dongle to your gaming laptop.
    2. Set it up as your only active display (disable the integrated display's output), using hotkeys on your keyboard. For instance on a Razer blade, it's Fn+F4. It'll take a few toggles, as Windows has permutations for Internal, Clone, Extend, and finally Secondary Only.
    3. Once the internal display turns off, you should be good to connect - give it a shot.


    • You do not need to go into your GPU management settings to force Parsec to use the dedicated GPU. Just let it use the integrated GPU.
    • The hardware encoder should be used anyway. You can validate this by checking the Parsec console for SRV.encoder and its returned value.
    • You can also check with the Task Manager, under Performance, and note that GPU 1 (assuming this is your dedicated GPU) will show activity, particularly when doing something like dragging a window around. The integrated GPU should remain idle.
    • If you force Parsec (or its executables, rather) to use the Nvidia adapter, you might have anomalous behavior in the Parsec session, like black windows for the Console and the Parsec interface. 
    • It's helpful to also get a fallback remote desktop solution in place. Windows' Remote Desktop works nicely enough (just check that it's enabled or working).

    My prior post/experience, in case it helps anybody:

    Going to add a funny experience for a Razer Blade with a GTX 1060 - basically even if you set up Parsec's executables to use the Nvidia GPU (via Nvidia control panel), still no dice on connection.

    To add, the integrated GPU is used for the display framebuffer, so by disabling the IGPU, Parsec will connect just fine via the Nvidia GPU, but at the cost of the machine becoming unmanageable physically/locally (stuck display/image, due to a now-nonfunctional display buffer).

    In Parsec you can re-enable the Intel GPU and get everything working again. Maybe do that at the end of your session.

    I'm not aware of any suitable workarounds beyond this, but it might somewhat work for some of you.

    Oh, and if you get stuck in a situation where you cannot reconnect to re-enable the IGPU, try RDP, or boot up into safe mode, then re-enable the IGPU device.


Please sign in to leave a comment.