Random and persistent BSOD's

coldcrankcase · 06 Apr 2014

I am having repeated blue screens on my Samsung laptop. I have freshly reinstalled Windows 7 Home Premium, gone through the entire driver list and tried my best to install and update everything properly, and I still get near constant BSOD's, sometimes as frequently as 15 seconds apart. I have no clue what the problem is, but attached is the SF grab all thingy. Ideas? Oh, yeah, here are my system specs:
Operating System
Windows 7 Home Premium 64-bit SP1
CPU
Intel Core i7 3610QM @ 2.30GHz 43 °C
Ivy Bridge 22nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard
SAMSUNG ELECTRONICS CO., LTD. SAMSUNG_NP1234567890 (SOCKET 0) 48 °C
Graphics
SAMSUNG (1920x1080@60Hz)
2047MB NVIDIA GeForce GTX 675M (Samsung) 50 °C
Storage
7GB SanDisk iSSD P4 8GB ATA Device (SSD)
698GB Hitachi HTS727575A9E364 ATA Device (SATA) 28 °C
698GB Hitachi HTS727575A9E364 ATA Device (SATA) 38 °C
Optical Drives
MagicISO Virtual DVD-ROM0000
Slimtype BD E DS6E2SH ATA Device
Audio
Realtek High Definition Audio
Network
Intel Centrino Advanced-N 6235

koolkat77 · 06 Apr 2014

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\Scrotorius Rex_06-04-2014\040614-37596-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`032476d0
Debug session time: Mon Apr  7 05:02:55.111 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:49.016
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e058028, fe200000, 11136}

Probably caused by : GenuineIntel

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

5: 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: fffffa800e058028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000011136, 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:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`03091b58 fffff800`035fba3b : 00000000`00000124 00000000`00000000 fffffa80`0e058028 00000000`fe200000 : nt!KeBugCheckEx
fffff880`03091b60 fffff800`03190463 : 00000000`00000001 fffffa80`0d77aa10 00000000`00000000 fffffa80`0d77aa60 : hal!HalBugCheckSystem+0x1e3
fffff880`03091ba0 fffff800`035fb700 : 00000000`00000728 fffffa80`0d77aa10 fffff880`03091f30 fffff880`03091f00 : nt!WheaReportHwError+0x263
fffff880`03091c00 fffff800`035fb052 : fffffa80`0d77aa10 fffff880`03091f30 fffffa80`0d77aa10 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03091d50 fffff800`035faf0d : 00000000`00000008 00000000`00000001 fffff880`03091fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03091d90 fffff800`035eee88 : 00000000`00000002 fffff880`03089180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03091dc0 fffff800`030784ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03091df0 fffff800`03078313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03091f30 fffff880`03e7bc61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`030b1b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19


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

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 - What it means and what to try

Thedoctor44 · 08 Apr 2014

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e011028, be200000, 5110a}

Probably caused by : hardware

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

4: kd> !errrec fffffa800e011028
===============================================================================
Common Platform Error Record @ fffffa800e011028
-------------------------------------------------------------------------------
Record Id     : 01cf51e345c57425
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/6/2014 21:59:06
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e0110a8
Section       @ fffffa800e011180
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         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000004

The machine check indicates the CPU has found a hardware fault in the computer which caused the PC to crash. The Cache error generally means the CPU is at fault.
Can you please stress test your CPU by running Prime95 by following these instructions.

Hardware - Stress Test With Prime95

coldcrankcase · 08 Apr 2014

Ok, so I ran the Prime95 stress test and the computer crashed the first time within a few minutes of starting the test. The second time I ran the test, it froze up within about 15 minutes. Holy crap, does this mean I need to replace the processor? That's going to be a mean trick on this laptop....

Any further ideas? Thank you!

Thedoctor44 · 09 Apr 2014

Yes, that sounds definitely like a CPU issue.
You might be able to replace the CPU in your laptop but that depends on your motherboard as well, unfortunately I don't have the time to go looking for which CPUs you can get as I'm really busy.
You could visit this section of the forums and ask if you can get a replacement.

Hardware & Devices - Windows 7 Help Forums

When you get a new CPU post back here the results and if you're confident the issue has been solved then mark the thread as solved.