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

Question

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?

Answer 1

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".