Put the summary of the bug you're having here
What I expected to happen was...:
For a normal grey cobblestone.
What actually happened was...:
When I mined the cobblestone it turned blue for a split second, I bearly got the screenshot you will locate lower on the page, that is the reason why it says there was another screenshot taken.
Steps to Reproduce:
1. Get a pickaxe
2. Break the block (have to be in survival mode since otherwise it would not appear)
3. Look and see how it turns blue for a split second.
Crash report:
---- Minecraft Crash Report ----
// Hey, that tickles! Hehehe!
Time: 1/25/20 12:25 PM
Description: Manually triggered debug crash
java.lang.Throwable at dbl.b(SourceFile:454)
at dbn.p(SourceFile:1511)
at dbn.d(SourceFile:964)
at dbn.d(SourceFile:619)
at net.minecraft.client.main.Main.main(SourceFile:204)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Thread: Render thread
Stacktrace: at dbl.b(SourceFile:454)
-- Affected level --
Details:
All players: 1 total; [dqb['Haukur'/128, l='MpServer', x=2047.66, y=64.85, z=-1485.97]]
Chunk stats:
Client Chunk Cache: 3025, 1253
Level dimension: minecraft:overworld
Level name: MpServer
Level seed: 7549635813985710432
Level generator: ID 00 - default, ver 1.
Features enabled: false
Level generator options: {}
Level spawn location: World: (176,67,144), Chunk: (at 0,4,0 in 11,9; contains blocks 176,0,144 to 191,255,159), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 326867 game time, 539663 day time
Known server brands:
Level was modded: false
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false.
Cheats: false
Server brand: vanilla
Server type: Integrated singleplayer server
Stacktrace: at dno.a(SourceFile:450)
at dbn.c(SourceFile:1921)
at dbn.d(SourceFile:634)
at net.minecraft.client.main.Main.main(SourceFile:204)
-- System Details --
Details: Minecraft Version: 1.15.2
Minecraft Version ID: 1.15.2
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_51, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 1061919864 bytes (1012 MB) / 1912602624 bytes (1824 MB) up to 2147483648 bytes (2048 MB)
CPUs: 4
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Launched Version: 1.15.2
Backend library: LWJGL version 3.2.2 build 10
Backend API: GeForce GTX 760/PCIe/SSE2 GL version 4.6.0 NVIDIA 432.00, NVIDIA Corporation
GL Caps: Using framebuffer using OpenGL 3.0
Using VBOs: Yes
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: vanilla
Current Language: English (United Kingdom)
CPU: 4x Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Linked issues
is duplicated by 3
Attachments
Comments 11
Done 😃

Isn't that just lighting? The item first appears as though it's in complete darkness (blueish dark), and then updates to the correct light level?
I can't seem to reproduce this. Does this happen consistently, @unknown? Could you please update your GPU driver first, you can find the driver here. After that, test it, if this still happens; please attach a video with the F3
menu open demonstrating this issue.
@unknown, the reporter is not using a modded version, see the crash report in the ticket.
This only happened recently with 1.15.2.

I have this issue as well while running the latest AMD drivers, so it is a game issue rather than a driver issue.
I can confirm this issue on 20w13a, 20w13b and 20w14a as well, despite using the latest NVIDIA drivers.

Can this still be reproduced in 1.16-pre5?
Cannot reproduce in 1.16-pre5.
I can confirm it cannot be longer reproduced in 1.16-pre5.
Please attach a force crash report (
F3
+C
for 10 seconds while in-game) to this ticket.