At shutdown I always get the following error:
The insruction at "0x02d41611" referenced memory at "0x02d41611". The
memory could not be "read".
Sometimes I also get the same message for memory 0x02d7f207. A memory test
utility found no errors. Any ideas?
Put the exact error message into Google, here are some tools & info
that may help.
You may get more info from minidumps. Make sure it is Enabled.
Control Panel --> System --> Advanced --> Startup and Recovery -->
Settings ---> Write debugging
information --> Complete memory dump.
On XP and 2003 systems, mini dumps are located at
%SystemRoot%\Minidump, or c:\Windows\Minidump; kernel and full dumps
are located at %SystemRoot%\MEMORY.DMP or c:\Windows\MEMORY.DMP.
How to solve Windows system crashes in minutes
http://www.networkworld.com/news/2005/041105-windows-crash.html
http://www.codeproject.com/KB/debug/windbg_part1.aspx
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Install Debugging Tools for Windows 64-bit Version
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://forums.majorgeeks.com/showthread.php?t=35246
This primer will show you how to solve problems quickly. Using a tool
that costs nothing, you can solve approximately 50% of Windows server
and workstation crashes in a few minutes. The tool is WinDbg, the free
Windows debugger.
You've probably never used the debugger, don't have it and don't want
it. After all, it's a developer's tool, not an administrator's, right?
Yes, but what you need to know is remarkably easy to learn, and even a
rudimentary familiarity with the debugger could enhance your skills and
your resume.
Still hesitant? Think about this: After rebooting a crashed machine,
we've brought up the debugger, opened a memory dump file, given the
debugger a single command, and learned not only that the cause was a
driver, but also the driver's name — all in less than a minute.
Granted, the debugger was installed and configured, we knew what
commands to use and what to look for.
But so will you by the end of this article.
Or,
Grabtxt
http://www.snapfiles.com/get/grabtxt.html
http://halmisbah.blogspot.com/2008/07/grabtxt-10.html
Capture text from Windows error dialogs.
Grabtxt is a simple utility that enables you to capture the text
portions from many Windows dialog boxes. The captured text can be
copied to the clipboard (Ctrl+C) or used to search for details via
Google or Live.com with the provided shortcut buttons. The program can
be useful if you need to copy an error message for a bug report or want
to find out additional information via online search engines without
having to manually type the text. Grabtxt worked with most, but not
all, Windows dialogs that we tested.
Requirements: .NET Framework 2.0 W2000/XP/2003/Vista.
Or,
Event Log Explorer
http://www.softpedia.com/get/System/System-Info/Event-Log-Explorer.shtml
http://www.eventlogxp.com/
http://www.eventlogxp.com/download/elex.zip
Event Log Explorer is a free software for viewing, monitoring and
analyzing events recorded in Security, System, Application and another
logs of Microsoft Windows NT/2000/XP/2003/Vista ( 32 & 64 bit )
operating systems. It extends standard Event Viewer monitoring
functionality and brings new features. Free registration.
Or,
Extract troubleshooting info from Windows XP BSOD error messages
http://techrepublic.com.com/5100-10877-6053684.html#
Or,
http://www.eventid.net/search.asp
Or,
Windows Error Generator
http://www.netdevel.net.nz/index.php?mod1=netdevel/software
Ever wondered what Error(312) means ? Look it up with this, or have it
list all the errors your operating system is able to give. Also good
for programmers who need to throw a specific system error. Go to
Software menu.
