Problem with a dual monitor configuration?
Problem with a dual monitor configuration?
I've been experiencing this problem lately. My dual-monitor configuration often shows identical output on both screens, almost like they're connected to the same main display. No clear trigger seems to cause it, but certain actions increase its frequency. For example, putting my screens to sleep—especially after closing tabs in a game—usually triggers this issue. However, switching screens off and back on, or even while watching YouTube, it can occur too.
I've also noticed that restarting my PC during these moments sometimes resolves the problem, though only temporarily. This suggests a possible GPU-related issue, though I'm not entirely sure.
I ran DISM and SFC scans recently; the first scan a few weeks ago detected corrupted files during the SFC process, which I fixed and since then everything has been clean. I also performed a "dxdiag" check, but the results are unclear—I can't get GPU-Z to function properly and it keeps reporting an error about insufficient system resources.
I've completed a Windows update and driver repair, followed by another restart, but the issue persists. The motherboard is Gigabyte B450M DS3H, CPU is AMD Ryzen 7 2700, RAM is 16GB DDR4 at 2133MHz, GPU is AMD RX 580 8GB, power supply is Corsair CX650M 650W (80+ Bronze), storage includes a WD Blue 1TB HDD with 264GB free and a Kingston SSDNow V300 120GB with 10GB free. Monitors are an Acer KG271 C and an HP 22cwa; peripherals include a Perix MX-2000B mouse, Redragon S101 keyboard, Blue Yeti mic, and Corsair Void Elite headphones. I'm connected via a wired network and running Windows 10 64-bit.
Update your post with complete hardware details and operating system information. Provide PSU specifications, model, wattage, age, and condition of the original unit versus the new build. List all connected storage devices and confirm if their drivers are current. Share details about any monitors—make, model, capacity, and current usage. If applicable, note whether the monitors have dedicated drivers. Describe your network setup (wired or wireless). Indicate whether you use a wired or wireless connection. Ask about the functionality of the "WIN + P" command in opening the Project Window for options such as PC screen only, duplicating, extending, or showing additional screens. Also check if right-clicking an empty desktop area reveals a menu with GPU Control Panel and Display Settings. Review Reliability History and Monitor/Event Viewer logs to see if any error codes, warnings, or events precede the display reverting to duplicate mode.
The update confirms WIN+P functions correctly. Right-clicking doesn’t show extra options or a GPU Control Panel, but Display Settings are available. I’m not very experienced with the Event Viewer; the only relevant categories are under Warnings. Both "Kernel-PnP" and "Display" warnings appear. The Kernel-PnP alerts state that the driver failed to load for a specific device, while the Display warnings indicate the driver stopped responding but has since recovered. It seems the issue might be linked to driver troubleshooting.
I looked through the HID tree in Device Manager and spotted a device matching the error code path. It's labeled "HID-compliant headset." I really think this might be linked to your exes' Oculus headset, even though it hasn't been connected for over two years. It still appears as an option in my sound settings for Output and Input, which means my PC definitely remembers it. Hope this clears things up!
Good work!
Interesting point: The reincarnated Oculus might be responsible—wondering about the circumstances behind this development and why it seems so likely.
What to do:
In Device Manager, make sure "Show hidden devices" is selected. If not, checking the box could uncover additional entries.
A quick step would be to turn off that HID-compliant headset to see if the monitor issue disappears.
If that doesn’t help, removing the device entirely might be necessary. This carries some risk since we’re unsure what it actually is.
Right-clicking the device will open options, and you should see a "Properties" menu at the bottom.
Click on "Properties" and navigate through the tabs one by one.
Each tab reveals more details about the device or its drivers.
In the Details section, a dropdown appears with properties. Selecting one shows values that often include the manufacturer or product name.
You’re looking for confirmation that this is indeed the Oculus model. Once verified, you can safely uninstall the headset.
As a best practice, always back up important data at least twice to separate locations before making changes.
Check that the backups are accessible and intact.
Side note:
The power supply unit may be showing signs of strain after 8 years—this is something to monitor.
Another issue is the Kingston SSD. The boot drive is labeled "WD Blue" and marked as storage.
The SSD has only about 8% free space left, which is quite low for modern needs. Keeping at least 20-30% free space on any drive is standard advice.
Given the system’s age, failure is possible anytime.
The sudden reappearance of the Oculus without clear explanation is a red flag.
Make sure your backups are solid in case anything goes wrong.
I checked all the properties available, but there was no reference to Oculus. Both the manufacturer and provider are listed as Microsoft, and the driver is from 2009. This is really confusing! =D
I only turned it off temporarily, and nothing has changed yet. Only time will clarify if this stays the same. In the meantime, I’ll send the device details to the Microsoft site to see if anyone can identify it.
Thank you for your worry about my PC and for supporting me. I’ve been cautious for about three years now—just too stubborn to spend that much on a new setup. Hopefully she still has some power left.
This isn't exactly what I was expecting! =D I'm trying to keep it on, not turn it off. I'm still hoping for a reply on the Microsoft site before I remove that software.
Other error codes:
Errors:
-The OVRService couldn't start because it can't locate the required file.
-The AMDRyzenMasterDriverV20 also failed to start due to missing files (this keeps showing up multiple times).
Then some related issues with Razer Synapse (uninstalled since I no longer use it) and Secure Boot CA/Keys (recent issue with no resolution until next June).
Warnings:
-Certificate for the local system with Thumbprint 9f a0 2c a7 93 65 07 62 4d 0c a0 51 d5 8c ee 69 e0 46 6e 68 is nearing expiration or already expired.
-The rest are lengthy but don't matter much. The COM Server app lacks permission to launch, and there are "no internet connection" alerts, likely because it's still initializing.
I don't mean to spam this thread, I've just been working on this nonstop in the background. Took care of the OVRService error by disabling it in the services menu. (It was Oculus VR stuff)
The AMD error is just my CPU drivers, sorry.
The certificate for local system error is also still showing but I'm not sure that's important.
There was a new error though:
-Miniport driver failed to add device with status 3221225473
However it seems to have not triggered again after updating my CPU drivers.
It seems there could be an issue with the system drive. Files are being lost or damaged. Windows might continue running if it reverts to a default setting when configuration settings fail. Right away, back up all crucial data. Also, free some space on the 120 GB boot drive (Run "dism" and "sfc /scannow"). Windows may be able to locate and resolve the problem or missing files.