Hi,
Results verified by WinDBG, DumpCHK, BlueScreenView.
The Bug_Check was 74 CAUSE ntkrnlmp.exe which is a Windows component which
means something else drove it into Fault.
BugCheck 74, {2, fffff88002bfd9e0, 2, ffffffffc000014c}
Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a )
IMAGE_NAME: ntkrnlmp.exe
FAILURE_BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a
BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a
1. Check blossomz's reply in this thread ( I suspect those with this issue have been
trying to do some unusual over-clocking.)
2. Test the memory very thoroughly. Keep in mind that memory tests do not detect all errors
such as the tiny speed differences between modules that appear to be identical. So it may
be necessary to swap the modules in and out in different combinations and patterns. See
the memory testing methods in the next message.
3. Check with the System Maker's Support (Motherboard Maker for custom systems), their
on-line documentation and drivers, diagnostics, and ask in their forums about any known
issues.
4. Use the other methods in the troubleshooters previously posted and those below.
==================================================================
Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.
http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7
See this thread for information on using BlueScreenView, MyEventViewer, and other methods to
troubleshoot BlueScreens - top 3 replies (+1 other).
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990------------------------------------------------------
BCCode: 74 0x00000074
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. Thee keys and values might be missing if a user manually edited the registry.
Resolution
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.
BCCode: 74 0x00000074 <-- read thishttp://www.faultwire.com/solutions-fatal_error/BAD-SYSTEM-CONFIG-INFO-0x00000074-*1131.html?order=date
Methods to try:
Last Known Good Configuration :
Repeatedly tap F8 as you boot and select "Last Known Good Configuration".
Using Last Known Good Configuration
http://windows.microsoft.com/en-us/windows7/Using-Last-Known-Good-Configuration
System Restore "might help"
How to Do a System Restore in Windows 7
http://www.sevenforums.com/tutorials/700-system-restore.html
============================
You can try some of these in Safe Mode - repeatedly tap F8 as you boot.
If you do not have a Windows 7 disk you can borrow a friends as they are not copy
protected. Your System maker will also sell the physical DVD cheap since you already
own Windows. Also you can make a repair disk on another computer.
Try Startup Repair - (If at ANY point you gain some but not full access to Windows come
back and try Startup Repair again.)
How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html
What are the system recovery options in Windows 7?
http://windows.microsoft.com/en-us/windows7/What-are-the-system-recovery-options-in-Windows-7
Try StartUp Repair from Recovery Options or Windows 7 disk.
How to Run a Startup Repair in Windows 7
http://www.sevenforums.com/tutorials/681-startup-repair.html
Also from the COMMAND PROMPT of Recovery Console (if possible) or a Windows 7 disk
Start - type in Search box - COMMAND find at top of list - RIGHT CLICK - RUN AS ADMIN
sfc /scannow
How to Repair Windows 7 System Files with System File Checker
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Then run checkdisk (chkdsk).
How to Run Disk Check in Windows 7
http://www.sevenforums.com/tutorials/433-disk-check.html
Retry Startup Repair after Chkdsk.
If needed after those you can try System Restore from Safe Mode or the Recovery or Windows 7
disk.
How to Do a System Restore in Windows 7
http://www.sevenforums.com/tutorials/700-system-restore.html
**If you need to make repair disks - these help repair Windows not re-install.**Often a Repair Disk will help when the Recovery Disk does not.
Download Windows 7 System Recovery Discs - now charging $9.75 for the ISO
images to make the disks.
http://neosmart.net/blog/2009/windows-7-system-repair-discs/
How to Create a Windows 7 System Repair Disc - Free
http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html
======================================
If needed :
How to Boot to the System Recovery Options in Windows 7
http://www.sevenforums.com/tutorials/668-system-recovery-options.html
What are the system recovery options in Windows 7?
http://windows.microsoft.com/en-us/windows7/What-are-the-system-recovery-options-in-Windows-7
How to Do a Repair Install to Fix Windows 7
http://www.sevenforums.com/tutorials/3413-repair-install.html
Hope this helps.
Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.