New
#1
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
OSWindows 7 Ultimate X64
CPU
Motherboard
Memory
Graphics Card(s)
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.
Last edited by newbosaurusRex; 25 Jul 2012 at 08:02.
Quote