Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Hardware > FireWire & USB Audio Interfaces (Win)

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 08-26-2013, 12:23 PM
ZigaR ZigaR is offline
Member
 
Join Date: Mar 2013
Location: Kranj
Posts: 2
Default MBox Mini (3rd gen.) 1.1.7 driver causing BSOD

After installing the new driver I had high hopes, because the previous version had problems with ASIO on Win7x64, so I had to reinstall the driver every odd time after I restarted the computer and wanted to do some tracking.

Now I'm not tracking at all, because the new driver (1.1.7) causes a BSOD every so often (around every half an hour, it depends on how much I switch between different audio applications). It's the same on Win7x64 and Win8, genuine and fully updated. Anyone having the same problems and, better, knows how to solve them?
Reply With Quote
  #2  
Old 08-27-2013, 06:06 AM
JoelG's Avatar
JoelG JoelG is offline
Moderator
 
Join Date: Mar 2010
Location: Canada
Posts: 1,988
Default Re: MBox Mini (3rd gen.) 1.1.7 driver causing BSOD

Can you post the details of the BSOD? What file is causing it? Also you might want to do a memory test just to be sure:http://www.memtest.org/

Joel
__________________
Jam Space:
HP Elite 6300 / Core i5 3570 / 12GB RAM / Win 10 Pro
Pro Tools 2021 HD / Focusrite 18i20 + M-Audio ProFire 2626

Home:
Asus B450 Pro4 / Ryzen 5 2600 / 32GB RAM / Win 10 Pro
Pro Tools 2021 HD / Focusrite 18i20 + M-Audio ProFire 2626

Rig:
Eleven Rack / ART SLA1 / Two 2x10 Passive Monitors / FCB1010 w/ EurekaPROM
Reply With Quote
  #3  
Old 08-27-2013, 11:40 AM
ZigaR ZigaR is offline
Member
 
Join Date: Mar 2013
Location: Kranj
Posts: 2
Default Re: MBox Mini (3rd gen.) 1.1.7 driver causing BSOD

Hi,

I've uploaded the memory dump files HERE, and i'm pretty sure it's the driver that's causing the BSODs, because the problems appeared instantly after installing the latest driver. Also, Win8 has a bit more sophisticated BSOD that actually wrote out that it was the MBox driver that caused the fault (instead of just giving me the exit code and a generic error descripion, like Win7).

If you need any additional data please ask, I will provide anything that can be of use to you.

Thank you for the quick response!

Z
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
dalwdm.dll causing 6031 error and BSOD majorlabel Windows 19 09-07-2012 03:35 AM
dalwdm.dll causing 6031 error and BSOD majorlabel Windows 0 06-27-2012 06:02 PM
BSOD when reinstalling Mbox 3 Mini driver*Sandra report included davidleecarter 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) 5 01-24-2011 12:44 PM
Mbox driver causing kernals & crashes yanncrusoe 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 0 07-20-2009 12:20 AM
Could my Mbox mini be causing the 6086 error? flash0669 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) 5 09-03-2008 07:21 PM


All times are GMT -7. The time now is 04:57 AM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com