Colossal_Chaz

Hello, I am very keen to try and keep this thread on topic about the issues I, and others, are having. I have seen a few other threads on these forums where someone mentions "gaming" and everyone seems to lose their minds about it and the thread gets off topic. Having said that, I don't really understand why using your PC for multiple disciplins would have any kind of detrimental effect on the system, and it certainly shouldn't be leading to issues like the ones I am having. Its not like I am editing music whilst gaming, I am obviously only ever doing one at a time. I have been gaming and making music on the same pc systems for over 10 years now and have never run into issues like this, this is clearly something to do with the L6 drivers in particular having some kind of problem. The fact that it happens during gaming may point to the cause of these BSODs but I don't think a solution should be "don't game and make music on the same PC". There must be a better solution to this problem.

I am currently having a very similar issue to those in this thread too. I use my Helix as a full time sound card for my Windows 10 PC. When using it as normal in Windows I never experience crashes or BSOD and everything works fine, this extends to talking in discord with a mic I have plugged into the Helix. However whenever I play games (Experienced this in Dota 2 and CS:GO), all my audio and the game will occasionally stutter. Sometimes very briefly before returning to normal, and sometimes it will grind to a halt and I will get a BSOD. This has happened multiple times within the past two weeks however the problem has been ongoing since I got the Helix. Originally (a few months ago) games would just stutter and then occasionally completely freeze up (requiring computer restart), however it has now started giving me BSOD. So far this issue seems to be isolated to when I am playing games on the PC. I am yet to experience it when using the Helix within Ableton or any other program. I am certain that this issue is something to do with the Helix driver and some kind of driver conflict with something else. I downloaded BlueScreenView recently to view the past 2 BSOD that I have experienced, and the first one says that the cause driver was L6PodHd2.sys and the second one was L6Helix.sys (or something similar). Between these two BSOD I updated my Helix firmware from 2.7 to 2.81, as well as installed the latest version of HX Edit (along with all the drivers). So I believe I was using older drivers when the first one occurred and newer drivers when it occurred again. I also completely reinstalled Windows between these two BSOD, as I happened to be migrating from one SSD to a new one. I was really certain that a brand new windows install would fix the issue but alas. At present, the only USB devices I have plugged in are my mouse and keyboard, which I am fairly sure should not be experiencing compatibility issues? They don't have any extra software installed on the PC to support them they just plug in and go. When I experienced the first BSOD, BlueScreenView said that it was caused by L6PodHd2.sys and was something to do with ntoskrnl.exe much like what BeforeTheStorm posted further up. The second BSOD instead said that it was caused by Wdf01000.sys but that it was something to do with the L6Helix.sys. I have googled both of these associated files however found no real answer. The logical thing to do here would be to post these dmp files so that you guys can have a look, however since getting that second BSOD, I attempted to run the built in Windows Driver Varifier to see if it could give me any useful information. After doing this it stated that it required a reboot, which I did, which caused a bootloop where by windows would BSOD every time it attempted to start, displaying the error DRIVER_VERIFIER_IOMANAGER_VIOLATION, which was just brilliant. One system restore later and I was back to where I am now, relentlessly trying to google and find a solution to this incredibly annoying issue. However, within BlueScreenView I can see the dmp file created during this bootloop BSOD, and both the ntoskrnl.exe and Wdf01000.sys files are mentioned, as well as l6Helix_AvsFilter.sys which I haven't seen before but is clearly linked to the L6Helix.sys driver. Here is a screenshot of the program and i'll attached the dmp file if that is something I can do for people to look at. So something is clearly going wrong here with the Helix drivers and it is driving me insane. It seems like there is a very small number of people also experiencing this kind of problem and as a result troubleshooting is hard. I have also seen talk of people saying that they have had compatibility issues with the Helix and their Asus motherboards, which I have, so maybe the problem lies in MB compatibility? I have updated all of my motherboard drivers as well as graphics etc, I wonder if I should try to uninstall the audio drivers that have come with the motherboard although I don't think they are the issue. I would love some help in fixing this, surely we can pool our resources and try to get to the bottom of the issue. I haven't yet contacted L6 support however it does seem like people's experiences when doing this hasn't been very good... My system specs are listed below: Asus Z87-A Motherboard Intel I7 4770-K Processor Corsair Vengeance DDR3 1600MHz RAM Nvidia 660ti Graphics Card Corsair CX600M Power Supply Zowie FK1 Mouse CM Storm Quickfire TK LINE 6 HELIX EXTERNAL SOUND CARD Helix Problem.dmp