A software exception w/ a memory address is almost always due to some program, or process, either not reporting its memory addresses correctly, or telling the OS that it has released those addresses, when it has not.
The easiest way to track the program, or process, responsible for this is found in this ARTICLE. Event Viewer should help you find what is causing this.
In that article, there is a link to The Case of the Unexplained, by MS, but that link has been changed by MS. You will find the active links (per OS) in this ARTICLE.
PS - that old forum article is probably lost, and gone forever, as of the forum re-structuring some years ago.