Constant BSOD with error Codes

[yeeolhuntsman]

Fairly Fresh build.
-Windows 10 Pro
-Windows Version 1511
-Motherboard MSI Gaming M7
-Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
-16.0 GB RAM
-64-bit Operating System
-NVidia 1060 3gb Graphics Card
-2 Hard Drives, 1 SSD
1 HDD- 500gb Seagate
1 HDD- WD Blue Edition 1TB
1 SSD- System is stored here, Kingston 120gb SSDnow V+200 Series (SVP200S3120G) had this for a Year and a half or so.

All my Drivers are Up to date, just updated my BIOS, and I've still been getting all these Bluescreens, Sometimes One after another, sometimes i have a little cooldown before the next one happens.

Each time a BSOD happens i get a different code, and i've been through several. I've tried many different fixes Like:
-Reinstalling windows
-Updating all my Drivers
-Testing 1 ram stick at a time
-Memory Test
-Used windows check disk tool (It sometimes even crashed during this)
-many others i can't quite name

I'm lost on what is wrong, i'm at the point of thinking this SSD is at its final stage and is corrupting System Data files.

a couple of the Blue screen errors i received are:
-System_Service_Exception
-DPC_Watchdog_Violation
-Clock_Watchdog_Timeout
-Fltmgr.sys
-IRQL_Not_Less_or_Equal
-Driver_Overran_Stack_Buffer
-Driver_IRQL_Not_Less_Or_Equal (ClassPnp.SYS)

Many others i didn't take note of but these were the ones that were happening most commonly, Watchdog ones were more recent.

The Report:


System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-L0UGKPI
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: MS-7A57, MSI, Z270 GAMING M7 (MS-7A57)
CPU: GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17131294720 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 11/10/2017 11:01:42 PM your computer crashed
crash dump file: C:\Windows\Minidump\111017-4953-02.dmp
This was probably caused by the following module: cng.sys (cng+0xC97A)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80152EEC97A, 0xFFFFD00021867E68, 0xFFFFD00021867680)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 Fri 11/10/2017 11:01:42 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cng.sys (cng!EntropyProvideData+0x33B)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80152EEC97A, 0xFFFFD00021867E68, 0xFFFFD00021867680)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 Fri 11/10/2017 10:59:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\111017-4546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF802EE2442E6, 0xFFFFD00020AD6680, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 11/10/2017 10:56:53 PM your computer crashed
crash dump file: C:\Windows\Minidump\111017-5125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Fri 11/10/2017 10:55:31 PM your computer crashed
crash dump file: C:\Windows\Minidump\111017-5234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD001F8FE8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

Using
-WhoCrashed 5.54

It gave me details of a few of the crashes.

Please... i need help ASAP Before i go completely Insane... @_@

 

[Paul NZ]

Upload them to onedrive or a file sharing site then post the link

 

[yeeolhuntsman]

Upload them to onedrive or a file sharing site then post the link

Upload what to a file sharing site? And if its the bsod files. Where would I find them? As in folder location.
~Huntsman

 

[Paul NZ]

c;/windows/minidump folder the dmp files

 

[yeeolhuntsman]

https://1drv.ms/f/s!Av4bKprW9gLPgjZK_--Z6XY7Si3T
Crash Dump Files
Seems like you'll have to copy and paste the link into the URL bar.

Tell me if i have to change permissions or not... pretty sure you can just download and look through it.

 

[Paul NZ]

iaStorA.sys your sata drivers is causing one crash. esrv_svc.exe is causing a crash an Intel program, Intel driver update utility

tiworker.exe is crashing. Directx is crashing. Searchui.exe i crashing. Ntfs.sys is crashing. explorer.exe is crashing.

cng.sys is crashing. storport.sys is crashing.

nvcontainer.exe is crashing - Your video drivers. agent.exe is crashing. This may belong to Avira

intelppm.sys is crashing

I would update the sata drivers, uninstall or update that Intel driver utility, uninstall the Nvidia drivers, use DDU, reinstall them

If Avira is installed, uninstall it then use their removal tool to remove the rest of it

This file ADP80XX.SYS belongs to sata controller drivers. See if there are updated drivers for it.

What are the hdds connected to ? The sata ports on the mobo, or did you install some kind of sata card?

lsi_sas.sys is a sata driver I think. Were these drivers on the MSI site? megasas.sys is a raid driver.

Are you using the hdds in RAID?

I would say one or more of these drivers shouldnt even be there. One of them will be crashing your sata drivers and maybe ntfs.sys

percsas2i.sys is also a raid driver

I dont know why there are so many sata/ raid drivers on the hdd.

Was this a clean install of WIn10 or did you upgrade from Windows 7 or 8 or something?

If I were you, I would do a clean install of Windows 10 1709. Get the mediacreation tool get the ISO.

Then use rufus or burn the ISO to dvd. Wipe the lot.

Reinstall Windows

Is the latest BIOS on this?

And since you've got more than 1 hdd, did you unplug all but 1 hdd when you installed windows?

Because if you didnt files can be installed to the other hdds. If the other hdds are connected when you installed windows

I would start all over again. Whatever hdd you want to install windows on, leave it connected

Unplug the other 2. Reinstall windows. When the install has finished reconnect the other 2 hdds

 

[yeeolhuntsman]

Thank you @Paul NZ I will attempt this this afternoon, i will update if it worked or not. I just remember that even during windows installation i had crash errors... even though i formatted the SSD. I had to attempt several times to finally get windows to install.

 

[Paul NZ]

Is the firmware on the ssd up to date?

Where did windows come from ?? a DVD? ISO?

 

[yeeolhuntsman]

Came from an ISO, Which i installed onto my Bootable USB using the Windows 10 installation media.

 

[Paul NZ]

I would get the mediacreation tool get Windows 10 1709.. Use rufus http://rufus.akeo.ie/

Put a flash drive in a port.

If your mobo has a UEFI BIOS select GPT in rufus before you add the ISO. If it doesnt select MBR before you add the ISO

Wait for it to finish reboot change the bootdisk to the flash drive in the BIOS (enable UEFI if it's got an UEFI BIOS). Delete all the partitions. Install Windows

 

[yeeolhuntsman]

Even now that i've reinstalled windows, disconnected all drives except my ssd. Kept only 1 memory stick. I've even tried installing windows onto my 1tb hdd but yet im still getting constant blue screens. Same error codes. I also formatted the ssd and hdd before the installation. (Plugged in different times one time the hdd it failed. Then I unplugged the hdd and plugged in the ssd. Still getting errors.)

 

[yeeolhuntsman]

The errors happen most during updates.

 

[yeeolhuntsman]

Newer error:
Kernal_Security_Check_Failure

Sometimes it even blue screen when I do nothing after boot I just leave it idle on the login page and it bluescreens me.