BSOD every +- 3 Days ERROR 0x0000007B

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800738a028, be000000, 800400}

Probably caused by : GenuineIntel

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

0: 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: fffffa800738a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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:  wmplayer.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`035fda3b : 00000000`00000124 00000000`00000000 fffffa80`0738a028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`03190633 : 00000000`00000001 fffffa80`07217ea0 00000000`00000000 fffffa80`07217ef0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`035fd700 : 00000000`00000728 fffffa80`07217ea0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`035fd052 : fffffa80`07217ea0 fffff800`00ba8e70 fffffa80`07217ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`035fcf0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`035f0e88 : 00000000`00000000 00000000`5cf8476c 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`0307852c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`03078393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`5d0768f3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0934f500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5d0768f3


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

0: kd> !errrec fffffa800738a028
===============================================================================
Common Platform Error Record @ fffffa800738a028
-------------------------------------------------------------------------------
Record Id     : 01ce2f6e8a71aa02
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/2/2013 11:01:15 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : a7 06 02 00 00 08 10 00 - bf e3 9a 1f 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  @ fffffa800738a240

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

Error         : Internal timer (Proc 0 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x000000005d0768f3
  Misc.       : 0x0000000000000000

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy

King k said:

Thanks. I thought about Power... But ya. No one can supply surety to that theory.

If you thought about power, check it using eXtreme Power Supply Calculator. It will tell you the power required and the power actually being supplied.

King k said:

;-) Shot!

Make it a bit long then?

You would have to check the SSD mfg "Corsair website" for that :)

SSD Firmware Update - The Corsair Support Forums

Corsair

King k said:

It came to 654Watt TOTAL and recommended Corsair's 750Watt.

I currently have 750Watt Cooler Master GX

PS. What Firmware does the SSD need?

And, this result kinda shows that your PSU is not performing upto the mark. Plan to have a bigger one, as the recommendation is 750 watts total?