BSOD randomly when sometimes playing Minecraft or on Skype

[Framoman]

Hi,

I keep getting a BSOD randomly when on my PC. I have noticed it happening when on Skype, but it has also happened while playing minecraft so I don't know. I am a first time PC builder and have only had my PC for 2 days, and it has only started this today. When the BSOD flashes up, it says something about a hardware failure. I have run memchecker a couple of times and have passed.

Any help would be much appreciated and I have attached my dump files

Thank you in advance,

Sam

 

[Arc]

Hi Sam.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

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.

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

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.

Let us know about the wattage of your 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.
_____________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80087c5028, bf800000, 124}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80087c5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02feaa58 fffff800`0320b903 : 00000000`00000124 00000000`00000000 fffffa80`087c5028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`02feaa60 fffff800`02da4543 : 00000000`00000001 fffffa80`08809ea0 00000000`00000000 fffffa80`08809ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02feaaa0 fffff800`0320b5c8 : 00000000`00000728 fffffa80`08809ea0 fffff880`02feae30 fffff880`02feae00 : nt!WheaReportHwError+0x263
fffff880`02feab00 fffff800`0320af1a : fffffa80`08809ea0 fffff880`02feae30 fffffa80`08809ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02feac50 fffff800`0320add5 : 00000000`00000004 00000000`00000001 fffff880`02feaeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02feac90 fffff800`031fee88 : fffff880`09ed71b0 00000000`000013f1 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02feacc0 fffff800`02c8d12c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02feacf0 fffff800`02c8cf93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02feae30 fffff960`001862da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`09ed7140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!HANDLELOCK::vLockHandle+0x32


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

3: kd> !errrec fffffa80087c5028
===============================================================================
Common Platform Error Record @ fffffa80087c5028
-------------------------------------------------------------------------------
Record Id     : 01ce8ee211fba2a2
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/1/2013 18:50:22 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80087c50a8
Section       @ fffffa80087c5180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80087c50f0
Section       @ fffffa80087c5240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - bf fb da 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80087c5240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80087c5138
Section       @ fffffa80087c52c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 3 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x000000021dd3cd00
  Misc.       : 0x0000000000000086

 

[Framoman]

Hi Arc,

Thank you for replying!

I tried to do the things you said, and when I ran the "Windows 7: Hardware - Stress Test With Prime95", I blue screened almost instantly. Is this then due to a faulty CPU? I ordered my parts from Scan, and I did buy their ScanSure insurance, so I would be eligible for a replacement for any faulty or damaged part, its just I need to know what is faulty. Anyway, I have attached updated dump files, and hope you can let me know what my fault is.

And btw, my PSU is a Corsair 650w.

Thankyou very much man,

Sam

 

[Arc]

So it is the furmark test that produced an instant BSOD.

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 124[/COLOR], {0, fffffa800885e028, bf800000, 124}

Probably caused by : GenuineIntel

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

I would ask for the Speccy screenshot again.... twice. Once after say one hour of normal run, and one after two hours of normal run.

 

[Framoman]

No, Prime95 caused the BSOD, it also causes my PC to restart sometimes when I run it. Anyway, I will send you my Speccy screenshot, ans I'll post another in an hour.

Thanks again.

 

[Arc]

Lol ... the most dangerous temps are attributed to the GPU ... actually I got stuck with that idea ... so despite of reading the post, typed what came from the unconscious

Dismantle the PC. Clean everything inside there. Clean the air vents, and the fan grills, specially; so that it can blow the hot air out easily. Take special care to the GPU fans.

While re-seating the computer, apply new thermal paste to the CPU.


Now continue to monitor the temps. Let us know those temps.

 

[Framoman]

FYI I was playing games prior to this so that's the cause of the GPU temperature, or should it not be that high anyway? And also I have no thermal paste as my heat-sink came pre applied :/


EDIT

I stopped playing games 5 mins ago, here is attached screenshot of temps

 

[Arc]

I can suggest only, acceptance or refusal is on you

Thermal paste is available in any shop that sells computers etc. Ask for Arctic Silver.

Or, take it to a technician who can do it all for you. But you need to do it.

 

[YoYo155]

Sorry to burge in, but what are the OP CPU temperatures while under load?

 

[Framoman]

Ok Arc, thankyou

And by under load, what would you do to test this?

 

[YoYo155]

Ok Arc, thankyou

And by under load, what would you do to test this?

I saw you tried Prime95.
Does it give you enough time to at least remember, by looking in speccy,
what the temperature is before it bugchecks?

 

[Framoman]

I don't think it's my temperature that is causing any issue, my Speccy showed a max of 73 degrees on my CPU before BSOD. All other components were 30-40 degrees. I think it's hardware failure, but I don't know what hardware.

 

[YoYo155]

What is your full system spec?

Just saw you already stated your PSU.

If it is the VS650w it might not be compatible with the new intel chips
code name "haswell" due to the low sleep and idle state of this new type of processors.

Try going into the BIOS and disabling the C6 & C7 states.

 

[Framoman]

Yeah ahah.

 

[YoYo155]

I'm sorry, I edited my post ^ .

 

[Framoman]

Ok, I'll try that now


Btw it is the tx650m

 

[Framoman]

What setting will these states be listed under, I can't seem to find them :/?

 

[YoYo155]

I'm pretty sure that in the UEFI it's under:

OC> CPU Features> INTEL C-STATES.

 

[Framoman]

Right I have found it. It is disabled anyway, so should I enable it and set its limit to 6??

 

[YoYo155]

The TX650m appears to be compatible with "haswell" so no dice there, no point in changing
anything if its already disabled.

But can you post the Voltage readings, and RAM timings?