Adobe “memory could not be read” errors often stop after an Acrobat update, a security toggle change, and a repair install.
The popup looks scary: a long string of numbers, then “the memory could not be read” or “could not be written.” In many cases it isn’t failing RAM. It’s Windows closing an app after a bad memory access. The fix is usually a clean set of checks that remove the trigger on your PC.
Why The Message Shows Up In Adobe Apps
“Memory could not be read” is a Windows-style crash message. It can appear with Acrobat/Reader, Photoshop, Premiere Pro, Illustrator, or the Creative Cloud desktop app. The cause is often one of these patterns:
- Outdated app build — A bug in a specific version trips a Windows protection rule.
- Security sandbox clash — Acrobat’s protected features can collide with certain file locations.
- Plug-in conflict — PDF add-ons, preview handlers, printer drivers, and GPU tools can hook in and crash the app.
- Damaged settings or cache — Corrupt preferences can break startup or file open.
- Driver mismatch — Graphics drivers can expose crashes when acceleration is on.
You’ll see similar wording across many programs because Windows raises the alert, not Adobe. Your job is to remove the specific setup that makes the app hit that guardrail.
Fast Checks That Catch Most Cases
Start here. These take minutes and often fix the issue outright.
- Restart Windows — Close every Adobe app, reboot, then open one app and test.
- Save the file locally — If the crash happens from email or a download bar, save to Desktop, then open from there.
- Try a browser viewer — Open the same PDF in your browser. If it opens fine, the file is likely okay.
- Disable PDF add-ons — Pause PDF printers, preview handlers, and Outlook add-ins, then test.
| What You See | Most Likely Cause | First Check |
|---|---|---|
| Crash only when opening from Outlook | Temp folder + sandbox clash | Save attachment, open from a normal folder |
| Crash on startup before the window loads | Install or graphics path issue | Repair install, turn off acceleration |
| Random crash after long sessions | Cache bloat or driver issue | Clear cache, update GPU driver |
Fixing Adobe Memory Could Not Be Read Errors On Windows
If the fast checks didn’t clear it, work through the fixes below in order. Each step changes one variable, so you can tell what worked.
Update Acrobat Or The App First
Start with updates. Adobe ships bug fixes in regular Acrobat builds, and many memory crashes clear after moving to the latest version. Update Acrobat via Help → Check for Updates, then reboot and test. If you’re on Reader, update it too before testing again.
- Install the latest Acrobat build — Update, reboot, then open the same file in the same way.
- Update Creative Cloud desktop — Install its updates so shared components stay aligned.
Adjust Acrobat Security Toggles
When the crash happens during file open, Acrobat’s enhanced security can be the trigger. Try one change at a time, restart Acrobat, then test.
- Toggle Protected Mode — Preferences → Security (Enhanced) → switch “Enable Protected Mode at startup,” then restart.
- Toggle AppContainer — In the same panel, switch “Run in AppContainer,” restart, then test again.
If a toggle stops the crash, keep that setting for now and stay current on updates. Later, after a new Acrobat build, try turning it back on and retest.
Repair The Install And Reset Preferences
Next, repair the installation, then reset preferences if needed. This replaces damaged app files and forces clean settings.
- Run Repair Installation — Acrobat Help → Repair Installation, then reboot.
- Reset Acrobat preferences — Close Acrobat, rename its user preference folders, then launch again.
- Test with a fresh Windows user — If it works in a new account, the issue is tied to your profile settings.
Test Without Graphics Acceleration
Acceleration is a common crash amplifier. Turn it off as a test, then decide whether to keep it off or update the GPU driver and retry.
- Disable 2D acceleration — Preferences → Page Display → turn off 2D graphics acceleration, then restart Acrobat.
- Update the GPU driver — Install the current driver from your GPU maker, reboot, then retest with acceleration on.
Adobe Memory Could Not Be Read When Opening A File
This pattern is common: a PDF opens fine when saved to Desktop, but crashes when opened straight from Outlook, Teams, or a browser temp folder. The file itself may be fine. The handoff path can be the problem.
Fix Email And Temp-Folder Opens
- Save attachments first — Save the PDF to a normal folder, then open it from there.
- Disable PDF preview — Turn off Outlook preview for PDFs and test again.
- Open from a test folder — Copy the PDF to C:\PDF-Test and open it from that folder.
Check Sync Tools And Antivirus Scans
Sync tools can lock a file for a moment. Antivirus can scan at open time. Either can push Acrobat into a crash if it is already unstable.
- Pause syncing — Pause OneDrive or similar tools, then open the same file again.
- Add an allow rule — Add Acrobat’s process to your security tool’s allow list and retest.
Once the crash stops, bring your usual workflow back one piece at a time so you can spot the exact mix that triggers it.
If You See The Error In Premiere Pro, Photoshop, Or Illustrator
In heavier Creative Cloud apps, memory crashes often follow large projects, long sessions, or GPU-heavy effects. The fixes are still familiar: clear caches, reduce GPU stress, and remove unstable plug-ins.
- Clear caches — Premiere Pro Media Cache, Photoshop scratch disk temp files, and old previews can pile up and cause crashes.
- Switch to software rendering — In Premiere Pro, test the same timeline action with software-only rendering.
- Disable third-party plug-ins — Move plug-ins out, test stability, then add them back one by one.
If it only happens in one project, duplicate that project and remove one suspect asset type at a time, like a single effect chain or a specific font file. This isolates what the app chokes on.
Windows-Level Checks When It Still Won’t Stop
When updates, repairs, and toggles don’t fix it, treat it like a Windows conflict. The goal is to find the extra tool, driver, or service that’s destabilizing Adobe apps.
Use A Clean Boot To Find Conflicts
A clean boot starts Windows with only Microsoft services. Microsoft documents the msconfig flow. Use it to spot clashes with driver utilities, PDF preview handlers, or security suites.
- Run msconfig — Hide Microsoft services, disable the rest, reboot, then test Acrobat.
- Re-enable in small batches — Turn items back on until the crash returns.
- Remove the offender — Uninstall or update the tool that brings the crash back.
Repair Windows Files And Memory Settings
- Run SFC and DISM — Repair Windows system files, reboot, then test again.
- Set virtual memory to system-managed — Let Windows size the page file unless you have a tested reason to change it.
- Run a memory test — Use Windows Memory Diagnostic if you see similar crashes in many unrelated apps.
Read Windows Crash Notes For A Clear Lead
If the crash is stubborn, Windows often records a short note that points to the failing module. You are not chasing every code. You want the name that repeats.
- Open Reliability Monitor — Search for Reliability Monitor, open it, then click a red X on the day of the crash.
- Copy the faulting module — Note the module name and the app version shown in the details pane.
- Match it to a change — If the module is a plug-in, printer driver, or security tool, update or remove that one item and retest.
If you see the same module across crashes, you’ve found target to fix.
Habits That Keep The Error From Returning
Once you stop seeing the popup, a few habits lower the odds of it coming back.
- Update on a schedule — Keep Acrobat and Creative Cloud apps current, then reboot after patch days.
- Keep the system drive roomy — Leave space for caches, temp files, and Windows paging.
- Open PDFs from normal folders — Save attachments first and avoid temp-only paths.
- Keep plug-ins tidy — Install only what you use and remove old plug-ins after app updates.
If you still hit the popup, capture the basics before you reach out for help: app name and version, Windows version, GPU model, driver version, and the exact action that triggers it. That short checklist speeds up diagnosis.
adobe memory could not be read often feels random, but it follows patterns. Fix the pattern that matches your case and the crash stops repeating.
When you see adobe memory could not be read again after a long stretch of stability, treat it like a regression: check the last Windows update, driver update, or new plug-in, then retest after rolling back that one change.