Larry Ortiz5 said:Grab WhoCrashed. Once it's installed, just hit the Analyze button. It'll generate a log explaining why your PC restarted. Copy that log here on the forum so we can take a look.
On Mon 22.9.2014. 13:44:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!ExFreePoolWithTag +0 x1B1)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF956E1510, 0xFFFFFFFF956E16F0, 0xA3C0240)
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: ntkrpamp.exe .
Google search: ntkrpamp.exe BAD_POOL_HEADER
On Mon 22.9.2014. 13:44:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092214-16921-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x121C6B)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF956E1510, 0xFFFFFFFF956E16F0, 0xA3C0240)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows ® Operating system
company: Microsoft Corporation description : NT kernel & system
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.