When Windows is starting up I get an error message that reads: The
instruction at "0x7c918fea" referenced memory at "0x00000010". The memory
could not be "written". Click on OK to terminate the program or click on
cancel to debug the program.

Then when windows is shutting down it reads the same message but with a
"0x6a2a2fe7" number.

What can I do to stop these errors?

Run a /thorough/ check for hijackware, including posting your hijackthis log
to an appropriate forum.

Checking for/Help with Hijackware
http://aumha.org/a/parasite.htm
http://aumha.org/a/quickfix.htm
http://aumha.net/viewtopic.php?t=5878
http://wiki.castlecops.com/Malware_R...:_Introduction
http://mvps.org/winhelp2002/unwanted.htm
http://inetexplorer.mvps.org/data/prevention.htm
http://inetexplorer.mvps.org/tshoot.html
http://www.mvps.org/sramesh2k/Malware_Defence.htm
http://defendingyourmachine2.blogspot.com/
http://www.elephantboycomputers.com/...moving_Malware

When all else fails, HijackThis v1.99.1
(http://aumha.org/downloads/hijackthis.zip) is the preferred tool to use.
It will help you to both identify and remove any hijackware/spyware with
assistance from an expert. **Post your log to
http://forums.spybot.info/forumdisplay.php?f=22,
http://castlecops.com/forum67.html,
http://forums.subratam.org/index.php?showforum=7,
http://aumha.net/viewforum.php?f=30, or other appropriate forums for expert
analysis, not here.**

If the procedures look too complex - and there is no shame in admitting this
isn't your cup of tea - take the machine to a local, reputable and
independent (i.e., not BigBoxStoreUSA) computer repair shop.

--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org

Richard wrote:
> When Windows is starting up I get an error message that reads: The
> instruction at "0x7c918fea" referenced memory at "0x00000010". The memory
> could not be "written". Click on OK to terminate the program or click on
> cancel to debug the program.
>
> Then when windows is shutting down it reads the same message but with a
> "0x6a2a2fe7" number.
>
> What can I do to stop these errors?