Reoccuring BSoD Problem

edit: new realtek audio drivers from here:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
(there were reports that the old driver was corrupting kernel memory)

Ok, it looks like you got a bugcheck, updated your BIOS and replaced your memory. then got another bugcheck a few weeks later.
The cause of both bugchecks is not clear but it is most likely a buffer overflow cause by a driver.

I would suspect one of these three:
nvhda64v.sys Thu Nov 28 05:38:09 2013 (nvidia audio driver for HDMI)
RTKVHD64.sys Tue Jun 12 03:02:32 2012 (Realtek(r) High Definition Audio Function Driver )
mbam.sys (malwarebytes driver Thu Feb 28 12:33:07 2013, just old and you might want to remove or update)


nvxdsync.exe was running.
My guess it that there is a bug the nvidia HMDI audio driver that caused a buffer overflow and corrupted memory that belongs to other drivers.
Or there is some interaction between the nvidia sound driver and the older realtek sound driver. ( bug could be in the realtek driver as well, I don't know)

I suspect the bug is triggered by using the nvidia program nvxdsync.exe (sound control app? you might look up what it does)

I would recommend that you disable the nvidia audio driver in control panel->device manager-> high definition audio devices.
or disable the one on your mother board, depends on which one you use most.


Notes: you did not have any detected memory corruptions in any loaded windows core files. The corruption was in shared data structures in the drivers memory space. Basically, a driver corrupted memory, later a windows driver went to get its data from memory and detected the corruption and called a bugcheck.

Windows will load drivers in a different order each time it boots. Most drivers don't look for corruption but a few do look in a effort to isolate damage
to the OS from a virus or driver errors. This is why you will not get a bug check on each boot but still have the same problem, it is just not detected
until a core windows driver's data is corrupted and that driver calls a bugcheck.
(directx called one bugcheck, and a memory manager routine called the other)









debug info:
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff800`5627f000 PsLoadedModuleList = 0xfffff800`5654ba20
Debug session time: Sat Jan 18 11:30:14.299 2014 (UTC - 8:00)
System Uptime: 0 days 0:00:19.012



BugCheck A, {fffff700010a2888, 0, 0, fffff80056313183}


nvxdsync.exe
mbam \??\C:\Windows\system32\drivers\mbam.sys Thu Feb 28 12:33:07 2013

RTKVHD64.SYS Realtek(r) High Definition Audio Function Driver Jun 12 03:02:32 2012

RTKVHD64 \SystemRoot\system32\drivers\RTKVHD64.sys Tue Jun 12 03:02:32 2012
nvhda64v \SystemRoot\system32\drivers\nvhda64v.sys Thu Nov 28 05:38:09 2013

Identifier = REG_SZ AMD64 Family 21 Model 1 Stepping 2
ProcessorNameString = REG_SZ AMD FX(tm)-8120 Eight-Core Processor

Processor ID 120f6000fffb8b17
Processor Version AMD FX(tm)-8120 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 3100MHz
Current Speed 3100MHz

BIOS Version 2104
BIOS Starting Address Segment f000
BIOS Release Date 11/21/2013
Manufacturer ASUSTeK COMPUTER INC.
Product SABERTOOTH 990FX R2.0

memory
bank 0: none
bank 1: 4096MB 1333MHz Kingston 99U5403-043.A00LF
bank 2: none
bank 3: 4096MB 1333MHz Kingston 99U5403-043.A00LF


core OS files not corrupt in memory

--------------------------------------
BugCheck 139, {3, fffff88007fb6510, fffff88007fb6468, 0}
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff88007fb6510, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff88007fb6468, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application.
This overrun could potentially allow a malicious user to gain control of this application.

------------------------------------------------------
machine 2
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Debug session time: Wed Dec 25 11:26:03.581 2013 (UTC - 8:00)
System Uptime: 0 days 0:34:10.298

BugCheck 139, {3, fffff88007fb6510, fffff88007fb6468, 0}
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff88007fb6510, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff88007fb6468, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved



BIOS Release Date 07/10/2012
Manufacturer ASUSTeK COMPUTER INC.
Product SABERTOOTH 990FX R2.0
memory
bank1 and bank 3: 4096MB 1600MHz Manufacturer2

the malwarebytes driver might be the current one. I think you can do a scan without installing the driver. you might do that to remove possible points of failure.

looks like kernel data corruption again. using a bad address.
looking at your os image, the only thing i can think of it to turn off your special hardware for your usb 3.0 in BIOS and see if the problem goes away.
I mention this because it looks like you have generic usb 3.0 drivers but there were lots of versions of hardware that had bugs in their circuits with USB 3.0. These circuits with bugs in the electronics require custom drivers to work correctly. SO, disable usb 3.0 on the motherboard, put your devices on usb 2 and hope.

confirm that a checkdsk /f /r of your drive is ok
confirm that your OS files are ok use
cmd.exe as admin then run
sfc.exe /scannow
maybe swap your memory between their slots and run a RAM test?

BugCheck 4E, {8d, b7faf, 410080, fffff68000073b83}
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: 000000000000008d,
Arg2: 00000000000b7faf
Arg3: 0000000000410080
Arg4: fffff68000073b83

the description for Arg1= 8d = The page-free list is corrupted. This error code most likely indicates a hardware issue.

i did not find any corrupt OS modules in the debugger.

run memtest86 http://www.memtest86.com/ if it works then swap your memory modules slots and run it again. If it still works after that you are back to hunting down a driver corruption issue.