Thanks for the support everybody. Right now I succeded on installing EOS without boot loader. So the plan now is to somehow get a boot loader installed so I would be able to actually start the EOS. Earlier problems with that is that as soon as the new boot loader try to write something system freezes again, so I have to trick the windows boot loader to think is is the ‘linux one’
Microsoft Windows boot loader location
On certain UEFI motherboards like some boards with an Intel Z77 chipset, adding entries with efibootmgr or bcfg from the UEFI Shell will not work because they do not show up on the boot menu list after being added to NVRAM.
This issue is caused because the motherboards can only load Microsoft Windows. To solve this you have to place the .efi file in the location that Windows uses.
Copy the BOOTx64.EFI file from the Arch Linux installation medium (FSO:) to the Microsoft directory your ESP partition on your hard drive (FS1:). Do this by booting into EFI shell and typing:
Shell> mkdir FS1:\EFI\Microsoft
Shell> mkdir FS1:\EFI\Microsoft\Boot
Shell> cp FS0:\EFI\BOOT\BOOTx64.EFI FS1:\EFI\Microsoft\Boot\bootmgfw.efi
After reboot, any entries added to NVRAM should show up in the boot menu.
but I still need to also install the boot loader I guess
Still thinking, but open to suggestions