ASIO drivers and BSOD

[Utente39]

When i start Cubase 12, if Generic ASIO Low Latency or ASIO4ALL are select a BSOD occurs.

One of error message I read reports:

STORE_DATA_STRUCTURE_CORRUPTION

[Deep_World]

Hi  @Utente39 
 
Welcome to the HP Support Community!

Thanks for reaching out!

I understand that your Victus by HP 15.6-inch Gaming Laptop is encountering a Blue Screen error when launching Cubase 12 while using Generic ASIO Low Latency  drivers. I will do my best to help you.

To better understand the issue, could you kindly confirm the below details ?

• Does the BSOD occur only with Cubase 12, or have you noticed it with other audio applications as well?
• Are you using the laptop's built-in audio device or an external USB audio interface?

In the meantime, kindly try the below steps and confirm  : 

1. Update Windows completely:
   • Go to Settings -Windows Update and install all available updates.
   • Restart the laptop after the updates are installed.
2. Update HP drivers and BIOS:
   • Use HP Support Assistant to check for the latest BIOS, chipset, and audio driver updates.
   • or via the website - click on the link - https://support.hp.com/ 
3. Reinstall the audio driver:
   • Open Device Manager.
   • Expand Sound, Video and Game Controllers.
   • Uninstall the audio device and restart the system.
   • Windows will reinstall the driver automatically.
4. Test without ASIO4ALL:
   • If you have an external audio interface, kindly install and use the manufacturer's official ASIO driver instead of ASIO4ALL.
   • Third-party ASIO drivers can sometimes cause system instability due to low-level audio driver conflicts.
5. Check system files:
   • Open Command Prompt as Administrator and run: 
   • sfc /scannow
6. Perform HP Hardware Diagnostics - click here for steps
   • Restart the computer and repeatedly tap F2 during startup.
   • Run the System Tests, especially Memory and Storage tests, to check for any underlying hardware issues.

Additionally, the error STORE_DATA_STRUCTURE_CORRUPTION can sometimes be associated with memory, storage, or driver-related issues. Running the HP diagnostics and ensuring all drivers are up to date can help identify the root cause.

I hope this helps. 

[Utente39]

Hi. This all details needed. 

1) The issue occurs just with Cubase. The problem occurs just when ASIO drivers are selected.

If I start Cubase in recovery mode and I select M-Audio Air 192-6 or Zoom L20r drivers (both of them are externwl cards) all works fine. I applied a temporary fix by installation of FlexAsio.

The issue occurs just between integrated Realtek and Generic Low Latency ASIO (native Cubase ASIO drivers) or with Asio4all

2) I already installed bios updates

3) I already installed Realtek Audio card updates

4) I already tried to uninstall and install again audio drivers

5) I already updated Windows 11.

6) I already all system hardware diagnostic and no problem has been found, also audio card test was ok

So... Realtek cards works with Cubase just if I use the opensource Asio driver "FlexAsio". 

Both Asio4ll and integrated Cubase ASIO causes Windows crash, so the problem is not when I use Cubase, it occurs when the computer comunicate with these drivers.

It seems just a driver bug. I know ASIO4ALL and Cubase ASIO works on deepest levels with audiocard, FlexASIO is more light and this is reason why with FlexASIO works fine. 
Please note I'm an IT specialist, so I know about procedures.

[Deep_World]

Hi @Utente39 
 

Thanks for your response and Thank you for the detailed update and for confirming the steps completed. Since you are an IT specialist and have already performed the standard steps, I would like to provide a more direct response based on the information shared.

From your findings, the issue does not appear to be related to Windows, BIOS, hardware itself. 
 

The fact that cubase works correctly with your external M-Audio Air 192-6 and Zoom L20R interfaces and HP Hardware Diagnostics passed successfully, Windows, BIOS, and Realtek drivers are fully updated and reinstalling the audio drivers did not change the behavior. and as your mentioned FlexASIO works without causing a BSOD and the BSOD occurs specifically when Generic Low Latency ASIO or ASIO4ALL attempts to interface with the integrated Realtek audio device.
 

This suggests a compatibility issue between the Realtek audio driver implementation and the ASIO wrapper drivers being used.
 

 Since the hardware diagnostics pass and the Realtek device functions normally for standard audio operation, the behaviour points to a driver-level compatibility issue rather than a hardware failure.

Based on all the steps completed  this currently appears to be a software driver compatibility issue rather than a defect with the Victus hardware itself. 

I hope this helps.