BSOD : Driver corrupted pool netio.sys

Question

Keep geting these BSOD Lops I have triad all th dell diagnostics, AVG scans, AVG tune-up, Malware, Hitman, Driver doctor, searched forums and nothing seems to stop it. It seems dell support is harder to get hold of even though i have the full warranty and paid for the extended home warranty, Seems to be no place anymore to file a claim.   computer name: BILLT-LAPTOPwindows version: Windows 8.1 , 6.2, build: 9200windows dir: C:\WINDOWSHardware: Inspiron 7720, Dell Inc. , CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz Intel586, level: 68 logical processors, active mask: 255RAM: 8443346944 totalVM: 2147352576, free: 1920315392 Crash Dump Analysis Crash dump directory: C:\WINDOWS\MinidumpCrash dumps are enabled on your computer.On Mon 6/23/2014 8:08:25 AM your computer crashedcrash dump file: C:\WINDOWS\Minidump\062314-53843-01.dmpuptime: 3 days, 02:18:49This was probably caused by the following module: netio.sys (NETIO!IndexHashAdd+0x3C) Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80036F06A5B)Error: DRIVER_CORRUPTED_EXPOOLfile path: C:\WINDOWS\system32\drivers
etio.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Network I/O SubsystemBug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 6/23/2014 8:08:25 AM your computer crashedcrash dump file: C:\WINDOWS\memory.dmpuptime: 3 days, 02:18:49This was probably caused by the following module: netio.sys (NETIO!IndexHashAdd+0x3C) Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80036F06A5B)Error: DRIVER_CORRUPTED_EXPOOLfile path: C:\WINDOWS\system32\drivers
etio.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Network I/O SubsystemBug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Thu 6/19/2014 8:06:49 AM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061914-35593-01.dmpuptime: 23:49:37This was probably caused by the following module: netio.sys (NETIO!WfpPoolAllocNonPaged+0x20) Bugcheck code: 0xC5 (0x10, 0x2, 0x0, 0xFFFFF800504A9A5B)Error: DRIVER_CORRUPTED_EXPOOLfile path: C:\WINDOWS\system32\drivers
etio.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Network I/O SubsystemBug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Tue 6/17/2014 2:36:07 PM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061714-33218-01.dmpuptime: 00:01:55This was probably caused by the following module: netio.sys (NETIO!IndexHashDelete+0x39) Bugcheck code: 0xA (0x22, 0x2, 0x0, 0xFFFFF8034B100AA7)Error: IRQL_NOT_LESS_OR_EQUALfile path: C:\WINDOWS\system32\drivers
etio.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Network I/O SubsystemBug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 6/16/2014 5:59:15 PM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061614-104968-01.dmpuptime: 00:04:19This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x19 (0xE, 0xFFFFE001CC35B0B0, 0x1E, 0xD01BA441EA5210AD)Error: BAD_POOL_HEADERBug check description: This indicates that a pool header is corrupt.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 6/16/2014 5:54:28 PM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061614-105015-01.dmpuptime: 00:02:20This was probably caused by the following module: netio.sys (NETIO!IndexHashClassify+0x31A) Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF800AC173EB0)Error: IRQL_NOT_LESS_OR_EQUALfile path: C:\WINDOWS\system32\drivers
etio.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Network I/O SubsystemBug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 6/16/2014 2:03:08 PM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061614-161937-01.dmpuptime: 00:03:31This was probably caused by the following module: ndis.sys (ndis!ndisNsiEnumerateAllIfStackEntriesFull+0xBD) Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF801880E5E89)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: C:\WINDOWS\system32\drivers
dis.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Network Driver Interface Specification (NDIS)Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Mon 6/16/2014 1:58:11 PM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061614-41109-01.dmpuptime: 01:34:14This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x41287, 0xB, 0x0, 0x0)Error: MEMORY_MANAGEMENTBug check description: This indicates that a severe memory management error occurred.This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 6/16/2014 12:17:09 PM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061614-88781-01.dmpuptime: 00:14:38This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x41287, 0x3B, 0x0, 0x0)Error: MEMORY_MANAGEMENTBug check description: This indicates that a severe memory management error occurred.This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 6/16/2014 12:02:07 PM your computer crashedcrash dump file: C:\WINDOWS\Minidump\061614-43796-01.dmpuptime: 00:02:26This was probably caused by the following module: mrxsmb20.sys (mrxsmb20!Smb2DereferenceDirCacheObject+0xF6) Bugcheck code: 0xC2 (0x7, 0x1200, 0x0, 0xFFFFE00143FC10C0)Error: BAD_POOL_CALLERfile path: C:\WINDOWS\system32\drivers\mrxsmb20.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Longhorn SMB 2.0 RedirectorBug check description: This indicates that the current thread is making a bad pool request.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Conclusion 44 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: avgwfpa.sys (AVG Firewall driver, AVG Technologies CZ, s.r.o.)If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

PudgyOne · Answer

BillToothaker, Did you try removing AVG using the AVG Removal Tool then restart thew computer? The conclusion states that the problem is with AVG Firewall driver. Rick

Locked Topics – Laptops General

Was this post helpful?