Windows 10: Bootvid.dll BSOD when switching KVM-2 computers-multiple builds

I have 2 computers which I control with a KVM. One computer has Windows 8.1, the other is currently on build 10166 but have tried last 3 builds and problem exists on all and series of events exactly the same no matter the build. Problem did not exist on earlier builds of Windows 10 as I have been testing Windows 10 since last fall..

System #1 Dell Precision T1500-Intel I5-quad core-8 gb ram- Geforce 210 graphics- dual boot Windows 8.1 & Windows 7.
System #2 HP Quad Core AMD-8gb ram-Geforce 8400 GS graphics Windows 10 build 10166 (upgraded from Windows 7)
Iogear 2 port KVM with audio

The first time I switched between the 2 computers Win10 blue screened indicating problems with bootvid.dll, pshed.dll, and atmfd.dll (Adobe Type Manager). . I ran SFC which found and fixed atmfd.dll and atmlib.dll. Now, when I switch the kvm I blue screen with errors left only in bootvid.dll and pshed.dll. This will happen every time I switch KVM. I have no problems with the Windows 8.1/7 computer.

Here's what I've tried:
Downloaded and installed latest video card drivers from Nvidia
Ran second SFC no errors.
Ran Memtest-no errors.
Ran chkdsk-no errors.
I have gone so far as to do a fresh install of Windows 7 on System #2 and then upgraded to build 10166 again but problem persists.
I have tried a second KVM switch.
Moved my husband's computer into my office and upgraded his Windows 7 to Windows 10. He has same video card, dual core Intel cpu 4 gb ram. Get exactly same error on his computer.

I have no problem switching Windows 8.1 or Windows 7 with either kvm switch, only Windows 10.

The only thing I haven't yet done is a fresh install of Windows 10.

I've spent at least 40 hours trying different builds and reinstalling from backup and am at my wits end. I can't understand why this did not occur in earlier builds. I can't figure out if it is a problem with the native vga driver in Windows 10 or with the Nvidia driver. Each of the video cards use the same 341.44 driver. It's going to be a bad deal if the Windows 10 RTM will not work with a kvm switch. Any of you guys have any ideas. I've exhausted all of mine.

:)

 

KVM switch USB not reinitializing

I've had the TK-409K KVM switch from Trendnet now for about a year and I don't have to switch between computers very often so I'm not sure when the problem started. I have a Window 10 desktop and a mac laptop hooked into the ports 1 and 2 of the KVM box.
If the switch is set to the Windows computer when the computer boots, the mouse and keyboard and monitor work with no problem. However, if I switch to the mac and then back to the Windows computer, the monitor works but not the mouse and keyboard. I have to
reboot Windows to get the mouse and keyboard to work again. When I switch to the Windows computer, the light on the KVM box never stop blinking. Does anyone have any suggestions?

 

Microsoft can you please, for the LOVE OF GOD, put in an option to disable automatic monitor detection in Windows 7 and up?

Have you thought about using a KVM switch in your setup?

That might alleviate the detection as the KVM switch should report to all your systems that there's a monitor there even if there isn't (switched away) at that particular moment.

Another option is to setup one computer as the "master" and then the other computers as headless and remote desktop into them.

I've done both types of setups over the years with multiple monitors and never had an issue.

 

Since no one offered any advice I am following up with what I found to be a solution to my problem. The problem was not caused by using a kvm switch but by the fact that somehow doing an upgrade as opposed to a clean install either does not overwrite all of Windows 7 dll's or drivers somehow get corrupted during an upgrade. Who knows? I do know that a clean install fixes everything. Since I was having the same problem on multiple machines I was going around in circles. I've always done clean installs in the past but since new builds have been coming so fast I chose to try the upgrade route just to see how it would go so that I could relate my experience to my friends who are planning to upgrade and who do not know how to perform a clean install. Well, now I can. My advice will be -DON"T!!
It can open up a whole can of worms.

 

The symbols for Windows 10 haven't been released yet, that's probably why no advice was offered. I haven't been able to read a single W10 crash dump as of yet.

 

I use a KVM with various machines - always plugged in to my primary (w10) machine which displays on primary monitor then secondary machine (I manually redo the VGA & USB cables as required) varies between XP, and Vista which displays on a secondary screen. When primary KVM option is selected then W10 screen display is extended across the two.

I know that W10 auto-detects input type; traditional mouse & keyboard vs touchscreen etc so im guessing thats why kvm buggers up display, esp at boot time no have to disconnect kvm from primary machine, fix then reconnect - annoying head-under-the-desk time wasting!! Anything I can do to improve and use as a more permanent fix?

Thanks.

 

You can use an EDID emulator putting it between your Win10 system and the KVM switch which does not have full-time EDID feeding via DDC channel of the display connection. Use the EDID emulator first clone the EDID table of your monitor. Then after the clone procedure, you can put it between your Win10 system and the KVM switch. Some EDID emulator may need an external power sources or using USB bus power to keep it alive.