UEFI: How to repair kali-linux grub dual boot with Windows 10

[_defalt]

Whenever I install kali linux, I never for once enjoy it.. Always Grub rescue issue.. What's the problem? Is it my system? Or what?... I use hp, Windows 10..720gb hard drive.. 80gb partitioned for Linux only... But I install kali now, I shut down later, after like 5 hours when I on system, I see Grub rescue again and this kali is really needed.. I don't know what to do again m. Please help me.. Please

When it jumps to grub rescue mode, post the output of ls here.

[embermage1]

Well I have a new question based on this issue.
First here is the output of fdisk -l

root@Kali-Chaos:~# fdisk -l
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6748ECF3-6336-4440-BCFD-1125C2E87896

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1026047 1024000 500M EFI System
/dev/nvme0n1p2 1026048 1288191 262144 128M Microsoft reserved
/dev/nvme0n1p3 1288192 477663577 476375386 227.2G Microsoft basic data
/dev/nvme0n1p4 477665280 479655935 1990656 972M Windows recovery environment
/dev/nvme0n1p5 479655936 500082687 20426752 9.8G Windows recovery environment


Disk /dev/nvme1n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8a8e6123

Device Boot Start End Sectors Size Id Type
/dev/nvme1n1p1 2048 292968447 292966400 139.7G 83 Linux
/dev/nvme1n1p2 292970494 500117503 207147010 98.8G 5 Extended
/dev/nvme1n1p5 292970496 312500223 19529728 9.3G 82 Linux swap / Solaris
/dev/nvme1n1p6 312502272 500117503 187615232 89.5G 83 Linux


Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x48742778

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1000212479 1000210432 477G 7 HPFS/NTFS/exFAT

So as you can see, I have 2 NVME drives, and one SSD drive. NVME0N1 is the one that came with the system and is the one that the Windows 10 install is on (also the EFI partition I used for the grub fix in this thread). NVME1N1 is the second NVME drive and has a KALI install and a Ubuntu install on it. The SDA drive is simply data drive for the three OS systems to use. When installing 2018.2 Kali ran into the grub issue. Researched the forums and found this fix, used it, and for /dev/sda used /dev/nvme0n1. The grub-install line went without any issues, the update-grub however popped multiple warnings and only found the Ubuntu install. Sure enough after the umount and reboot, only Kali and Ubuntu were options to boot into. So I guess my question is how to correct the pointers so as to have all three OS availible.

[embermage1]

And I feel like an idiot, I might have found the fix.