Try the dbg version of dgvoodoo and see the log if there is any error message in it. Probably something with a display mode / refresh rate that's unsupported with that monitor.
Wasn't exactly sure how to use debugview so I just did the whole log after clearing the screen right before starting the game and stopping the capture right after the game didn't load.
TBH, it's weird. The game does not crash but quits. I can only see one dgVoodoo error in the log, but I don't know what it is have to do with the monitor. Maybe it's completely normal, but a log from a monitor on which the game is running is needed to compare the two.
It's not aligned vertically with the other but it's offseted by 3 pixels. Maybe that? Or with Win10 your other monitor is the primary so this one does not have negative coordinates which the game might not like for some reason?
I don't know, but you can give it a go by experimentally change the order of the monitors, to have this one being the primary.
It should not be. But, you can compare the 2 logs coming from the working and nonworking monitors. If they are the same (dgV error appears even with the working case) then I don't have idea.