HELP – BSOD Cannot get into Safe Mode – System Restore doesn’t help

Topic

New Reply

Hello folks,
My pc has been doing fine with exception of IE 64 hanging and not opening. After much reading, resets, turning off helper apps, none helped.
I went to msconfig and clicked “diagnostic mode”. I rebooted, came to initial Windows Screen, then BSOD – Ox00000074.
I have read many threads to no avail, all talking about memory being bad. That is not the case.
I “CANNOT” get into Safe Mode, Boot Mode, well any mode from F8. I let Win7 do the diagnostics and repair, to no avail. I let Win7 do a System Restore, which it said completed fine, still BSOD.

I’m currently on a second drive on this same pc, but it is NOT up to date, however, I can access the other problem drive from this drive.
IS there a way or workaround where I can access the other drives msconfig and change diagnostic back, or access the registry on that drive and change
msconfig back to regular start-up. There is no doubt in my mind that the “diagnostic mode” caused the problem.

Thanks in advance for any thoughts and possible resolution you may have.

Tom

Reply | Quote

Replies

Cause

The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is unlikely, because the boot loader, known as NT Loader (NTLDR) in versions of Windows prior to Vista, checks a hive for corruption when it loads the hive.

This bug check can also occur if some critical registry keys and values are missing. These keys and values might be missing if a user manually edited the registry.
Resolving the Problem

Try restarting the computer by selecting “last known good configuration” in the boot options.

If the restart does not fix the problem, the registry damage is too extensive. You must reinstall the OS or use the Emergency Repair Disk (ERD) that you previously created by using the Windows Backup tool.

WinDbg Output Example:BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR was corrupt. This is unlikely, since the osloader will check a hive to make sure it isn’t corrupt after loading it. It can also indicate that some critical registry keys and values are not present. (i.e. somebody used regedt32 to delete something that they shouldn’t have) Booting from LastKnownGood may fix the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency Repair Disk.

What is the code in the final set of brackets after the 0x74?

Reply | Quote

satrow,

That’s what I’m going to do. Nothing has worked.

A quick ? –
In the registry, where are the settings “made” to msconfig as far as “Selective Start-Up”, Diagnostic etc. Just want to know what turns them on/off.
My thoughts were to get to the hive, save it to my current disk, and make a reg. change to mscofig to “load all start-up items”, move the hive back to the defective drive.
Just to see IF it would correct the boot problem?? Maybe this can’t be done or is not feasable??
Thanks so much,
Tom

PS – Don’t know the bracketed code – I’m almost afraid to try and boot up that drive for fear I cannot get back to this usable one??? – I looked at the old C: drive and a lot of the info is blank – for instance the Windows Folder is empty. “Users” is empty. and so on.

Reply | Quote