These forums are read only, please use our new forums here.

Main :: POD X3

POD X3 Pro causes BSOD during the Windows shutdown?
by jahra on 2013-01-31 23:31:26

Hi there, folks,

As a preamble, my set-up:

- Intel i7 based comp, Z77 chipset, 16 Gb of RAM

- Windows 7 Home Premium SP1 and all the latest updates from the Windows Update

- M-Audio ProjectMix I/O firewire beast set up as the main (default) audio interface

- Line6 Pod X3 Pro used as a guitar pre and processing unit, connected to the ProjectMix via S/PDIF (ProjectMix as a sync master), AND connected via USB (a host built into the chipset) to the PC for moving patches to and fro

- ProTools 10 as DAW

- Latest firmware and drivers for all the gear, of course

Now, the issue:

Now and then when when I shut down the OS, it shows me "Windows is shutting down" message (or whatever it says) for an unusually long time - 5 to 10 minutes - and then it crashes with a BSOD.

What I've noticed lately is that it only occurs when I had both ProjectMix and Pod powered up during my session at the same time. When it's just ProjectMix and ProTools, I have no problem shutting down whatsoever.

Browsing through these forums I stumbled across this "usb drop out" issue causing similar problems, but then I realised it concerned X3 Live units only...

Can it be that the drivers of both devices I have (both are effectively just soundcards from the PC's p.o.v.) somehow fight for the OS resources, or the OS can't decide which one to shutdown first (I know, sounds silly)?

What I think I'll do tonight is I'll try to work with X3 Pro unplugged from USB (but still connected via S/PDIF) before I power on everything, and see what happens during shutdown.

The real question is: If my guess is right, and I should run only one sound device visible to the OS at a time, and I disable X3 Pro as a sound device, but keep it connected via USB, will I still be able to transfer patches to/form the Pod via USB?

Any ideas/suggestions/other possible reasons for BSODs during shutdown?

Thanks in advance,

Whoever is interested in the results of my experiments - shout, and I'll keep you posted.

Re: POD X3 Pro causes BSOD during the Windows shutdown?
by Wozy73 on 2013-02-03 02:23:15

Hi Jahra,

I had a similar problem with my ordinary X3. Suddenly it produced BSOD while shutting down the PC and it shot the Adobe Flash Plugin and the Windows Media Player after a short time of using.

I tried everything like reinstalling all drivers like the Line6, the Motherboard and soundcard-drivers. Yesterday I looked into this board and found that there are problems with the USB and POD X3 Live. And because I am using a Laptop I often had to plug the peripherials and did not take care in which port I plugged them in.

Now I plugged the X3 into the port which I was using during the first installation and: It works :-)

Maybe this could be the same problem as yours ... try the different USB-Ports.

With kind regards


Re: POD X3 Pro causes BSOD during the Windows shutdown?
by jahra on 2013-02-03 22:02:01

Hi Wolfgang,

Thanks for the reply!

After series of experiments over the weekend that included different sequence of switching the devices on and off and running/not running the ProTools, I've figured out the likely cause of my BSOD issue.

It does have something to do with the sync over S/PDIF, it seems. During my sessions I use ProjectMix as a sync master, and Pod X3 Pro as a sync slave.

Now, when I try to shut the Windows down with both devices powered on (and sync locked) I get a BSOD 10 out of 10 times.

When I switch the Pod first (thus breaking the sync) and THEN shut down the OS, it shuts down perfectly 10 out of 10.

Cannot power down ProjectMix first, 'cos it's a firewire device, and switching it off while Windows is running can cause a BSOD in its own right

So my hypothesis is that Windows cannot handle sync locked drivers properly during shutdown - it cannot decide which to kill first or should it kill the drivers at all it seems (whocrashed tool does not produce anything meaningful out of memory dumps, just pretty generic words abuout driver power state failure).

Ok, now my problem's solved, again - through an empiric experiment. My regards and best wishes to the support team.

The information above may not be current, and you should direct questions to the current forum or review the manual.