0something0

My calculations show (G(2.6457580 * 10^19 kilograms)(40400 seconds)^2 / (4π^2))^(1/3) = 417940.868 meters. I also learned that for this application, merely putting it in the Google search bar is more accurate since Wolfram appears to round it to significant figures. This is confirmed using the Wiki's figure for a synchronous orbit gives me 60000 + 357940 = 417940 meters for the semi-major axis. Using the first figure to calculate the mass of Minmus of sanity-checking, I get ((417940.868 meters)^3 * 4 pi^2 )/((40400 seconds)^2 * G) = 2.64575801 × 10^19 kilograms, consistent with the Wiki.
Calculating using the precision figures gives me orbital parameters that have no noticeable drift.
Parameters:
Eccentricity: 0.8444756065
Linear eccentricity: 352940 meters
Semi-major axis: 417940.868 meters
Periapsis: 65000 meters (5000 meters from "sea level")
Apoapsis: 770881.736 meters
 

SOLVED!!!! 
I changed the hardware id of the speakers in Device Manager.
For anyone reading this in the future, (or future me),  go to Device Managers,  Sound, Audio, and Game controllers, click on the speakers that you are using, go to properties, then details. Than click on the "properties" drop down and go to "Hardware IDs". I clicked on the id that was not selected and the problem was solved!
It tends to be a good idea to try different things to narrow down the source of the issue (i.e. is it a KSP problem? a Unity problem? a driver/OS issue?)