You have a number of options for doing this, but I think the cheapest may be to use a $35 Chromecast. According to this site full desktop sharing is a beta feature of Chromecast:
How to setup desktop screen sharing to Chromecast?
The setup of desktop screen sharing is very simple and
straightforward. You do not need any additional software or hardware.
In Chrome browser, click the Google Cast button, you will see the
available Chormecasr devices in your network as shown below.
You can click the arrow icon in the right. The options will be shown
Cast current tab. This is the default. The Chromecast tab will be cast to Chromecast.
Cast entire screen (experimental). This will share the desktop screen, not just a Chromecast tab, to Chromecast.
Audio mode. This will only send audio output to Chromecast. The screen or Chrome tab will not be shared.
You can click “Cast entire screen (experimental)” to start the desktop
Of course, before sharing the desktop screen with the Chromecast
device, there is a warning message letting you know that Google cast
wants to share the screen and audio output (with Chromecast). You must
click “Yes” to approve the screen sharing.
Once the desktop screen is shared to Chromecast, Google cast will
indicate the screen is being captured and played on the Chromecast
At the same time, a notification of “Google cast is sharing your
screen” will be shown on your desktop.
Now, the the desktop screen and audio is shared to Chromecast. You
should be able to enjoy the video or music on your TV.
There are other options specifically designed for wireless screen sharing, like Intel WiDi. However, your computer must support it and the TV may need an adapter. This page has a good list of other alternatives.
On your laptop, all your displays are connected to the Integrated GPU (the Haswell - based Intel HD Graphics 4600), something you can confirm by:
Navigating to the "Set PhysX configuration" tab on the Nvidia Control Panel. It will show you how these displays are wired to the Intel Integrated Graphics controller.
Opening the Intel HD Graphics control panel, from where you'll be able to adjust advanced display settings for the 4k panel you have.
You mentioned that the 4k display panel is connected via DisplayPort, correct? In that case, you'll want to turn on DisplayPort MST (Multi-Stream Support) IF such an option is available. Its' often enabled for Daisy chained setups and where the same panel is fed by two DisplayPort 1.2a cables.
An example of such a setup where DisplayPort MST would be of use would be with a single Dell Ultra HD 4k Monitor P2715Q 27-Inch Screen LED-Lit Monitor , or a daisy-chained setup such as this one here.
It would also be useful if you shared your monitor's make and model here, might help with troubleshooting.
Notes from Intel's Quick Reference Guide for the Intel 4th Generation Core Processor Graphics, Haswell:
The main requirement for supporting 4K@60 on DP SST (single-stream transport) is that the core display clock (CDCLK), which is configured by SBIOS, must be set high enough to drive the dot clock required by the mode. Usually 4K@60 has a 536MHz dot clock, so it requires a 540MHz CDCLK.
If the system OEM did not configure the CDCLK at 540MHz for thermal, power saving, or other reasons, then the system will not be able to drive 4K@60 over a single DP stream. Also, Haswell ULT (-U) and ULX (-Y) are limited to 450MHz and 337MHz CDCLK, so they will not be able to do 4K@60 SST. ULT should still be able to do 4K@60 MST, though. ULX can’t because 4K MST still requires HBR2.
This shouldn’t affect DP MST tiled displays because for those, Intel uses two streams, each for one half of the display, reducing the pixel clock.
Additionally, 4K support is only available on the Core processor graphics. Celeron and Pentium do not support 4K. All Core Haswell processors will support HBR2 with the exception of Haswell ULX.
Here is a reference guide that can be of help with Intel's Collage Mode, which controls DisplayPort's SST and MST modes.
As far as I know, without additional hardware this is not possible. I'm sorry.