That "SuchandSuch.exe" probably is the name of your own application?
> Access violation at address 00503D57 in module "SuchandSuch.exe". Read
> of address 0x00000004
> Can I jump to this location in the source code in the debugger?
If the address lies within your own code, or within your components
there you also have source code, then you can use Search -> Find error
and you can easily jump to that address in your source code.
If the address lies within Windows DLL files, you are out of luck.
Most often when I face errors that are ourside my scope are in some way
related to Windows Printer Driver problems. The error may even pop up
sometime after using some erroneous or non-compatible Printer driver.
The second most common error lies within my own code. That error address
does not reveal the exact place what causes the error. But debugging
line by line, I can trace the problematic line that makes Windows DLL
error to appear, and I can fix it or go around it.
Occasional errors, errors that appear only about once a week or two and
only at the customer's site, they are the most difficult to locate.