Please uninstall ASUS AI Suite 3, it is known for causing bluescreens.
Invalid memory was referenced, this might be caused by the Windows File System.
Please run below tests, if the hard drive tests comes clean then run the memory test.
If the memory test comes clean, then run driver verifier to find any offending drivers.
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arg1: ffff9c62ffff9c58, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff803af6c3d83, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000002, (reserved)
3: kd> k
Child-SP RetAddr Call Site
ffffd000`25e617c8 fffff803`af7f4285 nt!KeBugCheckEx
ffffd000`25e617d0 fffff803`af6cb17c nt! ?? ::FNODOBFM::`string'+0x11185
ffffd000`25e618c0 fffff803`af7dd9bc nt!MmAccessFault+0x62c
ffffd000`25e61a30 fffff803`af6c3d83 nt!KiPageFault+0x13c
ffffd000`25e61bc8 fffff803`af6c0f22 nt!MiSubsectionUsingExtents+0x3
ffffd000`25e61bd0 fffff803`af6c0a85 nt!MmCheckCachedPageStates+0x3b2
ffffd000`25e61d70 fffff803`afa5d0d7 nt!CcMapAndRead+0xe5
ffffd000`25e61dd0 fffff801`4cf1181c nt!CcMapData+0x97
ffffd000`25e61e40 fffff801`4cf10fc8 NTFS!ReadIndexBuffer+0xdc
ffffd000`25e61ef0 fffff801`4cf109f7 NTFS!FindNextIndexEntry+0x328
ffffd000`25e61fb0 fffff801`4cf0ea5b NTFS!NtfsContinueIndexEnumeration+0xc7
ffffd000`25e62060 fffff801`4cf0dcf3 NTFS!NtfsQueryDirectory+0x60b
ffffd000`25e62450 fffff801`4cf0dc09 NTFS!NtfsCommonDirectoryControl+0xa3
ffffd000`25e62490 fffff801`4c307895 NTFS!NtfsFsdDirectoryControl+0xb9
ffffd000`25e62500 fffff801`4c3052d8 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a5
ffffd000`25e62590 fffff801`4ca5d4fe FLTMGR!FltPerformSynchronousIo+0x308
ffffd000`25e62640 fffff801`4c306d21 Wof!WofPreDirectoryControlCallback+0x24e
ffffd000`25e62700 fffff801`4c3068cc FLTMGR!FltpPerformPreCallbacks+0x2f1
ffffd000`25e62810 fffff801`4c3059fa FLTMGR!FltpPassThroughInternal+0x8c
ffffd000`25e62840 fffff801`4c3057fe FLTMGR!FltpPassThrough+0x16a
ffffd000`25e628a0 fffff803`afa94af6 FLTMGR!FltpDispatch+0x9e
ffffd000`25e62900 fffff803`afa9496f nt!IopSynchronousServiceTail+0x176
ffffd000`25e629d0 fffff803`af7defa3 nt!NtQueryDirectoryFile+0xcf
ffffd000`25e62a90 00007fff`fd615484 nt!KiSystemServiceCopyEnd+0x13
00000013`e47fe548 00000000`00000000 0x00007fff`fd615484
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests
- Short Drive Self Test
- Short generic
- Long generic
If the short generic fails, no need for the long generic.
Do not run SeaTools on an SSD as the results will be invalid.
Disk Check - Windows 7 Help Forums
Run HDTune to
- scan for errors, no quick scan but full scan
- check the health,
It may take some time, but please take the time you need to perform it properly.
Let me know what the results are
- of the error scan,
- make a screenshot of the health of every hard drive and post the screenshots,
- post screenshots with the benchmark of the
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ needs to be run for at least 8 passes
for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero
errors here. Even a single error will indicate RAM failure.
Please make a backup
of your important files and get your rescue media or create one
Please create a restore point.
Please follow this tutorial to run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.