BSOD [ntoskrnl.exe (nt+0x75C40)]

jakocomputer · 30 Mar 2013

Been having this problem with this laptop for a while now and have tried many fixes.
Any help would be appreciated. Thank you in advance.
(SF Diagnostic Tool Files attached)

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: ***********
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD A4-3300M APU with Radeon(tm) HD Graphics AMD586, level: 18
2 logical processors, active mask: 3
RAM: 3735977984 total
VM: 2147352576, free: 1968156672

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 3/28/2013 3:07:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032713-36629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E6C940, 0x0, 0xFFFFF80002E6C940)
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 Thu 3/28/2013 3:07:08 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bckd.sys (bckd+0xE37B)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E6C940, 0x0, 0xFFFFF80002E6C940)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\bckd.sys
product: K9 Web Protection
company: Blue Coat Systems, Inc.
description: K9 Web Protection 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.
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: bckd.sys (K9 Web Protection Driver, Blue Coat Systems, Inc.).
Google query: Blue Coat Systems, Inc. BAD_POOL_HEADER

On Thu 3/7/2013 4:51:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030713-28298-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E51940, 0x0, 0xFFFFF80002E51940)
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 Wed 3/6/2013 3:05:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030613-34460-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x44 (0xFFFFFA800403F940, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 driver has tried to requested an IRP be completed that is already complete.
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 that cannot be identified at this time.

On Sun 3/3/2013 8:03:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030313-20607-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E23940, 0x0, 0xFFFFF80002E23940)
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 Sun 3/3/2013 1:36:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030313-27190-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E23940, 0x0, 0xFFFFF80002E23940)
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 Thu 2/28/2013 12:49:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022713-29796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E12940, 0x0, 0xFFFFF80002E12940)
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 Sun 2/17/2013 11:02:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-29764-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E17940, 0x0, 0xFFFFF80002E17940)
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.

Northernsoul55 · 30 Mar 2013

From your latest crash dump:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff80002e6c940, 0, fffff80002e6c940}
Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
Followup: Pool_corruption
---------
0: kd>
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.

Problem Driver: bckd.sys
bckd.sys Mon Feb 13 19:07:30 2012 (4F395F72)
Relates to: Blue Coat K9 Web Protection - K9 parental web filter

http://www1.k9webprotection.com/support/overview
Either uninstall completely or update the program/drivers.

Other driver issue:

fffff880`07487578 fffff880`013c20c1*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
SYMEFA64+0x1120c1

Relates to: Symantec Extended File Attributes
Please update all Norton/symantec drivers as they are very outdated:

SYMDS64 SYMDS64.SYS Mon May 16 23:15:03 2011 (4DD1A1E7)
SYMEFA64 SYMEFA64.SYS Sat May 19 02:29:56 2012 (4FB6F794)
SYMEVENT64x86 SYMEVENT64x86.SYS Tue Nov 22 18:30:48 2011 (4ECBEA58)
SYMNETS SYMNETS.SYS Sat Nov 12 21:11:53 2011 (4EBEE119)

Alternatively uninstall Norton/Symantecs from your system:

https://www.sevenforums.com/tutorials/78961-av-uninstallers.html

As an alternative install MSE:
Microsoft Security Essentials.
Recommended from a strict BSOD perspective, compatibility & stability
compared to other antiviruses/internet security software.

Microsoft Security Essentials - Microsoft Windows

Cheers

Dave

jakocomputer · 30 Mar 2013

Thank you for you fast reply. I have re-installed both items and will let you know if there are more problems.
Thank you once more.

Northernsoul55 · 02 Apr 2013

No problem.

Look forward to any feedback.

Cheers

Dave