0x0000001A (BSOD)

I'm seeing a generic memory management error here, this could indicate that the memory has physically gone bad.
Testing it is simple enough but requires some time (as you need to allow for 5 to 7 passes of the test to get a reliable result)

To do that follow the instructions at the following link:
RAM - Test with Memtest86+

it is best to simply allow the test to run overnight or while you are at work or school to give it enough time to perform 5 to 7 passes.
base debugger info follows:

Code:

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000058
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  nvSCPAPISvr.ex

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880083e2620 -- (.trap 0xfffff880083e2620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880083e2828 rbx=0000000000000000 rcx=0000000000000008
rdx=fffff880083e27e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b3f970 rsp=fffff880083e27b0 rbp=000000000a000000
 r8=0000000000000000  r9=fffffa8005951060 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReleaseConfirmedPageFileSpace+0x40:
fffff800`02b3f970 4c8b6e58        mov     r13,qword ptr [rsi+58h] ds:00000000`00000058=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a2db9a to fffff80002a81700

STACK_TEXT:  
fffff880`083e24b8 fffff800`02a2db9a : 00000000`0000001a 00000000`00041287 00000000`00000058 00000000`00000000 : nt!KeBugCheckEx
fffff880`083e24c0 fffff800`02a7f7ee : 00000000`00000000 00000000`00000408 fffffa80`04aa1900 00000000`00000801 : nt! ?? ::FNODOBFM::`string'+0x42b65
fffff880`083e2620 fffff800`02b3f970 : 00000000`00000001 00000000`00001000 fffff700`01080000 fffffa80`03074640 : nt!KiPageFault+0x16e
fffff880`083e27b0 fffff800`02af4f48 : 0a000000`00020070 55555555`55555555 00000000`00000408 00000000`10238000 : nt!MiReleaseConfirmedPageFileSpace+0x40
fffff880`083e2830 fffff800`02ab4e79 : 00000000`00000000 00000000`1039ffff fffffa80`00000000 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x33758
fffff880`083e29f0 fffff800`02d98f20 : fffffa80`0735a780 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`083e2b10 fffff800`02d9932b : 00000980`00000000 00000000`10000000 fffffa80`00000001 fffffa80`05732860 : nt!MiUnmapViewOfSection+0x1b0
fffff880`083e2bd0 fffff800`02a80953 : 00000000`00000000 00000000`00000001 fffffa80`05951060 00000000`00000004 : nt!NtUnmapViewOfSection+0x5f
fffff880`083e2c20 00000000`773af95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00cde808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773af95a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42b65
fffff800`02a2db9a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42b65

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42b65

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42b65

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

MarkJ said:

Memtest can miss minor faults so try running the PC on one memory stick at a time. Use memory intensive programs like low level games or watching/transcoding video for at least three to four hours with each stick, you may find that one of them will cause a crash.

The error codes can also relate to a faulty driver, did you install anything new just before the crashes started, new software, hardware, driver updates, etc?

You should also switch on Windows Update from the Control Panel, you should be on SP1 by now.

Driver verifier could also route out a possible driver conflict.
I just don't like suggesting it since it very often leaves the pc unbootable if there is a major driver issue.