BSOD Windows 7

Code:

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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000013b00d, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000010890c, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b0338c to fffff80002a73740

STACK_TEXT:  
fffff880`072bdf28 fffff800`02b0338c : 00000000`0000004e 00000000`00000099 00000000`0013b00d 00000000`00000002 : nt!KeBugCheckEx
fffff880`072bdf30 fffff800`02ae59f7 : 00000000`00000000 fffff680`00371c30 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`072bdf70 fffff800`02a47c23 : fffffa80`05219060 fffff700`00008e2a 0000007f`fffffff8 fffff8a0`0135de20 : nt! ?? ::FNODOBFM::`string'+0x3223e
fffff880`072be000 fffff800`02a4668a : fffffa80`05219060 fffffa80`00000003 fffff880`000063cb fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`072be8b0 fffff800`02d58dcf : fffff8a0`021f8a20 fffff880`072bec20 00000000`00000000 fffffa80`048b0730 : nt!MmCleanProcessAddressSpace+0x96
fffff880`072be900 fffff800`02d31635 : 00000000`000000ff fffffa80`05219301 00000000`7ef7a000 fffffa80`053fc060 : nt!PspExitThread+0x92f
fffff880`072be9c0 fffff800`02a501db : 00000000`00000001 00000000`00000000 fffff880`00961000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`072be9f0 fffff800`02a50620 : 00000000`00000000 fffff880`072bea70 fffff800`02d3174c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`072bea70 fffff800`02a72a37 : fffffa80`048b0730 00000000`05abe928 fffff880`072bebc8 0000007f`ffffffff : nt!KiInitiateUserApc+0x70
fffff880`072bebb0 00000000`75062dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`05abe908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75062dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02b0338c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

what I'm seeing basically is the same thing. A memory corruption caused by a bad driver.
however the first dump is clearly a result of
rdyboost.sys ( rdyboost+5063 )

rdyboost is for usb or flash ram mostly, and can be easily disabled.
One of the others will probably have more luck with the primary failure in the newer file.
All I can get out of it is a memory fault caused by internet explorer.

Sorry what I'm saying is I couldn't trace the actual source of the first dump file outside of memory corruption.
That means either... the memory is corrupted, or a driver is responsible.
I had no luck finding said driver, one of the more experienced debuggers might be able to give you more.
I wouldn't be surprised if the Mcafee networking/security suite is actually to blame.