Critical Structure Corruption

Hello my desktop computer has been crashing a lot this past week.  In this past week twice whie booting up I have recieved the error Kernel Security Check Fallure and I have check The Driver Verifier Manager and also ran sfc scannow with no troubles.  Just today I was watching an online video for my College and the computer crashed giving the error message Critical Structure Corruption Error.  I checked the memory with the Windows Memory Diagnostice tool and everything checks out.  Any help you guys can do would be great since I like to use this computer for school work and crashes can really hurt if I lose work.

-Thanks

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 

Sorry about the confusion, I had trouble uploading the files last time.  I believe I got them this time, sorry about the delay

-Kylor W. Jones

Your UEFI/BIOS (version F20) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

C: drive only has about 6% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

These devices are disabled.  Did you deliberately disable them?  If so, why did you disable them?

 

Intel® Ethernet Connection (2) I219-V    PCI\VEN_8086&DEV_15B8&SUBSYS_E0001458&REV_31\3&11583659&0&FE    This device is disabled.
Killer e2400 Gigabit Ethernet Controller    PCI\VEN_1969&DEV_E0A1&SUBSYS_E0001458&REV_10\4&325A602&0&00E2    This device is disabled.

Please re-enable them and update their drivers.

The drivers load into memory before the device is disabled, and they remain in memory despite being disabled.

Feel free to disable them again AFTER they have been updated.

Only 2 entries in the WER section of the MSINFO32 report.

Have you recently run a disk cleaning utility (such as CCleaner)?  If so, please do not use it again until we are finished troubleshooting.

Have you tweaked any settings to stop the system from recording these events?

Please uninstall Gigabyte EasySaver and EasyTune (if installed)

They are known to cause BSOD's on some Windows systems.

If this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Wed Jan 18 11:34:40.083 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011817-11593-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:19:01.783
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 109, {a39ffde3131a97af, b3b70a69659a8625, fffff808d68c3e30, 1}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a39ffde3131a97af, Reserved
Arg2: b3b70a69659a8625, Reserved
Arg3: fffff808d68c3e30, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    101 : General pool corruption
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  F20
  BIOS Release Date             11/04/2016
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z170X-Gaming 7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 17 19:01:05.101 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011717-11578-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:2 days 7:43:15.128
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 109, {a39ffbdf1ebf15b5, b3b70865713f69df, fffff80099307eec, 1}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a39ffbdf1ebf15b5, Reserved
Arg2: b3b70865713f69df, Reserved
Arg3: fffff80099307eec, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    101 : General pool corruption
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  F20
  BIOS Release Date             11/04/2016
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z170X-Gaming 7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jan 14 11:17:02.829 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\011417-20609-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:1 days 0:05:17.634
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 139, {3, ffff8b0078fc7290, ffff8b0078fc71e8, 0}
BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff8b0078fc7290, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff8b0078fc71e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  F20
  BIOS Release Date             11/04/2016
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z170X-Gaming 7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Wed Jan 18 11:34:40.083 2017 (UTC - 5:00)**************************
regi.sys                    Mon Apr 16 11:19:10 2007 (462393EE)
SiLib.sys                   Thu Jul 15 18:08:26 2010 (4C3F86DA)
SiUSBXp.sys                 Thu Jul 15 18:27:13 2010 (4C3F8B41)
rikvm_58664B3D.sys          Fri Oct 29 06:52:09 2010 (4CCAA759)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
npf.sys                     Thu Feb 28 20:31:24 2013 (513004EC)
AppleCharger.sys            Sun Oct 27 21:59:21 2013 (526DC4F9)
file_tracker.sys            Thu Sep  4 08:49:39 2014 (54085FE3)
fltsrv.sys                  Tue Nov 11 07:01:53 2014 (5461FAB1)
snapman.sys                 Wed Nov 12 05:54:05 2014 (54633C4D)
iocbios2.sys                Thu May 28 16:42:10 2015 (55677DA2)
asstahci64.sys              Tue Jun 16 23:36:23 2015 (5580EB37)
bwcW8x64.sys                Fri Jun 19 16:04:49 2015 (558475E1)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
tib.sys                     Fri Jul 17 04:27:03 2015 (55A8BC57)
ICCWDT.sys                  Sun Sep 20 03:59:19 2015 (55FE6757)
iaStorA.sys                 Wed Nov  4 05:27:49 2015 (5639DDA5)
cthda.sys                   Mon Nov  9 01:22:37 2015 (56403BAD)
athw8x.sys                  Thu Jan 28 04:52:54 2016 (56A9E4F6)
ccSetx64.sys                Thu May  5 18:33:33 2016 (572BCA3D)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
Ironx64.SYS                 Fri Sep  2 17:44:25 2016 (57C9F2B9)
SRTSPX64.SYS                Fri Sep  2 21:56:42 2016 (57CA2DDA)
SYMEVENT64x86.SYS           Thu Sep  8 15:47:29 2016 (57D1C051)
SRTSP64.SYS                 Tue Sep 13 21:14:58 2016 (57D8A492)
SYMNETS.SYS                 Wed Sep 14 22:43:10 2016 (57DA0ABE)
EraserUtilRebootDrv.sys     Fri Sep 16 22:16:39 2016 (57DCA787)
eeCtrl64.sys                Fri Sep 16 22:16:39 2016 (57DCA787)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
SYMEFASI64.SYS              Wed Oct 12 14:18:04 2016 (57FE7E5C)
BHDrvx64.sys                Fri Nov  4 05:39:20 2016 (581C5748)
nvvad64v.sys                Fri Nov 25 10:43:56 2016 (58385C3C)
IDSvia64.sys                Fri Dec  2 12:58:53 2016 (5841B65D)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan 17 19:01:05.101 2017 (UTC - 5:00)**************************
gdrv.sys                    Thu Jul  4 00:27:55 2013 (51D4F9CB)

Hey about the WER section of the MSINFO32 report I do not think I changed this is this a sign of a virus and what are the instructions to turn it on again,

-Once again thanks for your help.

If this is the result of a virus infection, please post in the Am I Infected forums for assistance in resolving this:  http://www.bleepingcomputer.com/forums/f/103/am-i-infected-what-do-i-do/