|
| I agree. Just about the only thing you can tell from the numbers without a
memory dump is the nature of the error, especially if the instruction at
0x12345678 accessed memory at 0x00000000 (indicating a null pointer). Even
then you'd have to find out what module instruction 0x12345678 belongs to.
If you're willing to do some work (i.e. configuring your box to capture a
error report to post), I can try to help you with the problem.
What OS are you using?
Mike
"Carl Frisk" <c.frisk@REMOVE.verizon.net> wrote in message
news:oE_7f.9847$tl5.8280@trnddc02...[vbcol=seagreen]
> *********** doesn't help much. Can you post the actual numbers?
> --
> ...Carl Frisk
> Anger is a brief madness.
> - Horace, 20 B.C.
> http://www.carlfrisk.com
>
>
> "JimmyBoy" <me@myhouse.com> wrote in message
> news:e87vl1db5sap70fefjuug3j2cfrjobjjg4@4ax.com...
|
|