Member Avatar for k48dolly

Hi everyone, I am new here and am in need of help. I have a laptop vostro 1500 and have windows xp. I was on the computer one night, then I turned it on on the morning to find a nightmare. after I turned it on, it asked for my password, then it went black, then blue with a error message: Stop:c000021a {fatal system error} The session manager initialization system process terminated unexpectedly with a status of 0xc000026c (0x00000000 0x00000000) The System Has Been Shut Down.
I have tried to start it in safe mode, and last good known configuration, dosen't work.
I don't know what to do, but this thing has all my work information on it, and I don't have a back up.
Can someone please help?

  • 6 Contributors
  • 6 Replies
  • 450 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by BritLee

Dani AI

Generated

Stop: c000021a (status 0xc000026c) means a critical user‑mode subsystem (commonly winlogon.exe or csrss.exe) has stopped and XP shut itself down. Common root causes are corrupted system files (disk errors), a bad update/hotfix, or failing RAM. Several replies in this thread point at all three: flagged an update, had success after fixing bad sectors and restoring corrupt .sys/.dll files, suggested a repair from the XP CD, and noted memory as a possible hardware cause.

Priority sequence (safe, practical approach):

  1. Recover personal data first. Boot the machine from a rescue environment (Linux live USB, Windows PE or a boot CD like Hiren’s), or remove the laptop drive and attach it to another computer. Copy the whole profile folder (C:\Documents and Settings\<username>), any Outlook PSTs, desktop files and any project folders to an external drive before attempting repairs.

  2. Check and repair the disk. With the XP CD -> Recovery Console run:

    chkdsk /r

    This finds and repairs bad sectors and can recover unreadable files (as described).

  3. Repair system files. If chkdsk helps but Windows still won’t start, try an in‑place Repair Install from the XP CD (setup -> press R to repair the existing installation). This replaces core system files while keeping programs and user data. If a specific hotfix is suspected, inspect the drive (once mounted) for $NtUninstallKBxxxxxx folders or the dllcache to restore original files.

  4. Test hardware. Run Memtest86 from a USB stick and try booting with memory modules swapped/removed one at a time to rule out bad RAM.

If those steps fail, a clean reinstall (after confirming a full backup) or professional data recovery are the last resorts. The safest immediate action is: back up data, run chkdsk, test memory, then attempt repair install.

Recommended Answers

All 6 Replies

Member Avatar for Bob_180_Bob

Hi,
You will have to boot your PC from the win XP installation disk and do a system repair. If you don't know how, just google it and you will find full instructions.

Member Avatar for sparkax

The update KB925902 is known to cause this problem.
If it has recently been installed - remove it.
Reboot and see if problem remains.
If the BSOD has gone and you want the update -try reinstalling the
update in Safe Mode.

Member Avatar for k48dolly

The update KB925902 is known to cause this problem.
If it has recently been installed - remove it.
Reboot and see if problem remains.
If the BSOD has gone and you want the update -try reinstalling the
update in Safe Mode.

Hi, don't mean to sound dumb but what is BSOD

Member Avatar for caperjack

Hi, don't mean to sound dumb but what is BSOD

bsod=Blue screen of DEATH

Member Avatar for terriegg

i had to scan my disk for bad sectors. The scan results gave me two files which were corrupt and corresponding hdd sectors were fixed by the scanner making the files essentially unreadable. One was a .sys and the other was a .dll. Backup of dll was present in dllcache folder and the backup of sys file was present in windows hotfix folders. This PC was running XP. Once i restored the corrupted files, i was able to use windows xp :)

Member Avatar for BritLee

This is a problem of your RAM it useally happen when the RAM got so heated or the RAM is going to be finished in few days.

<snip>

Edited by crunchie because: Snipped url. Keep it spam free.
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.