Multiple BSOD's constantly shutting Dell Inspiron 580S down

Lately my computer crashes a few times a day. I also have a Dell Printer v515w Printer that was working fine up until about 2 months ago and now I have to turn the computer off and back on in order to get anything to print. I have attached the debug file from my computer. Computer stats are in my profile. I did download the Reviver Soft Registry Fix and ran it. It fixed over 2,000 registry errors. Thank you!

Sorry for the delay in responding.

We see norton here causing blue screens for you,

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {21, fffff8a01f13c000, 1010, 4000000000001010}

*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Probably caused by : SRTSP64.SYS ( SRTSP64+7f401 )

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

Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: https://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Run Disk Check on your Hard Drive(s): Disk Check

If this does not provide stability and as the last memory dump shows memory errors, test RAM.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\debug-GAIL-DESKTOPPC-Mon_03_17_2014_232612_93\031714-58141-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`030446d0
Debug session time: Tue Mar 18 00:52:28.385 2014 (UTC + 6:00)
System Uptime: 0 days 19:05:45.806
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800695e1d0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800695e1d0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  DataSafeOnline

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ee7d50 to fffff80002e76bc0

STACK_TEXT:  
fffff880`081695f8 fffff800`02ee7d50 : 00000000`0000001a 00000000`00041790 fffffa80`0695e1d0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`08169600 fffff800`02e633df : fffffa80`00000000 00000000`0875ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`081697c0 fffff800`02e75e53 : ffffffff`ffffffff fffff880`08169a90 fffff880`08169a98 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`081698c0 fffff800`02e72410 : fffff800`030f5027 00000000`00000010 00000000`00000086 fffff880`08169a88 : nt!KiSystemServiceCopyEnd+0x13
fffff880`08169a58 fffff800`030f5027 : 00000000`00000010 00000000`00000086 fffff880`08169a88 00000000`00000000 : nt!KiServiceLinkage
fffff880`08169a60 fffff800`0314b1cd : 00000000`08660000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlFreeUserStack+0x27
fffff880`08169a90 fffff800`0314b531 : fffff880`00000000 00000000`050ee100 00000000`7ef8f000 00000000`00000000 : nt!PspExitThread+0x5dd
fffff880`08169b90 fffff800`0314b639 : fffffa80`0e50b060 00000000`00000000 fffffa80`0e50b060 ffffffff`dc3cba00 : nt!PspTerminateThreadByPointer+0x4d
fffff880`08169be0 fffff800`02e75e53 : fffffa80`0e50b060 fffff880`08169ca0 00000000`7ef8f000 fffffa80`0bd2bf00 : nt!NtTerminateThread+0x45
fffff880`08169c20 00000000`771417ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`050ee1a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771417ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`02ee7d50 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.