Need help again interface issue

Hello all once again
 
as some of you know I've changed my system I am now using an ASUS all in onewith 4 gb ram with and amd A6 elite.
 
I have installed X3 had some issues's with non essential plug-ins failing to install but I'm not to worried about that.
 
Its seems my focusrite scarlett 2i2 is causing my system to crash. I have installed the drivers from their site. Whilst adding plug-ins or even playing around with the audio settings in my computers control panel it will come up the message " Audio device disconnected" and then causes windows 8.1 to give the blue screen of death with the message APC_INDEX_MISMATCH.
 
It then reboots the system.
 
I have dug my line 6 gx studio out and this seems to work fine so I'm pretty sure there's an issue with either the drivers or the audio interface its self.
 
Anyone else come across this before and are there any cures.
 
I have sent Focusrite an email aswell
 
Many thanks
 
Stuart

Are you sure you downloaded the correct drivers from Focusrite? This is what is posted on Microsofts site about that error. If so then I would try a USB 2 port. Seems the issue was with USB 3. Always use the same port you used when installing the drivers so f you swap to a USB 2 port, re install the drivers. 

 

Cause

The most common cause of this bug check is when a file system or driver has a mismatched sequence of calls to disable and re-enable APCs. The key data item is the Thread->CombinedApcDisable field. The CombinedApcDisable field consists of two separate 16-bit fields: SpecialApcDisable and KernelApcDisable. A negative value of either field indicates that a driver has disabled special or normal APCs (respectively) without re-enabling them. A positive value indicates that a driver has enabled special or normal APCs too many times.

Remarks

This is a kernel internal error. This error occurs on exit from a system call. A possible cause for this bug check is when a file system or driver has a mismatched sequence of system calls to enter or leave guarded or critical regions. For example, each call to KeEnterCriticalRegion must have a matching call to KeLeaveCriticalRegion. If you are developing a driver, you can useStatic Driver Verifier, a static analysis tool available in the Windows Driver Kit, to detect problems in your code before you ship your driver. Run Static Driver Verifier with the CriticalRegions rule to verify that your source code uses these system calls in correct sequence.
 

I will have a butchers with some of these suggestions and will report back.

Problem solved plugged it into a hidden port thats meant to be for charging usb devices turns out to be a usb 2.0 port.
 
I can be a clut sometimes!!
 
Thanks for all the help though.
 
Kind regards
 
Stuart

I can't seem to find any other usb ports on this system there are 4 usb 3 ports and then just the one usb 2 charging port  which seems to be the only one that doesn't cause my interface to turn on and off or crash my system.