Periodic reboots

[GRAYGHOST]

My Windows XP System reboots at random times while playing some games!

When I run the System event viewer, I get the following:

"The computer has rebooted from a bugcheck. The bugcheck was:
0x100000d1 (0x00008698, 0x00000007, 0x00000000, 0xf7556bd4). A dump
was saved in: C:\WINDOWS\Minidump\Mini121605-03.dmp."

I can't find anything useful about the stop message "0x100000d1", nor
any of the parameters!

Can anyone help?

I have changed video cards & memory. Before I change out the CPU or
motherboard, I'd like to know if anyone else has had this problem and
how they may have solved it! I have tried running WINDBG, but I do
not have the SYMBOLS file that it requires and Microsoft is no help
for a novice like myself. Any help would be greatly appreciated!!!

grayghost

 

[Guest]

Please specify you hardware

 

[Unk]

My Windows XP System reboots at random times while playing some games!

When I run the System event viewer, I get the following:

"The computer has rebooted from a bugcheck. The bugcheck was:
0x100000d1 (0x00008698, 0x00000007, 0x00000000, 0xf7556bd4). A dump
was saved in: C:\WINDOWS\Minidump\Mini121605-03.dmp."

I can't find anything useful about the stop message "0x100000d1", nor
any of the parameters!

Can anyone help?

I have changed video cards & memory. Before I change out the CPU or
motherboard, I'd like to know if anyone else has had this problem and
how they may have solved it! I have tried running WINDBG, but I do
not have the SYMBOLS file that it requires and Microsoft is no help
for a novice like myself. Any help would be greatly appreciated!!!

grayghost

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 message indicates that the system attempted to access pageable memory using a
kernel process IRQL that was too high. The most typical cause is a bad device driver. It can
also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

DRIVER_IRQL_NOT_LESS_OR_EQUAL
http://support.microsoft.com/?kbid=810093
http://aumha.org/win5/kbestop.php#0xd1


Windows XP has a default setting to "Restart on failure"
You can change this restart behavior if you want.

Click Start, Settings, Control Panel, System, Advanced
In the Startup and Recovery section, click on the "Settings" button to open the Startup and
Recovery window.
In the System Failure section, uncheck "Automatically restart", Click "Apply", "OK"

After that change the computer will no longer restart when a system failure occurs. Instead it
will probably throw up a "Blue Screen Of Death" with a STOP error message and then halt
completely, requiring a manual power off and restart (or reset if it has a hardware reset
switch). But the contents of the STOP error message will give a specific clue
as to the underlying cause of the problem.

Don't be suprised, if after changing the setting, things appear to run just fine.
Some errors are so minor that they will only show up in the Event logs and not produce a BSD.
However, they would still evoke the restart if the setting were changed back to the default.

 

[GRAYGHOST]

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 message indicates that the system attempted to access pageable memory using a
kernel process IRQL that was too high. The most typical cause is a bad device driver. It can
also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

DRIVER_IRQL_NOT_LESS_OR_EQUAL
http://support.microsoft.com/?kbid=810093
http://aumha.org/win5/kbestop.php#0xd1


Windows XP has a default setting to "Restart on failure"
You can change this restart behavior if you want.

Click Start, Settings, Control Panel, System, Advanced
In the Startup and Recovery section, click on the "Settings" button to open the Startup and
Recovery window.
In the System Failure section, uncheck "Automatically restart", Click "Apply", "OK"

After that change the computer will no longer restart when a system failure occurs. Instead it
will probably throw up a "Blue Screen Of Death" with a STOP error message and then halt
completely, requiring a manual power off and restart (or reset if it has a hardware reset
switch). But the contents of the STOP error message will give a specific clue
as to the underlying cause of the problem.

Don't be suprised, if after changing the setting, things appear to run just fine.
Some errors are so minor that they will only show up in the Event logs and not produce a BSD.
However, they would still evoke the restart if the setting were changed back to the default.

Thanks for the response! I will try changing the memory module first.
I have a DFI mobot (NFII 400-AL), an AMD 2800+ CPU, a GeForce 6600
video card, 200GB and 80 GB HDD. I built it my self a couple years
ago. I started having is problem a month ago and have periodically
worked on it since. I will get back to yall!! Again, THANKS!

grayghost

 

[GRAYGHOST]

Thanks for the response! I will try changing the memory module first.
I have a DFI mobot (NFII 400-AL), an AMD 2800+ CPU, a GeForce 6600
video card, 200GB and 80 GB HDD. I built it my self a couple years
ago. I started having is problem a month ago and have periodically
worked on it since. I will get back to yall!! Again, THANKS!

grayghost

Hello! Upon further review! Is stop code (0x100000d1) the same as
(0x000000d1)? I get stop (0x100000d1). After changing the "Settings"
to uncheck "Automatically restart", I got the BSOD and the the same
stop code and parameters as above. The site you mentioned does not
have this particular stop code (0x100000d1). Thanks for your
response!

grayghost

 

[GRAYGHOST]

I checked the manufacturer's specification for my motherboard ( I had
done this before, but not looked for the RAM specs). The NFII 400AL
mobot requires RAM with 2.5v, the two sticks of Kingston 512MB DDR400s
were 2.6v. I have replaced them with 2 sticks of RAM with 2.5v and I
ran the whole day without a reboot. Now that sounds amazing to me.
Maybe I'm counting my chickens before they are hatched. But so far, so
good.

The BIOS for my mobot allows me to specify DIMM voltage of 2.5v. 2.6v.
2.7v and 2.8v. When I got the two sticks of 512 (2.6v) I must have
changed the BIOS to 2.6, at least that is how it was set when I
looked. It may be that the Award BIOS allows these settings but the
mobot does not like the RAM to have 2.6v. It only seemed to show the
reboot problem when I'm using the video card in games, which probably
stresses the DIMMs. (Only a guess).

Anyway, if it fails I will let you guys know!

THANKS a bunch ! I am glad this group exist!

grayghost