Ouch. I have the original "Version 1" of that board (note that yours clearly states Version 2 / V2), I bought it almost (but not quite) 2 years ago by my estimate. I'll have to check to be sure how long, but definitely over a year now. I only wanted the lower end GD65, but none was in stock, and it was for my existing Thuban, not BD or PD.
It has been a source endless frustration.
1.) the BIOS is crazy. There are lots of settings available for the OC section, as expected, but none of them ever indicate what the default or auto values are. For example, I'd want to play around with the CPU PLL voltage to see how it affects stability, but if I decide to remove it from Auto, I see a choice of voltages but I don't know where to start (which ones are the "Safe" voltages) because there is no indication at all of what Auto is set to or what are the supposed 'safe' values.
2. I recently had an 8350 available, and since it was very cheap and a direct, painless CPU swap for the 1090T rig, I took it. Even at stock, it is more than a match for my 1090T at 3.9 (but I only really run that 1090T at 3.7 for 24/7 use), so the cheap upgrade CPU swap is well worth it. But the mobo, again, proved to be a source of frustration (it's been sporting the latest BIOS for quite a long time now). Still the same problems with defaults not being shown, but there's also a new problem of the vcore being limited to a max of 1.449V (!) As a result, I could only reliably get to 4.3GHz on all cores. Note that on my 1090T, the vcore limit was much higher than 1.449V, in fact my OC logs show I once tried using 1.462V on my 1090T while experimenting with OC limits. I can only conclude they deliberately capped the vcore for the 8350.
3.) The board has no LLC option that I can find, anywhere. And I need it because the board works differently depending on whether it is running my 1090T or my 8350. On the 1090T, whatever vcore I set is some sort of baseline, but the vcore shoots up at load. For example, I'd set it to 1.399V, and it would idle at slightly lower (say, 1.38V), but at load it can get as high as 1.48V, for example in Prime95 or IBT. But on the 8350, the behavior is the reverse. If I set it to 1.290V, that would be it's idle vcore, then on single thread loads it would drop down to 1.280V, then in full load (Prime95 / IBT) it would stabilize at a much lower 1.264V. At the max allowable vcore of 1.449, my max vcore at load only gets as much as 1.384V, and it is nowhere near enough to make 4.4GHz stable.
4.) Throttling. The board automatically throttles the 8350, unless you turn on an option in the BIOS called "HPC mode". I would have failed to notice this if I had not run a bench suite I made composed of my normal duties. From stock settings, for example, I could just crank vcore to max (since 1.449 is very low on the "adventurous scale"), set base clock to 4.2, and Turbo to 4.6. It would pass P95 all day, but it won't actually bench much higher than at stock. Then I noticed that during P95, CPUz would be showing fluctuating clocks (instead of a nominal 4.2, it would fluctuate from 3.4 to 4.2 briefly every now and then). In fact, before I saw this, I thought it was stable at 4.4. Turning off CnQ (or enabling HPC mode, or both) removes this throttling / fluctuation, but also exposes the "supposedly stable" to not stable at all. It's annoying. And this throttling is present even at stock - at pure stock settings, I've seen the brief fluctuations from 3.4-4GHz every now and then while under prime95 large fft.
In short, although this board has served me well for what I believe is almost 2 years now, and has performed adequately for the 1090T it used to run until 2 weeks ago despite its obvious flaws, it has even more flaws and drawbacks running Piledriver.
I sincerely hope the V2 revision has improved on all of this.
UPDATE: According to my financial records, I bought this mobo Oct 1, 2011, Saturday. It is indeed 2 months and change short of 2 years old. I do hope this V1 is no way indicative of how your incoming V2 model will perform.