Jeremy,
I don't have an answer but I have a simular problem in Win2K:
_____________________________________________
Application popup: XPCOM:EventReceiver: NETSCP.EXE - Application Error : The instruction
at "0x0789e7a4" referenced memory at "0x077319bc". The memory could not be "written".
Click on OK to terminate the program
_________________________________________________
I'm writing to request if you find an answer I would greatly appreciate a post. Likwise
If I find anything I'm post t you.
Regards
Kevin
On Sunday, February 16, 2003 at 9:05 pm, Jeremy McCormick wrote:
>I thought this was worth reposting due to the high "annoyance" factor:
>
>
>I experienced several strange problems in Windows 2000, SP-3 today,
>none of which I have had before (well, recently):
>
>1) I received a mesg. about the system log being corrupt. I disabled
>the Event Viewer, rebooted and deleted my logs. Then I restarted
>Event Viewer. This seemed to correct the problem, as I am now
>getting logs from Applications, etc.
>
>2) "netstat -a" stopped working completely. It shows *nothing* under
>any of
> the columns. I don't know how to correct this.
>
>3) My editor of choice, Ultra Edit 32, has developed several strange
>problems:
>
> a) Always shows the Ultra Edit File Associations box when loading
>even when
> I click "Don't Show This Again."
>
> b) About 3-5 seconds after exiting, a dialog shows:
>
> ----------------------------------------
> Application popup: UEDIT32.EXE - Application Error :
The
>instruction at
> "0x6061fdc3" referenced memory at "0x00000000".
The memory
>could not be
> "read".
>
> Click on OK to terminate the program
> ----------------------------------------
>
>4) Internet Explorer 6 seems to freeze very frequently, especially
>when dealing
> with multiple text boxes. I have had a lot of this behavior in
>the past,
> but recent updates seemed to have fixed it (apparently not!).
>
>
>5) Microsoft Visio 2000 has stopped working completely with the error
>mesg.:
>
> Faulting application visio.exe, version 10.0.525.4, faulting
>module
> hpzntp04.dll, version 2.80.0.0, fault address 0x0001fdc3.
>
>6) Photoshop 5.5 has stopped working with a similar error mesg. as
>the Ultra
> Edit one:
>
> ----------------------------------
> The instruction at "0x6061fdc3" referenced memory at "0x00000000".
> The
> memory could not be "read".
> ----------------------------------
>
>
>I have installed no service packs, hot fixes *or* drivers in the last
>week, I swear, and both Visio and Ultra Edit had been running
>perfectly.
>[snip!]
>
>
>So I solved this today.
>
>
>The network print server, Windows SE with print sharing, was turned off. Somehow
>this was causing these applications to crash fatally (Word also, though this wasn't
>in the original posting).
>
>
>I'm not sure if the same result would have occurred had the print server been running
>Windows 2000 with full TCP/IP instead of NetBIOS.
>
>
>I am really curious if anyone has an idea why the fact that the print server was
>off would cause fatal "read" protection errors, crashing several programs that use
>the print driver, rather than erroring "gracefully", loading the application and
>showing a dialog indicating that the installed printer was in fact not present.
>Basically, I'm wondering if this is the fault of Windows or the given applications.
> Given the number and variety of different crashing applications, I'm going to blame
>this one on Windows.
>
>
>IE 6 still crashes like crazy, especially when I tab between text boxes. I *loathe*
>that browser and have tried to switch to Mozilla. The nice integrated file browser
>aspect of IE makes it hard to avoid though. Oh, well, at least my applications
aren't
>crashing anymore.
>
>
>Cheers,
>Jeremy McCormick
