Infinite restarting


R

Rayne

Hi,

My 5-year-old Fujitsu laptop recently has this problem of rebooting
infinitely. I did not install any new hardware or software. The only
thing different that I did was that for the past 3 years, I only ran
it on AC power, and right before this problem occurred, I unplugged
the power and ran it on the battery for about half an hour.

The laptop starts booting up, and while the Windows XP screen is
running, I would get the following screen:

"Checking file system on C:
The type of the file system is FAT32.

One of your disks need to be checked for consistency.
...."

The laptop then continues to check disk consistency. Occasionally,
it'll report some entries that need to be repaired, while other times
there aren't any repairing to be done.

The laptop then restarts itself, sometimes after the check is
completed, other times while the check is still running. Right before
the laptop restarts, I'll get the blue screen for a couple of seconds
(too fast to really see what it says). I am able to get the blue
screen to stay on my screen by using one of the F8 options, though,
and it says:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
....
Technical information:
*** STOP:0x000000D1 (0x73656CD7, 0x00000002, 0x00000000, 0xF902BA68)
*** w22n51.sys - Address F902BA68 base at F9007000, DateStamp 404c5c4c

I am unable to get into safe mode - the system hangs at agpCPQ.sys.
Trying to load the last known good configuration doesn't work - the
laptop continues to restart itself. I also don't have the Windows XP
CD, so I can't try to use the Recovery Console method that I've seen
suggested on the Net.

What can I do?

Thank you.
 
Ad

Advertisements

P

Pegasus [MVP]

Rayne said:
Hi,

My 5-year-old Fujitsu laptop recently has this problem of rebooting
infinitely. I did not install any new hardware or software. The only
thing different that I did was that for the past 3 years, I only ran
it on AC power, and right before this problem occurred, I unplugged
the power and ran it on the battery for about half an hour.

The laptop starts booting up, and while the Windows XP screen is
running, I would get the following screen:

"Checking file system on C:
The type of the file system is FAT32.

One of your disks need to be checked for consistency.
..."

The laptop then continues to check disk consistency. Occasionally,
it'll report some entries that need to be repaired, while other times
there aren't any repairing to be done.

The laptop then restarts itself, sometimes after the check is
completed, other times while the check is still running. Right before
the laptop restarts, I'll get the blue screen for a couple of seconds
(too fast to really see what it says). I am able to get the blue
screen to stay on my screen by using one of the F8 options, though,
and it says:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
...
Technical information:
*** STOP:0x000000D1 (0x73656CD7, 0x00000002, 0x00000000, 0xF902BA68)
*** w22n51.sys - Address F902BA68 base at F9007000, DateStamp 404c5c4c

I am unable to get into safe mode - the system hangs at agpCPQ.sys.
Trying to load the last known good configuration doesn't work - the
laptop continues to restart itself. I also don't have the Windows XP
CD, so I can't try to use the Recovery Console method that I've seen
suggested on the Net.

What can I do?

Thank you.

If the problem is caused by a bad registry entry then you can probably fix
it with a manual System Restore - see here:
http://support.microsoft.com/kb/307545. The method relies on you being able
to access the hard disk. Here are a few options:
a) Borrow a WinXP CD from a friend, then start the Recovery console.
b) Boot the machine with a Bart PE boot CD (www.bootdisk.com).
c) Temporarily install your disk as a slave disk in some other WinXP PC.
This is not a trivial exercise and if you're inexperienced in such things
then you should ask a computer-savvy friend to assist you.

If the problem is caused by some file corruption then a repair installation
may fix it. You will need the correct type of WinXP CD
(Home/Professional/OEM/Retail).

If all else fails then a factory restore will fix the problem. Read the
manual that came with your PC to see how it's done. You might lose all data
files in the process - do you have backups?
 
R

Rayne

If the problem is caused by a bad registry entry then you can probably fix
it with a manual System Restore - see here:http://support.microsoft.com/kb/307545. The method relies on you being able
to access the hard disk. Here are a few options:
a) Borrow a WinXP CD from a friend, then start the Recovery console.
b) Boot the machine with a Bart PE boot CD (www.bootdisk.com).
c) Temporarily install your disk as a slave disk in some other WinXP PC.
This is not a trivial exercise and if you're inexperienced in such things
then you should ask a computer-savvy friend to assist you.

If the problem is caused by some file corruption then a repair installation
may fix it. You will need the correct type of WinXP CD
(Home/Professional/OEM/Retail).

If all else fails then a factory restore will fix the problem. Read the
manual that came with your PC to see how it's done. You might lose all data
files in the process - do you have backups?

That's the problem. I was going to back up my data when this problem
happened. Is w22n51.sys related to some driver, that I can uninstall
so I can at least boot up normally and back up my data?
 
M

Malke

Rayne said:
That's the problem. I was going to back up my data when this problem
happened. Is w22n51.sys related to some driver, that I can uninstall
so I can at least boot up normally and back up my data?

The w22n51.sys belongs to an Intel wireless network adapter. However, your
issues may be hardware-related instead. A corrupted wireless network
adapter wouldn't stop you getting into Safe Mode.

I would back up your data *now* by doing one of the following:

1. Boot with a Bart's PE or Linux Live CD and copy the data to an external
hard drive. I prefer to use Knoppix Linux. Booting with Knoppix gives you
the additional information as to whether this is hardware or software. If
the system behaves perfectly in Linux, then you know Windows is corrupted.
If the system behaves badly in Linux, then you know it's a hardware
problem.

2. Pull the drive and put it in a USB external drive enclosure and connect
it to a working PC to copy the data off.

After that, I would do hardware diagnostics to be sure the hardware is
sound.

http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

If the hardware is good, you can proceed with the fix Pegasus gave you or do
a clean install of Windows. If you can't borrow a matching Dell XP install
CD, then a generic OEM one will work but a Dell disk is preferable.

Malke
 
Ad

Advertisements

P

Pegasus [MVP]

If the problem is caused by a bad registry entry then you can probably fix
it with a manual System Restore - see
here:http://support.microsoft.com/kb/307545. The method relies on you
being able
to access the hard disk. Here are a few options:
a) Borrow a WinXP CD from a friend, then start the Recovery console.
b) Boot the machine with a Bart PE boot CD (www.bootdisk.com).
c) Temporarily install your disk as a slave disk in some other WinXP PC.
This is not a trivial exercise and if you're inexperienced in such things
then you should ask a computer-savvy friend to assist you.

If the problem is caused by some file corruption then a repair
installation
may fix it. You will need the correct type of WinXP CD
(Home/Professional/OEM/Retail).

If all else fails then a factory restore will fix the problem. Read the
manual that came with your PC to see how it's done. You might lose all
data
files in the process - do you have backups?

That's the problem. I was going to back up my data when this problem
happened. Is w22n51.sys related to some driver, that I can uninstall
so I can at least boot up normally and back up my data?

============

Funny how the need to back up important files becomes essential immediately
*after* the system has failed. Time to review your backup philosophy!
Important files must be backed up regularly (e.g. weekly) to an independent
medium that is kept well away from the main PC for most of the time. A 2.5"
disk in an external USB case would make an excellent but low-cost backup
device. Two is even better so that you can alternate between them.
 
Ad

Advertisements

R

Rayne

That's the problem. I was going to back up my data when this problem
happened. Is w22n51.sys related to some driver, that I can uninstall
so I can at least boot up normally and back up my data?

============

Funny how the need to back up important files becomes essential immediately
*after* the system has failed. Time to review your backup philosophy!
Important files must be backed up regularly (e.g. weekly) to an independent
medium that is kept well away from the main PC for most of the time. A 2.5"
disk in an external USB case would make an excellent but low-cost backup
device. Two is even better so that you can alternate between them.

I disabled my LAN (as well as Wireless LAN and modem) in the BIOS and
(for now, at least) I am able to boot up.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top