Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSODs - fileinfo.sys, ntoskrnl.exe, netio.sys

16 Jul 2012   #1
newbosaurusRex

Windows 7 Ultimate X64
 
 
Random BSODs - Please Help!!!

Attachment 222956Just put this cheap comp back together with a new MOBO and new RAM
Updated BIOS to newest version I could find (Vista) *(could this be my problem?)
Updated GPU to 8.17.13.142
Updated Windows with all important updates
Ran Memtest 86 with no errors
Also removed AVG using the remover tool suggested in other posts

OS Windows 7 Ultimate X64

CPU AMD Athalon 64 3200+

Motherboard A8ME-FM

Memory 2X 1GB Sticks Komputerbay

Graphics Card(s) Nvidia GeForce 7800GT

Been randomly getting BSOD here is the recent whocrashed info
and I attached the dumps and perfmon /report
(Need anything else?)
any help would be GREAT!
THANKS

On Mon 7/16/2012 6:38:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071612-28640-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x1066)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A003EBB980, 0xFFFFF8A003EBB980, 0x5000404)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 7/16/2012 6:38:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0xC8F7)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A003EBB980, 0xFFFFF8A003EBB980, 0x5000404)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 7/16/2012 2:25:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071612-27343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x41284, 0xFFFFF68000043001, 0x4897, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug 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 which cannot be identified at this time.


On Mon 7/16/2012 6:42:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071612-28578-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1495B)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80054C2CA0, 0xFFFFFA80054C2CA0, 0x4000004)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 7/14/2012 3:46:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071312-34578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8C, 0x1, 0xFFFFF960001A288A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/14/2012 2:36:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071312-29921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x5002, 0xFFFFF780C0000000, 0x2D19, 0xFF002D79FFFFFFFE)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug 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 which cannot be identified at this time.


On Fri 7/13/2012 1:54:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-41812-01.dmp
This was probably caused by the following module: avgidsfiltera.sys (avgidsfiltera+0x1B88)
Bugcheck code: 0x19 (0x3, 0xFFFFFA80012326C0, 0xFFFFFA80012326FC, 0xFFFFFA80012326C0)
Error: BAD_POOL_HEADER
Bug 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgidsfiltera.sys .
Google query: avgidsfiltera.sys BAD_POOL_HEADER




On Thu 7/12/2012 10:47:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-41421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xBE (0xFFFFF8A000954180, 0x6CB000004586F121, 0xFFFFF88005990720, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



My System SpecsSystem Spec
.
17 Jul 2012   #2
newbosaurusRex

Windows 7 Ultimate X64
 
 

here is the whocrashed info from today:

On Tue 7/17/2012 6:17:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071712-30890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A011D126A0, 0xFFFFF8A011D126A0, 0x5000109)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug 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 which cannot be identified at this time.


On Tue 7/17/2012 6:17:37 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A011D126A0, 0xFFFFF8A011D126A0, 0x5000109)
Error: BAD_POOL_HEADER
Bug 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 which cannot be identified at this time.
My System SpecsSystem Spec
19 Jul 2012   #3
newbosaurusRex

Windows 7 Ultimate X64
 
 

Here is the whocrashed info from today

On Thu 7/19/2012 12:31:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-22718-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x23178)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A001A63C00, 0xFFFFF8A001A63C00, 0x5000301)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 7/19/2012 12:31:12 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x8AF89)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A001A63C00, 0xFFFFF8A001A63C00, 0x5000301)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 7/19/2012 12:14:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-22218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8001FB7A00, 0xFFFFFA8001FB7A80, 0x408001C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug 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 which cannot be identified at this time.
My System SpecsSystem Spec
.

22 Jul 2012   #4
newbosaurusRex

Windows 7 Ultimate X64
 
 

Here is the recent whocrashed info
crashed while playing a video in windows media player
any help would be great
thanks

On Sun 7/22/2012 11:52:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-21828-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x19E4D4)
Bugcheck code: 0x116 (0xFFFFFA8001CE22A0, 0xFFFFF8800F3A24D4, 0x0, 0x2)
Error: VIDEO_TDR_ERROR

file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 301.42

company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 301.42
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 301.42 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR





On Sun 7/22/2012 11:52:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D000)
Bugcheck code: 0x116 (0xFFFFFA8001CE22A0, 0xFFFFF8800F3A24D4, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 which cannot be identified at this time.

My System SpecsSystem Spec
23 Jul 2012   #5
newbosaurusRex

Windows 7 Ultimate X64
 
 

Here are the recent files gathered using the SF Diagnostic Tool

Stilllll looking for some help

Thanks
My System SpecsSystem Spec
25 Jul 2012   #6
newbosaurusRex

Windows 7 Ultimate X64
 
 

still looking for some help
system is still unstable
thanks
My System SpecsSystem Spec
Reply

 Random BSODs - fileinfo.sys, ntoskrnl.exe, netio.sys




Thread Tools




Similar help and support threads
Thread Forum
BSOD random W7 Pro x64, error NETIO.SYS \ ntoskrnl.exe
Hi there, my colleague is getting random BSOD on his relatively new Dell E6330 with W7 Pro x64. I have grabbed some dump files and tried to understand them in BlueScreenView, but they don't make a lot of sense to me, but these two items are frequently mentioned: NETIO.SYS \ ntoskrnl.exe. ...
BSOD Help and Support
Random BSOD : DRIVER_IRQL_NOT_LESS_OR_EQUAL, NETIO.SYS & ntoskrnl.exe
Hello, And first of all thank you for spending your time to help us, I'm very grateful. My PC randomly crashes. The BSOD mentions a couple of things like NETIO.SYS or ntoskrnl.exe : STOP:0x000000D1 (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xFFFFF8800191E6FD) NETIO.SYS...
BSOD Help and Support
Random BSODs with netio.sys always being pointed to
Okay so, I've been trying to fix issues with my computer for a good while now. Used to be where it'd crash almost every time I tried to do anything. Was able to trace it to a power supply issue. But a couple weeks later I started getting BSODs again. They're random and far less frequent (maybe once...
BSOD Help and Support
BSOD - fileinfo.sys and ntoskrnl.exe
The 3 crashes included were before I: -updated Realtek HD audio drivers -disabled the AMD HD audio driver -turned HD sleep to never -updated video driver System has been running with no issue since Sept 2011 up until July 2012. I've already done a repair install so I don't not have all the...
BSOD Help and Support
Random BSODs [+NETIO.sys, afd.sys, tcpip.sys]
Just after upgrading to Windows 8 x64 I started getting some BSODs while on Windows. I have already tried to update the LAN driver according to Asus's recommendation, but it didn't helped at all. EDIT: It usually happens when I'm doing whatever on Windows, but it's quite common if I'm using...
BSOD Help and Support
Random BSODs related to NetIO.sys
Hello, I upgraded my system to Windows 7 Ultimate x64 a month or two ago from Windows XP Pro. Ever since the upgrade, I have been getting random BSODs that can occur when the system is completely idle (while I am at work) or while it is busy. It does not seem to have any sort of pattern. I...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 14:03.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App