The instruction at "0x00000000" referenced memory at "0x00000000&

[euston]

The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read".

This seems to be a hot topic on several forums. It also affect Windows 2000. I have only noticed it very recently. Some people think that it is caused by bad memory. My hunch is that a Windows update patch is the cause of the problem. On realising the existence of the problem, I recovered my system from a 3 week old Ghost image. The problem did not exist 3 weeks ago but it is there now on that restored copy of the system which has since had Windows updates applied but little else in the way of change.

The problem occurs when programs close. The error message box contain the text at the head of this thread.




Null illegitimus carborundum

 

[bcastner]

Uninstall Yahoo Toolbar.


____________________________
Users Helping Users

 

[euston]

Thanks Bill. Yahoo! is not installed. At least, it does appear in the Add/Remove Programs list. There is almost no mention of Yahoo! in the registry. The problem seems to be in abeyance at the moment. I can shut down my machines without the aforementioned message box making an appearance.

I am most careful not to install Yahoo or Google toolbars. Everyone seems to be offering them. Since I use Opera (now at version 9.02), I wouldn't be using them anyway but I avoid contaminating Internet Explorer with them, even so.

????????????????????????????

Null illegitimus carborundum

 

[linney]

You can read this long post if you like, Bill (I think) believes it is only useful as a cure for insomnia. It does tend to confirm what you already know, and that is, that it is a widespread problem without any one fix to solve it.

Reading your story of "before and after" the common denominator would be the CD/DVD drive itself or other attached hardware, unless you installed something else after the Image was restored and before the fault occurred?

...the memory cannot be "written".
thread779-1276537

 

[bcastner]

Thanks linney.

The message: "The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read"."

Is a slightly different animal then the discussion referced by linny above.

The only instruction at that address should be a JMP instruction to initialize the BIOS.

Any other reference to this memory address is a processor failure error, and quite serious.






____________________________
Users Helping Users

 

[euston]

It has happened with both Windows XP and Windows 2000 (latest MS security updates and SPs). The common factor is that both machines use Jetway V400DB system boards and Athlon XP processors (XP 1600+ and XP 2500+). It would be extremely unlucky for both processors to fail at the same time. I have run MemTest86(3.2) on both systems without revealing any errors.

At the moment, the problem seems to have gone quiet. I was able to provoke the condition on Windows XP by installing and using the following tweak software: 'xpTuner' and 'TweakXP-Pro'. However, I also use JerMar 'Tweaki...for Power Users' which works well with XP even though it predates it and 'Tweaki...for Power Users' has had no detrimental effect. In fairness to 'xpTuner' and 'TweakXP-Pro', I reinstalled Windows XP with SP2 slipstreamed onto the original installation CD and they now work with no ill effects. I had previously progressed from Windows XP original through SP1 and then SP2.

Presently, my hunch is that the problem is software generated and the symptoms are merely irritating though they do diminish one's confidence in the integrity of each affected Windows installation.

How much insanity is due to Windows quirks?

%-)

Null illegitimus carborundum

 

[euston]

I have a niggling thought about the Windows XP SP2 Data Execution Prevention feature which, when enabled for all programs, might have a hand in this problem. I reverted to the default option and it had an effect, I believe. Trouble is that it is very difficult to provide evidence for a zero effect.

Null illegitimus carborundum

 

[BadBigBen]

To turn of DEP completely, go to the Boot.INI file and edit the option /noexecute=optin to /execute...

if the symptoms disappear then most likely it had to do with it or a badly programmed driver...



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[bcastner]

At the moment, the problem seems to have gone quiet. I was able to provoke the condition on Windows XP by installing and using the following tweak software: 'xpTuner' and 'TweakXP-Pro'. However, I also use JerMar 'Tweaki...for Power Users' which works well with XP even though it predates it and 'Tweaki...for Power Users' has had no detrimental effect. In fairness to 'xpTuner' and 'TweakXP-Pro', I reinstalled Windows XP with SP2 slipstreamed onto the original installation CD and they now work with no ill effects. I had previously progressed from Windows XP original through SP1 and then SP2.

With great respect for Ben's advice above, maybe you should not be using these Tweaking tools?

Apparently there are no problems if you use a clean install with XP SP2 slipstreamed.



____________________________
Users Helping Users

 

[euston]

Yes, I know but I can't resist them. Being forbidden the company of fast women, it's my only pleasure.



Null illegitimus carborundum