The new dumpfile is not a driver verifier enabled dumpfile, probably the bsod became before Driver Verifier started.
Code:
Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {ffffdff040601700, 8000000001c80121, ffffd00022a073b0, a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4418b )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffdff040601700, Virtual address for the attempted write.
Arg2: 8000000001c80121, PTE contents.
Arg3: ffffd00022a073b0, (reserved)
Arg4: 000000000000000a, (reserved)
Debugging Details:
------------------
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: ACS.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
TRAP_FRAME: ffffd00022a073b0 -- (.trap 0xffffd00022a073b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000042 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802b9c4fd0c rsp=ffffd00022a07540 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0020100000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!MiInsertPageInFreeOrZeroedList+0x21c:
fffff802`b9c4fd0c f0480fc1ae00170000 lock xadd qword ptr [rsi+1700h],rbp ds:00000000`00001700=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff802b9d9928b to fffff802b9d46770
STACK_TEXT:
ffffd000`22a071e8 fffff802`b9d9928b : 00000000`000000be ffffdff0`40601700 80000000`01c80121 ffffd000`22a073b0 : nt!KeBugCheckEx
ffffd000`22a071f0 fffff802`b9c3d738 : fffffa80`0073e3c0 ffffd000`22a07340 ffffdff0`40600000 fffffd80`00001d58 : nt! ?? ::FNODOBFM::`string'+0x4418b
ffffd000`22a07240 fffff802`b9d4f9bc : 00000000`00000001 fffffa80`006fbe80 00000000`00000042 00000000`00000000 : nt!MmAccessFault+0xbe8
ffffd000`22a073b0 fffff802`b9c4fd0c : fffffd80`000016f8 fffff802`b9f01280 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
ffffd000`22a07540 fffff802`b9ccbc37 : 00000000`00026a14 00000000`00000042 00000000`00000070 ffffe001`a5492b40 : nt!MiInsertPageInFreeOrZeroedList+0x21c
ffffd000`22a07610 fffff802`b9c65a20 : fffffd80`00003800 ffffd001`00000000 00000000`00000002 00000000`000000c2 : nt!MiInsertLargePageInFreeOrZeroList+0xd7
ffffd000`22a07660 fffff802`b9c655da : 00000000`00000002 fffff802`00000070 00000000`00000000 fffff802`b9cd39f2 : nt!MiGetFreeOrZeroPage+0x370
ffffd000`22a076d0 fffff802`b9c638f3 : fffff802`b9f00bc0 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MiGetPage+0x7a
ffffd000`22a07740 fffff802`b9c3cfe1 : 00000000`00000002 00000000`adbf9000 ffffd000`22a07a00 fffff680`0056dfc8 : nt!MiResolveDemandZeroFault+0x323
ffffd000`22a07890 fffff802`b9d4f9bc : ffffe001`a5b7f080 ffffe001`a5d79080 00000000`13524e78 00000000`00000020 : nt!MmAccessFault+0x491
ffffd000`22a07a00 00007fff`d67454bf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000000`1ba0f790 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`d67454bf
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4418b
fffff802`b9d9928b cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4418b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 568b1c58
IMAGE_VERSION: 10.0.10586.63
BUCKET_ID_FUNC_OFFSET: 4418b
FAILURE_BUCKET_ID: 0xBE_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0xBE_nt!_??_::FNODOBFM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xbe_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {463ab379-ba7d-e86a-84c4-449f00e9fb43}
Followup: MachineOwner
---------
Usual causes: Device driver, Memory
Your other dumpfiles also mentioned memory corruption
Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+"to stress test the RAM.
How to run "Memtest" - RAM -Test with Memtest86+ - Windows 7 Help Forums
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory DiagnosticTool
You can stop the test even if a single error is found during the test. Otherwise continue the test for 7-10 passes and post a screenshot with next reply. 7 passes is the recommended bare minimum but more passes will give better result.
These drivers predates windows 10, please update from supportpage mobo
http://www.asrock.com/mb/Intel/Z170%...oad&os=Win1064
Also update all your other current drivers to the latest versions on this page.
e1d65x64 Thu Jun 18 18:37:56 2015
Driver Description: Intel(R) Gigabit Adapter NDIS 6.x driver
Driver Update Site: http://downloadcenter.intel.com
iaStorA Mon Jul 27 11:26:48 2015
Driver Description: Intel RST (Rapid Storage Technology) driver
Driver Update Site: http://downloadcenter.intel.com/Default.aspx
See if there are newer drivers avaliable
LGBusEnum Fri Apr 24 23:21:00 2015
LGJoyXlCore Fri Apr 24 23:20:57 2015
Both logitech devices
lgcoretemp Tue Jun 09 18:52:10 2015
Coretemp