BSOD during DOW:DC - SYSTEM SERVICE EXCEPTION

[Pheoxy]

BSOD during playing games.
They have started glitching or freezing for 5 seconds and sometimes the screen would turn off.

I know my computers getting older and it does have a few problems it just needs continuous maintenance, any help would be appreciated because I won't be able to buy anything until I can get a job.

View attachment 291197

EDIT: This might help,

"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff800032ad19c, 0xfffff88007598030, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102613-35053-01."

 

[Arc]

Hi Pheoxy.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus (you may keep dual monitor program and fences .
5. Apply > OK
6. Accept then restart.

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
​

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_________________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800032ad19c, fffff88007598030, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeTerminateThread+314 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032ad19c, Address of the instruction which caused the bugcheck
Arg3: fffff88007598030, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!KeTerminateThread+314
fffff800`032ad19c 488b6d00        mov     rbp,qword ptr [rbp]

CONTEXT:  fffff88007598030 -- (.cxr 0xfffff88007598030)
rax=0000000000000000 rbx=fffffa8019bf8b50 rcx=fffffa800ca6a380
rdx=00fffa8019bf8b58 rsi=fffffa8019bf8b58 rdi=0000000000000000
rip=fffff800032ad19c rsp=fffff88007598a10 rbp=00fffa8019bf8b58
 r8=0000000000000000  r9=0000000000000000 r10=fffff80003449a60
r11=fffff88007598a60 r12=fffff80003448e80 r13=00000000ffffff7f
r14=0000000000000001 r15=fffffa800ca2b100
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
nt!KeTerminateThread+0x314:
fffff800`032ad19c 488b6d00        mov     rbp,qword ptr [rbp] ss:0018:00fffa80`19bf8b58=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Rainmeter.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800035a2008 to fffff800032ad19c

STACK_TEXT:  
fffff880`07598a10 fffff800`035a2008 : 000007ff`fffae000 00000000`00000000 00000000`00000000 fffffa80`19bf8b50 : nt!KeTerminateThread+0x314
fffff880`07598a90 fffff800`035a2531 : fffff880`00000000 fffff800`035c4d00 000007ff`fffae000 00000000`00000000 : nt!PspExitThread+0x418
fffff880`07598b90 fffff800`035a2639 : fffffa80`19bf8b50 00000000`00000000 fffffa80`19bf8b50 00000000`0000ff00 : nt!PspTerminateThreadByPointer+0x4d
fffff880`07598be0 fffff800`032cce53 : fffffa80`19bf8b50 fffff880`07598ca0 00000000`777c45c0 fffffa80`0fb3d4e0 : nt!NtTerminateThread+0x45
fffff880`07598c20 00000000`777117ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`07e2f458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777117ea


FOLLOWUP_IP: 
nt!KeTerminateThread+314
fffff800`032ad19c 488b6d00        mov     rbp,qword ptr [rbp]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KeTerminateThread+314

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

STACK_COMMAND:  .cxr 0xfffff88007598030 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KeTerminateThread+314

BUCKET_ID:  X64_0x3B_nt!KeTerminateThread+314

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

 

[Pheoxy]

I'll give it a go tonight.