What does this mean?
IceDragonArt
Posts: 12,548
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
WARNING: libpng warning: iCCP: known incorrect sRGB profile
I get this when Studio crashes with an kernel exception error..
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
It is a general warning that the color palette profile is not the program expects for the image slot. Example would be a .jpg file a strength slot instead of a grey scale .tif or .png format. I suspect everyone get those, I know I do and they haven't caused any crashes for me.
I wonder what causes the whole kernel exception thing then. It keeps saying unable to recover from a kernal exception. That's great except I don't know what it means. Or how to fix it lol. Doesn't happen all the time just occaisionally. But enough that I have gotten very vigilant about saving my projects before I hit the render button.
I was told the message about the sRBG profile are caused by png icons in your library that are missing that information and in fact that the sRGB profile isn't actually a requirement for modern png format images anyway so you can ignore it as it doesn't cause DAZ to crash or even hurt it doing anything except slow it down if the very slightest bit.
For the other error message, 9 times out of 10 though kernel exception errors are caused by video card driver crashes and in my experience with DAZ Studio the most likely cause for your crash is you ran out of memory on your video card for a render or had an item loaded know to cause a DAZ Studio render crash like that modeled ivy on that pergola product.
Why are they not removing stuff known to cause crashes or at least telling people what they are? I have plenty of memory and almost never experience any kind of slowdown when rendering and the scene that caused it last was not anything that should tax my video card.
Well the sRGB errors is from a 3rd party open source library they are using. They could contribute to the open source project that they are using by contributing bug fixes and i'm sure they do a times. Those warning do no harm though and can be helpful to the programmers to really figure out what is wrong in some instances.
The other error message about the kernel exception they do fix those sort of errors where they have access when possible or at least warn you about the situation when it isn't a bug. DAZ has given me warnings about low memory for instance and suggested the DAZ Studio functionality would be degraded.
For the ivy 3D model and the pergola 3D model crash bug DAZ programmers have no access to that fix. It is nVidia's to fix. They can contribute the bug fix to nVidia to fix the problem but they still have to wait for nVidia to decide to incorporate the fix and then distribute the fix so that DAZ Studio can incorporate it.
And finally for out of memory there is nothing that can by done as that usually isn't a bug anymore. It used to be a bug but unintended memory leaks that used to cause these out of memory bugs are pretty rare with today's programming languages. Often the OS a program is running on will agressively shut down programs that keep claiming more and more memory once usage gets up to 100%.
If a file isn't properly tagged with a profile, which is what sRGB is, then it cannot convey the proper gamma information to D|S. That could affect things like the apparent brightness of a texture. You could luck out and have it look right, or it might not. All image files that are expected to have a profile should have one, especially for Iray. It's part of what makes consistent renders.
That said, you should not get crashes because of it. I'd be sure to log a ticket with Daz about this. See if you can isolate the image or image set that gives you the problem. If it's one of theirs, they can fetch it from their database. If not, you might send it to them if requested.
A kernel exception could be thrown by something in the graphics library (which is open source, and Daz could fix it and submit the changes), or from D|S itself, or from your specific graphics driver.
Okay thanks everyone! I know its not a memory problem as I keep close tabs on that and I rarely come even close. (this is a newer computer and while I didn't know about studio when I got it last year I tend to pump as much ram and memory into it as I can afford since I also play some really resource intensive games. Although not much lately since Studio tends to suck up all of my free time lol) I will start taking notes of what's in the scenes that are causing the crashes and what the log files say at that particular moment as well and once I have gathered some more info will turn a bug report in. I do have a Nvidea card but I haven't updated it mostly because I keep reading about issues with the updates that I just don't want to deal with.
As far as the "known incorrect sRGB profile" problem goes, I have no issue with taking the textures into Photoshop and resaving them with the right profile. I just don't know how I'd go about it. Any suggestions?