W2k error - at times - no pattern;

[Guest]

This error occurs for no particular reason - annoying!

=====================================
The instruction at "0x007d3642" referenced memory at "0x00000001". The
memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program
======================================

clicking on either one will close what ever program I'm in and at times -
BSOD into a memory dump.

Any suggestions appricated !!

 

[Steve Parry]

This error occurs for no particular reason - annoying!

=====================================
The instruction at "0x007d3642" referenced memory at "0x00000001". The
memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program
======================================

clicking on either one will close what ever program I'm in and at times -
BSOD into a memory dump.

Any suggestions appricated !!

try running a CHKDSK C: /F on your drive and reboot to let it run

 

[Guest]

Hi and thanks for the quick responce/help!!

Just got through with the hour (or longer) of memory testing using the
suggested testers - no problem shown. I'm running (1 gig) 800 fsb rdram (4 -
512 chips), as you know - they have to run in pairs.

Look forward to your/anyones suggestions as to what to do next.

 

[Guest]

Almost forgot to mention - that I also ran chkdsk c:/f at bootup with no
errors.

Thanks!!

 

[Dan Seur]

This may be one of those rare instances where a bit in some executable
was flipped by mischance (cosmic ray, power glitch, UFO, etc) and causes
an aberration whenever it finds itself in the CPU. Worst kind of
'apparent intermittent', much prolonged observation required, followed
probably by reinstalling some piece of software.

Could also be a simple bug you're encountering. Without wads of info
about exactly what's being done on your system at the moment this occurs
(what processes are running), it's hard to help. Someone may know of
tools that can examine, for example, system modules bit-for-bit for
correctness.

Almost forgot to mention - that I also ran chkdsk c:/f at bootup with no
errors.

Thanks!!

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0614-1, 04/04/2006
Tested on: 4/6/2006 11:15:37 AM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com