dForce Kernel Compilation Crash

ainm.sloinneadh

Daz crashes everytime I try to simulate a dForce scene. It tells me I need to compile the dFroce kernel, which makes sense as it's a fresh operating system install. I click ok. It crashes. The crash dump doesn't tell me much beyond a problem with KernelBase.dll in the SysWOW64 System32 Windows folder:

DAZStudio.exe caused UNKNOWN_ERROR in module "C:\Windows\System32\KERNELBASE.dll" at 0033:0000000083E8CF19, RaiseException()+105 byte(s)

Nothing in the log file. Nothing else in the crash report. Button to submit bug report to Daz greyed out.

I've been troublehsooting this for a few hours and am stumped.

Context behind everything:

• I recently added another harddrive to my machine.
• I've freshly installed Windows 10 on it, along with Firefox, Windows Media codecs and device specific drivers.
• I still have the drive with my previous version of Windows because I like to keep backup plans (and I was using Daz on it until a few days ago)
• The two versions of Windows 10 are the same.
• My GPU is an nVidia RTX 3060. I've installed the same driver version as on the other installation of Windows. I've also tried several other drivers from the past two years.
• The only other things on the new drive are DIM, Daz, the starter modules and my entire Daz library.
• Everything else in Daz works brilliantly. The fresh install feels a lot snappier and it's super quick at loading off the new drive.
• But I can't compile the blooming dForce Kernels without crashing :'(
• I've tried reinstalling Daz studio and the dForce start package too. Same issue.
• For the more technically minded, I've run DSIM and SFC to check for corruption. I've also tried to copy the KernalBase.dll from the other installation across in case there's an issue in that, but haven't been able to break into my system folder yet. But I've been able to compare the files and they look identical. The issue appears to be in something Daz is trying to launch through KernalBase? I'm assuming the OpenCL libraries, which makes me think there's an issue with the driver installation. But I've clean reinstalled maybe a dozen times, and have tried 4 different driver versions just to be safe (I'm glad the HD is fast :'D)

Anyone any ideas? Or any pointers on how I can troubleshoot further? I don't even have a proper crash report that I can send to Daz for a look.

crosswind

So your Win10 and Daz Studio application are both x64 ?

ainm.sloinneadh

crosswind said:

So your Win10 and Daz Studio application are both x64 ?

Windows certainly is. But yeah, Daz is looking in the System32 folder - my mistake. I thought there were Win32 versions of the DLLs in the SysWOW64 for legacy stuff. Does that mean Daz is a 32bit application? Surprising if so.

ainm.sloinneadh

crosswind said:

So your Win10 and Daz Studio application are both x64 ?

Daz is 64 bit too.

ainm.sloinneadh

Hmmm, I fixed it. I created a new local account on the Windows installation and reinstalled on that. I guess the profile on the other account was corrupted out of the box - probably didn't have access to the appropriate folder to launch whatever Daz was using KernelBase to launch. Odd.

crosswind

OK ~ that should be fine from application perspective. Since dForce uses your graphics card but there's no need to seek issue from OpenCL other than the driver itself...

I would suggestu you use DDU to completely clean Nvidia driver and residuals on your system, then install a new fresh driver for testing... https://www.wagnardsoft.com/display-driver-uninstaller-DDU-

Not affirmative if it'll work with your case but DDU has been greatly helping with similar cases for many people...

crosswind

ainm.sloinneadh said:

Hmmm, I fixed it. I created a new local account on the Windows installation and reinstalled on that. I guess the profile on the other account was corrupted out of the box - probably didn't have access to the appropriate folder to launch whatever Daz was using KernelBase to launch. Odd.

You use the account with ADMINISTRATORS auth. ?

ainm.sloinneadh

crosswind said:

ainm.sloinneadh said:

Hmmm, I fixed it. I created a new local account on the Windows installation and reinstalled on that. I guess the profile on the other account was corrupted out of the box - probably didn't have access to the appropriate folder to launch whatever Daz was using KernelBase to launch. Odd.

You use the account with ADMINISTRATORS auth. ?

Yup. I'm assuming the account permissions were created broken. That's the only thing I can think of that could have been that account and the one it worked on.

crosswind

OK ~ got it. Don't use ADMINISTRATORS... there'll be other potential issues, e.g. when using Daz to XXX bridges, importing may fail in other applications, etc...

ainm.sloinneadh

crosswind said:

OK ~ got it. Don't use ADMINISTRATORS... there'll be other potential issues, e.g. when using Daz to XXX bridges, importing may fail in other applications, etc...

Ah, good to know - thanks! I assumed that group would work with eveything flawlessly. I wonder if me playing about on it caused the issues on the user account or in Daz linking stuff up.