Last edited: Aug 29, 2021

VM expert now, on first use? lol
Did you make sure that you allocated enough ram for the VM OS as well as the VM daw etc?
And then bear in mind that your hardware and software running the VM also needs what it would usually have allocated to be perfectly functional too.
Yes, it's not a perfect situ but it can work well actually, if you have enough ram.

edit:

I believe there are others to try too.

 

No I'm not an expert, but I soon realized there is several problems when using an audio workstation in a virtual machine, so to put 2+2 together when trying and failing simple tasks wasn't that hard. I have 64GB ram, 12 cores Ryzen 9, two large ssd's with 3GB/s workflow - and I reserved 6 cores, 16GB ram and a 200GB diskspace as HDD.
Never got asio running, never really found the soundcard on more than 3 attempts on starting a vm. Had problems with UAC elevation even in win7 which I've never had before (on Intel, on the other hand, that could be it)

Already here: It's too much hassle. Hours went by with nothing to show for.

Why is WL6.1.1 crashing for no apparent reason when idle? Can somebody please explain that?

Edit: Could my Radeon R5 200 be an issue for stability? It's never stuttering or feeling sluggish running 3xHD screens, but it is very old and low spec. So why that card? It was available and silent, and I don't play games.

 

Last edited: Aug 29, 2021

Hi @dnz2dbt
I only use a VM to do just a single stem bounce through a plugin, or maybe render some audio from some MIDI instrument I don't normally have on my platform or something.
Yet I would never expect a VM to handle a normal workload that easily, because really you are running two systems simultaneously.
I'm no expert either, but I'm surprised it was so problematic for you.
There are lots of settings to tend to to make everything somewhat more smoove though.

 

I checked the event viewer just now, and it report two errors everytime it shuts down.
Attached a textfile with both errors.
Any clue?

 

@dnz2dbt Your machine is powerful enough to run win10 in a vm when i give you a suggestion i though you where somewhat familiar with vms my apologies anyway maybe i had issues with that failing module in the past or it was something different there is a portable version of wavelab around give it a try also if you work very intensively on wavelab maybe is time for a purchase don't forget to do backup if you experimenting with software

 

I'm already running win10, and tried to run win7 in vm, but the new problems quickly became larger than the old one.
I have thought about going legit many times, but combined with all the rest of the audioz I mess around with, it probably wouldn't work. If i had this as a profession and made money with the studio, I would just grab the retail version and never look back, but that's not the case.
I'll gladly provide more detailed info about the error if anyone's interested.

I'm actually suspecting the hardware to be the problem right now and is going to try win7 just to see if the idle crash still appears. It could be some cpu-thread is simply dropped if the system senses it is redundant.

There is a ton of settings in the bios and I understand less than half of them...

 

Last edited: Aug 31, 2021

@dnz2dbt well a search on the failing dll shows some had issues with wavel 5 and win7 may fix the issue i won't post a link here just search the module name and you will notice the thread remember do backup before replacing anything

 

Thanks. Backup is not needed at this point as I'm still evaluating what version of OS I'm gonna run, so trial and error is a part of the process.
My first noob-attempt will be to get that module downloaded from elsewhere and replace it in both locations in the system, if that does anything.

Edit: of course those are not even remotely interchangeable, as they control the whole process between modules in a specific application... But I looked inte the portable version of wl611, and the modules have different sizes and dates than the installed ones, so now I test a portable version instead and hope for the best. Last time I tried that everything went to shit, but I probably had a broken system before that. This W10 1909 LTSC seems really solid so far.

Edit2: Doesn't matter what version of wl611 i use. Same module, but not same version, still rips it apart in idle. I just watched it dissapear before my eyes. Almost same error, it's only the location of the files that change. It's also always 3 minutes between idle-start and crash. That could be a clue.

Maybe I should try to find the absolute latest release of wl611p. There could be one that has addressed this. Win10 is already 6 years old.

 

Last edited: Aug 31, 2021