Hello Andrew89898 and welcome to the Forums,
Your first rar is incomplete, please rerun the SF Diagnostic Tool again and make sure that MSINFO, DXDIAG and Host.txt are included this time.
More info BSoD Posting Instructions.
----------
Your initial dump file points to this;
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80096d3028, be000000, 100110a}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
Usual cause: Fatal hardware error.
More info Bug check 0x124_0.
----------
If we dig deeper in the dump file we see that the following driver is the cause of your BSoD;
Code:
2: kd> dps fffff880063b0000 fffff880063b6000
fffff880`063b44e0 fffffa80`0a086a90
fffff880`063b44e8 fffffa80`0a016800
fffff880`063b44f0 fffff880`063b4550
fffff880`063b44f8 fffff880`04f1fe92Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
igdkmd64+0xbae92
Driver reference table: igdkmd64.sys.
----------
Since I do not have the MSINFO and DXDiag files, I do not have all the information required to pinpoint the integrated chipset, so I will have to advice you to update it using the Driver Update Utility - Graphics.
After doing this, please completely remove the old driver by running a scan with Driver Sweeper.
----------
Now when we look at the dump files created after running Driver Verifier, we see this;
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {0, 0, 0, 0}
Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+109 )
Followup: MachineOwner
---------
It points to tcpipreg.sys, which is a Windows driver that shouldn't fail on it's own.
If we look at the stack, we see this;
Code:
STACK_TEXT:
fffff880`035e7488 fffff800`0356a4ec : 00000000`000000c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`035e7490 fffff800`0356af2b : 00000000`00000293 fffff800`0310784c 00000000`00000003 fffff800`03107a90 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`035e74d0 fffff800`0357bba8 : 00000000`6547654c 00000000`00000080 00000000`00000010 fffff880`0000007f : nt!ExAllocatePoolSanityChecks+0xcb
fffff880`035e7510 fffff800`0357be17 : 00000000`00000000 00000000`00000000 fffff980`6547654c fffff980`1f03efec : nt!VeAllocatePoolWithTagPriority+0x88
fffff880`035e7580 fffff880`0673d5a1 : 00000000`00000000 00000000`00000000 fffff980`1f03efd0 fffff800`0357713c : nt!VerifierExAllocatePoolWithTagPriority+0x17
fffff880`035e75c0 fffff880`0673c7bb : fffff880`06743c20 fffff980`1f03efd0 fffff980`1b8aaf90 fffff980`1f03efd0 : tcpipreg!InterfaceAddressRegKeyChangeHandler+0x109
fffff880`035e76f0 fffff880`0673ba59 : fffff880`00000001 00000000`00000103 fffff980`1b8aaf70 00000000`00000001 : tcpipreg!TcpipRegQueryAndUpdateKeyValue+0x363
fffff880`035e7780 fffff880`01991754 : fffff880`06741a60 00000000`00000004 00000000`00000000 00000000`00010202 : tcpipreg!TcpipRegStartRegistryKeyNotification+0xbd
fffff880`035e77d0 fffff880`0673c293 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`06747073 : NETIO!RtlInvokeStartRoutines+0x34
fffff880`035e7810 fffff800`034c7787 : 00000000`00000006 fffffa80`0bfc87b0 fffffa80`0bfba000 00000000`00000001 : tcpipreg!DriverEntry+0x257
fffff880`035e7860 fffff800`034c7b85 : 00000000`00000010 00000000`00000000 00000000`00000010 00000000`00010206 : nt!IopLoadDriver+0xa07
fffff880`035e7b30 fffff800`030e6261 : fffff880`00000000 ffffffff`800006a4 fffff800`034c7b30 fffffa80`06d38660 : nt!IopLoadUnloadDriver+0x55
fffff880`035e7b70 fffff800`0337abae : 00000000`00000000 fffffa80`06d38660 00000000`00000080 fffffa80`06caf300 : nt!ExpWorkerThread+0x111
fffff880`035e7c00 fffff800`030cd8c6 : fffff880`03365180 fffffa80`06d38660 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035e7c40 00000000`00000000 : fffff880`035e8000 fffff880`035e2000 fffff880`035e6ef0 00000000`00000000 : nt!KxStartSystemThread+0x16
It again points to tcpipreg.sys, but this time also to NETIO.sys, which is yet another Windows driver.
----------
Let's look at the other dump file you got from Driver Verifier;
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80096b7028, be000000, 100110a}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
Hmm, another hardware error..
Code:
0: kd> dps fffff80000b97000 fffff80000b9d000
fffff800`00b9bc00 fffff800`00b9bed0
fffff800`00b9bc08 00000000`00000004
fffff800`00b9bc10 00000000`00000000
fffff800`00b9bc18 fffffa80`07349900
fffff800`00b9bc20 fffff880`04dc8f70Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
igdkmd64+0x138f70
Code:
fffff800`00b9c840 00000000`00000000
fffff800`00b9c848 00000000`0000000f
fffff800`00b9c850 00000000`00000000
fffff800`00b9c858 ffffd89e`375aa5af
fffff800`00b9c860 fffff880`048e5dc0Unable to load image iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
iusb3xhc+0x6adc0
Driver reference table: iusb3xhc.sys.
Two failing drives this time; the integrated graphics chip driver, and the USB port driver.
----------
I would advice you to update the USB driver from here. After doing this please completely remove the old driver by running a scan with Driver Sweeper.
----------
After updating both drivers, please upload the requested files and follow ascomputers his advice on your RAM.
Good luck and keep us posted,
Nommy