I believe that the Mac OS X and PC volume blast issues are actually quite different.
On Mac OS X:
The volume is originally controlled by the master volume on the Mac. The volume can be further modified by using the buttons on the Geek Out, but these changes are not reflected by the master volume setting on the Mac - the Mac doesn't know that you've modified the volume.
If, after playing with the Geek Out volume buttons to the change the volume, you then go back to modifying the volume with the master volume slider on the Mac, the first thing that happens is that the volume on the Geek Out will jump back to whatever the Mac master volume was set at. So, if you have Mac / master volume turned all the way up, and then you turn the volume to be very quiet with the physical Geek Out buttons, you are going to get a big, possibly huge, possibly painful, volume jump the next time you touch the master volume control in Mac OS X. You can get the opposite effect by starting with a very low Mac/master volume, and then raising the volume with the physical Geek Out buttons. The next time the master volume is touched, the Geek Out volume will jump back down to the very quiet levels that it started out at.
I've also accidentally blasted my ears with some whacky switching from Audirvana+ to iTunes or Spotify (or any other software where the audio stream is no longer processed by Audirvana+ before going out to the DAC). I'm not exactly sure what the combination of actions is that needs to reproduce the problem because it doesn't occur systematically, but I've seen the volume suddenly jump to 0db when switching between audio playback applications. I consider this to be more user error rather than some inherent problem with the Geek Out - this seems to me to be more about audio software vying for control of the audio output, rather than some volume control issue on the DAC.
On a Microsoft Windows-based system:
From my understanding, it sounds like just touching the "down" volume button on the Geek Out can make the master volume suddenly jump to 0db. I'm kind of surprised that everyone is expecting this to be fixed with a firmware update; maybe it can and will be, but I would have thought that this was a bug that needed to be fixed in the Windows driver that needs to be installed in order to even make the Geek Out work on a Windows PC.
I happily avoid the issue by not using Windows operating systems with the Geek Out, and on Mac OS X by either not touching the Geek Out volume buttons at all, or by only making very slight/fine volume adjustments with them. I also now take a little extra care with when switching between Audirvana+ and other audio playback software to ensure that the volume level hasn't jumped to 0db...