New
#1
Random BSODS - different files every time
Just 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
(and installed microsoft security essentials)
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 system is unstable afraid to do anything on it
attached the sevenforums.zip file from the sf diagnostics tool
and here is the recent whocrashed info
the latest couple were when I attempted to watch a video in windows media player
(Need anything else?)
any help would be GREAT!
THANKS
-------------------------------
RECENT CRASH WHILE IDLE
-----------------------------
On Thu 7/26/2012 5:09:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072612-27437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0100F1B80, 0xFFFFF8A0100F1B80, 0x5000215)
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 Thu 7/26/2012 5:09:45 PM 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, 0xFFFFF8A0100F1B80, 0xFFFFF8A0100F1B80, 0x5000215)
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.
---------------------------------
-----------------------------------
On Mon 7/23/2012 10:27:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-25671-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x19E4D4)
Bugcheck code: 0x116 (0xFFFFFA8005D0D010, 0xFFFFF8800F3AE4D4, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 258.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 258.96
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 258.96 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR
On Mon 7/23/2012 10:27:03 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 (0xFFFFFA8005D0D010, 0xFFFFF8800F3AE4D4, 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.
On Mon 7/23/2012 1:21:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-21593-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x19E4D4)
Bugcheck code: 0x116 (0xFFFFFA800211E4E0, 0xFFFFF8800F3C54D4, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 258.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 258.96
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 258.96 , 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\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 258.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 258.96
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 258.96 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR
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: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.
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 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 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; 26 Jul 2012 at 19:15.