You would think so, wouldn’t you?
Graphics drivers accumulate state bugs with uptime.
Even on modern computers, be then Windows, Mac, or Linux, you have to restart once in a while.
And multiple applications using the drivers at the same time (even in the background) can jiggle system bugs that otherwise wouldn’t be seen.
I’ve had YouTube Music, XSplit VCam, and Cubase all provoke bugs that don’t happen (or happen less) when they are not running. All of those use some graphics resources, and, more importantly, use the graphics drivers in slightly different ways. Meanwhile, IHV testing almost always just test in the context of a single application at a time.
That’s not what that log message is saying. The “64 bit atomics support” is not a requirement for D3D11.
The IID_ID3D11InfoQueue interface not being present may indicate some failure in device initialization earlier on. Note that the documentation for this interface says that you have to turn on debug layer in the D3D setup. If you don’t have that turned on / initialized, then that query won’t work, which might not even be a problem for the engine – you just won’t get told about certain rendering problems.
So, I don’t think you’ve found the correct log messages related to the problem yet. Everything you posted seems okay, at least as if it won’t prevent editor starting.
If I was seeing engine startup problems on this system, and I hadn’t rebooted yet, I would reboot first.
If that doesn’t fix it, and I hadn’t made any other software/hardware changes, then I would try clean uninstall and reinstall of NVIDIA drivers.
If that doesn’t work, I don’t know what I’d try next.