Hi,
We have two different bug checks:
BAD_SYSTEM_CONFIG_INFO (0x74)
The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is usually 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. Thee keys and values might be missing if a user manually edited the registry.
CRITICAL_OBJECT_TERMINATION (f4)
This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
-- 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
Unfortunately, given the above, the only usual workaround is to do a clean install of Windows as there is no way to 'repair' a registry that is so corrupted that it leads to this bug check. The only other thing aside from a clean install that works (but usually never does) is attempting to load a Last Known Good Configuration via the Boot Options.
The I/O error concerns me a bit as it may indicate a hardware issue with your HDD. An I/O error is when any hardware device (hard disk, flash drive, etc) cannot perform its basic input/output actions such as reading or copying data. When this is the case with a hard disk itself, or any storage related media, it's due to the device PHYSICALLY failing. Do note that with hard disks, the connections can be faulty as well (i.e the SATA cables from the controller on the board to the hard disk itself). At times, things like we see here (corrupt registry) can cause it as well.
Regards,
Patrick