System Reboots

  • Thread starter Thread starter Earl Partridge
  • Start date Start date
E

Earl Partridge

XP Home
The machine reboots itself occasionally.
I'm waiting for an AMI BIOS update. While looking into Setup I noticed the
Primary Graphics Adapter was PCI. Since there is no PCI adapter, I changed that
to "On Board AGP".

It's up and running, waiting to see if it reboots again. Any thoughts as to whether or
not this change I made will have any effect?

Earl
 
Is the graphics realy onboard and AGP? Is it still working?
XP Home
The machine reboots itself occasionally.
I'm waiting for an AMI BIOS update. While looking into Setup I noticed the
Primary Graphics Adapter was PCI. Since there is no PCI adapter, I changed that
to "On Board AGP".

It's up and running, waiting to see if it reboots again. Any thoughts as to whether or
not this change I made will have any effect?

Earl
 
There is definitely no PCI card. And the machine works so I guess that means
the "graphics" is working. And, by changing that in the CMOS, did not help.
It did reboot again.
Earl

Is the graphics realy onboard and AGP? Is it still working?
XP Home
The machine reboots itself occasionally.
I'm waiting for an AMI BIOS update. While looking into Setup I noticed the
Primary Graphics Adapter was PCI. Since there is no PCI adapter, I changed that
to "On Board AGP".

It's up and running, waiting to see if it reboots again. Any thoughts as to whether or
not this change I made will have any effect?

Earl
 
Earl Partridge said:
XP Home
The machine reboots itself occasionally.
I'm waiting for an AMI BIOS update. While looking into Setup I noticed the
Primary Graphics Adapter was PCI. Since there is no PCI adapter, I changed that
to "On Board AGP".

It's up and running, waiting to see if it reboots again. Any thoughts as to whether or
not this change I made will have any effect?

Earl
Click to expand...

If it still reboots open Control Panel - System and go to the Advanced
tab. Click on the Settings button in the Startup and Recovery
(bottom) section of the Window. In the Startup and Recovery window
click on the checkbox for "Automatically restart" to clear it if it is
selected, then click on OK and Apply as needed to exit.

That should put an end to the sporadic reboots. However they may be
replaced by a "Blue Screen Of Death" STOP error message. If that does
happen then the contents of the STOP error message, including the STOP
code, all 4 parameter values, and any file or module names mentioned
will be a direct clue as to the underlying cause of the problem. Post
that detailed information back here.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
With Auto Restart disabled, I have received several blue screen Stops.
Some have indicated memory dump, but this latest blue screen does not
indicate a memory dump.
I got this: 0x00000067 (0x00000001, 0x0000000D, 0xC0000005, 0x00000000)
Earl
 
Repeat and amplify...
With Auto Restart disabled, I have received several blue screen Stops.
Some have indicated memory dump, but this latest blue screen does not
indicate a memory dump.
I got this: 0x00000067 (0x00000001, 0x0000000D, 0xC0000005, 0x00000000)

(New Note) Prior to that blue screen I had upgraded BIOS and was
disappointed
that I still got that blue screen within about 2 hours after the upgrade.
Now, (next
day), I left the machine on overnight and it had not rebooted. That's over
a period
of about 15 hours. Maybe that BIOS upgrade has solidified...

Earl
 
Maybe spoke too soon. I just did a reboot and within 15 minutes got one of
those windows offering to report to Microsoft (not a blue screen). The top
part
indicated:
Error Signature:
BCCode: 1000008e BCP1: C000001D BCP2:E1BF7D51 BCP3: F729C978
BCP4: 00000000 OSVer: 5_1_2600 SP: 2_0 Product: 768_1

Does this provide any insight?

Earl
 
I did get another blue screen with the following:
------------------------
Stop 0x0000008E (0xC0000005, 0xBF802911, 0xF7627988, 0x00000000)
Win32k.sys - Address BF802911 Base at BF800000, Datestamp 45f013f6
-----------------------
This after I had replaced Win32k.sys from another machine.

I ran the diagnostic, no errors found. I have now replaced the memory,
rebooted
and now waiting to see what happens.

Earl
 
Earl Partridge said:
Repeat and amplify...
With Auto Restart disabled, I have received several blue screen Stops.
Some have indicated memory dump, but this latest blue screen does not
indicate a memory dump.
I got this: 0x00000067 (0x00000001, 0x0000000D, 0xC0000005, 0x00000000)

(New Note) Prior to that blue screen I had upgraded BIOS and was
disappointed
that I still got that blue screen within about 2 hours after the upgrade.
Now, (next
day), I left the machine on overnight and it had not rebooted. That's over
a period
of about 15 hours. Maybe that BIOS upgrade has solidified...

Earl
Click to expand...

OUCH!!!!

Here is what Microsoft says about that error code:
Bug Check 0x67: CONFIG_INITIALIZATION_FAILED
The registry couldn't allocate the pool needed to contain the registry
files. This should never happen, since it is early enough in system
initialization that there should be plenty of paged pool available.
http://msdn2.microsoft.com/en-us/library/ms795675.aspx

Sounds like a hardware related issue of some kind to me, but I will
check further and see if I can find anything else.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
Earl Partridge said:
Maybe spoke too soon. I just did a reboot and within 15 minutes got one of
those windows offering to report to Microsoft (not a blue screen). The top
part
indicated:
Error Signature:
BCCode: 1000008e BCP1: C000001D BCP2:E1BF7D51 BCP3: F729C978
BCP4: 00000000 OSVer: 5_1_2600 SP: 2_0 Product: 768_1

Does this provide any insight?
Click to expand...

0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
is the same error as
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
This indicates that a kernel-mode program generated an exception
which the error handler did not catch.
http://msdn2.microsoft.com/en-us/library/ms794023.aspx

With this error code the value in parameter 2 (E1BF7D51 in your
example) is the memory address where the error occurred. If we can
identify which item (Windows component, application program, device
driver, etc.) is using that memory address then that would point to a
prime suspect.

I hope you chose the option to report this error to Microsoft. There
are two very good reasons for doing this:
1. If this is a known error with a specific cause and maybe even a
fix, you will get an immediate response with a web page showing you
this information.
2. If there is no information about your exact error condition then
the details are added into the product support dept's incident data
base. Errors with high numbers of reported incidents and especially
those with possibly serious consequences (such as STOP errors that
shut down the machine causing potential loss of or damage to data) are
selected from this data base for detailed investigation by product
support specialists.

One further point. If this same error code keeps recurring, check the
values of both parameter 1 and parameter 2 and compare these wtih
previous instances. If these parameters are consistent for repeated
instances of the error then that indicates that a software related
issue is the most likely cause. On the other hand if the error code
is the same but parameters 1 and 2 (for this specific error code) tend
to be different each time then that indicates that it is more likely
to be a hardware related issue of some kind, such as bad RAM,
overheating, power supply defective, etc etc.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
I have tried different memory, 3 different hard drives, removing programs,
etc.
I have concluded that this machine is not compatible with XP. I now have
Windows 2000 running on it and it appears to be stable.
Earl
 
Back
Top