So this is probably not something the devs of Create can tackle and they might not even deem it high priority however I thought I'd open the issue if anyone is searching on google. Also because it seems the devs of create anticipate some use of shaders with their mod so they may be interested in bugs that happen when using them. I do have a workaround for this issue as well which I'll explain is not great.

My setup is as follows:

1. Install recommended Forge.
2. Install Create and Optifine.
3. Add shaders; I'm using Complementary Shaders, but any I've tested will recreate this error.
4. Enable shaders. Load into the game.
5. Now enable "Render Regions" in performance.
6. Place a shaft. Observe OpenGL Error 1281 (See attached photo, and pastebin for log).
   

Log: https://pastebin.com/BJiXKPH7

This seems to only happen with the shaft, haven't tested every block in Create yet. Why does this matter? Well render regions happens to be the difference between 30-40Fps or 80-90Fps when using Shaders on higher render distances than 4 chunks. Again, I'm not pointing fingers at Create as this is an Optifine feature that isn't meshing well and that's how the Optifine cookie crumbles all too often.
The easiest way around this issue is just to not use render regions and suck up the frames, but it would be oh so amazing if this render regions debacle could get sorted. As far as I know AE2 also has this issue with their cables. From past experience when Optifine had a "Use VBOs" option enabling it would illicit a similar response no matter what items were placed. Maybe this is more of a shader issue, maybe its more of a Optifine issue, I'm not sure. I do know this is the main issue I'm stuck on at the moment with modded Minecraft.

Thanks for the time,
Maevarienn <3

Tl;dr:
Local idiot tries to expect a good time using Optifine. Please ignore if not concerned with Optifine.

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.

This happens without shaders as well.

I had that error, but no rendering issues like you did. I didn't have any shaders applied. It shows up mostly when traveling between dimensions and into unloaded chunks. Also, I had render regions turned on.