BSOD after installing new cpu fan??

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

The BSODs are indicating to memory corruption, though. So let us have a test?

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.

Stress test the CPU.
Hardware - Stress Test With Prime95

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 .

Let us know.
__________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffb22938a90b8, 0, fffff800035f23e0, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+2b0 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffb22938a90b8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800035f23e0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003701100
GetUlongFromAddress: unable to read from fffff800037011c0
 fffffb22938a90b8 Nonpaged pool

FAULTING_IP: 
nt!MiGetWorkingSetInfo+2b0
fffff800`035f23e0 498b4228        mov     rax,qword ptr [r10+28h]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88010e25760 -- (.trap 0xfffff88010e25760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff680000af004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800035f23e0 rsp=fffff88010e258f0 rbp=fffff88010e25b60
 r8=fffff88010c1fcc0  r9=fffff7000109f180 r10=fffffb22938a9090
r11=fffff700010b1f38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiGetWorkingSetInfo+0x2b0:
fffff800`035f23e0 498b4228        mov     rax,qword ptr [r10+28h] ds:fffffb22`938a90b8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000354653b to fffff800034c9bc0

STACK_TEXT:  
fffff880`10e255f8 fffff800`0354653b : 00000000`00000050 fffffb22`938a90b8 00000000`00000000 fffff880`10e25760 : nt!KeBugCheckEx
fffff880`10e25600 fffff800`034c7cee : 00000000`00000000 fffffb22`938a90b8 00000000`00000000 fffffa80`06acd670 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`10e25760 fffff800`035f23e0 : fffff880`10e25b60 00000000`00000000 00000000`00000070 fffff880`00000000 : nt!KiPageFault+0x16e
fffff880`10e258f0 fffff800`03829a25 : 00000000`fffeffff 00000000`119d1001 fffffa80`06acd670 fffffa80`00000001 : nt!MiGetWorkingSetInfo+0x2b0
fffff880`10e25980 fffff800`034c8e53 : 00000000`00001610 fffffa80`06acd670 00000000`00000000 00000000`0564e1a8 : nt! ?? ::NNGAKEGL::`string'+0x4c5f3
fffff880`10e25a70 00000000`76ec14ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0564e188 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ec14ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetWorkingSetInfo+2b0
fffff800`035f23e0 498b4228        mov     rax,qword ptr [r10+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiGetWorkingSetInfo+2b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+2b0

BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+2b0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_nt!migetworkingsetinfo+2b0

FAILURE_ID_HASH:  {8a7a1726-eb26-0c5c-558a-74066c003dba}

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

Unfortunately it detected failure.

Attachment 303477

You have to replace the CPU. If it is within warranty, RMA it.