Checklist
Bug description
Hello,
I encountered a consistent crash while using Flarial Client with Minecraft Bedrock (Windows GDK).
Below are all the details that may help identify and fix the issue.
Crash Summary:
Error: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Signal: SIGSEGV (11)
Access Type: Read
Fault Address: 0x00000000000000F0
Exception Address: 0x00007ffe1c909ca0
Context:
The crash happens immediately after switching screens
Transition: third_party_server_screen → hud_screen
Last action type: screen_change
ClickGUI was not active
Occurred during normal gameplay, no manual interaction at the moment
Technical Details:
The crash originates inside Flarial.Client.Release.dll
Stack trace shows repeated calls within the client before returning to Minecraft.Windows.exe
Likely a null pointer dereference when accessing HUD-related data
The address 0xF0 suggests reading from an uninitialized or freed object
Environment:
Platform: Minecraft Bedrock (Windows GDK)
Graphics API: D3D12 (observed from stack)
Suspected Cause:
A HUD-related feature attempting to access server data after leaving or switching context
Possibly a widget or overlay that depends on server state
The issue appears when returning from a server screen to in-game HUD
Steps to Reproduce:
Launch the game with Flarial Client
Join a server
Leave or switch from server screen
Return to HUD
Crash occurs
Additional Notes:
Disabling the client prevents the crash
Issue seems specific to Flarial, not Minecraft itself
Might be related to HUD modules like server info, stats, or overlays
this massage is AI-generated to help u fix it (i hope)
EDIT:
I found the issue.
The problem was caused by a module called ItemTracker. I disabled it, and now the issue is gone.
Checklist
I have checked the FAQ
I have searched the issues of this repository and believe that this is not a duplicate
Bug description
Hello,
I encountered a consistent crash while using Flarial Client with Minecraft Bedrock (Windows GDK).
Below are all the details that may help identify and fix the issue.
Crash Summary:
Error: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Signal: SIGSEGV (11)
Access Type: Read
Fault Address: 0x00000000000000F0
Exception Address: 0x00007ffe1c909ca0
Context:
The crash happens immediately after switching screens
Transition: third_party_server_screen → hud_screen
Last action type: screen_change
ClickGUI was not active
Occurred during normal gameplay, no manual interaction at the moment
Technical Details:
The crash originates inside Flarial.Client.Release.dll
Stack trace shows repeated calls within the client before returning to Minecraft.Windows.exe
Likely a null pointer dereference when accessing HUD-related data
The address 0xF0 suggests reading from an uninitialized or freed object
Environment:
Platform: Minecraft Bedrock (Windows GDK)
Graphics API: D3D12 (observed from stack)
Suspected Cause:
A HUD-related feature attempting to access server data after leaving or switching context
Possibly a widget or overlay that depends on server state
The issue appears when returning from a server screen to in-game HUD
Steps to Reproduce:
Launch the game with Flarial Client
Join a server
Leave or switch from server screen
Return to HUD
Crash occurs
Additional Notes:
Disabling the client prevents the crash
Issue seems specific to Flarial, not Minecraft itself
Might be related to HUD modules like server info, stats, or overlays
this massage is AI-generated to help u fix it (i hope)
EDIT:
I found the issue.
The problem was caused by a module called ItemTracker. I disabled it, and now the issue is gone.