Random BSODs 0x1000007e, ffffffff`c0000005

Hi Dot.

The crash dump is not providing enough information. But based on the bugcheck code, I think you should do the following:

Make it sure that the SSD is running with the latest firmware.
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

The BIOS is old.

Code:

BiosVersion = 6.00 PG
BiosReleaseDate = 04/17/2009

Plan to update it, if possible.
EVGA | Support | Product Specs

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.

Let us know the results.
______________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800028d8b46, fffff8800338c8e8, fffff8800338c140}

Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800028d8b46, The address that the exception occurred at
Arg3: fffff8800338c8e8, Exception Record Address
Arg4: fffff8800338c140, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!PspReturnQuota+46
fffff800`028d8b46 488b5d00        mov     rbx,qword ptr [rbp]

EXCEPTION_RECORD:  fffff8800338c8e8 -- (.exr 0xfffff8800338c8e8)
ExceptionAddress: fffff800028d8b46 (nt!PspReturnQuota+0x0000000000000046)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

CONTEXT:  fffff8800338c140 -- (.cxr 0xfffff8800338c140)
rax=0000000000000000 rbx=ffdff80002a57940 rcx=ffdff80002a57940
rdx=0000000000000000 rsi=0000000000000000 rdi=00000000000004a8
rip=fffff800028d8b46 rsp=fffff8800338cb20 rbp=ffdff80002a57940
 r8=fffff80002854000  r9=00000000000004a8 r10=0000000000000000
r11=fffff80002a57940 r12=fffffa800a2e0f30 r13=0000000000000000
r14=0000000000000000 r15=fffffa8019ee3b00
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!PspReturnQuota+0x46:
fffff800`028d8b46 488b5d00        mov     rbx,qword ptr [rbp] ss:0018:ffdff800`02a57940=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  ffffffffffffffff

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b01100
 0000000000000000 

FOLLOWUP_IP: 
nt!PspReturnQuota+46
fffff800`028d8b46 488b5d00        mov     rbx,qword ptr [rbp]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002c00693 to fffff800028d8b46

STACK_TEXT:  
fffff880`0338cb20 fffff800`02c00693 : ffdff800`02a57940 00000000`000004a8 fffffa80`19ee3b00 00000000`00000d05 : nt!PspReturnQuota+0x46
fffff880`0338cba0 fffff800`02bc0576 : fffffa80`19ee3b20 fffff800`02b9db97 fffffa80`158403d0 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x14910
fffff880`0338cbd0 fffff800`028d2e5c : 00000000`00000000 00000000`00000000 fffffa80`0a2e0f30 fffffa80`19ee3b20 : nt!ObpFreeObject+0x266
fffff880`0338cc20 fffff800`028a8cc0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff6fc`40056998 : nt!ObfDereferenceObject+0xdc
fffff880`0338cc80 fffff800`028d3261 : fffff800`028a8c10 fffff800`02a6f330 fffffa80`0a359b50 00000000`00000000 : nt!PspReaper+0xb0
fffff880`0338ccb0 fffff800`02b662ea : 00000000`00000000 fffffa80`0a359b50 00000000`00000080 fffffa80`0a345040 : nt!ExpWorkerThread+0x111
fffff880`0338cd40 fffff800`028ba8e6 : fffff880`03186180 fffffa80`0a359b50 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0338cd80 00000000`00000000 : fffff880`0338d000 fffff880`03387000 fffff880`0338c9e0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!PspReturnQuota+46

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

STACK_COMMAND:  .cxr 0xfffff8800338c140 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!PspReturnQuota+46

BUCKET_ID:  X64_0x7E_nt!PspReturnQuota+46

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

OK, let us know how it goes.