kernelbase.dll error

skyejordan99

I've been troubleshooting DAZ for almost a day now because of kernelbase.dll error.
I've included all the files needed below, with screenshot ofcourse.

Richard Haseltine

Looking through the log, it appears you have some Out Of Touch hair or other hair with their shader applied in the scene. Check for updates, or make sure that none of the hair surfaces using their shader has a map in Transmitted Colour. This is discussed in the DS beta and release threads.

crosswind

If I remember correctly, the crash caused by rendering OOT hair comes from iray libarary.dll rather than kernelbase.dll...  But still, please first check if you have updated OOT hair product (Tjark Short Hair for Genesis 8 Males), then retry rendering.

Besides, the log tells that you ran out of VRAM with your 3050 once then you might've turned on Allow Fallback to CPU then Memory allocation failed errors were reported for twice...as well as the errors : failed to compress texture on GPU, then compress with CPU instead, then it further failed and DS crashed.

So can you confirm if you rendered with GPU or CPU ? Because usually kernelbase error mostly relates to CPU...

stefan.hums

The lack of physical memory (RAM) is the cause of the crash. From the errorlog.xml:

  <syserror>
    <code>0x00000008</code>
    <description>Not enough memory resources are available to process this command.</description>
  </syserror>

Well, with only 8 GB RAM and only 4 GB VRAM for the GPU, this scene will never ever render on this machine.

An OS like Windows 10/11 usually takes about 5 GB RAM already, what is left for Daz Studio, scene and render data will exceed the 8 GB dramatically and will be swapped to the Windows page file. And the screenshot of the error already confirms this:
Total Page File Memory: 32588 MB
Available Page File Memory: 193 MB
Means the page file is full already. No more memory left for swapping data - Daz Studio crashs, no ifs and butts.

crosswind

That's it. Load a Base figure for a test or at try to add more virtual memory before another test with current scene. TBH... it may not be a good choice to run DS and render with this notebook...