Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
February 29, 2000
In tip 2033, we first discussed this BSOD.
Another possible reason is that the System account does NOT have Full Control of the %SystemRoot%System32Config folder.
To resolve the problem, you need an alternate install of WinNT, preferably on a different drive, partition, or folder.
Boot the alternate install and grant the System account Full Control of the original installations hive(s).
You May Also Like