4pre blue screen

[TScottBassist]

So I just got my 4pre in yesterday and spent around six hours trying to make it work. In that span of time my computer went to the BSOD four times....

And by the end I still can't get it to work as my main sound card, nor can I manage to actually record sound. It will process sound that I put into it and send it out of the main outs and the headphone outs. And CueMix can affect volume, pan, trim, all that good stuff. So the 4pre is working and properly connected to my computer...... leading me to believe that the MOTU drivers are at war with my Realtek audio drivers or perhaps something else.... as my biggest audio gear fanatic friend has informed me that apparently third party antivirus software can cause havoc with audio interface drivers.

So to be on the safe side and to give the most information possible here is my hardware set-up as well:

Mobo: Asus M5A97
CPU: AMD FX-4100 Quad Core
RAM: Kingston HyperX Blu 2x4Gb DDR3 1600
SSD: Patriot Pyro 120GB
HDD: Seagate 500GB

I'm running Windows 7 and using McAfee Internet Security and the 4pre is connected via USB

HELP!!!!!!! PLEASE!!!!!

[MoraAli]

Because of your knowledge of your HW i think you have tried this, but still.

http://www.motunation.com/forum/viewtop ... 76#p422176

Let me know if you solved your issue.

[torrentg]

Please see my thread here:

http://www.motunation.com/forum/viewtop ... 14&t=51005

They have helped me personally in the past. Let's hope for a repeat, shall we?

But you're using USB, so your issue may be different.

I do suggest to remove McAfee in safe mode with the tool from them to do so. Then test. If you still need more help, I'll analyze your crash for you and tell you what is or may be going on.

Install MSE to replace McAfee.

[TScottBassist]

Sorry for not getting back to this in any sort of timely manner.

I called Motu and was guided through by one of their tech support team members and found out the issue had two main causes:

Cause #1 I had plugged the 4pre into a USB 3.0 jack thinking that 3.0 is backward compatible to 2.0. Ha! Was I wrong!

Cause #2 There was a new driver update (while this sounds like a very newbie sort of issue I submit for consideration that in the text Motu had placed on their site at the time had the incorrect software version listed. [They have fixed the typo in more recent updates.])

Once I did those two things I was good to go!