IO Error in RAM. "Memory not read error" request help.

IO Error in RAM. "Memory not read error" request help.

'The instruction "0x013755e6" referenced memory at "0x00000004 ". The memory could not be read. Click OK to terminate program. Click on CANCEL to debug program.'

Using W2k Pro I am getting the above error every couple of days from several pieces of commercial software.

RAM tests ok on a RAM exerciser.

Is this a known W2K OS error or is the fault such in the RAM that I should replace my RAM boards.

Address is always reported at very low end i.e. 0x04 to 0x16. Any suggestions much appreciated.

 

That particular error is almost always (maybe always always) an application issue rather than bad physical memory.

Usual cause is a buffer overflow because an undersize buffer was set up or a memory leak or similar.

I can't find a match for 0x013755e6 in any searches.

What app(s) are likely to be doing the deed? And is it always when you are doing the same operation or after the app has been up a certain period of time or other common factors?

 

Hi Newt,

Yes, I agree, problems like this tend to arise from applications software. This originated in NOPDB.EXE or maybe NOPDB.DLL v 7.0.0.24 which is part of the current Norton Utilities (Y2003) in Norton SystemWorks.

The code has probably generated an illegal instruction earlier back, which has bombed out here.

Symantic Support had written to me and advised me to re-install their software, but this is a bit of a pain. Particularly as the support analyst commenced by stating I should reboot my OS every few days. I know of Unix systems that will run a full year without a re-boot.

One thing to come out was Symantic referred me to one of their links on performing a clean boot of Windows 2K, and its quite a nicely set out paper. The link, for those who might be interested.

Title: 'How to perform a clean boot of Windows 2000'
Document ID: 2000110615402439
Web URL: http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2000110615402439

Cheers

 

Pain in the hindparts to reload maybe but at least you now know where the error is from and how to fix.

And nice link for the clean boot. Thanks.