Topic: System crash

Since moving onto Win7, then Win8, I have yet to see the bluescreen. If Podium crashes, it is a rare occurrence, and the system is intact. On previous OS, the bluescreen would emerge in Podium and other DAWs.

Unfortunately, ASIO drivers are subsequently not accessible. I am able to use DirectSound or wmd. These are always reliably there to use. Or unplug then plug in my audio interface; the manufacturer’s ASIO driver for that device is then available for use.

I have also dispensed of VSTs I suspected were involved in catastrophic crashes. But essentially, I believe the more recent OS’ are way more stable. If you want to recover work, deselect Preferences > Editors > Activate power when opening arrangement editor to edit track assignments within the arrangement, or delete the objects in the Device List.

Best wishes in your troubleshooting. I recommend sending Frits the *.pod file via pm for debugging 🙂

In case you are still searching for answers, I hadn’t been by the forum much until now and will offer my 2 cents on your problem, as I have experienced something like it long ago in Podium AND other DAWs. First, it must be emphasised that this is not a feature limited to Podium. Locked up drivers occur with all DAWs. Second, I also want to stress that it is almost never the DAW that is at fault — DAWs do not truly ‘lock on’ to ASIO drivers — the other way around might be a more acurate description. I have even seen the quite common result of the driver holding on so stubbornly that, if you open your Task Manage on your PC, you will see what is called a ‘ghost incidence’ of your DAW still supposedly up and running sometimes many minutes after you have closed the true version (or it has crashed). This is an example of what the best of these often dodgy drivers are capable of doing.

There is more that could be said; however, since drivers, even today, still vary so much in quality and performance, that I must skip some comments. Might I suggest, if this issue continues, that you ‘pull the plug’ literally on your driver by removing the input cord that the driver is connected with, before then closing down the DAW? This is only one of several tricks, but in some cases we learn not to do a lott of ASIO settings changes as well while operating. Try to change things only when you must, and check to see that such changes ‘took’ and all is continuing to operate accordingly. As odd as this sounds, one almost has to treat the ASIO as a badly spoiled child and attempt to be firm with it, almost to the point of ‘training it’ to function as you require. The next step if continued troubles, of course, is to switch to one more reliable.

Of more that could be discussed, I’ll just end by asking whether you have ever installed and run any audio software that could have damaged or corrupted your sound stack, such as the infamous NCH Software and its products such as SoundTap? If so, I can tell you that I have had to fix a little over a half dozen machines from stupid shims left behind after uninstalls and related corruption. These can seriously interfere with the proper operation of you ASIO and any DAWs you use. If NO, then dismiss the mention. Cheers and best wishes getting things sorted! -Tele