opening two documents in acrobat pro causes weird behaviour.

Adobe issue

Windows 10 21H11 19044.3086 Custom government SOE. (recently re-imaged)

Dell Latitude 7400 laptop, 32gb ram, I7 cpu, 2 x 27” external monitors connected via dell USB-C dock.

Acrobat pro DC v2020.012.20048

User views everything on the 2 large screens, the laptop screen remains closed.

User has 2 x 12mb files, approx. 60 pages comparing side by side (one on each monitor).

One of the docs is the original, a copy was made to update the contents using the original as a source. Both docs have Draft watermarks on all pages.

Documents contain text, pictures, graphs, diagrams.

Both files loaded into Acrobat and then one peeled off onto the second screen

After approx. 10 minutes of use the screens will flicker, at around this time the entire bottom half of the document will either grey out or white out, the page is still there, you can scroll up/down, but you now have a grey/white box instead of the normal content of text/pics.

Then things start to go wrong, the screens will both go black, sometimes the desktop will refresh, like the video drivers crashed and recovered, and the screens come back, most times the screens go black, stay that way and you will need to reboot the device.

Main laptop screen which is not used will also be black.

Tried duplicating the error on another identical laptop, slightly different result, but ultimately the program will crash the device. 

As a workaround I tried opening one with Acrobat reader and the other with Acrobat pro and that has seemed to work ok, but its a workaround, not a fix.

Error messages:

On start up both documents display this error message:

The original publisher is unknown and unknown software it was created with.

If you scroll up and down the document too fast. Document returns to normal on pressing OK.

Again, if you scroll up and down too fast. Document returns to normal on pressing OK.

When things start going wrong, either a black page or this, white with artifacts.

Multiple “Error processing page” errors pop up.

System resources remain nominal. No memory leak detected.