Rendering and driving a panel can be different jobs
Many laptops list both integrated graphics and a discrete GPU. The discrete GPU can render frames for an application while the integrated adapter drives the built-in panel. Some designs provide a hardware switching mode, and external ports may connect through different adapters. Seeing two entries in Device Manager is normal; it does not prove that one driver is redundant.
Record the exact laptop model and graphics configuration. A generic tutorial about the same chip does not establish how that laptop routes its panel, HDMI port, or dock. Consult model documentation for any hardware switching options before changing them.
Map each display and application
Use Settings > System > Display > Advanced display to inspect the connected adapter reported for each active display. For an application's rendering preference, inspect Windows graphics settings and, where useful, Task Manager's GPU engine while the application is running. A graphics preference can influence rendering but does not move a physically wired panel to a different GPU.
Compare built-in and external screens individually. If a game renders on the discrete GPU but the internal panel shows a black image, investigate the presentation path and panel state rather than immediately declaring the discrete adapter absent. If only a docked monitor fails, test its path directly.
Check package branches against system integration
The laptop maker may provide coordinated integrated and discrete packages for brightness, panel switching, power, and sleep. GPU vendors may provide a newer supported branch for an application. Neither source is universally superior for every laptop. Match exact model support, Windows build, hardware ID, and release notes to the original symptom.
Do not uninstall the integrated adapter to force a game to use the discrete GPU. On designs where the integrated path drives the panel, that can remove a functional output. Preserve the previous official packages and a recovery route before changing graphics software.
Isolate rendering from output and power transitions
Compare the application on internal and external displays, and compare simple desktop output with the demanding workload. A failure only in one app can arise from its settings or compatibility, while a panel that loses brightness controls after a driver change suggests system integration. Repeat sleep/wake and docking if either was part of the original failure.
Test one documented graphics preference or supported package change at a time. Write down which adapter rendered the task, which adapter was associated with the display, and whether the image, brightness, and battery behavior changed. An improved frame rate with broken wake is not a clean success.
Keep a visible recovery path
Before installing, save work, retain a prior supported package, and know how to access Windows Recovery if the normal desktop disappears. If the image fails only after the new package loads, use the graphics recovery guide and reverse the single timed change. Do not layer another generic graphics package over an unexamined regression.
If artifacts or missing output appear before Windows starts, or the panel fails with several known-good modes and recovery environments, stop software experiments and contact the laptop maker with the topology and test results.