Edward,
In addition to Mamamegs' suggestion, you might want to take a look at
Problem Reports and Solutions applet found in Control Panel. From there you
can report system errors to Microsoft for research and see if there are
workarounds/fixes already available.
Or, you can try and analyze crash dump file that Windows creates when STOP
error (BSoD) occurs by yourself. In many cases crash dump analysis will
allow you to determine exact cause of the error. You can download "Debugging
Tools for Windows" from Microsoft web site and use them to analyze crash
dumps.
However, the problem with debugging tools is that it may be a bit too
complicated for uninitiated to deal with kernel debuggers output.
That's why I wrote a script that simplifies the process by parsing debugger
output and presenting only minimum amount of information that might be
useful in tracking the cause of error. My local IT community was using it
for some time and feedback was quite positive so I decided to post it on my
blog:
http://4u3u.spaces.live.com/blog/cns...7B5E!311.entry
Hope this helps.
--
Alexander Suhovey
"Edward Ray" <ewray@newsgroup.nospam> wrote in message
news:13487A24-8481-4F2D-B392-C7139E965200@microsoft.com...
> The problem resolution refers to
> http://support.microsoft.com/kb/293078/en-us which appears to have nothing
> to do with the BSOD message.
>
> The BSOD message every time:
>
> REFERENCE_BY_POINTER
>
>
> *** STOP: 0x00000018 (0x00000000, 0x84565398, 0x00000002, 0xFFFFFFFF)
>
>
> If anyone has seen this and has an idea about a resolution, much
> appreciated.
>
> --
> Edward Ray
> CCIE Security, CISSP, GCIA Gold, GCIH Gold, MCSE+Security, PE
>