As an update/closure I've stopped trying to diagnose the issue. My belief is somewhere in the adobe installation or third-party plug-in something was corrupted. I ended up wiping and reinstalling windows and my adobe programs, not installing the MotionArray plug-in (this was the last one to install when things crashed occasionally). I had been using the Dropbox plug-in and it had been stable and fine. Prior to reformatting the system i had uninstalled the plug-ins one at a time and it did not change the failure rate. Currently I'm back to editing in a stable way on windows 11 with premiere 2024 and encoder 2024 but wasted a ton of time and didn't learn anything from a crash perspective. thanks to those that offered some diagnosis methods. ... View more

performed a memory test, no issues found ... View more

thank you. i just did a hard drive check and no faults were found. gonna check out RAM diagnostics next. ... View more

I've been able to document a few of the sad-face blue screen codes, they differ on each crash: K_MCODE_EXCEPTION DRIVER_IRQL_ACUSS.. MEMORY_MANA... SYSTEM_SERVICE_EXCEPTION If it's not a sad-face blue screen Adobe Encoder just closes during the export either prompting the "adobe had to close" survey window or it just closes without that prompt.   I've only made headway in discovering that I can export an h.264 30FPS (the source source mat'l encoding) directly back out (event recode to h.265) and it's fine using GPU acceleration, but when i add a single adjustment layer (to the 5 min clip) that leads to crashing. It's repeatable to remove the layer, export fine, re-insert the layer and crash. I've deleted the layer and re-built it but same crashes occur. There's no other effects, just the single layer video with an adjustment layer. ... View more

Hello. I rolled back to previous graphics drivers using the Studio driver. When first dealing with the crashes I updated my graphics driver and that didn't resolve so I went backwards, no improvement, went backwards again and no improvment. I've now rolled back my premiere to an even older variant (23.6) and no improvement. I can take in h.264 30FPS and export it alone just fine, but if I add any adjustment layers (keeping the same encoding) both Premeire and Encoder will crash. If i try to export to h.265 or Quicktime it also crashes. ... View more

apologies. I get the blue screen with the sad face. as quick as it shows up windows automatically restarts before i can see any error codes. i'll try and record with a phone to catch the code. ... View more

and yes, significant memory exists beyond the required file size on the drive. I've also tried multiple drives (also separate partitions within those drives) ... View more

for added context using adobe premiere/media encoder are the only programs that generate this crash. computer runs ultra stable othewise. ... View more

tried an export using h.265 and it went through with no issue surprisingly. I repeated the same process with all the same settings and it blue screened around 75'ish percent. blue screens last less than 2 seconds so i can't see if there are any error codes presented. Currently trying to figure out how to see windows crash logs.. ... View more

the error comes up as an Adobe "Adobe Media Encoder had to close" and I'm offered a *.dmp file that I don't know what to do with. ... View more

Hello, there's no error message that comes up when activating the fonts. Example just represented itself. I have a working file via the Cloud in Illustrator. Previously activated font (Owners). Was working with the file, saved. Powered down desktop. Came back a couple hours later and re-launched Illustrator only to see the the text objects with the red overlay (note Illustrator did NOT preempt me with a "Font not found" pop up window) of the text. Over in the text properties field the font name says " *Owners " as if the font is not active. Going immediately over to Adobe Fonts I see that the font is indeed active. If I go into Adobe Fonts, deactivate the font and reactivate the font (while keeping Illustrator open) it will remedy the problem but obviously we can't be doing this to a series of varying fonts. ... View more

thanks for the feedback. I didn't expect the scrubber to be such an intensive feature. Everything worked so smoothly until the update.  ... View more

I notice when I create a new tool preset for the Zoom tool, and then select that new preset the Scrubby Zoom becomes checked (but remains greyed out). As soon as I click out of the sub-menu the scrubby zoom goes back to unchecked and greyed out.  ... View more

Disabling it does not change the outcome. I’ve cycled the app as well 😕 ... View more

I can understand the perspective of artistic versus sellable so thanks for the feedback. This image is certainly one that is hard to make it fit something else. I think I'm still trying to submit work and understand the reasons for rejections as it's frustrating to see images rejected with such generic reasons (i.e. technical issues) and just think....."what in the world does that mean and how do I improve????" Just trying to learn  and improve the marketability of my images . Ciao ... View more

Thanks for the feedback! Yeah, the over exposed area was I'll say, necessary for sake of the image type, but ended up looking fitting in the end result. I feel like the white balance is pretty true to form on this one, don't recall exactly, but looking at the colors I think I just pulled up the saturation a bit. ... View more