Hello,
I updated my work PC from Pro 3.6.3 to 3.7 this morning, and now every time I open a project (existing or new) or open the "options" window, the whole machine hard crashes and displays "Stop Code: KERNEL_SECURITY_CHECK_FAILURE 0x139" then reboots. The ArcGIS Pro basic program window (with the list of recent projects, etc.) being open doesn't cause any problems.
This is massively disruptive for obvious reasons - has anyone else seen similar behavior? The machine is running Windows 11 25H2 and has been otherwise completely stable, nothing else causes this crash, I've narrowed it down to opening a project or the "options" window from the settings page.
I was able to successfully upgrade my cloned python environment with no issues, though I haven't tried running any scripts yet. I haven't found any log files that suggest anything one way or the other, either in windows or related to ArcGIS Pro.
Has anyone else seen anything like this? I have logged a support case but though I'd reach out here first just in case someone knew a quick fix.
Thanks!
John
Solved! Go to Solution.
Certainly. Hopeful the support analyst has additional ideas to assist. In the meantime, you can try a Perform an ArcGIS pro Soft Reset and see if this helps.
I did search the Esri Support Services cases for the "Stop Code..." error but besides your case, do not see any previous cases listing this item.
In full transparency, I did use the Esri Support AI chatbot asking for an explanation of the error message and this is what it returned:
<CLIP>
`Stop Code: KERNEL_SECURITY_CHECK_FAILURE (0x139)` is a **Windows Blue Screen (bugcheck)**. It means Windows detected **kernel-level corruption or an illegal operation**—most commonly caused by a **faulty/buggy device driver** (often GPU, storage, network, USB), **security/antivirus filter drivers**, or **RAM/disk issues**. It’s **not an ArcGIS Pro-specific error code**.
If this happens while using ArcGIS Pro, Pro is usually just **triggering** an underlying driver/system problem (heavy GPU drawing, lots of I/O, security scanning temp/workspaces, etc.).
Try these checks:
- **Update or roll back drivers** (start with GPU, then chipset/storage/network).
- If allowed by IT, **test without third‑party antivirus/EDR** or with temporary folder exclusions (Esri notes security software can interfere with Pro’s file access): [Troubleshooting General Function Failure errors in ArcGIS Pro](https://support.esri.com/en-us/knowledge-base/000040196)
- Run Windows integrity checks: `sfc /scannow` and `DISM /Online /Cleanup-Image /RestoreHealth`
- Test **RAM** (Windows Memory Diagnostic) and **disk** (SMART/CHKDSK).
- Check `C:\Windows\Minidump\` and Event Viewer/Reliability Monitor; the minidump usually points to the **specific driver**.
<END CLIP>:
I then followed up with I'm using 3.7 and this was it's response:
<CLIP>
ArcGIS Pro 3.7 itself doesn’t generate KERNEL_SECURITY_CHECK_FAILURE (0x139)—that’s a Windows BSOD usually tied to a driver or hardware issue. For Pro 3.7, the most relevant troubleshooting is GPU/driver stability:
Update your GPU driver from the manufacturer (NVIDIA/AMD/Intel). If you’re on a laptop, use the laptop OEM driver track first.
Esri guidance: Troubleshooting Performance Issues in ArcGIS Pro
In ArcGIS Pro, switch the Rendering engine (this can avoid a problematic DirectX 12 driver path):
If Pro reports graphics adapter issues, Esri notes this can be due to a corrupted/out-of-date driver:
Compatible graphics adapter not found
<END CLIP>
So it's a start and something to bring up with the Esri Support Services analyst when you speak with them. Hope this helps a little bit.
Thanks, I appreciate you looking into it. That's all more or less what I found - I'm hesitant to start making any changes to drivers or the operating system, since everything was working correctly before this update. Worst comes to worst I can uninstall 3.7.0 and roll back to 3.6.3.
I would be curious to see if changing the rendering engine does anything, but again, when I click "options" in the settings page, as soon as it begins the process of "creating geoprocessing cache" - that's when the machine crashes and reboots.
Certainly. Hopeful the support analyst has additional ideas to assist. In the meantime, you can try a Perform an ArcGIS pro Soft Reset and see if this helps.
I'm cautiously optimistic, but a soft reset seems to have resolved the issue. I'm able to open projects (and the "options" page) without this crash now. I haven't tried running any big analysis yet, I'll report back if the behavior returns.
Thank you for your suggestion!