Frequent BSOD problem

Yes, Intel(R) Dual Band Wireless-AC 7260 is failing there, despite of having up-to date drivers. Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

BTW, I see that Daemon tools is still installed there. May be you are not paying attention to it? And startup items are not reduced too.

What are the results of the tests we suggested earlier?

It is network failures over the last three updates. We have seen the same earlier too, a few times, that network is failing without adequate cause. You may go through those discussions if you want.

Software- or Configuration-related Crashes
BOSD after clean up

In the mean time, perform the following tests .....

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the CPU.
Hardware - Stress Test With Prime95

BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, fffff88001a598bd}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001a598bd, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b8100
GetUlongFromAddress: unable to read from fffff800030b81c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!IppProcessDeliverList+dd
fffff880`01a598bd 6c              ins     byte ptr [rdi],dx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9bbb0 -- (.trap 0xfffff80000b9bbb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8015f96640 rbx=0000000000000000 rcx=0000000000000004
rdx=fffff88001b68128 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001a598bd rsp=fffff80000b9bd40 rbp=fffff88001b69800
 r8=fffff88001b69800  r9=fffff88001b6e9a0 r10=0000000000000010
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!IppProcessDeliverList+0xdd:
fffff880`01a598bd 6c              ins     byte ptr [rdi],dx ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e80129 to fffff80002e80b80

STACK_TEXT:  
fffff800`00b9ba68 fffff800`02e80129 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9ba70 fffff800`02e7eda0 : fffff880`0664d600 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9bbb0 fffff880`01a598bd : 00000000`00000000 fffff880`01b69800 fffff800`00b9be40 fffff880`05930627 : nt!KiPageFault+0x260
fffff800`00b9bd40 fffff880`01a58e39 : 000000f4`00870000 fffff800`00b9beb1 fffff800`00b9be30 fffff800`00b9be30 : tcpip!IppProcessDeliverList+0xdd
fffff800`00b9bde0 fffff880`01a56adf : 00000000`00000000 00000000`16682401 fffff880`01b69800 fffff880`01b69800 : tcpip!IppReceiveHeaderBatch+0x23a
fffff800`00b9bec0 fffff880`01a560b2 : fffffa80`16681b80 00000000`00000000 fffffa80`16682401 00000000`00000007 : tcpip!IpFlcReceivePackets+0x64f
fffff800`00b9c0c0 fffff880`01a554da : fffffa80`16682460 fffff800`00b9c1f0 fffffa80`16682460 00000000`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff800`00b9c1a0 fffff800`02e8c878 : fffffa80`165e2670 00000000`00004800 fffff800`03009cc0 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff800`00b9c1f0 fffff880`01a55bd2 : fffff880`01a55400 00000000`00000000 fffffa80`14249b02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff800`00b9c2d0 fffff880`018c20eb : fffffa80`1668a8d0 00000000`00000000 fffffa80`163bd1a0 fffffa80`163bd1a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff800`00b9c340 fffff880`0188bad6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff800`00b9c3b0 fffff880`01805ac1 : fffffa80`163bd1a0 00000000`00000002 00000000`00000007 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff800`00b9c830 fffff880`052cac84 : fffffa80`16572000 00000000`00000000 00000000`00000000 fffffa80`165e2670 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff800`00b9c880 fffffa80`16572000 : 00000000`00000000 00000000`00000000 fffffa80`165e2670 fffffa80`00000001 : Rt64win7+0x1ac84
fffff800`00b9c888 00000000`00000000 : 00000000`00000000 fffffa80`165e2670 fffffa80`00000001 fffff880`01a674d0 : 0xfffffa80`16572000


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !tcpip
    fffff88001a598bc - tcpip!IppProcessDeliverList+dc
    [ 8b:9b ]
1 error : !tcpip (fffff88001a598bc)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

0: kd> lmvm rt64win7
start             end                 module name
fffff880`052b0000 fffff880`05382000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Wed Apr 10 08:30:34 2013 (5164D5D2)
    CheckSum:         000DB44C
    ImageSize:        000D2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It is not an unique situation. Many a times it is seen that when more than two DIMMs are occupied the computer BSODs, despite of all RAMs are individually good.

That is an issue of the motherboard's part only. If it is a must for you to use more than two RAM sticks, contract the board manufacturer and RMA it.