PC keeps crashing into BSoD

I've checked the event viewer, this is the one I think it's the crash report:

License Activation (slui.exe) failed with the following error code:

hr=0x8007139F

The event log after that one was:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000f64, 0x0000000000000002, 0x0000000000000000, 0xfffff80310207852).

I've checked activation in update and security and it says my windows is not activated, which is true, but, is it normal to get BSoD for not having an activated version of windows?, I installed it using their MediaToolCreation, should I be looking for another event log? Also, after installing windows 10 I added a hard drive to my PC, and it says the hardware has changed, which again is true, the thing is, could I be getting all this BSoD because I added a hard drive after installing windows 10? (Btw the hard drive isn't formatted in NTFS so windows can detect it but can't read it)

 

Hello and thank you, (yes that is my actual name)
Alright, I will disconnect the second hard drive thank you
I'll download the software too thank you
The machine is a custom build (CPU: Ryzen 5 3600 GPU RX 580 RAM LPX DDR4 3200 PC4-25600 16GB 2x8 MOBO ASUS Prime B550M-A (WI-FI)
It's a new build (Built sept 2020) and yes it has windows 10 pro
It's been working with no issues and then the crashes started (come to think of it, I think they started around the time I connected the secondary drive to the PC)
When the crashes happened I wasn't doing anything that required a lot of resources (watching youtube videos in some occasions and playing League of Legends and didn't have any other app open)
No I haven't made any changes to the RAM PSU or GPU

 

Hello, first of all, no, windows wasn't activated before the crashes started (it has never been)
Second, here's what Who Crashed found

This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0xF64, 0x2, 0x0, 0xFFFFF80310207852)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Thank you

 

And btw, shortly after I sent that reply I run into a crash again, here's what Who Crashed said about it
I think it's important to mention I haven't taken the secondary drive out yet, and a bit before the last crash occurred I formatted the secondary drive, I think that might have triggered it again. Sorry
I have now taken the secondary drive out (finally)

This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0x130, 0x2, 0x1, 0xFFFFF8070EE875AF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time

I think it's important to mention I haven't taken the secondary drive out yet, and a bit before the last crash occurred I formatted the secondary drive, I think that might have triggered it again. Sorry

 

Thank you so so much for all the help, ok, as soon as I save my important files I will wipe and do a fresh install!

From what i've read, if I leave windows unactivated will result in just some minor cosmetic inconveniences, therefore leaving in unactivated won't be an issue, correct?

(Quick edit)
Shortly after posting this reply I got another BSoD, according to Who Crashed caused by

This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8299)
Bugcheck code: 0x1 (0x7FFC5ED0C034, 0x0, 0xFFFF, 0xFFFFF406BF948B80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Even though the error is different, the cause is the same, so looks like ntkrnlmp.exe is going to be giving me some headaches if I don't wipe and install again soon

 

Well if I don't need to buy a key that's always a plus, also, yes, I disconnected the secondary hard drive, I've also been getting a lot of blue screens since I last posted up to a point where they occur like 5 minutes after I start the PC, I've also gotten a new one "memory_management"
I think they happen so often because I'm opening apps right of the bat without giving the pc time to properly start.
Here's the last crash report,

This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x1 (0x7FF94E64C034, 0x0, 0xFFFF, 0xFFFFC18141EA7B80)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

Well, for having an OS running on my computer.

 

But I'm installing it with their MediaToolCreation method.

 

Understood, thank you very much for the assistance provided.