Copy link to clipboard
Copied
Error: HRESULT error: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. Rebboted, widnows up to date, drivers up to date. Can someone please help me??
Copy link to clipboard
Copied
I'm receiving the same error. Windows 10 and Nvidia drivers are up to date with the latest drivers. The fact that this occurred after the latest Creative Cloud updates indicates a bug that needs to be addressed by Adobe! Please fix this.
Copy link to clipboard
Copied
Having the same issue, wich is really annoying. Hope they fix it soon.
Copy link to clipboard
Copied
As a followup to my previous post I would like to suggest running sfc /scannow from a Command Prompt run as an administrator. If you are unfamiliar with how to do this, you can type cmd in the search bar which will show Command Prompt as the best match. Then right click on Command Prompt and select "Run as Administrator". When the window opens, run the sfc /scannow command. In my case, apparently one of the recent updates/drivers did cause Windows folders security issues that needed to be corrected - here is an excerpt from the sfc log that shows the error:
"Overlap: Directory \??\C:\WINDOWS\System32\drivers\en-US\ is owned twice or has its security set twice". This was also noted for an additional Windows folder. After running the sfc command and rebooting I am no longer receiving the error. Hope this works for you.
Copy link to clipboard
Copied
Ho anch'io lo stesso identico problema!!!!
Copy link to clipboard
Copied
Running the sfc /scannow solved my issues. Thank you! No idea what it curred since I'm not the right person to interpret the logg, but worked it did.
Copy link to clipboard
Copied
Hi, I´m having the same problem and not really a tech-type for doing any system corrections as gregdes52 suggests 😞
I'm trying to find the older version but it seems to vanish from dropdown bars.
Is there any possibility and where I could download older version? Thanks a lot.
Copy link to clipboard
Copied
OH, I've just found older version in desktop CC, not online 😄 Anyway, I hope this problem with GPU device will be solved soon!
Copy link to clipboard
Copied
Many thanks gregdes52 for your suggested path. I ran the command and it found no issues. I'm on Windows 11, fully updated with all ASUS drivers fully updated. In my case this error occurred as I was moving screens around between my ASUS laptop (with 2 screens) and my Benq monitor. I'm going to try the simple, aka "dumb end user" reboot and see if that "fixes" it for now.
Copy link to clipboard
Copied
Unfortuately the "fix" I suggested recently was short-lived, as it returned with a vengeance after rebooting due to a Windows Update. I ran the sfc /scannow command again, and this time it had no effect! This bug only happens for me when running Bridge and selecting the first image - after which Bridge shuts down after I click OK in the error window,
Adobe - please fix this bug as soon as p[ossible as it is obviously affecting many users!!
Copy link to clipboard
Copied
Here's an interesting heads-up...In addition to the HRESULT error --I was having trouble with both Bridge and Photoshop not wanting to open. This morning I did an uninstall - powerdown - reinstall of a clean version of Photoshop and everything seems to be running faster/better/smoother. Not sure if the issue was related a funky upgrade process that was "fixed" by a full install...or if I'm now on a slightly different version of Photoshop...for reference I'm now on v24.0
Copy link to clipboard
Copied
Really looking forward to a fix for this.. I can't use Bridge AT ALL.
Copy link to clipboard
Copied
I got the same issues. I can't use Bridge at all.
Copy link to clipboard
Copied
Je to otravné a chce to opravit. ProsÃÃÃm. Stěžuje mi to práci.
Copy link to clipboard
Copied
I got the same error. I can't use Bridge
Copy link to clipboard
Copied
Getting same error and constantly crashing
Copy link to clipboard
Copied
As much as I don't like downgrading drivers due to possible security issues, I did so this morning to test if the latest Nvidia Studio driver (v522.30), was causing the HRESULT issue. If your PC is using an Nvidia graphics card, you can find previous drivers at this location: https://www.nvidia.com/Download/Find.aspx?lang=en-us#. Simply select your product series and type and current Operating System, and click Search and a selection of drivers will be displayed.
I actually tried two different drivers, one I had downloaded previously and had saved on my PC (v516.59), and the newest driver prior to the very latest driver (v517.40). After doing a "Clean Install", Bridge worked perfectly on both without any errors. To prove the latest Nvidia driver was the issue, I reintalled the latest Studio driver (v522.30), as a "Clean Install", and sure enough the HRESULT issue returned!
I then reinstlled the v517.40 version, and Bridge is again working perfectly. Some suggestions before attempting the driver downgrade: 1) If possible, back up your system or create a system restore point. 2) Close down all other running apps before reinstalling the previous driver. 3) Select the "Clean Install" check box as this will insure remants from the previous driver are not possibly conflicting with the current driver installation.
Good luck - I hope this works for those who have Nvidia graphic cards and are still experiencing the HRESULT error.
Copy link to clipboard
Copied
Thank you for sharing! I'd love to try this but I'm hesitant for reasons I'll state below and wondering if anyone else has this same issue alongside the issue in this thread.
I've been having many problems lately with my NVIDIA driver and Bridge/Photoshop. My Acer ConceptD refuses to make NVIDIA the primary graphics card no matter how many times I select this in the NVIDIA control panel. I finally figured out that the high-quality audio driver that comes with NVIDIA was causing errors so once I disabled that everything finally started working!!
However, after updating and running the new Bridge and PS, I started getting this error which seems to simultaneously kick the programs back to the default Intel driver. It also says my Intel is out of date but I have installed the most recent one. Also, it's defaulting back to the Intel driver even though I have it set to use the NVIDIA one.
I recently tried updating my NVIDIA driver but it caused over a month's worth of repair issues; after the "successful" update and prompted restart, the install completely wiped any trace of ANY NVIDIA driver! I did a system restore and plenty of other tutorials I read online but nothing worked. By some miracle, I was able to locate the original driver install that came on my computer and have that reappear (no idea how I did this). I know my NVIDIA driver is outdated (2020) but I'm terrified to try another update and have it totally wiped out again.
Has anyone else experienced this? Extremely frustrating spending $1200 on a laptop made specifically for creators yet nothing seems to be compatible. Work that I could have finished in 3 days has turned into 6 weeks of troubleshooting errors every single morning. I'm spending all my available work hours on troubleshooting these programs instead of my actual work and it's getting absolutely exhausting.
I've attached my DxDiag log for the crash that happened today. Any help or insight is greatly appreciated!!
Copy link to clipboard
Copied
Hi,
The mentioned issue is fixed in the latest patch release #13.0.1.583. Please install and confirm if that fixes the issue.
You can refer to the issues fixed in the patch at the following link https://helpx.adobe.com/bridge/kb/fixed-issues.html
Thanks,
Bridge Team
Copy link to clipboard
Copied
Rahul,
I'm sorry to say that not only did the latest Bridge update not fix the issue, it made it worse! Now it's forcing Bridge into "Software Rendering" mode, which basically eliminates any value gained by adanved GPUs. I've attached 2 files showing the error and the fact that I completed the upgrade to v11.0.1.383.
Please fix this properly - subscribers are paying for this app and can't use it properly!!
Copy link to clipboard
Copied
@Rahul Saraogi has there been an update for this error that continues with the latest update? Very frustrating paying money for these products that do not work and don't have a reasonable solution.
Copy link to clipboard
Copied
Hi all,
We're happy to announce the release of Adobe Bridge Beta (13.0.2.630). This update includes the fix for this issue. Also, this Beta release includes several bug fixes done in the 13.0.1 public release. For details, see Fixed issues.
Steps to install/update
Install: Go to the Creative Cloud desktop app and select Beta apps in the left sidebar of the Apps panel. Then select install for your beta app.
Update: Go to the Creative Cloud desktop app, click on Update in the left sidebar of the Apps panel and Check for updates. Then click update for your beta app.
Let us know if this Beta release resolves the problem for those affected, and share your feedback.
Thanks,
Mohit
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Mohit,
While the latest two versions of Bridge have improved the occurence of the dreaded "HRESULT ERROR", unfortunately it has not eliminated the error, as I have still on occasion experienced the error. Like a good former tech I attempted to duplicate the error, but was unable to do so. After unchecking the "Use Software Rendering" checkbox that got reenabled after the error, I rebooted, rechecked the box, and retested and was unable to reproduce the error.
Being that the Windows OS is still prone to memory leaks I can't help but feel that this error is more prone to reoccur after extended use of the Windows system without a reboot to clear memory issues, so I will retest after extended utilization of Bridge and Photoshop to see if indeed low memory availability is factoring into this issue.
I have 16GB of RAM on the laptop that reexperienced the issue, so that should be sufficient in most cases, but having worked with Windows for many years, I know for a fact that pretty much any amount of RAM will run into issues without an occasional reboot. I will continue to monitor the situation.
Thanks for your efforts,
Greg
Copy link to clipboard
Copied
Find more inspiration, events, and resources on the new Adobe Community
Explore Now