BSOD while watching video on win media player, error 0x0000004e

dennis1 · 31 Jan 2012

BSOD while I was watching a movie using windows media player and had a few Google Chrome tabs open. This has happened several times already with no apparent pattern. Built my system at the end of 2010, added the GPU 2 months ago. Has been happening before and after the addition.

Specs:

Windows 7 Home Premium 64 bit full retail
CPU: AMD Phenom II X6 1075T
MOBO: ASUS M4A88TD-V EVO/USB3 AM3 AMD 880G
GPU: AMD RADEON HD 6950 2GB
RAM: OCZ Platinum 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
HDD: Western Digital Caviar Black WD1002FAEX 1TB 7200 RPM SATA
PSU: CORSAIR Enthusiast Series CMPSU-650TX 650W

.zip attached. Any help would be greatly appreciated. Thanks!

dennis1 · 31 Jan 2012

One more detail: When I added the GPU 2 months ago I also added 8GB RAM (2x4GB)

Dave76 · 31 Jan 2012

Since you have added RAM, let's check that first.
Are the two kits from the same manufacturer? Same frequency and timings?

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs - one SPD tab for each different RAM card, one of the 2GB card and one of the 4GB card.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

You've had 15 crashes since last June.

The latest is STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, ?memory
Cause
This error is typically caused by a driver passing a bad memory descriptor list. For example, the driver might have called MmUnlockPages twice with the same list.
It's blaming tcpip.sys, which is a Windows TCP/IP Driver, this is a Windows driver and likely not the cause but the result.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000032f918, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003128108 to fffff800030c8c40

STACK_TEXT:  
fffff880`040453b8 fffff800`03128108 : 00000000`0000004e 00000000`00000007 00000000`0032f918 00000000`00000001 : nt!KeBugCheckEx
fffff880`040453c0 fffff800`03139856 : 00000000`00000000 fffffa80`0a1c0640 fffffa80`0a595000 fffffa80`0a4de7a0 : nt! ?? ::FNODOBFM::`string'+0x175b6
fffff880`04045400 fffff800`030cbe48 : fffffa80`0a4d0004 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x37875
fffff880`04045490 fffff880`019424a0 : 00000000`000000f5 00000000`00000002 fffffa80`0a595010 00000000`00000000 : nt!IopfCompleteRequest+0x168
fffff880`04045580 fffff880`0196c23e : 00000000`00000009 00000000`00000000 fffffa80`0a8baad8 00000000`00000000 : tcpip!TcpCompleteTcbSend+0x40
fffff880`040455b0 fffff880`019423e2 : 00000001`00000014 00000032`00000000 fffffa80`0a595010 fffff880`01956f34 : tcpip!TcpShutdownTcb+0x50e
fffff880`040456f0 fffff880`019655f4 : fffffa80`0a249d5c fffffa80`0d3dfb00 fffffa80`0a0b5b80 fffffa80`0cf33080 : tcpip!TcpAbortTcbDelivery+0x32
fffff880`04045720 fffff880`01957d54 : ffff0000`00000000 00000000`00000000 fffffa80`8a46e976 00000003`00000000 : tcpip!TcpTcbCarefulDatagram+0xc44
fffff880`040458d0 fffff880`0195667a : fffffa80`0a8e6a80 fffff880`0194eb00 fffffa80`0a8baa01 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`04045a80 fffff880`019582ab : fffff880`068949a2 fffffa80`0aa45000 00000000`00000000 fffff880`01611700 : tcpip!TcpMatchReceive+0x1fa
fffff880`04045bd0 fffff880`0194f1c7 : fffffa80`0a8e6a80 fffffa80`0a897830 fffffa80`0000084c 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`04045ca0 fffff880`0194ed3a : 00000000`00000000 fffff880`01a6e9a0 fffff880`04045e60 fffffa80`0c03a3b0 : tcpip!IppDeliverListToProtocol+0x97
fffff880`04045d60 fffff880`0194e339 : fffff880`01a6e9a0 fffffa80`0c03a400 fffff880`04045da0 fffff880`04045e50 : tcpip!IppProcessDeliverList+0x5a
fffff880`04045e00 fffff880`0194c0af : fffffa80`0b2a10ac fffffa80`0aa45000 fffff880`01a6e9a0 00000000`0beed801 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`04045ee0 fffff880`0194b6a2 : fffffa80`0beecc40 00000000`00000000 fffffa80`0beed801 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`040460e0 fffff880`0194ab3a : fffffa80`0beed800 fffff880`04046210 fffffa80`0beed800 fffffa80`0bfc0000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`040461c0 fffff800`030d5618 : fffffa80`0c03b610 00000000`00004800 fffffa80`0a1d0b60 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`04046210 fffff880`0194b202 : fffff880`0194aa60 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`040462f0 fffff880`0179e0eb : fffffa80`0beee8d0 00000000`00000000 fffffa80`0b9e61a0 fffffa80`0b9e61a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`04046360 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TcpCompleteTcbSend+40
fffff880`019424a0 488b4e48        mov     rcx,qword ptr [rsi+48h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  tcpip!TcpCompleteTcbSend+40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e83e948

FAILURE_BUCKET_ID:  X64_0x4E_7_tcpip!TcpCompleteTcbSend+40

BUCKET_ID:  X64_0x4E_7_tcpip!TcpCompleteTcbSend+40

Followup: MachineOwner
---------

Go to the Asus M4A88TD-V EVO/USB3 website and update all of your drivers.
Be sure to update the LAN drivers.

Same stop code as above.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000032c3a8, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

Debugging Details:
------------------

BUGCHECK_STR:  0x4E_7

LAST_CONTROL_TRANSFER:  from fffff800030f4108 to fffff80003094c40

FOLLOWUP_IP: 
tcpip!TcpCompleteTcbSend+40
fffff880`016b14a0 488b4e48        mov     rcx,qword ptr [rsi+48h]

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

Followup: MachineOwner

This crash is STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver - it's blaming bckd.sys - K9 parental web filter
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800158f9bb, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003303100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
bckd+c9bb
fffff880`0158f9bb 0fb618          movzx   ebx,byte ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  GpuBoostServer

TRAP_FRAME:  fffff88009bdc510 -- (.trap 0xfffff88009bdc510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800da2a8b8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800158f9bb rsp=fffff88009bdc6a0 rbp=fffffa800dda60a8
 r8=fffff88001596af0  r9=0000000000000000 r10=fffff88009bdc570
r11=fffff88009bdc630 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
bckd+0xc9bb:
fffff880`0158f9bb 0fb618          movzx   ebx,byte ptr [rax] ds:0002:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d01e9 to fffff800030d0c40

STACK_TEXT:  
fffff880`09bdc3c8 fffff800`030d01e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09bdc3d0 fffff800`030cee60 : fffffa80`0a96a820 fffff880`0158fbfc fffffa80`0b6dc180 fffffa80`0a96a820 : nt!KiBugCheckDispatch+0x69
fffff880`09bdc510 fffff880`0158f9bb : fffffa80`0b6dc180 fffffa80`0b6dc180 fffffa80`0dda5ec0 fffffa80`0a96a820 : nt!KiPageFault+0x260
fffff880`09bdc6a0 fffffa80`0b6dc180 : fffffa80`0b6dc180 fffffa80`0dda5ec0 fffffa80`0a96a820 fffffa80`0dec9128 : bckd+0xc9bb
fffff880`09bdc6a8 fffffa80`0b6dc180 : fffffa80`0dda5ec0 fffffa80`0a96a820 fffffa80`0dec9128 fffff880`0158fbd2 : 0xfffffa80`0b6dc180
fffff880`09bdc6b0 fffffa80`0dda5ec0 : fffffa80`0a96a820 fffffa80`0dec9128 fffff880`0158fbd2 fffffa80`0a96a820 : 0xfffffa80`0b6dc180
fffff880`09bdc6b8 fffffa80`0a96a820 : fffffa80`0dec9128 fffff880`0158fbd2 fffffa80`0a96a820 fffffa80`0b6dc180 : 0xfffffa80`0dda5ec0
fffff880`09bdc6c0 fffffa80`0dec9128 : fffff880`0158fbd2 fffffa80`0a96a820 fffffa80`0b6dc180 fffffa80`0b6dc180 : 0xfffffa80`0a96a820
fffff880`09bdc6c8 fffff880`0158fbd2 : fffffa80`0a96a820 fffffa80`0b6dc180 fffffa80`0b6dc180 fffffa80`0dda5ec0 : 0xfffffa80`0dec9128
fffff880`09bdc6d0 fffffa80`0a96a820 : fffffa80`0b6dc180 fffffa80`0b6dc180 fffffa80`0dda5ec0 00000000`00000000 : bckd+0xcbd2
fffff880`09bdc6d8 fffffa80`0b6dc180 : fffffa80`0b6dc180 fffffa80`0dda5ec0 00000000`00000000 fffffa80`0dec9128 : 0xfffffa80`0a96a820
fffff880`09bdc6e0 fffffa80`0b6dc180 : fffffa80`0dda5ec0 00000000`00000000 fffffa80`0dec9128 fffffa80`0dda5ec0 : 0xfffffa80`0b6dc180
fffff880`09bdc6e8 fffffa80`0dda5ec0 : 00000000`00000000 fffffa80`0dec9128 fffffa80`0dda5ec0 fffff880`015909ca : 0xfffffa80`0b6dc180
fffff880`09bdc6f0 00000000`00000000 : fffffa80`0dec9128 fffffa80`0dda5ec0 fffff880`015909ca fffffa80`0a96a820 : 0xfffffa80`0dda5ec0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bckd+c9bb
fffff880`0158f9bb 0fb618          movzx   ebx,byte ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  bckd+c9bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bckd

IMAGE_NAME:  bckd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4df2909a

FAILURE_BUCKET_ID:  X64_0xD1_bckd+c9bb

BUCKET_ID:  X64_0xD1_bckd+c9bb

Followup: MachineOwner
---------

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
This is blaming the tdx.sys driver - this is a Windows driver and likely not the cause but the result.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800158bbd9, Address of the instruction which caused the bugcheck
Arg3: fffff88003a81b20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
tdx!TdxCreateControlChannel+a9
fffff880`0158bbd9 48895e18        mov     qword ptr [rsi+18h],rbx

CONTEXT:  fffff88003a81b20 -- (.cxr 0xfffff88003a81b20)
rax=0000000000000001 rbx=fffffa800d196e00 rcx=fffffa800b219940
rdx=fffffa800d32c000 rsi=000000000031cac6 rdi=0000000000000000
rip=fffff8800158bbd9 rsp=fffff88003a82500 rbp=fffff88003a825f8
 r8=fffffa800b219900  r9=fffffa800d196e18 r10=fffff80003015348
r11=0000000000000000 r12=fffffa800b219900 r13=fffffa800b219930
r14=000000000031cac6 r15=fffffa800ccc66f8
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
tdx!TdxCreateControlChannel+0xa9:
fffff880`0158bbd9 48895e18        mov     qword ptr [rsi+18h],rbx ds:002b:00000000`0031cade=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  EPU.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800158bbd9

STACK_TEXT:  
fffff880`03a82500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tdx!TdxCreateControlChannel+0xa9


FOLLOWUP_IP: 
tdx!TdxCreateControlChannel+a9
fffff880`0158bbd9 48895e18        mov     qword ptr [rsi+18h],rbx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tdx!TdxCreateControlChannel+a9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79332

STACK_COMMAND:  .cxr 0xfffff88003a81b20 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_tdx!TdxCreateControlChannel+a9

BUCKET_ID:  X64_0x3B_tdx!TdxCreateControlChannel+a9

Followup: MachineOwner
---------

Old or drivers that are known to cause crashes.

Code:

GEARAspiWDM.sys Mon May 18 20:17:04 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes

iTunes is known to cause crashes with Windows 7, un-install it for testing purposes.

Code:

sptd.sys     Mon Oct 12 04:55:14 2009 - SCSI Pass Through Direct Host - Daemon Tools (known issues with Win7)

Un-install Daemon Tools.

After un-installing the above apps, we can look at the RAM and see if there may be an issue.
Mixing RAM brands, frequencies and timings can cause instability.
Having more than 4GB RAM can require setting adjustments to get it to run stable.

dennis1 · 31 Jan 2012

Thanks for your detailed response. I'll run through your suggestions when I get home from work and report back.

dennis1 · 31 Jan 2012

Snips attached

Attachment 196124

Attachment 196125

Attachment 196126

Attachment 196127

Attachment 196128

Attachment 196129

Checking ASUS site for drivers now...

dennis1 · 01 Feb 2012

Voltages from BIOS:

CPU & NB Voltage Mode = Offset
CPU Offset Voltage = 1.3
CPU/NB Offset Voltage = 1.15
CPU VDDA Voltage = 2.5
DRAM Voltage = 1.5
HT Voltage = 1.2
NB Voltage = 1.25
NB 1.1V Voltage = 1.1
NB 1.8V Voltage = 1.8
SB Voltage = 1.1
Sideport Memory Voltage = 1.5

Thanks again for your help!

Dave76 · 01 Feb 2012

After you update your drivers and un-install iTunes and Daemon Tools.

Mixing RAM can cause instability, sometimes you can get them to work together by adjusting the settings.
If the RAM frequency and timing are on 'Auto' they will usually use the settings of the slower RAM, yours seems to be not set to either.

For testing purposes remove the 2X2GB OCZ RAM.
If we can get your system stable, you can try installing the 2X2GB RAM, you will have to set the frequency and timings manually to the slower RAM settings.

D/L your motherboard manual if you don't already have it.
M4A88TD-V EVO/USB3

Set the 2X4GB Mushkin RAM frequency to 'Manual' and 1333MHz (667MHz in your BIOS).
First four timings to 9-9-9-25, leave the rest on 'Auto'.
'Command Rate' to 2T.

Most AMD CPU (Integrated Memory Controllers) will need a CPU-NB Voltage boost of +0.10V, so if your default is 1.15V, set it to 1.25V.

Take a look at page 2-10 and 2-11 of your motherboard manual.
Put the 2X4GB RAM in slots DIMM A-1 and DIMM B-1, the blue slots. That is slots #1 and #3 when counting from the CPU.

If later you decide to install all four RAM cards, the 2X4 GB RAM shuld be on the DIMM A-1 and DIMM B-1, the blue slots. That is slots #1 and #3 when counting from the CPU. The 2X2GB RAM should be in DIMM A-2 and DIMM B-2, the black slots.
Let me know which slots you initially had the 2X2GB and 2X4GB ram installed in.

Just leave the 2X4GB RAM installed for testing.