BSOD on Startup, Reboot loops

[tmfwy]

I'll post some of the minidumps that were analzyed by WhoCrashed

Spoiler

On Sat 9/12/2017 7:20:13 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x11AD05)
Bugcheck code: 0xD1 (0x1C9D0, 0x2, 0x1, 0xFFFFF801D79FAD05)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 388.59
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 388.59
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 388.59 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


On Sat 9/12/2017 3:18:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\120917-6562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802348967F4, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/12/2017 2:39:10 PM your computer crashed
crash dump file: C:\Windows\Minidump\120917-6921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x1A (0x61941, 0x1F5AC8ED000, 0xD, 0xFFFFD20D579CFA00)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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 9/12/2017 2:39:10 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61941, 0x1F5AC8ED000, 0xD, 0xFFFFD20D579CFA00)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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 9/12/2017 11:45:28 AM your computer crashed
crash dump file: C:\Windows\Minidump\120917-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x139 (0x3, 0xFFFFA68F8A2C7330, 0xFFFFA68F8A2C7288, 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 9/12/2017 2:30:12 AM your computer crashed
crash dump file: C:\Windows\Minidump\120917-8250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x67F4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803214067F4, 0xFFFFC50BC7F87678, 0xFFFFC50BC7F86EC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Anyone able to provide additional suggestions? Most of the BSODs happen when I try to either: 1) Launch a game, 2) Install a program / driver, 3) Change some settings on my computer. I don't crash when I watch YouTube or surf the internet.

I suspect its either my motherboard / CPU but I don't wanna take apart everything until I am able to diagnose the root cause of the problem. Its quite a pain to put everything back together

Should I re-install Windows again? I've already done it 4 times already though. It wasn't easy to finish installing all my drivers without my computer crashing mid-installation.

This is most probably a motherboard issue

Had a similar example where a mobo was working fine with windows 10. Come time to reset. TOtally don't want to co-operate
Changed rams cpu psu ssd hdd, still have issues loading windows

Firstly. check to see if PSU faulty by taking out graphic card and using integrated graphic.
If same problem, then you need to troubleshoot motherboard isssue..... with another motherboard.