Multiple Bsods in win10

Yes. But by that I mean just the Dism /Online /Cleanup-Image /RestoreHealth, the installation on a USB, the mounted ISO file and they all work for me. If you have been having this problem since you built the computer, I would suspect a hardware issue.
Please make sure your SSD has the latest Firmware, please go into bios and tell me the CPU Temp, Motherboard temp, the +12V, +5V and +3.3V temps. Also, Do you have a spare hard drive we could use for testing? We need one that we can remove everything on it. And please upload a new DM Log collector so I can try to see if anything has changed.

I updated my ssd firmware. My 3.3v is 3.284 my 5v is 5.070 and my 12v is 12.096
my cup temp is around 55-57*c and my system temp is 43*c and I don't have a spare internal hd

Loiez, sorry for the delay. This is what I found in the last 3 dumps.

Code:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000004, The thread's stack pointer was outside the legal stack
 extents for the thread.
Arg2: ffffd001456b7540, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd001456b7498, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:

Code:

ffffd000`22c3bfa8  fffff800`bf61792cUnable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x21792c

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd001c414c5c0, ffffd001c414c518, 0}
Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::NotificationDpc+de )
Followup: MachineOwner
High Definition Audio Bus Driver

Code:

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ffc5d7e3aaa, Address of system call function or worker routine
Arg2: 0000000000000001, Thread->ApcStateIndex
Arg3: 0000000000000000, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffd00025e67b80, Call type (0 - system call, 1 - worker routine)
Debugging Details:

Code:

ffffd000`284a97a0  fffff801`eb7c1308 NETIO!handleTableLock
ffffd000`284a97a8  fffff801`f0f1b002Unable to load image appexDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for appexDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for appexDrv.sys
 appexDrv+0xb002

Code:

ffffd000`284a8558  fffff801`ee50d97fUnable to load image athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 athrx+0x1ed97f

I think you can tell that the dumps are all over the place. In looking through the dumps It seems like most of the errors (not necessarily the ones mentioned above) Seemed to be either Network or hard drive related.

The athrx.sys is the Atheros network adapter driver. If that is a wireless driver, can you try running without it installed for a while please.

Please go to Device Manager and see if you have any listings with a yellow triangle or any other indications they are not working.

Make sure you have updated drivers from your Motherboard"s web site http://www.gigabyte.com/products/pro...px?pid=4727#dl

I believe you have said you updated your SSD to the most current software.

Please run Seatools for DOS on your Mechanical Hard drive.

The CPU temps you quoted seem entirely too high for your CPU. What CPU Cooler do you have?

Try it that way, but it may end up having to remove the card. If it is a driver issue, it will still load the drivers when the card is detected on startup. But, try it that way and see if it helps.

Sure, upload a new DM log in a new post. With Seatools, make sure your BIOS Sata Controller is set to IDE. Seatools can't detect the drives set in AHCI mode. You will have to boot into bios and change to IDE and boot straight into Seatools. When the test is completed, go straight back into BIOS and change back to AHCI mode, then boot into the OS.