2016/08/03 02:10:41
Sajin
None of those .dmp files contain the 124 blue screen code. If you get a blue screen containing the 124 error code please upload that one.
2016/08/03 03:46:10
Sushihunter
Hey, I found the dmp file you wanted 
 
http://sabercathost.com/2GHi/080116-49904-01.dmp
 
2016/08/03 07:47:46
Sushihunter
2016/08/03 07:53:34
Cool GTX
Sushihunter
Got a new one for you...
 
http://sabercathost.com/1QGT/080316-52494-01.dmp
 


Morning
 
Did you do the "BIOS Dance"  ---- my post #56 ?
2016/08/03 08:33:04
Sushihunter
Cool GTX
Sushihunter
Got a new one for you...
 
http://sabercathost.com/1QGT/080316-52494-01.dmp
 

Morning
 
Did you do the "BIOS Dance"  ---- my post #56 ?




Hi: No, haven't had a chance yet, hopefully I can do it later tonight.
Having had a number of Asus MB's over the years, I quite agree about the Asus BIOS "issues".
 
Thanks!
2016/08/03 10:59:57
Sajin
Ok, I checked out the .dmp file with windbg and this is what I found...
 
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 8d9c98fc, 0, 0}
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: 00000000, Machine Check Exception
Arg2: 8d9c98fc, 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:
------------------

DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.23455.x86fre.win7sp1_ldr.160516-0600
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: ffffffff8d9c98fc
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x124_GenuineIntel
CPU_COUNT: 4
CPU_MHZ: 965
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: f
CPU_STEPPING: b
CPU_MICROCODE: 6,f,b,0 (F,M,S,R) SIG: B6'00000000 (cache) 0'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-RCO722P
ANALYSIS_SESSION_TIME: 08-03-2016 12:04:16.0886
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
88b85cc4 831267f7 8d9c98e0 831c0208 831c0200 nt!WheapCreateTriageDumpFromPreviousSession+0x32
88b85ce4 83127625 831c0200 8d9c98e0 831c0230 nt!WheapProcessWorkQueueItem+0x56
88b85d00 830d230b 831c0200 00000000 85dea030 nt!WheapWorkQueueWorkerRoutine+0x1f
88b85d50 8326145b 00000001 b9629f16 00000000 nt!ExpWorkerThread+0x10d
88b85d90 831059c9 830d21fe 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 66ca5dd7f6e07821a2bd4ba174d8a04fd8c5c006
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d73e5cc55c44b167f77894430e6ee2a68dcaef20
THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV
PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_BUS_PRV
TARGET_TIME: 2016-08-02T05:39:07.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x86
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-05-16 16:11:27
BUILDDATESTAMP_STR: 160516-0600
BUILDLAB_STR: win7sp1_ldr
BUILDOSVER_STR: 6.1.7601.23455.x86fre.win7sp1_ldr.160516-0600
ANALYSIS_SESSION_ELAPSED_TIME: 1d4
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_bus_prv
FAILURE_ID_HASH: {f507296b-20ca-dc3b-cebf-36d51efdb93d}
Followup: MachineOwner
---------
3: kd> !errrec ffffffff8d9c98fc
===============================================================================
Common Platform Error Record @ 8d9c98fc
-------------------------------------------------------------------------------
Record Id : 01d1ec802a1deba5
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 8/2/2016 5:39:07 (UTC)
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ 8d9c997c
Section @ 8d9c9a54
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 : 0x00000000000006fb
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ 8d9c99c4
Section @ 8d9c9b14
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : fb 06 00 00 00 08 04 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 @ 8d9c9b14
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ 8d9c9a0c
Section @ 8d9c9b94
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
Status : 0xf200084000000800
 
The above bolded error (BUSL0_SRC_ERR_M_NOTIMEOUT_ERR) means the processor sent out a read request to L0 cache and there was a delay in return (either a cache miss, or invalid data in cache). So I was definitely right about it being cpu related.
 
Do you have both 4-pin cpu power connectors plugged into the motherboard? If only using one please plug in the other and retest the system.
 

 
2016/08/03 20:08:29
Sushihunter

Sajin:
 
Great diagnosis - most of it far above my pay grade 
As you can see, both 4-pin connectors are plugged in. I took the photo a minute ago after reading your last post.

 
Just to be on the safe side, I will un-plug them and re-seat them, same with the plug on the PSU unit.
PS: Notice my nice shiny new EVGA 750 Watt G2 PSU 
 
Before you ask, the old PSU was plugged in here as well.
 
Also, I've seen some good deals on Craigslist for LGA 775 CPU's As soon as I have some extra cash, I think I will grab one.
Someone even has a Q8200 for only $10  There are a number of others as well in the $20 to $70 range, including one guy who has 22 CPU's for $20!!!
 
Sushihunter
  
 
2016/08/03 20:15:48
Sajin
Yep, looks like they are both connected. Time to try Cool GTX bios dance.
2016/08/03 20:32:56
Sushihunter
Sajin
Yep, looks like they are both connected. Time to try Cool GTX bios dance.




Yes. I do plan on doing this.
 
Experience has shown me that I need to be well rested and really think about this before jumping into the BIOS.
I'm not really hesitating - just want to make sure I do it right, as I haven't spent much time in the BIOS since I set the computer up in late 2007.
Amazing how you forget the details when you haven't done it for a while!
 

Use My Existing Forum Account

Use My Social Media Account