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

Edward Ray used his keyboard to write :
> 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.

This kb articles refers to win 2000, but it might give you an idea
where to look:
http://support.microsoft.com/kb/282503

--
Mamamegs.

I reject your reality and substitute my own.
(Adam Savage)

Nederlandse nieuwsgroepen voor Vista
alt.nl.os.windows.vista
microsoft.public.nl.windows.vista

_*mamamegs@gmail.com*_

Hi Edward,

The resolution is the same, you need an updated driver file for some piece
of hardware on the system. Not necessarily video, but something. The error
means that at some point in the driver file code sequence a pointer (some
value stored previously in system memory) is referenced that doesn't exist
or whose value is meaningless to the current operation. Sometimes this will
cause a loop as it attempts to correct itself (sort of an else/then bypass),
and for others the system will just simply stop (hence the BSOD) as it
doesn't know what to do.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org

"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
>

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
>

Finding the driver is going to be a challenge. I had Vista Ultimate Final
running on this machine for about two months now with no issues until now.
I tried uninstalling the video driver in safe mode, which caused Vista to
reinstall upon next normal boot. Still BSOD when shutting down or
restarting. Until I find the time, guess I will not be shutting down or
restarting for the time being...


--
Edward Ray
CCIE Security, CISSP, GCIA Gold, GCIH Gold, MCSE+Security, PE