@D Fosse Understood. Since we had just solved one case for this same error we thought we could at least provide that information here in case some could benefit from it. Other than ruling out Mac cases, we have no way to know if that Bridge Label issue may be affecting some Windows users here so we felt it best to post that information.   The Windows Bridge Label issue is 100% reproducible. So this only affects Windows users unable to use Camera Raw at all.   Regarding what issue may be affecting some or most users here, the main difficulty is that for us to be able to diagnose the problem we typically need a case we can reproduce on one of our machines. Short of that, other avenues are possible but tend to be rather painful and time consuming (but we can speak of that later if necessary). So it's worth asking first if anyone has any tips or specific steps on how our team can reproduce the problem. We're happy to try whatever steps people provide. It would be great if any such information allowed us to reproduce the problem, though often in cases like this steps that reproduce the problem for a given user on a given machine do not necessraily produce the same results elsewhere (for a variety of reasons). ... View more

The error message discussed in this thread is generic. It means that Ps has detected that something has gone wrong with Camera Raw plugin and that "something" was not caught earlier by the plugin. So the exact issue experienced by users seeing this error can vary.    The Bridge Label issue that Sameer posted about is an issue that engineering recently resolved for a Windows customer seeing this error message. It is a Windows-only issue and so cannot possibly apply to Mac users experiencing this error, but MAY apply to some Windows users. So it is just something that Windows users experiencing this error should check. A fix for that Windows issue (related to the Bridge Labels) will be included in an upcoming Camera Raw plugin release. ... View more

Possibly check to see if the motherboard mfr has an updated BIOS? Here are some additional threads which contain other ideas people have tried: https://www.reddit.com/r/AMDHelp/comments/jzfgj1/ryzen_9_5900x_random_crashes_with_whea/ https://www.overclock.net/threads/gigabyte-x570-aorus-xtreme-owners-club.1729350/page-42       ... View more

Hi Greg,   The issue is very likely that problems occur during some level of "heavy" use. Most programs do not make heavy use of most of the system computing resources. For example, browsing the web or sending email or editing documents are not going to place a heavy strain on the system. When it comes to applications making heavier use of the system resources (or perhaps using some system resource that other programs are not using) our sense, based on reading the postings discussing these types of crashes, is that the problem is more likely to occur under such heavy-load conditions. Why ACR is triggering the issue and some other resource intensive program such as Photoshop alone may not be doing so is not something we can speak to as we don't have a full understanding of the underlying hardware problem.   Some of the posts in the threads linked in a previous post above (about people experiencing similar crashes on systems with AMD CPUs) indicate many people encountered such problems when running certain games or running certain math-heavy stress test tools. Those are programs which tend to stress the system by crunching a lot of numbers very quickly, much as some Adobe applications do.   Whether you are talking to AMD directly or the manufacturer of your machine or motherboard, I would think it would be enough to indicate to them that you are getting this Hardware error in the Event Viewer when using a certain program or programs. Such an error should never be happening and it indicates a problem with either the hardware or the configuration of the hardware. Software should not be able to cause this type of a hardware error.   As previously mentioned, the ideas people have tried to resolve these problems are varied and they are discussed at some length in the previously listed threads and likely on other online forums. Clearly you have pursued undoing some of the Overclocking but there may be other ideas there to try.   It sounds like you may have assembed this system yourself. I would think a good place to start would be with the motherboard manufacturer as they could have experience with this type of problem and they may be able to provide some recommendations.   Finally, I see that in a recent reply above you listed your CPU as an "AMD Ryzen 7 5800X". My original interpretation of the family/model codes in the Computer Info.txt file you had provided in your original post here had me thinking it was a different AMD CPU. Chances are that either the data in the .txt file I viewed was wrong or (more likely!) I simply interpreted it incorrectly, but a double check in your windows system info to see what type of CPU Windows thinks is installed couldn't hurt. My guess is that it will be AMD Ryzen 7 5800X as you have indicated but on the offhand chance it's not it could be another possible avenue to pursue. ... View more

Hi Greg.   Thanks for the Event Viewer data you provided us. It seems to indicate a HW problem of some type (either with the CPU or with some type of interaction between the CPU and some other HW).   A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor APIC ID: 8 The details view of this entry contains further information.   So this is apparently saying a problem related to the CPU was detected.    The computer info you provided in the original post above indicates you have an AMD CPU (which looks to be either "Athlon" or "Opteron", if we're interpreting the codes listed there correctly).   A quick web search on "Cache Hierarchy Error" turns up (relatively rare but still plentiful) cases of AMD cpu users having very similar problems, many (but not all) from gaming.    Here are just a few relevant links / discussions we quickly found: Ryzen 5 3600 Fatal hardware error - Cache Hierarch... - AMD Community WHEA: Cache Hierarchy Error Processor Core  https://community.amd.com/thread/232625  https://www.reddit.com/r/AMDHelp/comments/hq7jcu/cache_hierarchy_error/    Given the Event Viewer report data, reading through these links strongly suggests to us that these are the same types of problems you are seeing also when it comes to the reboots.    The resolutions of problems in these reports is pretty varied. Some modified overclocked settings (do you know if you have an overclocked machine?). Some replaced CPUs. Some replaced GPUs. Some found that disabling Windows Fast Startup feature in the system's Power Options (and/or the BIOS?) fixed the problem for them (for example, see https://www.windowscentral.com/how-disable-windows-10-fast-startup). There are probably other ideas worth trying in the links above so I would encourage you to follow this trail.   We're not experts on this CPU hardware subject so we're now mainly repeating things we read in the links above. But here are some thoughts we have...   Have you built this machine yourself? If so, definitely read through some of the discussions linked above. If you purchased the machine you may want to contact the manufacturer and indicate you are experiencing these types of HW problems.   Some things to try (that we read about when reading through some of the links listed above)...   If you know the machine has been overclocked, maybe backing that down would be good. I'll assume henceforth that this is NOT the case.   Disabling the Windows Fast Startup as mentioned above in the Power settings (or maybe even the BIOS?) would be a simple starting point to see if that could either fix or improve the issues as a couple of people reported that helped them.   Otherwise some people found changing the GPU in the machine could help.   Others had luck changing the CPU but if you did not assemble this yourself you should have the manufacturer deal with that if it reaches that point.   Please let us know if there is anything else we can do to help but given the HW error report it appears to us to be an issue of a hardware problem with your system.   Also, if you do find a resolution which works telling us about it here would of course be helpful, as would marking this reply as the Correct Answer should it prove to be so.   Bruce Kaskel - Senior Computer Scientist II - Camera Raw Engineering - Adobe Inc. ... View more

Checking RAM: it's worth doing but I personally think it's a long shot in this case. So it would fall into the category of due diligence in order to rule it out. The old fashioned way required using a test tool like MemTest86 but I believe modern versions of Windows have a built-in ability to schedule a RAM test. A few minutes of searching online should indicate how.   Does Ps have the ability to do active logging as you describe... I don't work directly on the Ps product but I'm not aware of such a thing, no. Besides, if the overall problem is of a similarly random nature as the case we examined it is not clear that would help (if things just go boom at a seemingly random time, logging may not provide much insight).   For any case of a Ps crash (as opposed to a reboot), please always submit it with your email and also let us know about it here. No worries about pointing us to ACR. We need to follow every lead and reviewing that case did provide a lot of good insight for us. It did help to demonstrate how strange a case this is.   But the reboots suggest that something much more insidious is going on as modern operating systems such as Windows 10 are purposely designed so that programs cannot take down the entire computer as they effectively operate in a sandbox which insulates each program from the OS and all other programs. There should be no way a program by itself can reboot the machine (that happening usually implies a driver problem, an OS problem or a hardware problem, though of course Ps or another program could somehow be triggering it).    REBOOTS: Have you reviewed the Event Viewer to see what it may say about the reboots? Here is a link to a page which provides some guidance on how to do this.    Bruce Kaskel - Senior Computer Scientist II - Camera Raw Engineering - Adobe Inc. Votes   ... View more

Hi Greg,   The engineering team has analyzed the Crash Report case you encountered as this provides us with data of what is happening on your machine at the time (unlike the reboots, where we don't really have any data).   The Crash Report case showed that in that instance it crashed while using ACR inside Photoshop. It is a unique report in our database (we have not seen any others like it). The short story is that something went wrong very deep inside with addresses set up when Windows launched the program. The technical description here would be that the process IAT (import address table) contained a bad address to a Windows system function but the important thing is that this is not common and it is quite strange. From the look of it, it is probably not due to faulty RAM (something always worth checking) but rather it looks to us as if the address was specifically changed or simply not set correctly (which would be quite odd). So this suggests the issue is not really directly related to ACR, even though ACR code happened to be operating when the crash occurred.    It seems likely that this is somehow connected to the machine reboots although we haven't been able to think of anything which would cause both types of issues.   A program like Ps should not itself be able to trigger machine reboots. Such a problem is more commonly caused by a driver problem (or worse). I don't doubt what you are experiencing but so far we have not heard reports of this happening to anyone else.   Please keep us posted if you find out anything more. Jeffrey mentioned the possibility of a "damaged OS installation". Based on the types of severe problems you are seeing we can't help but wonder if there is some problem there.   Respectfully,   Bruce Kaskel - Senior Computer Scientist II - Camera Raw Engineering - Adobe Inc. ... View more

Thank you for following up. It is difficult to diagnose the problem further without access to your machine. Would you be willing to run some experiments using custom components we could provide? ... View more

Hello.   I would like to clarify about the "lighting controller" issue. The fact that we had found a report of a lighting driver which had caused a very similar problem, along with the fact that you actually have one (or more!) lighting controller drivers installed (though not the same one as in the old report) did seem like a promising lead. However be aware that this could be a red-herring... the problem could be due to any driver, though I expect it to be a driver that is not a very common one out in the world (since otherwise more people would be seeing this problem). So there's no need to overly focus on the 'lighting' aspect... it was in my mind merely a reasonable place to start.    Though it is admittedly a bit of a pain, We recommed a sequence of uninstalling a driver that you can later re-install, restarting your machine (don't skip that step) and then testing for the crash again. The evidence we (Adobe) have reviewed shows that an obscure control value on one of your CPU cores is getting corrupted. A driver bug (in some driver on the system) is the most likely explanation... in fact I encountered this EXACT type of problem happening in a bad printer driver years ago, so though it would seem extremely unlikely, I have actually seen this issue once before.   Other possible explations? Well, it could be an Windows OS bug (VERY VERY VERY unlikely in my opinion) or a faulty CPU (pretty darn unlikely, IMO).   If your are unable to pin down a driver on your system we could explore other ideas to try to find out what is causing this, but those likely won't be simple. So our thinking is that at this point in time, the most efficient way forward would be to follow the advice above to try to determine if some driver installed on the system is causing the problem (uninstall unecessary drivers for now and update any drivers on the machine which you feel are required). ... View more