You state this in your post #104
Why is that not a option.Reinstalling Windows is not an option
It is the proper way to do the install after changing the cpu and motherboard.
Why would one expect the the old motherboard bios, cpu, and driver specs to work with a new cpu and motherboard bios?
Have you been changing Boot Advanced options in msconfig?
Yes, I do have the drivers on auto-update, thanks. I have a problem getting EasyBCD to work and was looking for some tips.
Reinstalling Windows is not an option due to all the installed programs (many giveaways) which would not reinstall. As mentioned, the Advanced Boot options are not available at all.
Last edited by Vangelas; 28 Dec 2014 at 00:55. Reason: additional info
Those are the settings (Layback Bear's pic) I cannot access; from what I have read, it is due to Windows msconfig looking to the first partition (100MB) for the files to access the settings, instead of looking at the C: partition. I believe I need to change those settings due to the CPU change (or, perhaps if I fixed the bootmgr problem, the settings would probably adjust automatically).
Unless you have changed those setting before they should be proper.
Those setting have nothing to do with your reserve 100mb partition.
As far as I can tell you are not following any instruction or suggestions that we give you so I will be going.
Luck to you.
What mobo did you change from and to? I believe you said you did not do a clean install at that time.
Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Please also answer the questions about the motherboard. It is important. Please run and upload the
Blue Screen of Death (BSOD) Posting Instructions
and upload the unedited results here.
The 100MB System Reserved has nothing to do with msconfig. That is not your problem. Also, you do not have 8 cores, you have 4 cores and 8 threads. A thread is not a core and some programs read them as a core and some only read the actual cores.
Please download CPUz CPU-Z CPUID - System & hardware benchmark, monitoring, reporting and post screenshots of the CPU, Mainboard, Memore and SPD tabs. The SPD tabs will select eash Dimm slot from a dropdown box in the upper left portion of the screen, please only post the Dimm Slots populated with Ram.
If this is about you i7 3770 then it is a 4 core, 8 thread cpu and will never be more than 4 cores. Intel® Coreā
Edit: essenbe beat me to it.
sfc /scannow returns no integrity violations. The old mobo was ASUS P8 Z68-V PRO GEN3. The new mobo is ASUS P8 Z77 WS.I had dbpoweramp on an i7 at work and it definitely uses 8 threads when available.Here it still only uses 4 threads. I am posting the CPU-Z shots.
I am still wondering if anyone can help with my original question about the problem I have running EasyBCD.Thanks. In a separate post I will send the MS Win7 forum entries which prompted the question anonut msconfig.
A lot of people seem to have the problem where advanced boot options are not available in msconfig, and it always seems to relate to the boot partition; frequently seems to involve the 100MB partition.
The following may be wrong, and this is not the solution for me, but this is what prompted some of my questions :
In the MS Win7 Forums I read:
Question: "MSCONFIG will not let me check any of the boxes or enter "advanced options..." under the boot tab. I am the administrator and I have full ownership and permission of all files in the computer including the msconfig.exe"
Answer: "Hmm, I think I may have tracked down a clue. The system booted initially from the boot loader on the HFS+ volume, then handed off booting to the NTFS drive (I noticed I had the wrong boot drive selected, so I just picked the NTFS drive in the loader to boot Windows). So the BIOS may have tagged that as Disk 0 to the system. When Windows booted, it saw that it was booted from Disk 1, and msconfig/bcdedit is still looking for Disk 0 (the drive it would assume the system started up from), which isn't even a formatted drive."
...
"Yep, sure enough, msconfig works properly when boot-loaded from the BIOS (as disk 0), not from another loader. I'd classify that as a bug for sure, but a workaround would be to boot directly from the Windows drive - instead of, say, a dual-drive dual-boot setup. "
...
"IT worked!! I set the system reserved partition [disk 0] to the active partition in disk management and restarted, all things work fine. i can now access all portions of msconfig."
Where was the Active flag?
System Reserved should have been marked Active anyway, or Win7 normally would not boot unless you'd previously moved the System boot files to C.
Please post back a screenshot of Disk Management - Post a Screen Capture Image
Quote