STOP: message???

  • Thread starter Thread starter Xantipis
  • Start date Start date
X

Xantipis

After doing a "disable automatic restart" I get a lenghty message
( almost saying rebuild your machine) but in the
***STOP: it lists what appear to be 7 memory addresses(?) such as
0x0000006F,(0XC00000020 etc. ) A couple of them change from one time to
another.
Then a message below that ,
"Beginning physical dump of memory
Physical dump complete."

Is the "physical dump" the RAM, or possibly the cache on the CPU or
memory on the video card?

Since I do not have another machine capable of testing the PC3200
RAM I will have to buy more RAM to verify the veracity of the report..

I ran memtest86 on the RAM and from what I could understand
about the program the RAM "passed". (guess it didn't?)

Thanks for any answers.
Xan
 
Xantipis said:
After doing a "disable automatic restart" I get a lenghty message
( almost saying rebuild your machine) but in the
***STOP: it lists what appear to be 7 memory addresses(?) such as
0x0000006F,(0XC00000020 etc. ) A couple of them change from one time to
another.
Then a message below that ,
"Beginning physical dump of memory
Physical dump complete."

Is the "physical dump" the RAM, or possibly the cache on the CPU or
memory on the video card?

Since I do not have another machine capable of testing the PC3200
RAM I will have to buy more RAM to verify the veracity of the report..

I ran memtest86 on the RAM and from what I could understand
about the program the RAM "passed". (guess it didn't?)

Thanks for any answers.
Xan
Click to expand...
The 0x0000006F is a stop code. 0xC00000020 is an address. You should
search for the stop code for information about the cause of the crash.

"Physical dump" means a dump of the RAM. This dump by no means indicates
that there is anything wrong wih your RAM. Instead, an expert can deduce
why XP crashed by examining the dump.
Jim
 
Xantipis said:
After doing a "disable automatic restart" I get a lenghty message
( almost saying rebuild your machine) but in the
***STOP: it lists what appear to be 7 memory addresses(?) such as
0x0000006F,(0XC00000020 etc. ) A couple of them change from one time to
another.
Then a message below that ,
"Beginning physical dump of memory
Physical dump complete."

Is the "physical dump" the RAM, or possibly the cache on the CPU or
memory on the video card?

Since I do not have another machine capable of testing the PC3200
RAM I will have to buy more RAM to verify the veracity of the report..

I ran memtest86 on the RAM and from what I could understand
about the program the RAM "passed". (guess it didn't?)

Thanks for any answers.
Xan
Click to expand...

First of all, you should run "memtest86+" from http://www.memtest.org/
rather than "memtest86" which is now obsolete.

Second, the fact that you are getting a dump of memory contents says
nothing at all about whether the memory is "bad" or "good."

Third, go to http://www.aumha.org/a/stop.php to troubleshoot the
0x0000006F stop code. From what I see, it looks like you may have a
corrupted device driver. The KB articles about Win2k and NT 3.51
suggest direr problems.

Also see http://www.pcreview.co.uk/forums/thread-2424622.php

--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
 
1 > create a new folder on the desktop and call it "dumpcheck" or whatever
you like
2 > navigate to %systemroot%\minidump and copy the last few minidump files
to that folder.%systemroot% is normally c:\windows. They are numbered by
date. You can paste that address in address bar to get there.
3 > close the folder and right click on it and select Send to Compressed
(zipped) Folder.
4 > Upload the Minidumps to any free web hosting and give us the link
 
Xan

Is this the full Stop Error code?
*** STOP: 0x0000006F (0xC00000020,0x00000000,0x000000000,0x000000000)

You could try a Repair Install.
http://michaelstevenstech.com/XPrepairinstall.htm

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Gerry said:
Xan

Is this the full Stop Error code?
*** STOP: 0x0000006F (0xC00000020,0x00000000,0x000000000,0x000000000)
Click to expand...

Yes that was ONE of them.
I "seemed" to have gotten different messages depending how much memory I had
and which memory modules were installed.
I'll have to "swap" modules again and watch more carefully.
Probably will have to do a reinstall just so I can get some files
then do a clean install.
(I failed to mention I cannot even boot to windows, it just
keeps re-booting.)
Let me know if you have the deffinition of the STOP message.
Yhanks
Xan
 
Devil_Himself said:
1 > create a new folder on the desktop and call it "dumpcheck" or whatever
you like
2 > navigate to %systemroot%\minidump and copy the last few minidump files
to that folder.%systemroot% is normally c:\windows. They are numbered by
date. You can paste that address in address bar to get there.
3 > close the folder and right click on it and select Send to Compressed
(zipped) Folder.
4 > Upload the Minidumps to any free web hosting and give us the link
Click to expand...

Devil,
Thanks for the advice.
I failed to mention I cannot even boot to windows. It goes just so far
then reboots. I was able to get the error messages only when I did F8
and told it not to reboot.
I notice I have a choice of creating a "boot log".
Do you know IF I do a boot log how it is saved?
Would it be readable in DOS?
I can get to a C:/windows prompt by using the repair on my original
XP CD, but then where do I find the "bootlog" I created on the Hard drive
with
the installed XP?
Thanks
 
What are the other Stop Error codes you are getting?

You should post complete Reports or at least include the line under the
code if it refers to a file.

Your Stop Error code:
http://msdn2.microsoft.com/en-us/library/ms795754.aspx
Not helpful!

http://aumha.org/a/stop.htm
which led me to:
http://en.wikipedia.org/wiki/Windows_NT_Startup_Process#Session_Manager

I did appreciate you were not able to boot. I wondered about how you
might run System File Checker but you can't from that command using the
Recovery Console so I suggested a Repair Install. I was thinking
smss.exe could be the problem. Possibly you might copy a backup copy of
smss.exe to the system32 folder if the system will let you. I have found
no evidence that smss.exe is the problem. Just that it seemed logical to
connect the file when the error message to says initialization failed.

You asked about bootlogging. This Article may help:
http://www.smartcomputing.com/edito...cle=articles/2005/s1601/56s01web/56s01web.asp


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Back
Top