Member Avatar for 04ayasin

when i press f10 on my pc when it is booting up it displays the following:
Stop c000021a {Fatal System Error}
The session Manager Initialization process terminated unexpectedly with status of 0xc000003a (0x00000000 0x00000000) The system has been shutdown

does anyone know how i can resolve this problem thanks to all in advance

  • 3 Contributors
  • 4 Replies
  • 201 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

Brief summary: STOP c000021a is a fatal user‑mode failure — Windows reports that a critical user process (usually Winlogon or CSRSS) has terminated, so the kernel stops the system. It commonly follows a low‑level third‑party component, a failed update/restore, or disk/registry corruption; troubleshooting focuses on undoing whatever added or blocked required system files early in boot. (learn.microsoft.com)

Good catch by — Norton/Roxio GoBack and other boot‑level rollback/backup tools are frequent triggers because they install low‑level hooks that can interfere with setup and the Session Manager. If GoBack is present, disable it from its pre‑boot menu (press the GoBack boot‑screen key — often SPACE or Ctrl+Alt+G — then choose Disable), reboot and uninstall from Add/Remove Programs or the GoBack removal tools. Disabling will clear GoBack history; follow the vendor instructions before proceeding. (manualzilla.com)

If GoBack is not the issue or the crash persists, follow a short recovery sequence: try F8 → Last Known Good Configuration; boot Safe Mode and remove recently installed drivers/services; run a Repair/Recovery console and execute disk and file repairs; check for and clear pending file rename operations in the registry if updates were interrupted. Useful commands (run from Recovery Console or an elevated command prompt) include:

chkdsk C: /r
sfc /scannow

For stuck pending renames, load the offline hives and remove PendingFileRenameOperations under the Session Manager and RunOnce/RunOnceEx locations before rebooting. Back up registry hives before editing. (learn.microsoft.com)

Practical cautions: back up user data as soon as the system can be booted (even temporarily with GoBack disabled). Recovery images and some “system restore” tools can produce mismatched system files; if repairs fail a repair install or clean reinstall (using install media that matches the installed service pack) is often the reliable fix. The remark by about recovery tools being iffy is apt — treat them as helpful but not infallible. (learn.microsoft.com)

Recommended Answers

All 4 Replies

Member Avatar for zelkea

Have you change your disk configuration on this system? If not and you have GoBack installed check this thread.

AJZ

Member Avatar for 04ayasin

wow i never would have thought goback would be the culprit!!!
and its supposed to protect your computer hah

Member Avatar for zelkea

Agreed but that is what keeps me employed so I can't complain....... :)

AJZ

Member Avatar for jbennet

Yeah system recovery tools are iffy. (The OS recovery on my dell seemed to have some conflict when i upgraded to vista)

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.