I've been doing some research as to how to fix it but i haven't found anything yet.
After hearing about build 7068 i got my hopes up and downloaded it right away. After trying to install it i get the same BSOD right at the installation.
I am running 7000 on an AMD 64X2 Foxconn mbd, and yes, BSOD ON INSTALL of Win 7 64. Win 7 32 did install, runs ok for a few hours, then BSOD. Event log just shows lots of "surprise" system shutdowns. Gee.
This system is solid as a rock under XP 64. I mean no problems whatever.
Yes, I am slightly overclocked. But do you really expect me to try and figure out if and how to tweak my Northbridge voltage just to run Win 7?
Whining aside, my guess is that soon MSFT will stop supporting XP, and I will have to migrate (Vista is just too aggravating). So, HOW do I start hunting down these issues systematically? To WHOM do I send dumpfiles? Who at MSFT is a Win7 poc? Have not seen any answers to these questions on the Win 7 site.Shouldn't MSFT be ashamed of themselves?
FYI, my MSI Wind netbook runs both XP AND OSX Leopard flawlessly. Win7 on the MSI Wind had, no surprise to me, lots of driver problems, just like the Vista beta.
Windows 7 seems to put more of a load on the memory controller which tends to cause crashing if the voltages aren't up to snuff. I have an easy bios to use and it only takes a minute to raise the northbridge SPP voltage which made all the difference in system stability. Before I moved the up the SPP it was crash city all the time, especially when trying to move files accross the network.
It could be Ram voltage or the SPP voltage that is causing this issue but with so many different types of systems it's hard to nail this one down, but for me it was easy to fix after a frustration week of BSOD's.
From Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
The STATUS_SYSTEM_PROCESS_TERMINATED bug check has a value of 0xC000021A. This means that an error has occurred in a crucial user-mode subsystem.
Parameters
The following parameters are displayed on the blue screen.
ParameterDescription 1A string that identifies the problem 2The error code 3Reserved 4Reserved Cause
This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed. In response, the operating system switches to kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS. Therefore, this is one of the few cases where the failure of a user-mode service can shut down the system.
Mismatched system files can also cause this error. This can occur if you have restored your hard disk from a backup. Some backup programs might skip restoring system files that they determine are in use.
Resolving the Problem
Running the kernel debugger is not useful in this situation because the actual error occurred in a user-mode process.
Resolving an error in a user-mode device driver, system service, or third-party application: Because bug check 0xC000021A occurs in a user-mode process, the most common culprits are third-party applications. If the error occurred after the installation of a new or updated device driver, system service, or third-party application, the new software should be removed or disabled. Contact the manufacturer of the software about a possible update.
I finally solved my BSOD problem with Windows 7 Build 7000 - 7068 x64. It was an issue with my Sata drive and AHCI mode. Here are the steps i took to resolve the issue, hope it helps other with the same problem.
1) Went into Bios and set up my HDD to IDE/Compatibility mode.
2) Started up Windows Setup.
3) Once inside the desktop after first reboot go to HKLM\System\CurrentControlSet\Services\Msahci.
4) Change Start value from 3 to 0
5) Reboot back into Bios and change HDD back to AHCI.
After that i went back to Windows 7 and everything worked fine. Rebooted about 5 times to make sure i didn't get the BSOD again, so far everything is working good.
Quote