@Ozi

All the beta versions with AGESA differrent than the original v1.5.0.0 can be downloaded in the first post if you want to try them.

Zitat von Phoenix48 im Beitrag #166

---

@Ozi

All the beta versions with AGESA differrent than the original v1.5.0.0 can be downloaded in the first post if you want to try them.

---

BIOS with AGESA v1.5.0.0 updated to v15

Changelog:

[Changed] - OROM LAN Intel Boot Agent GE v1.5.86 -----> v1.5.88

I decided to check> CrosshairV-Formula-ASUS-1703.ROM with AMD AGESA OrochiPI v1.5.0.2 mod v7 - as a result, I managed to lower the DRAM CASH # to CASH Delay timing from 11 (as I posted in the photo) to 8 on this BIOS
It works stably, the display of the amd video card is correct
CPU Frequency Multiplier Not Working Correctly
RAM frequency management does not work
HT frequency is fixed at 2800 and does not change! ..

Help to understand. Before up-dating of BIOS, the processor held acceleration of 4670 hertz. Now the same settings, from the saved acceleration profile. But it is impossible to leave them the processor overheats. More than 90 degrees in seconds collect, and protection works, the computer is switched off. About 4560 hertz fell. Now overheating comes not so quickly, in 5 min. before temperature kept within 75 degrees in case of a maximum load.
If to drop everything on a default everything perfectly works. Also doesn't overheat and the blue screen doesn't appear.
CPU/NB recorded at 1:38 Volts but Volts raises till 1:42 the problem can here?
Fixing on parameter 1.39 Volts here everything is good CPU VCORE, this parameter doesn't change.
was at me so

became now so

@hasd65

I know the problem can't be the Bios itself because nothing was modified in it related to that. With that said, here are all you can verify:

- If you didn't clear the CMOS, loaded and saved the default values in the Bios and restart after flashing it before entering your own settings then it is not impossible that there are some glitches from your old Bios that didn't got overwritten properly. If in doubt, reflash and reset properly.

- Your settings for overclocking are probably fine. But it may be worth it to verify the other ones having an impact on the temperature. Verify if the Cool&Quiet feature is working. Verify also if your fan PWM for the CPU are set correctly if this apply to your cooling.

- From the symptoms you described, it is also very possible that your thermal paste is finished. If it is your problem, you should change it. This one is the cause i suspect the most to be your problem.

Just for reference, i remind you that the FX-8350 has a maximum operating temperature of 61°C (It is ideally also the max temp you should set in the CPU fan PWM in the Bios if you fan has 3 pins, if it has 2 pins then you should use CPU DC fan settings instead). Your CPU cooling and overclock settings should be set accordingly to try to stay within that limit.

Also for reference, i use "CoreTemp" when i want to see the CPU temp of each CPU core in real time in different conditions. You can google it if it can be usefull to you.

BIOS with AGESA v1.5.0.0 updated to v16

Changelog:

[Fixed] - Both modules AMD misc.bin should have been updated at the same time and to the same version as the modules 4392 and 4393

Some explanations: A long time ago, in the beginning at v1 to be precise, the AMD modules 4392 and 4393 were updated. But at the time, it was not at all a well known fact that the modules misc.bin was supposed to be updated at the same time as those for 4392 and 4393. Now that this fact is finally known and that i am now aware of it, i made the required corrections to the Bios. Please note that because misc.bin is only used with the modules 4392 and 4393, it will only be possible that you may see a differrence if you are using a RAID configuration. IDE or AHCI are not affected at all by this module. Furthermore, misc.bin affect only the AMD controller and not the AsMedia one. For those with a RAID, i am not using RAID presently and i don't know the AMD changelog for that module so it is unkown if you will see any improvement or not, be it in speed, responsiveness or just stability. If you are using RAID, for curiosity, it could be interresting to report your findings and results if you detect any differrence or not with this bios fix.

Just updated to the latest "stable" build, and so far so good, downclocking / C&Q working fine, gonna have a play about and see if I notice any improvements, appreciate it thanks

EDIT - Windows 10 is installed on 2x SSD in RAID0

Hi guys, sorry to hi-jack this thread, but my question could be related.

I have an Asus Crosshair V, running an FX-8370.

I have been using your modified BIOS - not sure which version at the moment. Even had some good success with overclocking.

However, lately, and about once a week this will happen. The partition information for all 3 of my drives (one Samsung SSD, and two mechanical drives) will be completely lost. Drives will show up in Windows (Windows 10 64bit) as un-initialized.

A simple restore from back up or running a partition recovery tool gets me back in business.

Would like to find the root cause and stop this from happening. Any ideas as to potential cause? (I have gone back to stock/default BIOS settings - still happens).

@rcchamp1

This is a very special problem you seems to have. One thing is for sure, it doesn't come from the Bios. I instead suspect something in Windows like the drivers or something like that... More the "something like that" part. Because i doubt that it is the same driver for each of your 3 drives and seeing 3 drives become uninitialized at the same time is a first to me. I admit that i am not able to guess many things that can do that. As far as guesses goes, some of those can be long shots. But i will try:

- There may be a setting in Windows that make your drives detected as removable drives. That can mess with them at the same time.
- Maybe a program is scanning all your drives once a week and unmount them to do the scan. But it somehow crash before re-mounting them.
- You have a virus or malware that makes your drives disapear by corrupting the filesystems of your drives.

And that is pretty much all i got for now. I can't think of anything else for now.

Maybe some more details would be usefull. Like...:

- Are your drives just unmounted or are all the partitions really gone? The two are not the same thing and using a software to correct the second can work even if the problem is just the first.
- Are they disapearing while you use Windows or is it always only at start-up? By the way, the best proof that it is not the Bios is that they show up in the Bios and reach the step of showing up in Windows (initialized or not).

My last comments are that if they are unmounted, then it is probably an "unmount" command passed by a program and i suspect a software in Windows (maybe Windows itself). But if it is the partitions then it is a corruption and i suspect a virus/malware the most. Also worth mentioning about partitions is the fact that altough a MBR partition is rather easy to corrupt, GPT is by far way harder. Whatever partition system is in your drives, to make 3 drives corrupt at the same time and make the partitions disapear don't usually happen by mistake. It feels volontary to me... Like done by a virus/malware.

Last possibility (even if i doubt it a lot) is that all your drives have simply too much errors in their filesystems. But 3 drives at the same time is beyond all odds... Anyway, you can try to use in the CMD prompt (as administrator) this command:

CHKDSK C: D: E: /X (C: D: E: are the letters of your 3 drives, replace the letters as needed) Answer "yes" everywhere then reboot.

Hope this help.

Phoenix48, thanks for the insight.

I have possibly stumbled onto the solution.

I was able to restore my partitions, rebuild MBR, etc using a bootable USB straight into Minitool partition wizard (similar to old school partition magic). Only to boot into windows and find that my drives were all nuked again.

A bit more background. Drive C: 1TB Samsung 850 Pro using MBR, Drive E: 4TB Seagate using GPT, Drive G: 10TB Western Digital using GPT. All 3 of these would get nuked.


So before rebooting and beginning the process all over again, I removed the Gigabyte Aorus graphics card RGB light tuning tool that was starting up at windows boot (part of the Aorus Graphics card engine software package). Just removed everything associated with that software. Part of it was some Patriot SSD RGB application.

So far I seem to be good, but not enough time has passed to really know for sure. Think I can go to sleep at this point not worrying quite as much.

I updated the latest stable version of the firmware - I have 2 ssd in a RAID 0 array - the speed increased thanks to Phoenix48!
RAID DriverVer=12/10/2012, 3.3.1540.40

hi i have problem instaled ssd hinix hfs256gd9tng, when computer starts give my massage pxe-e01: vendor and device ids do not match! i can use nvme ssd but is not in bios so cannot boot from it.

@rednik

Not sure i can help you a lot on that except try to point you in the right direction. This error is not related to the Bios but rather to a formating problem. Somehow, an error exist in you MBR or GPT registry on your disk. Most common causes are a disk format that was interupted and can also be caused by bad sectors in the disk MBR or GPT area. It can also happen when trying to put a 32 bits system on a GPT disk made for x64. Other causes probably also exists. I suggest you google them.

If you can't restore a MBR or GPT backup then I guess a clean and complete reformat of the disk is probably your best bet.

i think there is a problem with nvram i cant wiped it out even if i remove batery or use clrcmos notihng happen, time is just freeze, when diconnect all hard drives two boot option presist (windows boot manager) no mater what i do.