Random BSOD

The crash dumps are blaming hardware for the issue. Let us check the basic hardware components.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.

How To Clear CMOS (Reset BIOS)

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts

Also let us know the wattage of the installed PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

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

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.

Hardware - Stress Test With Prime95

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Let us know the results.
_______________________________________________________

Code:

BugCheck A, {ffffffffffffff88, 2, 1, fffff80002ed9656}

Probably caused by : hardware ( nt!KiProcessExpiredTimerList+156 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffff88, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ed9656, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
GetUlongFromAddress: unable to read from fffff8000310a1c0
 ffffffffffffff88 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiProcessExpiredTimerList+156
fffff800`02ed9656 ff4885          dec     dword ptr [rax-7Bh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFF88002D93FB0

TRAP_FRAME:  fffff88002d8c450 -- (.trap 0xfffff88002d8c450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa800dc3952f
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed9656 rsp=fffff88002d8c5e0 rbp=fffffa800dc39638
 r8=fffff88002d66301  r9=0000000000000002 r10=000000000000006a
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiProcessExpiredTimerList+0x156:
fffff800`02ed9656 ff4885          dec     dword ptr [rax-7Bh] ds:ffffffff`ffffff88=????????
Resetting default scope

MISALIGNED_IP: 
nt!KiProcessExpiredTimerList+156
fffff800`02ed9656 ff4885          dec     dword ptr [rax-7Bh]

LAST_CONTROL_TRANSFER:  from fffff80002ecce69 to fffff80002ecd8c0

STACK_TEXT:  
fffff880`02d8c308 fffff800`02ecce69 : 00000000`0000000a ffffffff`ffffff88 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02d8c310 fffff800`02ecbae0 : 00000000`00000000 00000000`00000003 00000000`02000000 fffffa80`0dc3ff38 : nt!KiBugCheckDispatch+0x69
fffff880`02d8c450 fffff800`02ed9656 : fffffa80`0dc395f0 fffffa80`0de054d8 fffffa80`0de054d8 00000000`00000102 : nt!KiPageFault+0x260
fffff880`02d8c5e0 fffff800`02ed94ae : 0000000d`c3f67102 fffff880`02d8cc58 00000000`0005c86a fffff880`02d672c8 : nt!KiProcessExpiredTimerList+0x156
fffff880`02d8cc30 fffff800`02ed9297 : 00000004`922809c1 00000004`0005c86a 00000004`922809c8 00000000`0000006a : nt!KiTimerExpiration+0x1be
fffff880`02d8ccd0 fffff800`02ec55ca : fffff880`02d64180 fffff880`02d6efc0 00000000`00000000 fffff880`0464a4d0 : nt!KiRetireDpcList+0x277
fffff880`02d8cd80 00000000`00000000 : fffff880`02d8d000 fffff880`02d87000 fffff880`02d8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiProcessExpiredTimerList+156
fffff800`02ed9656 ff4885          dec     dword ptr [rax-7Bh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiProcessExpiredTimerList+156

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  6.1.7601.18839

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned

FAILURE_ID_HASH:  {45769616-fd06-8c70-4b8b-74a01eddc0cd}

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

The crash dumps are not providing anything based on which we may blame Twitch. But as the user, you must understand it rightly. So, as you are feeling that the issue is with Twitch and nothing else, then I go with it.

Unfortunately we will not be able to troubleshoot an external thing causing code corruption to the system. I would suggest you to stay away from Twitch.