I am not sure if this is where I should post this, but I am running out of options.
I recently bought a new computer and after configuration and setup, I began to have issues in ArcGIS Online any time I do any work in Experience Builder, Dasboards, or just webmap viewer. After regular use for a few minutes, the display will freeze up, then turn black for several seconds before the display re appears with a message from AMD stating the "AMD drivers timed out" (picture attached).
From there, any map I try to access either has an error message (simply unable to load) or a message saying "Unable to display, WebGL2 Support is Required", despite ArcGIS Online working fine moments ago. Next thing I tried was ArcGIS Pro. (edit) Pro was working as expected until this evening, now the same thing occurs, forcing me to restart pro. I was able to reproduce when editing a layout.
I have also noticed that the GPU will also spike up to 60-100% frequently when loading data, and in Edge the SSD will spike up to around 40%. Lastly, when I close the browser and re-open, I am able to access the map and go about my work as normal until it happens again. I have been able to reproduce this issue on Edge, Firefox, and Chrome and I have tried all these troubleshooting steps:
- Repair Windows
- Uninstall and reinstall each browser (using Revo Uninstaller)
- Bios update
- Reinstall AMD Drivers
- Boot into a Linux distro on a USB and try in Firefox - sill saw issue
- Clear shader cache
In this case I am working with a Framework 16 with an AMD Ryzen 9 7940HS. Graphics are integrated Radeon 780M Graphics. Windows is up to date, BIOS is up to date, AMD Drivers are up to date. I am at an absolute loss at this point and have no idea what to do now.
Hello all, thanks for your responses! I got in touch Framework and they second the thought that it was a hardware issue. With some other testing, I was able to replicate the issue outside of ArcGIS using 3D Mark and a few other programs as well. They sent me a new motherboard and after I replaced it, I have not seen the issue appear since.