Hi @Bugatti you mentioned in another post that you are using
This build introduced the very new Advanced privacy. Sadly on some devices there have been reports of spontaneous reboots and seemingly random corruptions. I am very hopeful that the release of the next update – check out #e-smartphone-operating-system:development-updates – will solve (some of) this.
If you might be facing an Advanced privacy issue then you can check out Issues - Gitlab #Advanced privacy
GSI ROMs do have other issues from time to time, so this might take some teasing out.
In the section Support topics you will find Create a log @/e/.
Once you have platform tools sorted, and your device connected with Developer options > usb debugging on, you can use
$ adb logcat --help
to explore the options you can use with logcat.
In the case of the troublesome behaviour you report this command
$ adb logcat > logcat.txt
will produce a very long output usually from the last reboot.
This works well to record a predictable event; you reboot, start the logcat, allow the fail to happen and close. Perhaps be prepared to experiment with the options.
You ask what you can do to help; you could consider volunteering here Testing @/e/.
I am really not certain if /e/ puts GSI ROMs out for testing; but if you wanted to volunteer the first step is to introduce yourself as indicated in the link – if you say you have a GSI device to test, I guess they will let you know.
Getting Started on /e/OS