BSOD connecting M-Audio USB Fast Track 100% repro rate

Hello all,

I´ve been looking on the web some information about this BSOD related to M-Audio products, but none of your good advices to other users have solved anything to me.

The issue occurs when the M-audio card is connected to the PC and I launch Cubase 5.1, the BSOD will occur. For some reason, if I launch Cubase without the M-audio connected, it will open the program as expected.

So attached to this thread you will find the Zip containing the Dump file as descripted on the tutorial.

Please note that this is my first post here so any info that I may forgot to add just let me know and I will look for it.

Thanks beforehand.

Edit 1: reload the *.zip since I was missing the systeminfo data.
Edit 2: updated steps to the BSOD.

I have a Sonar studio. I have an MAudio Fastrack Ultra 8R and do not have any problems connecting this unit. I use this unit with several different PC's and do not have any problems with any of them Are you using the latest and correct driver from MAudio? Have you tried a different USB cable?

There is an MAudio forum for support. Have you been there? The Official M-Audio User Forums

Oh, so its just a problem connecting to one PC, running Cubase.

Try this, connect the unit to the PC and then go to the Device Manager and RIGHT click on the entry for the MAudio unit. Then, LEFT click "Uninstall". Also check the box to uninstall the drivers. Disconnect the MAudio unit from the PC and then reboot. After Windows starts, reinstall the MAudio driver software and after the driver install is completed connect the MAudio and Windows will detect and install it (like a new installation). If there were any corruptions in Windows this will take care of that (and may put the MAudio unit on a different shared Interrupt).

Now try Cubase and see if it works OK.

Try uninstalling the drivers using |MG| Driver Fusion (Driver Sweeper) 1.2.0 Download in safe mode from Advanced Boot Options

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.