odd errors

[greggustin]

if I am 'lucky' i get this:
the instruction at "0x13355cf0" referenced memeroy at "0x0000001d". The memory could not be "written".
Click Ok to terminte the propgram.
Click Cancel to debug the program.

(if I click cancel - the HD lite blinks for a few minutes
then system is ok for a while


If I am NOT lucky - weird things
like programs will not open
rt click on icon is corrupt
hitting start icon is corrupt

passed all memtest+ tests

ideas

 

[Steevo]

You might check system temps first.


Use Everest or Speed Fan.

 

[greggustin]

ok
I will later tonight
off to do the Mother's day gig
(hint hint to all of you )
but it is a laptop
monunted on a fan box
and this happens even on 1st boot
but will check temps later
thanks

 

[Steevo]

I get this at work sometimes with F@H running on one client and high temps. And the Dr. Watson log never points to the same program, and never malware.


I honestly have never found any reason why it happened to me other than high temps on a Intel.

 

[LeeJend]

Post (or check) the event log and see if it has any more details, like what program had the execution error.

From other posst this is supposed to be a memory issue (timing too tight, oerclocked etc.) so it could be the ram or the memory controller.

 

[Steevo]

From other posst this is supposed to be a memory issue (timing too tight, oerclocked etc.) so it could be the ram or the memory controller.

Off to the mothers day gig is not a reference to a gig of memory. :laugh: