BSOD after installing new cpu fan??

[alexhinbest]

i have no idea whats going, i scanned for any virus problems, latest norton 360 couldnt find any, used a nimda virus recovery tool (as it now has difficulties installing programs and sometimes chrome fails, although its working for now) and nothing can find any malicious software, here is the latest bsod details, i really need to get to the bottom of this, i haven no idea what is going wrong
thanks guys

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 50
BCP1: FFFFF683BF7A2E80
BCP2: 0000000000000000
BCP3: FFFFF800034B755B
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\012614-40529-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-95082-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[alexhinbest]

my pc:
windows 7 professional, 64 bit
nvidia 760 gtx
asus mobo
i5 overclocked to 4.1ghz

 

[Arc]

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

 

[alexhinbest]

View attachment 303472

 

[alexhinbest]

View attachment 303473

the first one might not have all the info but this one should do

 

[Arc]

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: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Let us know.
__________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        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
---------

 

[alexhinbest]

everything seems fine temperature wise

http://speccy.piriform.com/results/mSmV0mTABIXZjHPJl47uIPR

 

[alexhinbest]

View attachment 303475

heres the stress test

 

[Arc]

Unfortunately it detected failure.

View attachment 303477

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

 

[alexhinbest]

seriously? just like that, the cpu seems to be working fine??? it will cost a buttload to replace, just because one program detects failure, even though surely if it is busted, my pc wouldnt work??? there must be ways to validate this, other than one program and one person's evaluation? im not trying to be rude, its just cpu's are expensive and why would it just up and break? its been completely reliable up to this point and still appears to work fine.

 

[alexhinbest]

i am doing another stress test, this time making sure all the values are how they should be as suggested by the forum post about it

 

[alexhinbest]

20 tests have occurred now with no fails on the settings recommended on the thread. cpu temp is peaking at 67 degrees C, all cores are confirmed to be running the full 100% of their capacity, havent had a blue screen for a while now, after this i will test the RAM. how long should i be running this cpu torture tests for?

 

[Arc]

3 or 4 hours.

 

[alexhinbest]

i cant get the memory test to work with my usb stick, even though i followed the instructions explicitly

 

[Arc]

There are other options too. Using CD.

And, better you should have posted a screenshot of the test that made you sure that the CPU is not failing. We have seen the otherwise only.

 

[alexhinbest]

its just i gave up waiting after 25 or so successful tests for all the cores, it just seemed to be pointless waiting for another 20 or another 50, but i will run in it again at some point soon and will screenshot the results. i don't have a CD handy, why isn't the usb version running? it starts to boot then just doesn't do anything saying something like "x86" "off" at the bottom where it should be running the tests. the drive was formatted correctly and was fully working before this point. any suggestions?

 

[ICIT2LOL]

My 2 cents worth is I would strongly advise you get a CD and do that memtest. CD's are not hard to get and so cheap as opposed to anew CPU and you might just end up getting RAM instead of the CPU.

Arc has pointed out some error areas in the CPU and eliminating the RAM as a problem is going to make it a little easier to finger the problem.

My thoughts are maybe the CPU is faulty crap happens with anything in life. Just because a car comes off the production line looking like and working in perfect condition doesn't mean it is not flawed in some area and going to fail sooner or later.

I can see where you are coming from and I would be really ticked off too but those are the chances we all take with anything. But again that memtest is a priority.

 

[A Guy]

Your 2nd post indicates an overclock

i5 overclocked to 4.1ghz

Have you set the CPU back to stock settings to see if that is an issue? Resetting your BIOS to default settings might also eliminate any changes made. CPUs can fail, just as memory and/or Mother Boards. I personally had a 24/7 overclock for 3 years that started causing issues. Resetting the overclock has resulted in no errors since. A Guy

 

[Britton30]

Correct if you've overclocked with setting a few other things, voltage, LLC, Offset, etc., those will cause Prime to fail, it doesn't mean the CPU is faulty, only the settings. Crank it back to default setting as A Guy suggests.

FWIW, the tests in Prime are not all the same, each group of 20-25 uses different values so it is generally recommended to run it 24 hours, I personally think 8 is enough. Keep an eye on temps too. 90C max.

 

[alexhinbest]

ok thanks for all your suggestions guys, i will first try to get a memtest cd burned to check that RAM, but i yesterday i did swap the ram from the original two mobo slots to the other adjacent slots that have never been used and have not had a bsod since. however, i dont think this has for real solved the problem so i will check that ram. if the cpu does still experience problems in the second prime test then i will consider returning it to its original clock setttings