thanks for the feedback guys
Jimmer411, any chance you could try with 2.1.3? also, what was your config when you saw those problems?
soundood,
again, thanks for the detailed feedback. the short answer is that your board and in particular the BIOS in its current state is not compatible with AOD. None of the problems you mention (excluding nV GFX detection) can be fixed from the Application side. AOD can not work correctly if the BIOS doesnt support it properly. Typically AOD can work on a board with supported chipset even if the board has no AOD specific BIOS implementation. the functionality is of course limited (no clockchip control, some voltage items are no adjustable) but it works stable without crashes or hangs.
This particular board appears to be very problematic case as it does have certain AOD specific "hooks" in the BIOS but not fully and properly implemented. This is causing the problems you are seeing.
the website of that board model doesnt highlight support for AOD. And given the current state of things with this particular board vendor I dont expect them to add it.
This is very much the worst case scenario from AOD support point of view.
to be honest: if you want to get better AOD experience you need to run it on another board
Bookmarks