Topic: Podium gives occasional blue screens

Viewing 5 posts - 1 through 5 (of 5 total)
  • #1839
    kyran
    Participant

    Let me start by saying that I have never had any blue screens on this machine in the five/six years I’ve had it.

    It’s a P4 3GHz with 512 megs of ram, an ATI 9200 and a novation x-station using the novation asio driver, all on a nlited windows xp.

    I’ve had three blue screens so far, all when using podium.

    I can’t really remember what I was doing when I had the first one.
    The second one occured when I tried to load the podium.ini setup file during playback.
    The third time it occured when I was shutting down podium (and had pressed yes on saving the project) after I changed some color settings and stored those to an ini file (I didn’t do anything else that session except for loading an arrangement, so the arrangement was on, but not playing, when I shut down podium)

    I’ll try to write down the BSOD message next time it happens. (There’s probably a dump somwhere, I’ll try to locate that too)

    #14565
    Zynewave
    Keymaster

    Usually it is through drivers (which has kernel access) that blue-screens occur. If you can, try selecting a different ASIO driver such as ASIO4ALL, and check if the blue-screens still occur.

    Only blue-screen I’ve ever had with XP/Vista, was with a Waves demo plugin bundle. The Waves copy-protection system managed to blue-screen during the installation of the plugins 😯

    #14568
    kyran
    Participant

    I know it’s most likely through a driver.
    I’ll try ASIO4ALL, but I use 3 other hosts as well with the novation driver (ext2, FL and LIve) and none of them caused any blue screens with this driver. So my guess is that podium asks the driver to do something the other hosts don’t.

    I’ll report back when it happens again (which hopefully it doesn’t)

    #14572
    kyran
    Participant

    Got a blue screen again just now. I was still using the novation driver.
    I moved the cursor to the start of the arrangement and hit spacebar, after which the system gave a BSOD

    This was the message:
    IRQL_NOT_LESS_OR_EQUAL

    STOP: 0x0000000A (0xE215B124, 0x000000FF, 0x00000000, 0x804E5648)

    I’m installing ASIO4ALL as we speak.

    I have never had this with any other host.

    #14575
    DFusion
    Participant

    That error message says that it is some problem with your hardware.

    Something on your system might be damaged or doesn’t sit properly on your Motherboard or you have a bad driver.

    So try to update everything to the latest drivers and see if it helps.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.
Β© 2021 Zynewave