Re: Blue screen O.D. twice a day
- From: "NewScience" <newscience83@xxxxxxxxxxxxxx>
- Date: Tue, 19 Dec 2006 22:16:10 -0500
No you do not have to install the Symboils Package each time. However, if
your executable DTG does not match the Symbols File DTG (Date-Time-Group),
then if you have set the Preferences up correctly for WinDBG, then WinDBG
will go to the Windows Symbol Package web-site and automatically download
any symbols that are out-of-date.
I created a Shortcut for Windows Debugger set to the following:
Target: "C:\Program Files\Debugging Tools for Windows\windbg.exe" -v -y
"SRV*C:\Windows\System32\Symbols*http://msdl.microsoft.com/download/symbols";
-i "c:\Windows;c:\Windows\system32;c:\Windows\system32\drivers" -z
"C:\Windows\MEMORY.DMP"
This automatically opens the system crash dump C:\Windows\Memory.DMP file.
I also created a Registry .reg file to create an associated for any .DMP
files
--------------------------COPY AND PASTE TO FILE
..reg -----------------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.dmp]
@="dmpfile"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\DefaultIcon]
@="\"C:\\Program Files\\Debugging Tools for Windows\\windbg.exe\",0"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\shell]
@="Debug"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\shell\Debug]
@="&Debug"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\dmpfile\shell\Debug\command]
@="\"C:\\Program Files\\Debugging Tools for Windows\\windbg.exe\" -v -y
\"SRV*C:\\windows\\System32\\Symbols*http://msdl.microsoft.com/download/symbols\";
-i \"c:\\windows;c:\\windows\\system32;c:\\windows\\system32\\drivers\" -z
\"%L\""
------------------------------------------------------------------------------------------------------------
WHen installed in the registry, any .dmp file (when right-clicked), will
have a Debug option that will open the WinDBG program.
So, right-click on any C:\Windows\MiniDump\*.dmp file
By using the shortcut and the registry entry, you assure yourself that you
will always have to most up-to-date symbol.
For example, say MS updates ntdll.dll or ntoskrnl.exe, then next time you
have a crash and need to debug it, WinDbg will automatically retrieve the
new symbol table.
I'd tell you what to look for in the DUMP trace, but since I fixed my
problem, I haven't had one. I know to look for Process (something) after
entering the !analyze -v command
"Stevie" <Stevie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CD7CDE9F-87AE-4BB3-AD6E-392E7E9A88D7@xxxxxxxxxxxxxxxx
I set the system to do a full memory dump and would you believe it hasn't
crashed since
However i have viewed some mini dumps allhtough im not %100 sure what im
doing
Do you have to install the symbols every time you start debug
Anyway mini dump said
Problem caused by:-
Memory corruption (nt!Mmcopytocachedpage+275)
Memory corruption (nt!Mminswapprocess+2c7)
Ntoskrnl exe. (nt!pspreaper+25)
Thank you everyone for any help
Stevie M
"NewScience" wrote:
You can play around this over and over, seconf guessing everything. Try
the
Windows Debugging Tools as I mentioned and it will directly pinpoint the
problem.
Believe me ... I've gone thru this for over 4 months.
"Stevie" <Stevie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DD0A2A24-00F7-4FA9-9E6E-D554D6B7D2C1@xxxxxxxxxxxxxxxx
I recieve a blue screen or critical stop around twice a day with
diferent
error codes such as:-
irq-not-equal-or-somthing error code 4a
pfn list corrupt error code 4e
and some others, all at very random time although it dose seem to be
worse
when the machine is working hard
I have updated or reinstalled everthing I can think of and have run
several
debug programs, my windows seem to run realy good apart from the blue
screens.
Could defective memory cause different error codes, I would like to pin
point the error before spending £60 on new modules ????
.
- References:
- Re: Blue screen O.D. twice a day
- From: NewScience
- Re: Blue screen O.D. twice a day
- Prev by Date: Re: converting drive c: to ntfs
- Next by Date: Application
- Previous by thread: Re: Blue screen O.D. twice a day
- Next by thread: Re: Error messages an slow computer
- Index(es):
Relevant Pages
|
