XP won't start but continually checks disc and files.

[Hagan]

On turning the computer on, it gets stuck in a loop of checking the disc and
checking the files. No problems are found, but it merely starts the process
over again.

It will not start in Safe Mode.

Stopping the automatic restart on failure brings the following error message.

A problem has been detected and Windows has been shut down to prevent damage
to your computer.
This problem seems to be caused by the following file: win32k.sys
PAGE_FAULT_IN_NONPAGED_AREA
Technichal Information
*** STOP: 0x00000050 (0XC5F00023,0X00000000,0XBF8A80A4, 0X00000000)
*** win32k.sys – Address BF8A80A4 base at BF800000, Datestamp 48ce513a

I have tried using a startup CD by downloading ATW_WindowsXP_SP2_Boot_CD.ISO
but that produces the same result. Please would someone tell me how to
resolve this problem.

 

[HeyBub]

On turning the computer on, it gets stuck in a loop of checking the
disc and checking the files. No problems are found, but it merely
starts the process over again.

It will not start in Safe Mode.

Stopping the automatic restart on failure brings the following error
message.

A problem has been detected and Windows has been shut down to prevent
damage to your computer.
This problem seems to be caused by the following file: win32k.sys
PAGE_FAULT_IN_NONPAGED_AREA
Technichal Information
*** STOP: 0x00000050 (0XC5F00023,0X00000000,0XBF8A80A4, 0X00000000)
*** win32k.sys - Address BF8A80A4 base at BF800000, Datestamp
48ce513a

I have tried using a startup CD by downloading
ATW_WindowsXP_SP2_Boot_CD.ISO but that produces the same result.
Please would someone tell me how to resolve this problem.

The first Microsoft resolution of a 0x00000050 message points to an
out-of-date or defective video driver.
http://support.microsoft.com/kb/329293

The second mention is more insidious (and more likely):
---
This error message is caused by a kernel driver that is installed by the
following known rootkit spyware programs:
* Msupd5.exe
*Reloadmedude.exe
---
http://support.microsoft.com/kb/894278

You can find these, and others, by searching the Microsoft Knowledge Base
with
keyword = "0x00000050"