I have learned to not stuff with the Form_Load event.
And I even go further, and I am selective about what code I place in there (Some goes in to Form_Activate, with a wee flag to avoid the code running twice). (Not saying removing some code in this instance will help, since you say that you cannot even break on the first line)
I would try to avoid placing breaks in the Form_Load (if you can).
Use Debug.Print instead.

There will be some (many) that think I am too cautious.
And there may be some that say I am wrong.
If they say that to me, then I will say this to you -
I told the Doctor it hurts when I do this.
The Doctor replied, well don't do it.

Rob
PS I always have Task Manager running, and keep one eye on CPU usage, and one eye on memory usage. That has been informative for me on occasions. Can't do any harm.