Visual Studio 2017 debug error: "Frame not in module"


After updating Visual Studio, I attempted to resume debugging, and got the following errors:

"Frame not in module" "Exception thrown at 0x246E8BF8 in w3wp.exe: 0xC0000005: Access violation reading location 0x00000000."

What do these mean and how do I resume debugging?


2 Answers


After doing some digging, I got debugging working again by checking the "Common Language Runtime Exceptions" box in Exception Settings (there's a link to Exception Setting in the popup that had the second error), then changing the "Solution Platforms" from "Mixed Platforms" to "Any CPU".


This was problem for me when I was debuging CUDA program, and I was running Release (Cuda is slow in debug and has its own button to debug) on VS. So for anyone reading this, check it as well.

answered on Stack Overflow Feb 10, 2020 by Miro

User contributions licensed under CC BY-SA 3.0