BSOD after new hardware

The $100 dollars was pretty much just for him to tell me my old mechanical hard drive was bad. My windows still isn't activated. Could this be an issue?

I took it back to the guy this morning because he said he'd take another look at it, so i wont be able to run temperature test atm. I'll probably try to get it back from him today. I checked the device manager and it seemed that all the drivers were up to date (no warning symbols), but I did not try to install all new ones. I don't know if this makes overheating more suspect, but the first time it blue screened this time around it was about 10 minutes into playing AOE 2, then the next times I opened it the computer crashed immediately.

I got back my computer again and the guy confirmed all of the hardware seems fine, so it seems like a software problem. The computer only crashes when I have Steam open.

Which drivers do I need to install? I already did the graphics card one, and now I'm on to the motherboard drivers, but I don't know which ones I need. Also are there drivers for the ram, ssd, and processor?

Also I have CAM (hardware monitoring software) installed and my cpu was around 45 C and GPU 35 C. The computer crashed while CAM and steam were the only programs open.

So I've updated the drivers and I downloaded WhoCrashed. After analyzing the crash logs it said a third party could be to blame, specifically mentioning nvidia, so I tried updating the nvidia graphics drivers. The installer continues to fail, I've tried it through Geforce Experience, manually, and through the device manager. After trying a few different fixes to no avail I did a clean install of windows 10 to see if that could be the issue. After that the drivers still fail to install, so I'm really at a loss of what to do.

So I finally got the graphics card driver updated as well. Computer still crashed. Here are some crash logs:

On Sat 10/21/2017 12:27:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\102117-3484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x139 (0x2, 0xFFFFAA0C98B4FA20, 0xFFFFAA0C98B4F978, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 10/21/2017 12:27:12 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x2D475)
Bugcheck code: 0x139 (0x2, 0xFFFFAA0C98B4FA20, 0xFFFFAA0C98B4F978, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 10/21/2017 12:26:21 PM your computer crashed
crash dump file: C:\Windows\Minidump\102117-4312-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xEFF19)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80241A0FF19, 0x1, 0x64)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 10/21/2017 12:24:54 PM your computer crashed
crash dump file: C:\Windows\Minidump\102117-6828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x44 (0xFFFFBF0973FE3010, 0x120C, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 a driver has tried to requested an IRP be completed that is already complete.
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.



On Sat 10/21/2017 1:00:18 AM your computer crashed
crash dump file: C:\Windows\Minidump\102117-4765-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x827E2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFFF180BE227E2, 0xFFFFB2898B936E20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

MERGED QUESTION
Question from skylarts : "BSOD. Seems I've tried everything"











I cleared cmos ( that resets the settings right?) ,updated the bios to the newest version, but it's still crashing on the bios screen. It will show checking disk, trying to repair, or just a loading ring, but it always just crashes. What bug checks are you wanting me to look at? The stop codes on the blue screen?

I'm probably just going to reinstall windows again because that always seems to work.

Update: Just kidding now I can't even boot the windows installer. It shows window icon like it's about to start then black screen and restarts. It seems I'm going backwards.

MERGED QUESTION
Question from skylarts : "Windows 10 wont launch, Loops bios screen"

I've been having a bunch of problems with my computer after I made some upgrades if you want to see all my issues they are here http://www.tomshardware.com/answers/id-3550606/bsod.html This thread kinda died so I'm looking elsewhere for help.

Right now my issue is that when I start my computer the bios screen pops up and I can get into settings fine, but it will crash before windows even starts to load. I can't even get into the windows troubleshooting screen. F8 doesn't work, powering on and off 3+ times doesn't work.

I've been trying to reinstall windows with a usb installation, but even booting though the usb the computer just restarts after bios.

I've updated the bios to the newest version, cleared the cmos. I've done just about everything I can think of except buying an actual windows 10 installation disk. If anyone has something I haven't tried please help me out as I am not the most tech savvy person.

The computer is booting, going to the bios screen and then it rotates between just going black and restarting or it shows a blue screen and restarts. All of the stop errors look like it’s a driver issue, but I can’t get into the computer anyway to uninstall/install drivers. What am I supposed to do??

Update: I had tried running my old windows 7 installation disk before and it didn't work, but this time it did. However it crashed right after the installation before the set up. Reinstalled it and the same thing.

Now I'm trying to run my windows 10 installation usb to possibly fix it, but it's failing. On the plus side the windows troubleshooter is finally popping up so I can do some stuff, but I just don't know what to do.