@tayyar - Here, should be all relevant to your board things unlocked now, and BIOS/SMI lock disabled by default (you will need to disable first to flash this in, but after that should be always unlocked)
This time (only), to clear old NVRAM out, flash like this >> FPTw.exe -rewrite -bios -f filename.bin
Stop, DO NOT reboot if you get error doing the above flash, if you do, then reflash some other known working BIOS region first before you reboot (via FPTw.exe -bios -f filename.bin)
http://s000.tinyupload.com/index.php?fil...871397252196507

@Lost_N_BIOS No errors, flashed fine.

However there are three empty text but selectable boxes as shown in the screenshot. No big deal though.

Otherwise, I'm happy. There are tons of stuff now :)

Yes, sorry, there was a few things I wasn't sure about if you'd see options or not. Tell me what each one is and I'll remove them
1. OC Tuner
2. ?
3. ?

Oc Tuner
Start tuning?
Easy overclocking

Thanks, here is fixed. Tonight I will make one with microcode V7 for you
http://s000.tinyupload.com/index.php?fil...577098741340804

@Lost_N_BIOS thanks. now comes the final step :) waiting for the bios with v7

@tayyar - Due to microcode locations in this BIOS, and limited tools that can work with files in this location, this is a risky flash... Did you get your programmer figured out how to backup and program BIOS on this board?
Additionally, we may also need to replace that anomalous microcode I mentioned too, and those poses it's own risk. I'm fine with doing the edits, no problem, but without you having USB flashback or a known working flash programmer this is a much bigger risk than editing BIOS menus.
Do you want to order Ch341A + U Type Flat IC chip extractor and wait, or figure out your programmer you mentioned, or go ahead willy-nilly without a care in the world ? << The later there is only suggested if you have another system you could use while this one is down bricked waiting to be fixed.

Oh mate, as previously stated in my PM, I can't get it right now. I'll buy it after the 10th, using another computer shouldn't be issue as I can go to a friend's shop with the unseated chip and the flash programmer.

So let's wait for a week, shall we?

Thank you for everything you have done so far.

I can't remember everything we've discussed here, let alone PM too I only noticed on page one you said you had a possible programmer you might be able to use, but wasn't sure how etc.
Ohh yeah, you don't even have a second PC at all in the house, correct? So even once you have programmer you still have to go somewhere else to program back in, correct?
If yes, be sure to get U Type Flat IC Extractor too, without that you would probably damage the BIOS legs when trying to remove the chip. And, to be safe, you need to go where ever and make a BIOS dump with the programmer, then let me check it, then we proceed once we are sure you have a good dump/

Yes, I have no issue with waiting, and am glad you are OK to wait too. I'd much rather have you be prepared and ready for a brick here, than you tell me to go ahead and give you BIOS, and then it bricks leaving you with no machine.
If you want to be really prepared you could also purchase a second chip and put good BIOS on it too, before we start with the mod testing. That way if it bricks, you can easily pull chip, put in other one, then get into windows and program the bricked chip so you again have two working BIOS chips, then carry on with more testing.
That way, you only need to go somewhere else to dump the BIOS once. If you need help finding all the things I;ve mentioned, let me know where you are, or link me to the place you found CH341A and I'll try to find you the chip extractor + a second spare chip too (those are usually only $3 or so if you purchase a single)

You're welcome, and thank you for not wanting to rush into a possible bricking BIOS mod!

I don't know with which BIOS you made for me started but my Ram overclocking XMP profile didn't work. Both bios and CPU-Z reported 666mhz memory, rather than 800. So I returned back to the official locked bios and XMP works again.

So I kindly ask you to make me a V7 MC injected vanilla, locked official bios first for me to try through Windows/DOS.

If the machine doesn't boot, I'll try the official CAP/BIN/ROM file with the flasher. Then we'll continue whichever injection method works. I decided it'll be a hassle for both of us to go with the unlocked bios to find which setting broke XMP one by one. Seriously no need to go through all that. I'm fine with the locked bios with V7 MC.

My flasher will arrive today.

@tayyar - Probably you need to set other area to manual or XMP, on top of where you normally are setting XMP. I mean, since I made more BIOS options visible to you, the XMP or memory settings may also be in other areas, so it may need set in both locations.
Such as, in the new unlocked BIOS, at Advanced >> System Agent >> there is LOTs of memory settings there, anything you change in Ai Tweaker that is also here, needs changed to match (Such as DIMM profile >> Set XMP choice)
And, at Advanced >> System Agent >> Memory Config >> Custom Profile Control >> Memory Frequency Limiter << This needs changed, to max value, otherwise you are currently limited to 1333Mhz (your stock 667 you see in CPU-z) << This is main culprit.
Go back to this BIOS, and learn to use it with all the new settings, I bet you will miss it later if you don't. I doubt it's broken, I think all this just needs adjusted as well [winik]

What do you mean try through DOS/Windows?? Did you mean flash mod BIOS in windows? If yes, of course, it's only way, with FPT as you've been doing.

You should never flash stock BIOS with programmer, and you can't the CAP BIOS anyway, but in general don't do this you will loose ALL board specific data.
What you do is flash stock BIOS with EZ flash before you use the programmer, then you dump that BIOS and have someone check to confirm it's all OK. Then you have a clean stock BIOS dump that you can reprogram anytime with programmer.

If you want stock BIOS with v7 microcode still, flash stock BIOS with EZ Flash, then send me new dump by FPTw.exe -bios -d biosregstock.bin

@Lost_N_BIOS Yeah I checked those settings as well but probably couldn't do it. Most probably an error on my side rather than yours.

But I decided that I'm okay with the stock bios for now. There weren't many settings I needed and I'm in this thing solely for performance reasons.

I flashed the official stock via EZ Flash and dumped the bios as you asked, it's attached.

-----

I don't think I have any board specific settings TBH. If I do, are they irrevocably gone after stripping cap to rom/bin and flashing via flasher? I mean, can't I reflash the official stock CAP through EZ Flash after I revive the PC with flasher if the first v7 bios doesn't boot? So after we find the correct method of V7 injection, I can do a flash through W32/DOS to retain those specifics you mentioned?

Although I wouldn't care much about them. This is a cheap board and I doubt they added premium features like DTS etc.

Flasher didn't arrive yet, but it will arrive tomorrow. I can do without a PC for a day. I'm willing to try a V7 bios now.

Yes, there is no "probably couldn't do it" maybe you just weren't sure, so didn't change those?

I don't mind, if you want to use stock BIOS, it's OK with me But, that is a lot we both went through to get full BIOS menus unlocked, I'd assume you want to use eventually

Yes, if you flashed stock BIOS in with flasher, all your board specific data would be lost now, unless we fix (or already fixed before, I don't remember, and I don't see details info/notes on my end, so don't think we did)
All that is important there is LAN MAC ID, if you want to use ethernet, rest really isn't useful anymore since RMA time has passed.

If BIOS can't start due to V7 microcode for your CPU, then you wont be able to EZ flash or boot to BIOS, DOS etc, unless you put in some other CPU that uses different CPUID

You're confusing me, and I think maybe some of this process. There is no issues with microcode injection?
And if you currently have board details in place (serial, UUID< LAN MAC ID etc), they will remain always, unless you do some incorrect flash with stock BIOS (Which I never suggested here or anywhere)
I checked above file, all system specific details are missing in both areas of the BIOS. I can't check LAN MAC ID because we didn't dump GbE region and it may not have GbE on this board (Intel Gigabit LAN), LAN MAC ID probably stored in lan chip FW if you can use Ethernet now.

EZ flash, generally, you cannot flash mod BIOS, but if you can on this model it's OK to edit stock BIOS and flash with EZ Flash, system specific details will remain in place.
Only thing that would remove them would be if you flashed stock BIOS with FPT, which I never suggest you do, only dump BIOS with details in place with FPT, edit that, then reflash.

here is BIOS with v7 (leaving the anomalous 306C3 v12 in place for now), please test and then check live in-use ucode with HWINFO64 as seen in image below


Flash via >> FPTw.exe -bios -f v71.bin

http://s000.tinyupload.com/index.php?fil...381557650767702
If you now see v12 as ucode version, then we'll change that to v7 too, but I suspect if you see v24 w/ stock BIOS, then you'll see v7 in use now

I'm using Ethernet now, so as you said the LAN MAC ID is on the LAN chip.

Zitat

---

If BIOS can't start due to V7 microcode for your CPU, then you wont be able to EZ flash or boot to BIOS, DOS etc, unless you put in some other CPU that uses different CPUID

---

I know, what I meant was this (hypothetical scenario):

1- Assume that the BIOS you sent bricked my mobo
2- I used flasher hardware to flash one of the unlocked bios you sent me a week before
3- Revived the machine
4- Since you said flasher device makes me lose my mobo specific features, I lost them
5- But since my machine is up and running I use official CAP file via EZ-Flash
6- Bios is stock and my Mobo specific features are back? Or are they "irrevocably" lost because I once used a hardware flasher.

Again, I just want to learn because I don't care, since my ethernet mac ID is on the LAN chip.

I will be flashing v71 file you sent me in half an hour, after watching a TV show. If I lose the machine, at least I'd have the night's entertainment. :) lol

Will let you know soon.
------------------------------------

@Lost_N_BIOS

EDIT EDIT EDIT EDIT


IT WORKS!

Just checked bios and it showed v7 MC. Enabled all cores 34 x 100 in bios, deleted the mcupdate intel.dll and now I'm hitting all cores turbo. THANK YOU VERY MUCH!

If you think your labor shouldn't be discarded, you can add V7 to UnlockedF2 (all unlocked) bios, and I'll mess with the memory settings if I can get XMP settings to work.

HOLY MOLY! Thanks!

EDIT 2: My Realtek audio somehow got back by itself, and I restored the mcupdate dll and it still hits all core turbo. I'm happy. THANK YOU!

------------------

OLDER POST: Okay, I flashed the file and it didn't boot via restart, so I had to do a full power cycle. Now it boots but HWinfo suggests that I have MC25.

While flashing it said "GBE and PDR (or PBR) region not found but succesfully flashed it.

Also, my Realtek Audio doesn't work. It shows up in device manager but the Control Panel GUI says no device attached (probably a driver error?)

To your scenario - no, all motherboard specific details are lost already (now), using stock BIOS and EZ Flash will not put them back (that only leaves them in place, if they are there to begin with)
They will only be back, if we put back from stickers on your board (some info will have to be guessed, manufacture date to add to serial, and UUID can only be re-generate a new one). Good to hear your Ethernet works, MAC ID must be stored in chip FW then

Be sure you load optimal defaults after each BIOS flash. And really, you may want to start clearing CMOS after you flash too, then boot into BIOS, load optimal, save and reboot back to BIOS to make changes.
That may be why you lost audio for a second, fail safe may have been loaded/in-use

Great, v7 ucode in-use and all core turbo, very nice

Ohh, yes, GbE and PDR messaged can be ignored, your BIOS does not contain those regions so this is normal error to see.

You put in some effort there too, taking all those images and testing BIOS etc. But, if you really don't want to use it, we can just leave this as-is with the current BIOS.
If you do want to try again though, let me know, I will edit that with v7 too, then you can see if I was correct about the memory settings stuff I mentioned above.