I've never used that board myself, but my guess would be it's probably a matter of creating a custom DSDT file for your hardware if you haven't already. I find a proper DSDT can fix a lot of the 'glitches' sound issues, graphics, and sleep/restart/shutdown issues.
There are a number of good tutorials floating around for how to do this. I learned a lot about DSDT patching my systems using
this guide. I'm no expert, but I usually manage to futz my way through and get the systems I build working properly- it's mostly just following instructions and figuring out a few things that will be unique to your hardware.
Also, anybody else notice that text is less sharp compared to Windows? It may just be my eyes but it seems a tad blurrier.
Obvious question- but your graphic card is properly patched and you have hardware acceleration and native resolution on your monitor? Otherwise, it may just be the difference between OSX's font smoothing and Windows clear type.
Really dumb question but I'm booting into the 32bit kernel. Can I use all of my 8GB of ram (it lists 8GB in the About Panel) or am I limited to 4GB?
My (highly simplified I'm sure) understanding is that in OSX, apps coded for 64bit can still address more than 4GB of RAM even if the system kernel is only 32-bit. Macs prior to SL were able to make use of more than 4GB of RAM due to this. Also, if the app isn't coded in 64 bit to begin with, it will make little to no performance difference running in 32 bit or 64 bit OSX.