BSOD help

[no_name_needed]

Hey
would anyone be kind enough to explain what causes this BSOD please
Thanks in advance


computer name: TOADINAPINTGLAS
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: GBT___, Gigabyte Technology Co., Ltd., M57SLI-S4
CPU: AuthenticAMD AMD Phenom(tm) II X4 940 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4294500352 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 17/01/2015 15:11:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011715-11918-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00D7A2820, 0xFFFFF8A00D7A2820, 0xFA8008CD5A5004C0)
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 that cannot be identified at this time.



On Sat 17/01/2015 15:11:33 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 (0x3, 0xFFFFF8A00D7A2820, 0xFFFFF8A00D7A2820, 0xFA8008CD5A5004C0)
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 that cannot be identified at this time.

 

[varkanoid]

Usually caused by a driver issue. Are ALL your drivers up to date ?

Does actually give you a hint

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem

 

[no_name_needed]

Is there a program I can use to check everything is up to date