Random BSODs with random intervals (have files from SF diagnostics)

[justicar]

Getting random BSODS from 5 times a week to 2 times a week to 0 times a week its really random and i hope the files can describe the issue.

 

[Arc]

Hi justicar.

Uninstall Panda Free Antivirus using the tool supplied here.

Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Let us know for any further BSOD.
______________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0120b202c, 0, fffff88006643be0, 0}

*** WARNING: Unable to verify timestamp for NNSStrm.sys
*** ERROR: Module load completed but symbols could not be loaded for NNSStrm.sys

Could not read faulting driver name
Probably caused by : NNSStrm.sys ( NNSStrm+36be0 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0120b202c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88006643be0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003303100
GetUlongFromAddress: unable to read from fffff800033031c0
 fffff8a0120b202c Paged pool

FAULTING_IP: 
NNSStrm+36be0
fffff880`06643be0 488b040a        mov     rax,qword ptr [rdx+rcx]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  fffff880009d76e0 -- (.trap 0xfffff880009d76e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffff60000 rbx=0000000000000000 rcx=000007fffff60000
rdx=fffff0a01215202c rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006643be0 rsp=fffff880009d7878 rbp=fffffa8006ee88e4
 r8=000000000000005a  r9=0000000000000002 r10=fffff880009d7518
r11=000007fffff60000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
NNSStrm+0x36be0:
fffff880`06643be0 488b040a        mov     rax,qword ptr [rdx+rcx] ds:fffff8a0`120b202c=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003149bf0 to fffff800030cbbc0

STACK_TEXT:  
fffff880`009d7578 fffff800`03149bf0 : 00000000`00000050 fffff8a0`120b202c 00000000`00000000 fffff880`009d76e0 : nt!KeBugCheckEx
fffff880`009d7580 fffff800`030c9cee : 00000000`00000000 fffff8a0`120b202c 00000000`00000000 fffff8a0`0b2eca74 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`009d76e0 fffff880`06643be0 : fffff880`0662b20d 000007ff`fff60000 fffff8a0`0b2eca74 00800000`00102000 : nt!KiPageFault+0x16e
fffff880`009d7878 fffff880`0662b20d : 000007ff`fff60000 fffff8a0`0b2eca74 00800000`00102000 00000000`00000000 : NNSStrm+0x36be0
fffff880`009d7880 000007ff`fff60000 : fffff8a0`0b2eca74 00800000`00102000 00000000`00000000 fffff880`06649148 : NNSStrm+0x1e20d
fffff880`009d7888 fffff8a0`0b2eca74 : 00800000`00102000 00000000`00000000 fffff880`06649148 fffff880`02f69f40 : 0x000007ff`fff60000
fffff880`009d7890 00800000`00102000 : 00000000`00000000 fffff880`06649148 fffff880`02f69f40 fffffa80`0837c580 : 0xfffff8a0`0b2eca74
fffff880`009d7898 00000000`00000000 : fffff880`06649148 fffff880`02f69f40 fffffa80`0837c580 fffff880`009d7930 : 0x00800000`00102000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NNSStrm+36be0
fffff880`06643be0 488b040a        mov     rax,qword ptr [rdx+rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NNSStrm+36be0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NNSStrm

IMAGE_NAME:  NNSStrm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  538f2f31

FAILURE_BUCKET_ID:  X64_0x50_NNSStrm+36be0

BUCKET_ID:  X64_0x50_NNSStrm+36be0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_nnsstrm+36be0

FAILURE_ID_HASH:  {6ada0785-3aeb-c530-c162-17677b7102cc}

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

1: kd> lmvm NNSStrm
start             end                 module name
fffff880`0660d000 fffff880`06653000   NNSStrm  T (no symbols)           
    Loaded symbol image file: NNSStrm.sys
    Image path: \SystemRoot\system32\DRIVERS\NNSStrm.sys
    Image name: NNSStrm.sys
    Timestamp:        Wed Jun 04 20:07:37 2014 (538F2F31)
    CheckSum:         0004AEEE
    ImageSize:        00046000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4