Windows 8.1, uTorrent client, Cross3, BSOD

[kugmo]

...as the subject line has it, running Cross3 and a uTorrent client together under Win 8.1 results in an instant BSOD (blue screen of death).

I had just updated from 2.6 to 3.0, with many gigs under 2.6 and a few under 3.0 (with video mixing active), with ZERO problems or hiccups whatsoever (on a Samsung Ultra 5 - i5 with 4Gb RAM).

I installed NI's Audio 4 driver to check Cross timecode compatibility with my Denon SC2900 (*note: a couple of mapping issues there which i might bring up in another topic if I can't resolve it). Started up 2.6. No problems with config or running the timecode setup.

Note #1: Denon's FW update for the 2900 hybrid mode is really nice. No need for timecode CDs, just set the frequency under the player's utility menu.

Note #2: I am running minimal apps in the background. Micro$oft Defender, and uTorrent (set to run on Windows startup) are the most visible ones. Others are the requisite drivers and services required by Windows.

So after an hour's worth of mucking around with 2.6, I loaded 3.0. Within seconds of the Cross screen loading, a BSOD happened. Thinking it was the NI Audio4 driver, I uninstalled all NI drivers right after booting, restarted, then reloaded 3.0.

Another BSOD.

I rechecked the installed programs (and there aren't many), the only item that was "non-standard" to Microsoft, aside from Cross, was uTorrent. I proceeded to uninstall it, thinking that it was entirely unrelated.

Restarted the machine, re-ran Cross3. Guess what, no problems for a solid 30 minutes of mixing (MIDI - Reloop Terminal Mix 4).

Re-installed the Audio4 drivers. Re-ran Cross3. Ran for over one hour with me goofing around with the timecode setup).

I'm not sure what the exact reason for the BSOD is, but I have a feeling that it's some obscure interrupt hook that's coded into the uTorrent client, possibly a video or hard drive interrupt (i'm guessing the former, as video is the only difference between 2.6 and 3.0). But a program like uTorrent grabbing and wanting exclusivity on a video interrupt is rather weird, isn't it?

If anyone has a workaround for this, I'd like to know. I can live without uTorrent, but I'm really curious about what's causing this. Thanks.

[RoJeC]

Gave it a quick try; I can use the 2 at the same time in w8.1-32. Could it be that it crashes on a torrent that is active that moment?

[kugmo]

Gave it a quick try; I can use the 2 at the same time in w8.1-32. Could it be that it crashes on a torrent that is active that moment?

that's the thing: there were no active downloads/uploads. the torrent list was empty. this was on x64. RoJeC, i'll try different scenarios when i get back from (club) work, and get that crash happening. and if i get another BSOD, i'll keep it for for MV forensics.