BSOD randomly, sysdata.xml

The BSOD is being caused by Panda.
I suggest that you make a system restore point
Uninstall
Boot
Then install Microsoft Security Essentials, at least to test. MSE has never caused a BSOD
If you do not like MSE, Avast is an excellent choice
I have bolded the driver that is the cause of your problem.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_MATTIAS-PC-2015-01-21_174641,92.zip\012115-12932-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`03255890
Debug session time: Wed Jan 21 10:45:23.118 2015 (UTC - 5:00)
System Uptime: 0 days 0:04:58.930
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a00b45502c, 0, fffff880077e5be0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\NNSStrm.sys, Win32 error 0n2
*** 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
---------
2: 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: fffff8a00b45502c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880077e5be0, 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 fffff800032bf100
 fffff8a00b45502c 
FAULTING_IP: 
NNSStrm+36be0
fffff880`077e5be0 488b040a        mov     rax,qword ptr [rdx+rcx]
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88006ff86e0 -- (.trap 0xfffff88006ff86e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffff70000 rbx=0000000000000000 rcx=000007fffff70000
rdx=fffff0a00b4e502c rsi=0000000000000000 rdi=0000000000000000
rip=fffff880077e5be0 rsp=fffff88006ff8878 rbp=fffffa8007139594
 r8=000000000000005a  r9=0000000000000002 r10=fffff88006ff8518
r11=000007fffff70000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
NNSStrm+0x36be0:
fffff880`077e5be0 488b040a        mov     rax,qword ptr [rdx+rcx] ds:ffff:fffff8a0`0b45502c=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80003105bf0 to fffff80003087bc0
STACK_TEXT:  
fffff880`06ff8578 fffff800`03105bf0 : 00000000`00000050 fffff8a0`0b45502c 00000000`00000000 fffff880`06ff86e0 : nt!KeBugCheckEx
fffff880`06ff8580 fffff800`03085cee : 00000000`00000000 fffff8a0`0b45502c 00000000`00000000 fffff8a0`0a6c7b84 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`06ff86e0 fffff880`077e5be0 : fffff880`077cd20d 000007ff`fff70000 fffff8a0`0a6c7b84 00600000`00102000 : nt!KiPageFault+0x16e
fffff880`06ff8878 fffff880`077cd20d : 000007ff`fff70000 fffff8a0`0a6c7b84 00600000`00102000 00000000`00000000 : NNSStrm+0x36be0
fffff880`06ff8880 000007ff`fff70000 : fffff8a0`0a6c7b84 00600000`00102000 00000000`00000000 fffff880`077eb148 : NNSStrm+0x1e20d
fffff880`06ff8888 fffff8a0`0a6c7b84 : 00600000`00102000 00000000`00000000 fffff880`077eb148 fffff880`033e8f40 : 0x7ff`fff70000
fffff880`06ff8890 00600000`00102000 : 00000000`00000000 fffff880`077eb148 fffff880`033e8f40 fffffa80`0a9d60e0 : 0xfffff8a0`0a6c7b84
fffff880`06ff8898 00000000`00000000 : fffff880`077eb148 fffff880`033e8f40 fffffa80`0a9d60e0 00000000`00000082 : 0x600000`00102000
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
NNSStrm+36be0
fffff880`077e5be0 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
Followup: MachineOwner
---------

Once you make the change, submit any additional BSODs that you may get.
The most current BSODs were caused by Panda, even though you mentioned that you made the necessary changes. In fact the most current on Jan 21, was from Panda