Driver_IRQL_Not_Less_or_Equal

[cabdriver]

So, I just set up my new computer and put Pro Tools on, installed the driver for the interface, plugged in the firewire, and can go about my business for a while, but eventually, the computer will crash unexpectedly, the BSOD showing driver irql not less or equal and points to avidmboxpro.sys as the culprit. I haven't used Pro Tools yet (as I don't want the computer to crash whilst I'm working on a project). It ran Sibelius smoothly with no problem. I suspect it's a conflict with the on-board sound card/driver, as the computer has only crashes while I'm streaming audio/video from the internet. I have updated every driver (from device manager, I'm not sure if there are drivers I must update manually), I've disabled the HDMI audio driver, and reinstalled the Mbox drivers again. I'm not sure what else I should do; any suggestions?

Windows 7 Home Premium OEM, 64 bit
8Gb ram
3Ghz AMD processor
Pro Tools 8 LE
Mbox Pro 3
Realtek High Definition Audio

[cwsand]

Hi, It could be a compatibility issue with the firewire port - chipset or driver. Posting a SANDRA report as described here might help: Help Us Help You

Here's a link to some info on Avid Qualified FireWire Cards for Windows

You might also try this:
Enable Legacy FireWire Controller

[Darryl Ramm]

And installed exactly what driver version?

[cabdriver]

It's the most recent driver, 1.1.10. I've checked it's compatibility (works with PT LE 8.04, Windows 7), but one thing that worries me is that, when checking the drivers, avidmboxpro.sys is not digitally signed. Considering that that is the file the BSOD points to, would the lack of a signature be cause for alarm?

[Darryl Ramm]

You are really using an Mbox 3 Pro with Pro Tools 8 LE? That authorizes LE OK? Has that combo ever worked?

I kinda doubt Avid tests or officially supports this combination. Where did you see the claim that Pro Tools LE 8 is supported for that driver?

Has this Mbox 3 Pro ever worked OK on any other system? With Pro Tools 8 LE?

Not that any of that explains the blue screen here, but I am not sure this will work at all. For that you may well be into debugging the FireWire card, trying the FireWire legacy driver etc. has this FireWire card ever worked with this Mbox 3 Pro? Post a Sandra report as expected. Start at the "help us help you" link up the top of this web page.

[cabdriver]

I've had this for 4 years, 8 le has not had a problem with the Mbox 3 Pro

[cabdriver]

So, the AvidMboxPro.sys file is the only driver file on my desktop that isn't signed. Can I get a signature or a signed replacement file?

Has anyone ever had a problem like this?

[Darryl Ramm]

Originally Posted by cabdriver

So, the AvidMboxPro.sys file is the only driver file on my desktop that isn't signed. Can I get a signature or a signed replacement file?

Has anyone ever had a problem like this?

Not being signed is not the problem. Multiple posts here have suggested you look at the firewire card and legacy mode etc. have you done any of that?

[cabdriver]

T'wasn't the legacy mode. Fixed it by re-seating the card. Problem is now that every so often the sound'll cut out; no freezing or crashing, just losing the sound. I can fix it by pausing the video/audio for 10-30 seconds. Any way I could figure out how to stop it from cutting out?

[Darryl Ramm]

System fully optimized?

Trashed prefs and databases?

What make/model/spec dedicated audio/session drive are you recording to? How is it attached? (USB2, Firewire 800, SATA III?)

What payback engine buffer size?

Make sure "ignore errors" is not checked.

If that does not work I'd try a different Firewire card, just any different physical card with a TI chipset.