Reply to thread

Hi Pimsky,


Just to corroborate with what jcgriff2 has said, the first bugcheck argument being 0 in a Stop 0x124 means that it is a processor type error, we can see that it is a Machine Check Exception.

[CODE]1: kd> .bugcheck

Bugcheck code 00000124

Arguments 00000000`00000000 [COLOR=#0000ff]fffffa80`061fa028[/COLOR] 00000000`be200000 00000000`00011152[/CODE]


[CODE]

1: kd> !errrec [COLOR=#0000ff]fffffa80`061fa028[/COLOR]

===============================================================================

Common Platform Error Record @ fffffa80061fa028

-------------------------------------------------------------------------------

Record Id     : 01d158db17951785

Severity      : Fatal (1)

Length        : 928

Creator       : Microsoft

Notify Type   : [COLOR=#ffa07a]Machine Check Exception[/COLOR]

Timestamp     : 1/27/2016 23:40:42 (UTC)

Flags         : 0x00000000



===============================================================================

Section 0     : Processor Generic

-------------------------------------------------------------------------------

Descriptor    @ fffffa80061fa0a8

Section       @ fffffa80061fa180

Offset        : 344

Length        : 192

Flags         : 0x00000001 Primary

Severity      : Fatal



Proc. Type    : x86/x64

Instr. Set    : x64

Error Type    : Cache error

Operation     : Instruction Execute

Flags         : 0x00

Level         : 2

CPU Version   : 0x00000000000206a7

Processor ID  : 0x0000000000000001



===============================================================================

Section 1     : x86/x64 Processor Specific

-------------------------------------------------------------------------------

Descriptor    @ fffffa80061fa0f0

Section       @ fffffa80061fa240

Offset        : 536

Length        : 128

Flags         : 0x00000000

Severity      : Fatal



Local APIC Id : 0x0000000000000001

CPU Id        : a7 06 02 00 00 08 10 01 - ff e3 ba 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  @ fffffa80061fa240



===============================================================================

Section 2     : x86/x64 MCA

-------------------------------------------------------------------------------

Descriptor    @ fffffa80061fa138

Section       @ fffffa80061fa2c0

Offset        : 664

Length        : 264

Flags         : 0x00000000

Severity      : [COLOR=#ff0000]Fatal[/COLOR]



Error         :[COLOR=#ee82ee] I[/COLOR]CACHE[COLOR=#ff8c00]L2[/COLOR]_[COLOR=#00ffff]IRD[/COLOR]_ERR (Proc 1 Bank 7)

  Status      : 0xbe20000000011152

  Address     : 0x00000000430dbd40

  Misc.       : 0x0000007022004086



[/CODE]


Since you already ran Prime95 and experienced the crash again shortly after, that would suggest hardware failure; certainly sounds like overheating based on your description. You're already on the latest BIOS version for your laptop (68SVD Ver. F.60), and your CPU isn't overclocked:

[CODE]1: kd> !sysinfo cpuspeed

CPUID:        "Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz"

MaxSpeed:     2300

CurrentSpeed: [COLOR=#008000]2294[/COLOR][/CODE]


Given the age of the laptop, it seems like a safe assumption that you're well out of warranty. Depending on how comfortable you are with computers, you could try taking apart your laptop and seeing if the vents/CPU fan need to be cleaned. If it's very dusty in there, it could be causing you to overheat. HP's recommendation is just to blow compressed air into the vents, but it would be more thorough to take the back plate off and carefully remove any visible dust in the CPU fan or in the vents.


Back
Top