New
#31
It's still pointing at memory corruption, but it's still network related.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa98036c6368, 2, 1, fffff8000378a3bc} Probably caused by : memory_corruption ( nt!MiRemoveLowestPriorityStandbyPage+1bc ) Followup: MachineOwnerNisDrvWFP.sys is the Network Inspection System Driver.Code:Unloaded modules: fffff880`0a133000 fffff880`0a1a4000 spsys.sys fffff880`08224000 fffff880`08245000 NisDrvWFP.sy fffff880`01600000 fffff880`0160e000 crashdmp.sys fffff880`01430000 fffff880`0143a000 dump_storpor fffff880`0400c000 fffff880`042c6000 dump_iaStorA fffff880`042c6000 fffff880`042d9000 dump_dumpfve
Looking at your msinfo32 file to me it looks like e1d62x64.sys is probably causing memory corruption.
Before we attempt to do anything with that can you please run a disk check by following these instructions.
Disk Check
Then please download an run SeaTools for windows, then run by following these instructions.
SeaTools for DOS and Windows - How to Use