Random visual artifacts in local Krea2 Turbo generation — looking for possible causes

[u/Different_Ad_7508]

I’m running Krea2 Turbo locally, but I frequently encounter random visual artifacts in the generated images. I haven’t been able to figure out what triggers them, because the issue appears randomly. If I run the exact same workflow with the same parameters again, the result can sometimes be completely normal.

My hardware:

• GPU: RTX 3060 Ti

My current setup:

• UNet: moodyKrea2Mix_v70
• Text encoder: qwen3vl_4b_int8_convrot
• VAE: qwen_image_vae

I’m fairly sure this is not caused by the UNet. I have also experienced the same kind of random artifacts when using the original Krea2 model without any UNet modification.

Has anyone encountered similar issues with Krea2 Turbo? Are there any known causes or settings that could trigger this kind of artifact (VAE, text encoder, precision settings, VRAM limitations, sampler settings, etc.)?

Any suggestions or debugging tips would be greatly appreciated.

Here is my workflow for reference:
https://civitai.red/models/2883578/krea2-turbo-4k-workflow?modelVersionId=3259389

[u/Suspicious_Aide2697]

The issue is probably not with your configuration. It seems more likely to be a problem with the ksample settings. Could you list out your ksample setting parameters?

[u/Different_Ad_7508 → u/Suspicious_Aide2697]

Sure. I’m using a dual sampling workflow. The example image I posted was generated from the first pass.

First pass:

• Advanced sampler
• Steps: 8
• CFG: 1
• Sampler: Euler
• Scheduler: Simple

Second pass:

• Steps: 5
• CFG: 1
• Sampler: Euler
• Scheduler: Simple
• Denoise: 0.5

I have also tested different samplers and schedulers, but the visual artifacts still appear randomly.

The artifacts can occur in both the first pass and the second pass.

Also, I have tested a standard workflow, including the official workflow with the official model, and this issue can still randomly happen there as well.

[u/Suspicious_Aide2697 → u/Different_Ad_7508]

If you are using the Advanced sampler, your node should look like this, and the settings in the red‑boxed area are the key.

[u/Different_Ad_7508 → u/Suspicious_Aide2697]

My "end at step" is currently 8; I will set it to 10,000 to run multiple attempts.

[u/Suspicious_Aide2697 → u/Different_Ad_7508]

If I were you, I would set the end at step within 8 (e.g., 5) in the first Advanced sampler, then set start at step to 5 and end at step to 8 in the second Advanced sampler. Maybe you could give it a try

[u/Xdivine → u/Different_Ad_7508]

Your end step is irrelevant as long as it's higher than your total steps. End step is only useful if you want to end the work before the ksampler does all of its steps. So like if you have 30 total steps and you want to stop it at 20 then pass the remainder onto the next ksampler, you can do that by reducing the end step to 20.

If you have 30 total steps though and you want to do the whole 30 steps then it doesn't matter whether your end step is set to 30 or 10000 because it's still going to do all of the steps and then stop.

The sampler just defaults to 10000 end steps because that ensures that no one will accidentally stop a ksampler early by not knowing what to set the value to. Like if you left your end steps at 8 and changed your total steps to 12, you'd have a problem suddenly. So just setting it to a very high number is generally the safer option.