BSOD ATTEMPTED_WRITE_TO_READONLY_MEMORY(netio.sys) and IRQL

volie, this time it is listing the Realtek Lan Driver but still blaming it on Memory corruption

Code:

Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff80126c02818, 2277e4121, fffff803ed243570, a}
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------

Just as a suggestion, could you remove the Intel card since you are not using it anyway and see if that makes a difference?

Your last 2 dumps

Code:

BugCheck BE, {fffff800f6f823b8, 2276d1121, fffff8003e242790, a}
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
Probably caused by : NETIO.SYS ( NETIO!NetioCompleteNetBufferAndNetBufferListChain+9 )
Followup: MachineOwner

Code:

BugCheck BE, {fffff80064f52818, 2277e4121, fffff800af9ef570, a}
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
Probably caused by : memory_corruption
Followup: memory_corruption

It is still your network. The NTIO is the Network I/O Manager and the rt640x64.sys is your Realtek 8101E/8168/8169 NDIS 6.40 64-bit Driver.

When you removed the Intel Card, did you uninstall the driver? If not, please do that. Also, are you using the Windows provided driver or the one from Gigabyte?

Code:

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver...tPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f592ec14700, Reserved
Arg2: 0000000000000000, Reserved
Arg3: ee3274faf73cc52d, Failure type dependent information
Arg4: 0000000000000101, 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

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump
PG_MISMATCH:  10
MEMORY_CORRUPTOR:  ONE_BIT

Code:

Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffab005332672, 2, 0, fffff8016074c812}
Probably caused by : memory_corruption ( nt!MiDecrementAndInsertStandbyPages+d2 )
Followup: MachineOwner

Make sure your SSD Firmware is up to date and see if they have a utility to test it's health. Please run Seatools for DOS on your Mechanical Hard Drive http://www.sevenforums.com/tutorials...s-how-use.html

Are you running the X64 version of Chrome? If so, please uninstall it and install the X86 version.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.

When you have run the test, please let me know the results and then upload the BSOD Posting instructions BSOD - Posting Instructions - Windows 10 Forums. Upload them here. This will tell you how Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.

If you are overclocking, please set everything back to default levels. Please uninstall any Gigabyte utilities. Please download and install CPUz http://www.cpuid.com/softwares/cpu-z.html and post screenshots (https://www.tenforums.com/tutorials/1...en-forums.html) of the CPU, Mainboard, Memory and SPD tabs. On the SPD tabs you can select each Dimm Slot from a dropdown in the upper left of the SPD tab. Just provide screenshots of the tabs populated with Memory.

Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

Please go to your Motherboard's web site and see if you can install the Realtek LAN Driver for Windows 10 V.10.001.0505.2015

Also, Please make sure all Windows Updates are current and installed.