Solved BSOD (APC_INDEX_MISMATCH) running Cubase LE AI Elements 7

[softwaremaniac]

I read about that issue on various forums and I think I mentioned it before that you should try ASIO I'm glad we have finally found the cause.

 

[erixven]

Well, just for your information: Focusrite is hardware that connects the audio through ASIO too. So it's not really a matter if I should try ASIO. ASIO is inherent to a Digital Audio Workstation like Cubase. It is the way these DAW's communicate with the audio. The thing is, this Focusrite has excellent microphone preamps and has 18 ins and 8 outs, which is really not comparable with a software ASIO interface like ASIO4ALL. If the Focusrite works without BSOD's, I can record up to 18 tracks simultaneously. With the ASIO4ALL I can not even record one audio track since I have to use the silly microphone input of the laptop, which is a toy compared to the Focusrite quality AD-converters and preamps.
So this issue is not solved by concluding there is a software ASIO driver that doesn't crash my system.

 

[softwaremaniac]

Have you tried using another driver version for Focusrite? If you have to use it. Which exact piece of Focusrite HW do you have?

 

[erixven]

Hi softwaremaniac,

I have the Focusrite Scarlett 18i8 with the newest ASIO driver.

I have contacted Focusrite support by email and sent them the link to this thread. Awaiting their reply.

 

[softwaremaniac]

Keep me updated

 

[usasma]

Just FYI - there is a fundamental difference between stopping BSOD's on a user's system and debugging drivers.
When stopping BSOD's we look for the program that's causing them and remove the program - problem solved.
But with a buggy driver, one has to locate the exact place that the driver crashes at, then determine the cause of the crash, then fix the driver so that it no longer crashes (a much more detailed/involved process). This is not something that the average user can do (legally) and it would probably be cost prohibitive (hiring a driver developer is an expensive proposition).

If interested in debugging drivers, I'd suggest posting over at the listgroups in OSROnline ( OSR Online - The Home Page for Windows Driver Developers )

As for your question about why the thing would crash without Driver Verifier running and not crash with it running, there are numerous possibilities.
The next step would be to try different verifier tests on that individual driver ( the ASIO one from Focusrite ). This is a test that is better performed by the driver developers at Focusrite as they are familiar with how the driver(s) work. The selection of the verifier tests to use (and which combinations should be used) are an art that driver developers are well practiced at (and, unfortunately, I am not).

 

[erixven]

Hi softwaremaniac and usasma,

Thanks a lot for your help and advices so far. I will discuss the issue further now with Focusrite Support and keep you posted. I hope the driver developers at Focusrite will be able to track down the cause of the BSOD's.

 

[erixven]

Solved!

Hi softwaremaniac and usasma,

I can report the problem is solved!
Focusrite Support noticed my notebook has USB 3 ports.
They have a beta driver that is optimised for USB 3.
The current driver was apparently not suited for USB 3.
I installed that beta driver and... no more BSOD's.
The fact that the APC-INDEX_MISMATCH notice points to a hardware problem makes sense now.

Thanks a million for helping me debug this problem!
:thumb::thumb::thumb::thumb::thumb:

Erik

 

[softwaremaniac]

Thanks for reporting back.

 

[usasma]

Thanks for letting us know!