M-Audio- "No More irp Stack locations" AND "Bad Pool Caller"

Hi guys...
 
Running Windows 7 (no SPs)
 
I got a sudden BSOD stating "No more IRP Stack Locations" after about 2 hours of Sonar Work... Opened Blue Screen View which showed that it was caused by driver "MAudioFastTrackUltra.sys", Caused by Address "MAudioFastTrackUltra.sys+169bf".
 
Rebooted in safe mode, and realized that I'm once again having to go into the BIOS and change the boot driver (it's trying to boot from CD - instead of HDD).... I can't remember how I fixed that a while ago, so if anyone remembers, you can help me out there are as a side note... Thanks.
 
As recommended by another forum, I downloaded latest M-Audio FTU Windows7 64-bit driver and installed it.  Rebooted.
 
Immediately BSOD'd again, this time with "Bad Pool Caller".  Once again, the Blue Screen View shows it's caused by Driver "MAudioFastTrackUltra.sys" Caused by address "MAudioFastTrackUltra.sys+1247e".  Crash Address:  "ntoskrnl.exe+705c0"
Ran Scannow just to check on things... seems that everything is ok.... But everytime I open Sonar, I crash.  I'm not blaming sonar here, It's the FTU, I'm sure. 
 
The question is...anyone else out there with an FTU ever see this?
 
Any ideas for me? 
 
I can certainly post this to the M-Audio forums, and will, but thought I'd check here, first.  I'm sure that you will want to see the dump file, but I can never remember how to access the blasted thing. 
 
Thanks, boys!
Julianna 
 

I 2nd what Beagle says. M-Audio makes updates with they're drivers Windows version specific. For example, there's a driver for the plain Windows, then there's a driver update for service pack 1, and another driver update for service pack 2, etc..

I would update Windows, and then try M-Audio's most recent driver release for your audio interface.

The only thing I can go by is what happens to me (which is my fault) but I am only using Sonar 7 or MC4. If you are (by chance which can happen with my RME unit) in the wrong recording mode - say 44100 instead of what the project is in - say 48000, you (or actually me) will probably crash and may get the blue screen of death. Another way it happens is that (in my case) in Sonar 7 it gives a message as - nothing is sort of hooked up, and has a screen that says the driver is busy with something else using it, and do I want to "disable" the input and ouput or use them anyway. Well, if you try and use them, you may get the blue screen of death and the screen telling you something.

So turn off the computer and it should be the switch on the power supply in the back of the computer and not with trying the switch on the front (if appropriate) which will never turn off the computer, although it may restart it. If you do not have an off and on switch on the power supply in the back of the computer - unplug the computer. Wait a minute or so, and restart the computer, check your settings this time before opening Sonar and just check the audio device and try it again.
I have to change "settings" everytime I open a project and make sure the sample rate for recording is the same as what the project is. If you do a lot of projects at the same sample rate then usually it is simple to check before starting the program. If you are going to change sample rates according to which project, handy notepad may help to type it down like the name of the project and the sample rate and bit rate you used.
If not do not open a project and proceed to a blank screen in Sonar and check the audio (if it is like Sonar 7) and make sure the audio is what it should be as to bit depth and sample rate - in config.ini file for Sonar 7 I changed what is their default and made it so it will always be 24-bit to open with (because the default is 16-bit) and I will always use 24-bit on any project, although the sample rate (44100, 48000, 96000 whatever) may change, and checking the text file from Notepad will be used then before starting up any session.

Otherwise, the blue screen of death is just another message that may or may not actually be the problem (it's a computer and it does not think, it is only a program).

Well, otherwise I can not know what your setup is doing, so you may want to check it, or else there is a conflict somewhere that may have you thinking for awhile or asking someone for help.

It is hard to do it with remote assistence (not being in front of the computer) unless someone else has had the same problem and knows what it is.
??
This has happened to me, but not so much anymore.
It just happened to me because I have not used MC4 for a long time, and of course, duh, I was at the wrong sample rate so I got the blue screen of death. After I changed it to what MC4 usually is (44100 instead of 48000) it opened I looked at it, and checked it out and exited from the program - because I guess I just have it taking up room on my computer and only use Sonar 7 now.
Well, good luck!

Spacealf, I hadn't changed anything, but checked just to be sure something hadn't re-set... nope.  It's all still set to 48000 (both the Fast Track Ultra and SHS6).  But thanks for reminding me that this can sometimes happen.

Yeah, gcruz, last year I was running out of Ram and installed 4 more gigs.  They HAVE been compatible for this whole year, so I'd be surprised if that was my current problem as well.  A good thought though - and I'll certainly keep it in mind.

I posted this to a PC help forum as well, with full-on crash dumps logs - they suggest I head straight to M-Audio.

Anyone wanna buy an FTU?  LOL

Oh.. Yeah.  I fixed the boot order, but forgot to mention it.  Thanks, Spacealf.

BTW... Note into M-Audio forums, sent them the crash dumps.  have a feeling they will point their finger at SHS6.... So a call to Guitar Center to see how much they'd give me on an interface trade in... My friend at GC gives me some interesting advice: download Ableton demo to see if it's the interaction between the DAW and the FTU (seeing how it's only when I run Sonar that I crash).

IF it works ok in Ableton, I might upgrade to X1 Studio and see if that does the trick.  I really didn't want to do that.... :S. but, we shall see.... I have no intention of ditching Sonar, though, Fred.  LOL!

Interesting note: Loaded the Ableton Live trial and opened it... got an ugly message about not being able to find the audio channel, crashed and done.  

Loaded X1 Trial.  Worked like magic.

Check out my new signature. :D


The good news is that I'm "stickied" on the M-Audio forum, so I still plan on having them tell me what to do.