Several BSODs with Different Stop Messages

Newly built computer, I'll update my specs in the profile shortly (done).
Probably crashed 5 or 6 times.

Crashed while gaming, crashed while not gaming, crashed while I was at the store.
Could possibly blame xSplit for the crashes, as I can't remember if it's crashed while it isn't running.
Different errors each time: DRIVER_IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA (x2), UNEXPECTED_KERNEL_MODE_TRAP, KMODE_EXCEPTION_NOT_HANDLED, MEMORY_MANAGEMENT.

I removed one stick of RAM recently to test if it was bad, even though memory test didn't show any issues. All the crashes so far have been with both sticks.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64 - the original installed OS on the system? I installed it, newly built computer.
- an OEM or full retail version? It's an OEM version from one of my Dell computers.
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer
- What is the age of system (hardware)? A few days, it's newly built.
- What is the age of OS installation (have you re-installed the OS?) A few days.

-

Edit: One dump didn't get included. It was at C:\Windows\MEMORY.DMP. It's roughly 500MB in size. Here is the results of running a WinDBG on it:

0: kd> !analyze -v
Unable to get program counter
*******************************************************************************
* *
* 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: fffff80002e8df83, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007f8eb90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Page 9586dc3 too large to be in the dump file.

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

FAULTING_IP:
+0
3a06:df83 ?? ???

CONTEXT: fffff88007f8eb90 -- (.cxr 0xfffff88007f8eb90)
rax=0000000000000002 rbx=0000000000000000 rcx=23cf5fe230f80000
rdx=0000000000000100 rsi=0000000000000000 rdi=fffff9802330ee10
rip=fffff80002e8df83 rsp=fffff88007f8f570 rbp=00000000a000000c
r8=fffff880009ea180 r9=fffff880009ea180 r10=0000000000000100
r11=0000000000000000 r12=00000000a0000003 r13=0000000000000000
r14=0000000000000000 r15=fffff9802330eed0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
fffff800`02e8df83 0000 add byte ptr [rax],al ds:002b:00000000`00000002=??
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

UNALIGNED_STACK_POINTER: 010101013acc39ee

LAST_CONTROL_TRANSFER: from fffffa80084e7900 to fffff80002e8df83

STACK_TEXT:
01010101`3acc39ee 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1010101`3a103bc9


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

Hi there,

It seems there may be multiple issues going on. The first is a hardware problem, as suggested by some of the dumps and by your report on the crashes being with only both RAM sticks.

The second is a simple driver issue. Install the latest Realtek ethernet drivers from here: Realtek

Code:

Rt64win7.sys  Wed Jan 26 08:34:03 2011 (4D4022CB)

Continue testing with only one stick of RAM installed. You might also run Prime95 on both sticks at the same time: Hardware - Stress Test With Prime95

Note: Prime95 passing the sticks does not prove that they are good. False negatives are common, but any positive (error) should be treated seriously.

...Summary of the dumps:

Code:

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov  9 22:00:19.630 2011 (UTC - 5:00)
System Uptime: 0 days 0:37:36.474
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+159a3 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_0_Rt64win7+159a3
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov  9 22:37:32.248 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:25.091
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+330bc )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  XSplit.Core.ex
FAILURE_BUCKET_ID:  X64_0x1a_403_VRF_nt!_??_::FNODOBFM::_string_+330bc
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  9 19:02:20.751 2011 (UTC - 5:00)
System Uptime: 0 days 0:12:31.203
Probably caused by : fltmgr.sys ( fltmgr!FltpMoveIrpToCallbackData+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_fltmgr!FltpMoveIrpToCallbackData+17
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  9 04:00:47.418 2011 (UTC - 5:00)
System Uptime: 0 days 13:27:20.496
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for NETIO.SYS - 
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : NETIO.SYS ( NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+3e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+3e
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Nov  9 18:23:26.044 2011 (UTC - 5:00)
System Uptime: 0 days 0:21:22.121
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+56dcd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k+56dcd
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Nov  9 21:07:54.304 2011 (UTC - 5:00)
System Uptime: 0 days 1:19:44.662
Probably caused by : ndis.sys ( ndis!ndisParseReceivedNBL+da )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7f_8_ndis!ndisParseReceivedNBL+da
BiosReleaseDate = 05/10/2011
SystemProductName = TZ68A+
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

It's possible that one of the sticks wasn't seated properly, and removing it and reinstalling it did some good.

Without crashes, there is nothing else we can do. Just keep an eye on the system, and if you get another crash, post back and we'll go from there.