Spontaneous reboots revisited

[Guest]

Thanks to Rick Rodgers for the reply below.

Rick,
I did what you said, and have captured the following error messages.

*** STOP: 0x00000083 (0XC000000D, 0XBF88D385, 0XF236A0BC, 0X0000000)
*** win32k.sys Address BF88D385 BASE AT BF8000000, Datestmp 41107f7a

Can anyone tell me what the above means? or why I'm getting the
spontaneous reboots?

Thanks,

Thom Walker


Hi Thom,

Could be a number of things, but the reboot occurs because WinXP is set to
automatically restart on system failure. Disabling this behavior will
produce a stop error or "blue screen" when it happens. The information in
the stop error is vital to resolving the issue. Go to the control
panel/system/advanced tab, and click on the startup and recovery options. In
the system failure block, uncheck the option to automatically restart. Click
apply/ok and reboot if prompted. Then simply wait for it to happen again and
post back here with the details.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Mark L. Ferguson]

To repair all system files, go to Start/Run, and type: SFC /SCANNOW

 

[Guest]

Mark,
Thanks for the reply. I did as you suggested, and rebooted. Nothing
unusual to note, guess I'll just have to wait and see if that fixes the
problem.

But, could you tell me what SCANNOW does, and why you suggested I try that?

- Thom Walker

 

[Mark L. Ferguson]

running sfc scannow command:
http://www.microsoft.com/windowsxp/...e/using/productdoc/en/system_file_checker.asp

 

[frodo]

spontaineous reboots are often caused by hardware errors, usually memory
errors. most people tend to ignore this, but it's true. If your system
is rebooting/hanging occasionally (once or twice a week at least), and
never in the same place, suspect a memory error.

run memtest+ to find out. read all the instructions there. it fairly easy
to do and will provide peace-of-mind at least.

http://www.memtest.org/

get the "precompiled package for floppy", it's the easiest to use.
if you don't have a floppy drive then you'll need to get the bootable ISO
version and use your existing burner sw to create a CD.

 

[Guest]

Frodo,
Thanks for the reply, I will try that memTest, however, I have already d/l'd
and used the Dr. Memory Ram test (in burn in mode overnight) and it has
cleared both my 512 meg RAM cards.

I have noticed one "suspicious thing" that sort-of correlates with the
problem I've been having. I have Window Messenger installed (because Outlook
Express seem to require it, if I try to remove it, a pop-up tells me the OE
is using it), but never activate or use it. (I use AIM) However, lately
I've noticed that Windows Messenger just seems to arbitarily pop-up a sign-on
dialog (all by itself, I don't believe I initiate it, although I'm not sure
because I only see it when I come back to my computer and move or click the
mouse on a blank screen saver screen to get the screen to come back) and then
there the dialog is.

Could this unwanted pop up be causing the reboots?

The only other "new" thing that I did around the time the reboots started
was to install a new 250 gig hard drive. A standard IDE drive in a Master
position on the 2nd IDE chain.

Any other ideas you might have would be appreciated.

- Thom Walker

 

[Guest]

Ok, I got memtest+, but NONE of my DIMMS passes, which I thought
highly-suspicious, however, to be sure, I went out and bought a brand new
DIMM, tested that in the PC all by itself with memtest and it fails too, in
the same place as all the others (test #6).

I have another test from Doctor Memory, and all my DIMMS pass with easily on
multiple passes with that. Are you sure this memtest+ is reliable?

- Thom Walker