Re: Frequent "memory read" "memory write" errors !

From: Incognitus (in_at_ccurate.com.invalid)
Date: 07/16/04


Date: Fri, 16 Jul 2004 18:25:15 -0500

http://oca.microsoft.com/en/windiag.asp

"Pivert" <none.me@you.com> wrote in message
news:%23wpo%23E3aEHA.3476@tk2msftngp13.phx.gbl...
> Here first run of error reporting as requested :
>
****************************************************************************
> ***************************
> ERROR 1 - July16th, 2004- 22:03GMT+1
>
> While using Winrar to compress several files
>
> EXPLORER.EXE - Application Error
> Instruction at "0x773d698a" use memory adress "0x032ce504". Memory can not
> be "read".
> Click OK to cancel.
> Click Cancel to debug.
>
> Just after clicking OK message:
> EXPLORER.EXE - Application Error
> Exception "Unknown software exception ( 0xc015000f) has happened in
> application at 0x77f5fca7.
> Click OK to cancel.
> Click Cancel to debug.
>
> Again directly after OK
> EXPLORER.EXE - Application Error
> Instruction at "0x032c82b0" uses memory adress "0x032c82b0". Memory can
not
> be "read".
> Click OK to cancel.
> Click Cancel to debug.
>
> Clicked Ok. Nothing happens. Work continues. No explorer restart, but
opened
> folder views auto-closed.
>
> Winrar finished task normally.
> --------------------------------------------------------------------------

--
> --------------------
>
> ERROR 2 - July 16th, 2004 - 22:05
>
> EXPLORER.EXE - Application Error
> Instruction at "0x773d6983" uses memory adress "0x00e1220c". Memory can
not
> be "read".
> Click OK to cancel.
> Click Cancel to debug.
>
> Just after clicking OK message:
> EXPLORER.EXE - Application Error
> Exception "Unknown software exception ( 0xc015000f) has happened in
> application at 0x77f5fca7.
> Click OK to cancel.
> Click Cancel to debug.
>
> Just after clicking OK message again same message:
> EXPLORER.EXE - Application Error
> Exception "Unknown software exception ( 0xc015000f) has happened in
> application at 0x77f5fca7.
> Click OK to cancel.
> Click Cancel to debug.
>
> Just after clicking OK message once again same message:
> EXPLORER.EXE - Application Error
> Exception "Unknown software exception ( 0xc015000f) has happened in
> application at 0x77f5fca7.
> Click OK to cancel.
> Click Cancel to debug.
>
> Now Microsoft Internet Explorer
> An internal error has appeared in Internet Explorer.
> IE will shutdown.
>
> If you experience further problems, please reboot your computer.
>
> Clicked OK
>
> Explorer.exe - Application error
> Instruction at "0x77f5f00f" uses memory at "0xea20d057". Memory can not be
> read.
> blabla
>
> Explorer shuts down and restarts
>
> END first run of errors at July 16th, 2044 - 22:11
>
> Not bad :-)))))((((((((((
>
> Phil
>
> Will continue to record errors that w
>
****************************************************************************
> ***************************
> "Ron Martell" <ron@onlinehelp.bc.ca> a écrit dans le message de
> news:6m6gf0hmamen7bk1r3lucp7jni3vg88bq7@4ax.com...
> > "Pivert" <none.me@you.com> wrote:
> >
> > >Hi all,
> > >
> > >WinXPSP1a - 1024 MB DDR-PC3200 RAM. PIV-2.8GHz-FSB 800 - ASUS P4C-800E
> > >Deluxe Mobo
> > >
> > >Getting more and more frequent error messages mostly with explorer.exe
or
> > >iexplore.exe, sometimes other apps ( Acronis TrueImage for example),
with
> > >adresses varying. In explorer this happens mostly when right-clicking
or
> > >performing files operations ( copy / move /, ....).
> > >This never hangs the PC, just restarts explorer. But once happened, the
> > >phenomenon appears almost at each operation of explorer, thus have
> finally
> > >to reboot.
> > >
> > >MoBo Temp is 32 °C, far below danger.
> > >PC T° is 38-40 °C, also far below excess Temp.
> > >HD T° is also normal.
> > >( T° controlled with Asus Probe, SpeedFan and Motherboard Monitor)
> > >
> > >Memory swapped between slots A+C to B+D ( dual memory MoBo) : no
change.
> > >Tested each 512 Mb memory on each slot : no change.
> > >Goldmemory tests, MemTest86, Micrososft's Memory Diagnostic, DocMemory
> all
> > >show memory errors.
> > >
> > >Bought new RAM : same problem.
> > >
> > >Question :
> > >1 - is it most probably harware related ( no change since day 1, one
year
> > >ago !) : thus MoBo malfunctionning ( but cost about $ 200 - ? or
> > >     other hardware ???)
> > >2 - or could it reasonably be only software problem ?
> > >     Have tried booting with no programs running at all ( except WinXP
> > >istself) : no change.
> > >     Could Win XP repair help ?
> > >     Should I do a clean install ? ( but that's not an small job to do,
> > >since many progs installed for my professional activities !)
> > >
> > >Please give soem infos to decide what to do !
> > >
> > >Thanks !
> > >
> >
> > What is the exact wording of the error messages you are getting?
> >
> > As a general rule messages that contain the words ".... the memory
> > could not be read" or ".... the memory could not be written". are the
> > result of programming errors.  The read errors tend to be situations
> > where a program variable is being read without that variable having
> > been assigned an initial value or having a value written to it.  The
> > write errors tend to be situations where program design is inadequate,
> > such as saving an 11th item to an internal table that was defined as
> > having only 10 items in it.
> >
> > Good luck
> >
> >
> > Ron Martell     Duncan B.C.    Canada
> > -- 
> > Microsoft MVP
> > On-Line Help Computer Service
> > http://onlinehelp.bc.ca
> >
> > "The reason computer chips are so small is computers don't eat much."
>
>


Relevant Pages

  • Re: Frequent "memory read" "memory write" errors !
    ... Instruction at "0x773d698a" use memory adress "0x032ce504". ... Click Cancel to debug. ... Exception "Unknown software exception has happened in ...
    (microsoft.public.windowsxp.general)
  • Re: Error Message
    ... memory could not be "written". ... Click on OK to terminate the program ... Click on CANCEL to debug the program ...
    (microsoft.public.windowsxp.basics)
  • Application Error - Memory Couldnt Be Written
    ... memory could not be written. ... Click ok to terminate ... Click CANCEL to debug. ...
    (microsoft.public.windowsxp.basics)
  • svchost problems after clean install
    ... memory could not be "written". ... Click ok to terminate the program. ... Click cancel to debug the program. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Ok, so Im a lazy moron - Explorer crashes at startup
    ... Explorer May Generate an Application Error When You Close ... 2004 Windows MVP "Winny" Award ... > The instruction at "0x734301d5" referenced memory at "0x734301d5" ... > Clicking Cancel does apparently nothing, unless there a dump file created ...
    (microsoft.public.windowsxp.general)