Fatal System Error - Overclock.net

LegendaryC · 09-01-08

I've finally fixed my GPU BIOS. But now Windows is getting STOP C000021a Fatal System Error 0xc0000001 0x001003c0

Googled it and didn't get much help. I've tried ChkDsk (Found no errors.) I've tried System Restore (Through booting from the Vista DVD) and I get the "The Specified file has not been found" (0x80070002). Startup repair found an error but fixed it and said the system will start up correctly. (

) Now Startup repair says no problems found and that your problems might be caused by an unspecified change to your system configuration (My GPU getting it's BIOS flashed). Safe mode, and Start from last known configuration don't work either.

There's always something. Isn't there?

Lambent Darkness 7 · 09-01-08

This is what I found for you :

From a ms tech net article:

"I was having a lot of problems with Vista. My system was working beautifully on Vista. But all the sudden I received the Dumping Physical Memory blue screen, and my computer shut down. I was not doing anything special (reading blogs).

Any attempts to restart the computer gave me the following error:
STOP: c000021a (Fatal System Error)

Reinstalled vista, and I'm back. I ran utilities to check my HDD and RAM and have found no problems with them. I have the latest drivers, windows updates, antivirus definitions, etc.

I used to get the dumping physical memory error a lot (changed motherboard, both ram modules, reinstalled, upgraded to Sp1 and the problem went away for a while). However, in the past (prior to Sp1) it would never give me the c000021a error and not allow me to enter vista."

From my research, this is basicly the same thing I found other people doing to fix the problem. The most common cause of this error is a missing device driver dependency. This can happen even if the driver is not critical to boot. If the driver is not missing more than likely a file that a driver needs is missing. Had you recently uninstalled any software? If you know which apps you installed/uninstalled on your previous config, you might be able to figure out which app and/or driver caused this problem.

LegendaryC · 09-01-08

Quote:

Originally Posted by Lambent Darkness 7

This is what I found for you :

From a ms tech net article:

"I was having a lot of problems with Vista. My system was working beautifully on Vista. But all the sudden I received the Dumping Physical Memory blue screen, and my computer shut down. I was not doing anything special (reading blogs).

Any attempts to restart the computer gave me the following error:
STOP: c000021a (Fatal System Error)

Reinstalled vista, and I'm back. I ran utilities to check my HDD and RAM and have found no problems with them. I have the latest drivers, windows updates, antivirus definitions, etc.

I used to get the dumping physical memory error a lot (changed motherboard, both ram modules, reinstalled, upgraded to Sp1 and the problem went away for a while). However, in the past (prior to Sp1) it would never give me the c000021a error and not allow me to enter vista."

From my research, this is basicly the same thing I found other people doing to fix the problem. The most common cause of this error is a missing device driver dependency. This can happen even if the driver is not critical to boot. If the driver is not missing more than likely a file that a driver needs is missing. Had you recently uninstalled any software? If you know which apps you installed/uninstalled on your previous config, you might be able to figure out which app and/or driver caused this problem.

It's the nVidia driver and flashing my GPU BIOS caused it. That's what it is, I just don't know how to fix it.

Lambent Darkness 7 · 09-01-08

Quote:

Originally Posted by LegendaryC

It's the nVidia driver and flashing my GPU BIOS caused it. That's what it is, I just don't know how to fix it.

Ok, i'll see if it can find anything else out for you.

BountyHead · 09-01-08

Can you boot into safe mode? Uninstall the driver there?

noobdown · 09-01-08

lsass.exe - system error

Security Accounts Manager Initialization failed because of the following
error: A device attached to the system is not functioning. Error Status
0xc0000001. Please click Ok to shutdown this system and reboot into Safe
Mode, check the event log for more information.

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1561.)
This occurs when Windows switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised. 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 as a result of malware infestation or 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.

LegendaryC · 09-02-08

I reinstalled. All is good now.

Lambent Darkness 7 · 09-02-08

Quote:

Originally Posted by LegendaryC

I reinstalled. All is good now.

Sorry you had to reinstall. Everywhere I looked and researched (looked at a lot of articles) the users ended up reinstalling. Something got corrupted or missing with the drivers but could not find out what it was. Glad your up and running again.

		Overclock.net - Overclocking.net > Software, Programming and Coding > Operating Systems > Windows
Fatal System Error

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)