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?

score 7 · Accepted Answer · answered Dec 21 '17 at 23:08

7

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

answered Dec 21 '17 at 23:08

Choylton B. Higginbottom

2,236
3
24
34

2

Did not help me. I have it on Any CPU with-/out exceptions runtime language ex ckeck... It works on VS2017 but not VS2019 pfffff.... – HelloWorld Dec 11 '19 at 19:53
How to change solution platform? – Aelius Jun 03 '21 at 17:00

score 2 · Answer 2 · answered Feb 10 '20 at 18:45

2

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 Feb 10 '20 at 18:45

Miro

31
1

1

This is not an answer. Please read https://stackoverflow.com/help/how-to-answer Once you have enough reputation, you can use the comments section for further discussion – sinanspd Feb 10 '20 at 20:29

score 1 · Answer 3 · answered Sep 24 '21 at 10:24

Future travellers to this page, beware: I had the "Frame not in module", and it seemed my Stored Procedure was not configured properly. It was missing an ELSE statement in between a couple of IF BEGIN END blocks. The SP compiled, saved and ran without warnings or errors in SQL Server, but just exited after the line where it had expected the ELSE statement.

After putting the ELSE statement in, all problems disappeared, including the "Frame not in module" error.

score 1 · Answer 4 · answered May 11 '22 at 09:58

1

Deleting the .vs and obj folders, closing and reopening did the trick for me.

answered May 11 '22 at 09:58

Mario Vázquez

717
10
9

score 0 · Answer 5 · answered Aug 07 '22 at 11:53

0

Removing targetFramework=4.x from my compilation node in the web.config fixed this for me.

answered Aug 07 '22 at 11:53

Tom McDonald

1,532
2
18
37

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

5 Answers5

Linked