I am receiving frequent BSODs in Windows 8, which are either BAD_POOL_HEADER or DPC_WATCHDOG_VIOLATION but it only happens after XBMC has been running.
WhoCrashed and told me this:
System Information (local)
computer name: CMSL42-DESKTOP windows version: Windows 8 , 6.2, build:
9200 windows dir: C:\Windows CPU: AuthenticAMD AMD Phenom(tm) II X6
1090T Processor AMD586, level: 16 6 logical processors, active mask:
63 RAM: 16641871872 total VM: 2147352576, free: 1927999488
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 22/07/2013 12:05:06 PM GMT your computer crashed crash dump
file: C:\Windows\Minidump\072213-33649-01.dmp This was probably caused
by the following module: tcpip.sys (tcpip+0xDB024) Bugcheck code:
0x19 (0xD, 0xFFFFF880180041E0, 0xFFFFF88001D94024, 0x9239D5B78D234E2E)
Error: BAD_POOL_HEADER file path:
C:\Windows\system32\drivers\tcpip.sys product: Microsoft® Windows®
Operating System company: Microsoft Corporation description: TCP/IP
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 that cannot be identified at this time.
On Mon 22/07/2013 12:05:06 PM GMT your computer crashed crash dump
file: C:\Windows\memory.dmp This was probably caused by the following
module: nvlddmkm.sys (nvlddmkm+0x18A14F) Bugcheck code: 0x19 (0xD,
0xFFFFF880180041E0, 0xFFFFF88001D94024, 0x9239D5B78D234E2E) Error:
BAD_POOL_HEADER file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 320.49 company:
NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver,
Version 320.49 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver,
Version 320.49 , NVIDIA Corporation). Google query: NVIDIA
Corporation BAD_POOL_HEADER
On Sun 21/07/2013 8:25:06 PM GMT your computer crashed crash dump
file: C:\Windows\Minidump\072213-30045-01.dmp This was probably caused
by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code:
0x133 (0x1, 0x1E0D, 0x0, 0x0) Error: DPC_WATCHDOG_VIOLATION file path:
C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows®
Operating System company: Microsoft Corporation description: NT Kernel
& System Bug check description: The DPC watchdog detected a prolonged
run time at an IRQL of DISPATCH_LEVEL or above. This appears to be a
typical software driver bug and is not likely to be caused by a
hardware problem. This problem might be caused by a thermal issue.
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 21/07/2013 5:04:34 PM GMT your computer crashed crash dump
file: C:\Windows\Minidump\072213-29343-01.dmp This was probably caused
by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code:
0x133 (0x1, 0x1E0D, 0x0, 0x0) Error: DPC_WATCHDOG_VIOLATION file path:
C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows®
Operating System company: Microsoft Corporation description: NT Kernel
& System Bug check description: The DPC watchdog detected a prolonged
run time at an IRQL of DISPATCH_LEVEL or above. This appears to be a
typical software driver bug and is not likely to be caused by a
hardware problem. This problem might be caused by a thermal issue.
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 21/07/2013 4:31:53 PM GMT your computer crashed crash dump
file: C:\Windows\Minidump\072213-41153-01.dmp This was probably caused
by the following module: ntoskrnl.exe (nt+0x5A440) Bugcheck code:
0x19 (0xD, 0xFFFFF880184921E0, 0x0, 0x1E5DDB866E4D06BA) 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 Mon 15/07/2013 1:00:49 PM GMT your computer crashed crash dump
file: C:\Windows\Minidump\071513-75426-01.dmp This was probably caused
by the following module: tcpip.sys (tcpip+0xDB798) Bugcheck code:
0x19 (0xD, 0xFFFFF880153481E0, 0xFFFFF88001D57798, 0xCBFD93B7E3826D86)
Error: BAD_POOL_HEADER file path:
C:\Windows\system32\drivers\tcpip.sys product: Microsoft® Windows®
Operating System company: Microsoft Corporation description: TCP/IP
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 that cannot be identified at this time.
No comments:
Post a Comment