New
#121
all indications I am getting are hard drive/file system/memory.
A code 7E is typically a storage related issue. NTFS is the file system Windows uses.Code:Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80106082013, ffffd000731b1528, ffffd000731b0d40} Probably caused by : NTFS.sys ( NTFS!NtfsRemoveHashEntry+8b ) Followup: MachineOwner
Code:BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000025, Arg2: 0000000000000092 Arg3: 0000000000000005 Arg4: ffffc001e41e2370Code:PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000002, A list entry was corrupt Arg2: 0000000000098613, entry in list being removed Arg3: 000000000021efff, highest physical page number Arg4: 0000000000000001, reference count of entry being removedNotice the NTFS and FLTMGR entries above. Again NTFS is the Windows File System and FLTMGR is the Microsoft File system filter.Code:# Child-SP RetAddr Call Site 00 ffffd000`24c79dd8 fffff800`d59fa618 nt!KeBugCheckEx 01 ffffd000`24c79de0 fffff800`d58c69b1 nt! ?? ::FNODOBFM::`string'+0x17818 02 ffffd000`24c79ea0 fffff800`d5934ce3 nt!MiFlushSectionInternal+0x401 03 ffffd000`24c7a0d0 fffff800`d593228f nt!MmFlushSection+0xc7 04 ffffd000`24c7a180 fffff800`d58a49f2 nt!CcFlushCachePriv+0x55f 05 ffffd000`24c7a290 fffff801`13edb315 nt!CcFlushCache+0x16 06 ffffd000`24c7a2d0 fffff801`13edb80e NTFS!NtfsFlushUserStream+0xb9 07 ffffd000`24c7a350 fffff801`13e179a5 NTFS!NtfsFlushVolume+0x44e 08 ffffd000`24c7a4d0 fffff801`13e14c3c NTFS!NtfsVolumeDasdIo+0x1f5 09 ffffd000`24c7a580 fffff801`13e128b2 NTFS!NtfsCommonRead+0x21cc 0a ffffd000`24c7a730 fffff801`131f7895 NTFS!NtfsFsdRead+0x1f2 0b ffffd000`24c7a7e0 fffff801`131f5816 FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a5 0c ffffd000`24c7a870 fffff800`d5c94af6 FLTMGR!FltpDispatch+0xb6 0d ffffd000`24c7a8d0 fffff800`d5c94642 nt!IopSynchronousServiceTail+0x176 0e ffffd000`24c7a9a0 fffff800`d59deca3 nt!NtReadFile+0x672 0f ffffd000`24c7aa90 00007ff9`ab394e14 nt!KiSystemServiceCopyEnd+0x13 10 00000087`7bb7d538 00000000`00000000 0x00007ff9`ab394e14
We need you to 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.Code:BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000023, Arg2: 0000000000000007 Arg3: 0000000000000002 Arg4: ffffc001904db1f0