Daniel--
This error can mean a variety of things. Although it is difficult to write
error messages to be precise for stop errors, MSFT hasn't made much progress
in making them meaningful since they started writing them for years.
This message is often originated because when Windows switches into kernel
mode and a user-mode subsystem, such as Winlogon or the Client Server
Runtime Subsystem (CSRSS), is compromised and security can no longer be
guaranteed. Because Win XP can't run without Winlogon or CSRSS, this is one
of the few situations where the failure of a user-mode service can cause the
system to stop responding. This Stop message also can occur when the
computer is restarted after a system administrator has modified permissions
so that the SYSTEM account no longer has adequate permissions to access
system files and folders.
The messages can mean quite a number of things, and there are a several
nebulous MSKBs purporting to explain this one in different contexts. Many
of them are software origin as well as hardware, and after you rule out hdw
as the cause of this, and I belive you will, I'd do this:
Turn off deadlock detection in your XP driver verifier and turn off
inspection of your antivirus drivers (there will be about 5 depending on
which flavor of AV you have on the XP box).
1) You seem to be dual booting so on your XP boot type "verifier" in run box
and disable deadlock detection.
2) Disable the *inspection* by driver verifier of the software drivers--yep
I said software drivers of whatever Antivirus program you are using.
1. Click Start, click Run, and then type verifier.
2. After Driver Verifier Manager starts, click Display Existing
Settings, and then confirm that Deadlock Detection is turned on.
3. Click Back.
4. Click Create Custom Settings, and then click Next.
5. Click Select Individual settings from a full list, and then click
Next.
6. Click the settings that you want to turn on, make sure the Deadlock
Detection check box is not selected, and then click Next.
7. Click the drivers that you want to verify, and then click Next or
Finish if you choose all drivers on your computer.
8.
Restart the computer.
If you cannot log on to the computer after you restart with Driver Verifier
turned on, turn off Driver Verifier, but this occurence is rare. To do so,
start the computer in Safe mode, log on by using an account that has
administrator rights, start Driver Verifier, and then choose to delete the
existing settings. After you do so, Driver Verifier is turned off.
This alone is a much more common cause of BSOD stops of many stripes than
MSFT's engineers have come to recognized yet. A frequent comment you'll
hear from MSFT engineers is that 80% of BSOD stops are driver induced.
That's a real oversimplification. But I would review if you installed any
recent drivers on your XP box lately and make sure you're satisfied with
them.
I would also reburn the DVD, making sure that you use a slow speed, close
the session, use the ISO tab on your burning software if it has one, and
also add this little mentioned step:
Get to Dev Manager by typing devmgmt.msc in run/win key + pause break or Rt.
click My Computer>Prop>hardware tab>Device Manager if you like 5 steps
instead of one cmd. If you're set to PMI here change to DMO and if set to
DMO change to PMI:
a.. Click the + in front of IDE ATA/ATAPI Controllers
a.. Double Click the Secondary IDE Controller
a.. Click Advanced Settings
a.. Under Device 1 Next to Transfer Mode choose DMA (or vise versa)
a.. Click OK
a.. Reboot your System
Good luck,
CH
