BIOS change results in Stackhash crash?

I’m unable to load projects with QL Spaces in them.


Oddly it’s intermittent… The project seem to get to a certain size and then it won’t load.



Michael

Sounds like you have a problem with windows. Many time this happens due the fact people tend to upgrade there system, instead of install it from scratch. Sooner or later you get weird stuff happen, due old settings in programs.
A bios reset do not make this stuff happen. The only time id does is when you get a hardware error and you need to tweak settings to underpower some stuff from the default settings.
Also dust in the computer can make weird stuff to and make hardware working bad.

My advice is to save all work on the computer and reinstall windows 8.1 or windows 10( when they have fixed the issues Steinberg has with it or buy a new computer and install all your stuff there.
Sure its a lot of work, but in the end you will get a better “windows” and you get a better platform for audio work.
Also make sure you do not use junk antivirus program, like Norton.

Sounds like we’re onto something here. Its no coincidence my first QL Spaces crash was back in 2014.

I just clean installed Windows on a new drive, but I will be able to go back to my old OS if needed.

Update I have clean installed windows 7 on fresh SSD, and have encountered issues. Once I added Kontakt5 and QL Spaces as plugins, the session crashed when loading. Faulting module is ntdll.dll. BTW at this point I am determined to solve this. Ive been out of commission for over a week and and I’m worried that my clients will start to lose patience. Im happy to troubleshoot with any developer who wants to call me up.

Hmm. This looks familiar from the crash I was getting on my old OS:

Files that help describe the problem
AppCompat.txt
WERInternalMetadata.xml
memory.hdmp
minidump.mdmp


tempted to reinstall again and not run any windows updates. Idk what else to try if windows is at fault here…

Description
Faulting Application Path: C:\Program Files\Steinberg\Cubase 8\Cubase8.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Cubase8.exe
Application Version: 8.0.20.468
Application Timestamp: 5547e4e7
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18869
Fault Module Timestamp: 556366f2
Exception Code: c0000005
Exception Offset: 000000000005107c
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 1ec4
Additional Information 2: 1ec431522dadd7b81d0d55e3462a2d0e
Additional Information 3: 9fd1
Additional Information 4: 9fd16ded501ded700f609ca006c1cae1

Extra information about the problem
Bucket ID: 1243582

Installed Cubase 6.0 fresh from the disk. Project crashes Cubase 6.0 as well, mentioning QL SPACES as the fault module from the crash.

Description
Faulting Application Path: C:\Program Files\Steinberg\Cubase 6\Cubase6.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Cubase6.exe
Application Version: 6.0.0.229
Application Timestamp: 4cf95e39
Fault Module Name: QL Spaces x64.dll
Fault Module Version: 1.1.23.0
Fault Module Timestamp: 557e9935
Exception Code: c0000005
Exception Offset: 000000000008388b
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 95cf
Additional Information 2: 95cf3345cd70fef7fd94ef1b422f5870
Additional Information 3: d461
Additional Information 4: d46129ab79645961264a0171094a0f9e

Extra information about the problem
Bucket ID: 28640512

Apparantely the new OS had a BSOD while I was gone. I read that I should install Windows 8.1 SDK with WinDbg to read the minidump file. The file says: Probably caused by ntoskrnl.exe ( nt+748c0 )

Im gonna run MemTest86. Lets hope I have faulty RAM or something. IDK what else to do.

Memtest86 found 11 errors in the first 5 minutes. Wonderful.

Ran Memtest for days and eliminated 3 faulty ram sticks. Memtest runs clean. and I got a crash again. that’s great news that it’s not my ram!

Description
Faulting Application Path: C:\Program Files\Steinberg\Cubase 8\Cubase8.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Cubase8.exe
Application Version: 8.0.20.468
Application Timestamp: 5547e4e7
Fault Module Name: StackHash_52b8
Fault Module Version: 6.1.7601.18869
Fault Module Timestamp: 556366f2
Exception Code: c0000374
Exception Offset: 00000000000bfc22
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 52b8
Additional Information 2: 52b83f99a5c5b8b93785802b024d2e79
Additional Information 3: 2055
Additional Information 4: 2055f8eebdab35afa6480066fe4e8eec

Extra information about the problem
Bucket ID: 31656072

Hello Andrew,

given it is a new install, did you update the system drivers downloading the executable files from the motherboard manufacturer’s website? In the pic you posted, it looks like there are issues with the Intel Rapid Storage Technology (IAStorDataSvc), so the above could help. As for the nVidia, I can only recommend to re-install the driver or test another version, besides disabling the 3D acceleration and such.

If you didn’t resolve the BSOD minidumps, I can have a look at them (C:\Windows\minidumps).

Kind regards,

Hi Fabio, i installed intel rapid store, which was not installed on the other OS. How do I disable 3d accel on nvidia? I was concerned about that driver so I uninstalled the nvidia software and used the driver from windows 7 update.

I did install:
Intel chipset
Intel gigabit
ASmedia USB 3.0 controller

I also tried loading the old OS as well. Worked fine but I had a BSOd for Kernel data in paged area. I ran chkdsk and memtest again and hasn’t crashed again yet.

I’ll see if I can send some more dump files.

Thanks!

Andrew