@professor_jonny - I outlined for you which cbrom versions work, for the BIOS you initially linked (Stock Asus 2002) Corrupt microcode #1-2 is covered on how to fix in FAQ #1 on first page, remember I mentioned if you see this to check that.
I also said when I tested with xxx versions cbrom this did not happen, so you don't have to manually fix if you don't want too, you can instead use one of the versions I mentioned that do not cause the issue with this BIOS.

No need for me to re-test with stock rom, I gave you results above with many versions of cbrom and I used the Asus stock 2002 BIOS.
I checked your NCPUCode.bin and it looks fine to me, no problem there. If you need me to upload any Cbrom versions for you let me know

@Lost_N_BIOS - I Managed to get it to work with the stock 2002 bios with my created NCPUCODE.BIN originally it would not work and kept on getting corrupt microcode with every version that would actually update my bios file.
in the end I removed the microcode file completely then inserted a SLIC Marker using the pubkey method then patched in my MCPUCODE.BIN and it worked and verified without removing microcodes as suggested with the tutorial..

Yeah, I don't know about tutorial method, I've never read it, and I do not suggest (as general method) removing all microcodes or inserting a blank NCPUCode etc.
When you get dupes it's a simple fix, covered in the first FAQ, however for your BIOS, there is several versions of cbrom that do not give dupe errors or corruption etc, all those I mentioned inserts NCPUCode properly with one move and done.

I could not get the ones you suggested to mod the stock bios with my NCPUCODE.BIN only the one I hex edited the xenon microcodes in I used cbrom182 any thing above that would not mod it unless I used andy p slic tool to mod the bios first then just about any cbrom version worked.

@professor_jonny - Higher versino number with cbrom does not always mean newer release, and there is many instances where newer is not better or the compatible one to use with certain BIOS versions or certain entire chipset series.
I mentioned to let me know if you need any cbroms, you should have asked I can upload any version for you. I know you are done now, but would you like the ones I mentioned as working without issue on this BIOS, for future use?

@Lost_N_BIOS I managed to find a whole lot of cbrom files in a zip file on the net so I thin I will be ok in that respect.

I have flashed the bios and it works perfectly and the micro code verifies in regedit with what is patched in there with the fitted processor..

I'm nom looking to update the option roms for the silicon image 3132 raid controller and nvraid and nv boot agent.

I have found option roms for the silicon image controller as per link below but I'm unsure if these pci roms will work included in a motherboard bios image ? im looking at the version 7.7.03 which is newer than mine.

https://www.latticesemi.com/Support/ASSPSoftwareArchive

I'm also wondering as my chipset does not support ahci am I able to include the option rom for the pci ahci card in the bios as the current rom is a OTP device and I cant update it.

You need to research how to edit BIOS with "sensitive PPMinit module cbrom" (aka Minit, Meminit, PMinit, GV3) This is sensitive module, and cannot be moved at all, offset must remain exact and they place this at the end of your BIOS to prevent modifications.
It's a lot harder to edit a BIOS like this, many procedures are required to extract all modules, replace in exact updated order (with your update module), and keep that module at same exact offset usually require dummy module added or something else removed etc to keep same offset.
It's very involved, and tough to do if you are not used to doing it.

nForce 680i does not support AHCI, it's not the BIOS it's Nvidia , sometimes you can use RAID single disk, unsure if the controller on this board will allow that, but it should from what I looked around and see now.
On NVRAID, you can get latest rom here - AHCI & RAID ROM Modules
You need to edit it in many places for your device ID and then correct the checksum-8 bit to 0

On the SI, inside that package, 7703.bin looks to be the correct one, but you may need to add your device ID in there too, unsure. I see you will need to correct checksum-8 to 0 on that as well, if you have to edit it.

@Fernando - do you know about this Silicon Image 7703.bin - https://www.latticesemi.com/view_document?document_id=51783
Does he need to edit device ID or anything before insertion?

You may not be able to do this mod for a while, until you learn how to deal with and get around this sensitive module. Also, due to that, do not use any cbrom above 1.55, for any module modifications, or they may fail (Brick the board fail)

@Fernando - That's same ID already in the stock BIOS images too then, thanks! So no edits needed on the SI 7703.bin @professor_jonny it's already same VEN_1095_DEV_3132