Does it give a file name? if you can identify the driver name we might be able to fix it in safe mode by updating driver or removing buggy one?
If it is blaming ntoskrnl then that is windows and not going to be actual cause.
On another PC, download the
Windows 10 media creation tool and use it to make a win 10 installer on USB << its a handy boot drive if nothing else
change boot order so USB is first, hdd second
boot from installer, on 2nd screen after languages, choose repair this PC, not install
choose troubleshoot
choose advanced
choose start up options << this menu may not be here so try next step instead
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
PC will restart and load safe mode
if you can get to safe mode, update driver if we have a name for buggy one
have a look in device manager and see if any devices showing as unknown
If we didn't identify driver name before, go to c/windows and find your memory. dmp file.
Make a copy onto desktop and then copy it off desktop onto USB
unless its massive (it can be several gb so if it is, don't worry as its too big to upload), it might allow us to discover driver name causing this
If start up options menu wasn't available, you can try start up repair - this will scan PC and maybe fix this - will ask for logon info