0x124 bsod failure, can't tell what it is.

C3ran · 29 Dec 2012

0x124_GenuineIntel_PROCESSOR_BUS_PRV
First bucket_ID stop message, tried resetting the cpu into socket just to make sure, doesn't seem to be overheating.

I wasn't doing anything in particular, running win7 32bit SP1, no new hardware recently added, bios flashed to newest version, Clean install on the os as of last night, possible chipset drivers? I don't really know to be honest. Ran memtest on an earlier bsod on this system, found bad ram, took that out and bsods stopped for that error. Still nothing for these two (in attached file)

Please let me know if anyone needs any additional information.

**Pauly** · 29 Dec 2012

Hello C3ran, Welcome to SF

First off if your OCing in anyway stop, return everything to stock settings for the purposes of testing

If you havent already, fill in your system specs so we know what we are dealing with
System Info - See Your System Specs

Make sure you have read the guide on asking for help with BSOD so you know what we need
https://www.sevenforums.com/crashes-d...tructions.html

Run some scans to check against virus or infection
http://support.kaspersky.com/5350
Windows Defender Offline

Run some basic hardware tests
RAM - Test with Memtest86+
Disk Check (windows based check)
http://www.carrona.org/hddiag.html (bootable disk check)

Both dumps 0x124 BSOD Index Machine check exception
Stop 0x124 - what it means and what to try

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 858418fc, 0, 0}
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: 00000000, Machine Check Exception
Arg2: 858418fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, 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:  0
STACK_TEXT:  
8951fcc4 828dcb2d 858418e0 829738a8 829738a0 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8951fce4 828dd957 829738a0 858418e0 829738d0 nt!WheapProcessWorkQueueItem+0x56
8951fd00 82888a6b 829738a0 00000000 84548a70 nt!WheapWorkQueueWorkerRoutine+0x1f
8951fd50 82a14056 00000001 93681eec 00000000 nt!ExpWorkerThread+0x10d
8951fd90 828bc1a9 8288895e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
0: kd> !errrec [858418fc]
===============================================================================
Common Platform Error Record @ 858418fc
-------------------------------------------------------------------------------
Record Id     : 01cde57a10f03183
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/29/2012 4:08:08 (UTC)
Flags         : 0x00000002 PreviousError
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ 8584197c
Section       @ 85841a54
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x86
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006f6
Processor ID  : 0x0000000000000000
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ 858419c4
Section       @ 85841b14
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000000
CPU Id        : f6 06 00 00 00 08 02 00 - bd e3 00 00 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  @ 85841b14
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 85841a0c
Section       @ 85841b94
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200080000000800

C3ran · 29 Dec 2012

Sorry about not filling my system specs beforehand.

Nothing is overclocked, bios settings are default.
currently the OS is clean, no new drivers save the nvidia driver, and this stop error was occurring before the driver update.

chkdsk resulted in no hard drive issues, and memtest86 was the same with 0 faults after an hour of doing so.

Bios is still the most updated I could get from the asus website, and I guess I don't know what to do from here. I will try to update the chipset drivers from the asus website and reseating all hardware attached to see if that resolves the issue

**Pauly** · 30 Dec 2012

I would recommend running memtest for more than an hour if poss leave overnight and aim to get 5-10 passes with no errors
Have you been monitoring temps, ensure all heatsinks and fans are cleaned out and leave temp monitoring running on your desktop while you do stuff
Try everything else first then if you get stuck remove everything you can that still allows machine to run ie all HDDs except boot, all non essential usb stuff, all but one stick of ram (which can be tried in different slots) and unpopulate pcie slots if poss (dont know if you got on board gfx)

Mains things IMO are temps & ram

C3ran · 30 Dec 2012

It's the temp on my cpu, all of the faults point towards cpu failures, and memtest ran fine w/o faults again overnight, the cpu temp stayed well over 200 on towards a stop because of that, I'm going to mark this as solved, since that seems to be the fault here, the thermal paste is entirely gone from the cpu itself, will put some and replace two fans in the case today which weren't working properly.

Thanks for all of the help here Pauly I owe you one

**Pauly** · 30 Dec 2012

Glad to hear you seem to have it sussed just hope theres no damage to cpu cos that is a pretty high temp, get some new paste and check the cpu fan is ok those sort of temperatures can affect the fan blades and bearings and stuff double check it incase you need to get a new one while your getting the paste.

Any probs post back mate :)