cyborc

I've had the same issue. Like @underdog32, I also have high amount of RAM. (128GB). I can't find the post at the moment but someone on reddit suggested manually setting the paging file size. By default it's set to be managed automatically by Windows. At first I set it to 4096MB as the initial size and 8192MB as maximum size, but the crash on wake still occured. I changed it to initial 8192MB and max 32768MB and I've now done several sleep/wake cycles without launchbox crashing. Seems a little silly to crank the paging file up this high but it seems to work so far.

Here are my findings: Using Lord Monkus' pa_latency setting, I still had no sound with WDM-KS. I renamed all of my video folders so launchbox wouldn't play any videos, and also disabled all sound in bigbox, but there's still no sound with WDM-KS. WASAPI works fine though. According to logs WASAPI is 3.33ms latency on my setup and WDM-KS is 2.00ms latency. I tested back and forth with both outside of launchbox by launching mame via the command line and I couldn't tell the difference so I'm okay with using WASAPI unless this issue is figured out.

Hi Phil, I'm having the same issue. Groovymame (when launched via bigbox) has sound with portaudio when using WASAPI, but not WDM-KS. Ideally I'd rather use WDM-KS because it's lower latency, but WASAPI isn't too far behind. On my setup, WASAPi is about 3ms and WDM-KS is 2ms. Probably not even enough for the human ear to notice but you know how OCD us groovymame users are! ?