Windows 7 x64 BSOD - 0x124 - Please Help

divine123 · May 14, 2013

I already got several BSOD dmp files, but I dont know if they are the same error or they are a bunch of different one. please help.
I hope you can also help me know what causes the problem. PLEASE! :s6:

View attachment dmpfck.rar

partof · May 14, 2013

When do you get this BSOD?
Also having more information about your hardware would be nice.

Try to disable Dual-Core mode in BIOS and see if you can get OS to boot. You can get another BSOD, but with different code, if you do that.
If this doesn't help, I'd try to take out processor from its socket, then place it back and secure it with lever to be sure all its pins are connected with contacts.

Bugcheck clearly states there is hardware problem with your CPU.

Quick dump analysis with !analyze -v

Read More:

Code:

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


Loading Dump File [C:\Temp\dmpfck\051413-18546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*C:\TEMP\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c59e90
Debug session time: Wed May 15 04:48:20.546 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:07.546
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80029868f8, 0, 0}

Probably caused by : GenuineIntel

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

1: kd> !analyze -v
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        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: fffffa80029868f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  
fffff880`02fb96f0 fffff800`02cd7d29 : fffffa80`029868d0 fffffa80`018d7040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fb9c10 fffff800`02bb7217 : fffffa80`029868d0 fffff800`02c31658 fffffa80`018d7040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fb9c40 fffff800`02b1e865 : fffff800`02c933a0 00000000`00000001 fffffa80`02968c20 fffffa80`018d7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fb9c80 fffff800`02a9ea21 : fffff880`01052e00 fffff800`02b1e840 fffffa80`018d7000 00610062`0020002c : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fb9cb0 fffff800`02d31cce : 00730069`00670065 fffffa80`018d7040 00000000`00000080 fffffa80`0184ab30 : nt!ExpWorkerThread+0x111
fffff880`02fb9d40 fffff800`02a85fe6 : fffff880`009e9180 fffffa80`018d7040 fffff880`009f3f40 00200074`0066006f : nt!PspSystemThreadStartup+0x5a
fffff880`02fb9d80 00000000`00000000 : fffff880`02fba000 fffff880`02fb4000 fffff880`03757590 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

Output of !errrec fffffa80029868f8

Read More:

Code:

1: kd> !errrec fffffa80029868f8
===============================================================================
Common Platform Error Record @ fffffa80029868f8
-------------------------------------------------------------------------------
Record Id     : 01ce50f51e631987
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/14/2013 22:48:20 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fd
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : fd 06 00 00 00 08 02 00 - 9d 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  @ fffffa8002986b10

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

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

jcgriff2 · May 14, 2013

Hi -

Same findings here - hardware failure.
-

Code:

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Bugchecks on the 5 dumps - 0x124 = Windows Hardware Error Architecture (WHEA), which is a Machine Check Exception.

BSODs all occurred 8-11 seconds after boot-up:

Code:

System Uptime: 0 days 0:00:08.500
System Uptime: 0 days 0:00:07.546
System Uptime: 0 days 0:00:07.687
System Uptime: 0 days 0:00:08.375
System Uptime: 0 days 0:00:10.765

Did the BSODs just start on 9 May 2013?

Run - https://www.sysnative.com/forums/hardware-tutorials/3908-prime95-hardware-stress-testing.html

Regards. . .

jcgriff2

`

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 14 18:53:43.500 2013 (GMT-4)
System Uptime: 0 days 0:00:08.500
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029418f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 14 18:48:20.546 2013 (GMT-4)
System Uptime: 0 days 0:00:07.546
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029868f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 14 18:39:07.703 2013 (GMT-4)
System Uptime: 0 days 0:00:07.687
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`027d58f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May  9 21:40:14.375 2013 (GMT-4)
System Uptime: 0 days 0:00:08.375
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029c48f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May  9 19:33:29.765 2013 (GMT-4)
System Uptime: 0 days 0:00:10.765
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029d8038 00000000`00000000 00000000`00000000

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

divine123 · May 14, 2013

partof said:

When do you get this BSOD?
Also having more information about your hardware would be nice.

Try to disable Dual-Core mode in BIOS and see if you can get OS to boot. You can get another BSOD, but with different code, if you do that.
If this doesn't help, I'd try to take out processor from its socket, then place it back and secure it with lever to be sure all its pins are connected with contacts.

Bugcheck clearly states there is hardware problem with your CPU.

Quick dump analysis with !analyze -v

Read More:

Code:

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


Loading Dump File [C:\Temp\dmpfck\051413-18546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*C:\TEMP\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c59e90
Debug session time: Wed May 15 04:48:20.546 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:07.546
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80029868f8, 0, 0}

Probably caused by : GenuineIntel

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

1: kd> !analyze -v
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        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: fffffa80029868f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  
fffff880`02fb96f0 fffff800`02cd7d29 : fffffa80`029868d0 fffffa80`018d7040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fb9c10 fffff800`02bb7217 : fffffa80`029868d0 fffff800`02c31658 fffffa80`018d7040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fb9c40 fffff800`02b1e865 : fffff800`02c933a0 00000000`00000001 fffffa80`02968c20 fffffa80`018d7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fb9c80 fffff800`02a9ea21 : fffff880`01052e00 fffff800`02b1e840 fffffa80`018d7000 00610062`0020002c : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fb9cb0 fffff800`02d31cce : 00730069`00670065 fffffa80`018d7040 00000000`00000080 fffffa80`0184ab30 : nt!ExpWorkerThread+0x111
fffff880`02fb9d40 fffff800`02a85fe6 : fffff880`009e9180 fffffa80`018d7040 fffff880`009f3f40 00200074`0066006f : nt!PspSystemThreadStartup+0x5a
fffff880`02fb9d80 00000000`00000000 : fffff880`02fba000 fffff880`02fb4000 fffff880`03757590 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

Output of !errrec fffffa80029868f8

Read More:

Code:

1: kd> !errrec fffffa80029868f8
===============================================================================
Common Platform Error Record @ fffffa80029868f8
-------------------------------------------------------------------------------
Record Id     : 01ce50f51e631987
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/14/2013 22:48:20 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fd
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : fd 06 00 00 00 08 02 00 - 9d 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  @ fffffa8002986b10

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

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

Hi there, thanks for the response. So this clearly means that the problem is the CPU? and also all of this dmp files states the same? uhm and yah I forgot to post the hardware I got.

core 2 duo e4500 2.20ghz
2gb ddr2 667 RAM
Nvidia Galaxy Geforce GTX 260+
MSI P35 neo3 (motherboard)

divine123 · May 14, 2013

jcgriff2 said:

Hi -

Same findings here - hardware failure.
-

Code:

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Bugchecks on the 5 dumps - 0x124 = Windows Hardware Error Architecture (WHEA), which is a Machine Check Exception.

BSODs all occurred 8-11 seconds after boot-up:

Code:

System Uptime: 0 days 0:00:08.500
System Uptime: 0 days 0:00:07.546
System Uptime: 0 days 0:00:07.687
System Uptime: 0 days 0:00:08.375
System Uptime: 0 days 0:00:10.765

Did the BSODs just start on 9 May 2013?

Run - https://www.sysnative.com/forums/hardware-tutorials/3908-prime95-hardware-stress-testing.html

Regards. . .

jcgriff2

`

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 14 18:53:43.500 2013 (GMT-4)
System Uptime: 0 days 0:00:08.500
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029418f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 14 18:48:20.546 2013 (GMT-4)
System Uptime: 0 days 0:00:07.546
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029868f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue May 14 18:39:07.703 2013 (GMT-4)
System Uptime: 0 days 0:00:07.687
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`027d58f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May  9 21:40:14.375 2013 (GMT-4)
System Uptime: 0 days 0:00:08.375
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029c48f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May  9 19:33:29.765 2013 (GMT-4)
System Uptime: 0 days 0:00:10.765
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`029d8038 00000000`00000000 00000000`00000000

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

uhm hey man Ive tried checking it with prime95 but only with few passes and it says no errors. I dont knowHow long should run the test.

usasma · May 14, 2013

No, it does not mean it's the CPU. The CPU is only reporting the error, it'll take diagnostics to determine what the cause is.

Prime95 should run for a long time - I suggest 24 hours, others suggest as few as 8-9 hours.
Most errors will show up rather quickly - but it's the occasional one's late in the testing that are hardest to spot (and fix).

Please start with these free hardware diagnostics: Hardware Diagnostics

divine123 · May 14, 2013

usasma said:
No, it does not mean it's the CPU. The CPU is only reporting the error, it'll take diagnostics to determine what the cause is.

Prime95 should run for a long time - I suggest 24 hours, others suggest as few as 8-9 hours.
Most errors will show up rather quickly - but it's the occasional one's late in the testing that are hardest to spot (and fix).

Please start with these free hardware diagnostics: Hardware Diagnostics

uhm my I just know after the prime95 can I already know what causes the problem?
and by the way I'm already done checking the RAM and HDD, even the GPU with furmark last few days. though I dont know what to use for the motherboard. coz I suspect its the motherboard coz sometimes the motherboard wont detect (good) RAM so it wont start, but sometimes it does. and apparently i just lost the onboard LAN. I dont know if what I'm thinking about my motherboard make sense.

usasma · May 14, 2013

Unfortunately there are no motherboard tests. Those tests that do exist aren't very reliable - and only test a few components on the boards.
We figure out motherboard problems (basically) by ruling out everything else.

The only sure test is to replace the motherboard with another, known good board. I say this because I had problems with my Asus P6T Deluxe v1.0 board - and the replacement board had the same problem. I finally switched to an Asus P6T Deluxe v2.0 and all was well.

If you've run ALL the diagnostics, then it's time to move on to the hardware stripdown process: Hardware Stripdown Troubleshooting
Make a list of all the hardware - and post the test results (both the diagnostics and the replacements/removals/disabling) next to them. That'll help you keep track of what's been done and what hasn't.

Good luck!

divine123 · May 14, 2013

usasma said:
Unfortunately there are no motherboard tests. Those tests that do exist aren't very reliable - and only test a few components on the boards.
We figure out motherboard problems (basically) by ruling out everything else.

The only sure test is to replace the motherboard with another, known good board. I say this because I had problems with my Asus P6T Deluxe v1.0 board - and the replacement board had the same problem. I finally switched to an Asus P6T Deluxe v2.0 and all was well.

If you've run ALL the diagnostics, then it's time to move on to the hardware stripdown process: Hardware Stripdown Troubleshooting
Make a list of all the hardware - and post the test results (both the diagnostics and the replacements/removals/disabling) next to them. That'll help you keep track of what's been done and what hasn't.

Good luck!

Not all, not yet. I havent run Prime95 for quite a long amount of time. and also, I dont know what kind of result prime95 can give. And what does prime95 is checking anyway? is it the CPU?

partof · May 14, 2013

divine123 said:

partof said:

Read More:

When do you get this BSOD?
Also having more information about your hardware would be nice.

Try to disable Dual-Core mode in BIOS and see if you can get OS to boot. You can get another BSOD, but with different code, if you do that.
If this doesn't help, I'd try to take out processor from its socket, then place it back and secure it with lever to be sure all its pins are connected with contacts.

Bugcheck clearly states there is hardware problem with your CPU.

Quick dump analysis with !analyze -v

Read More:

Code:

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


Loading Dump File [C:\Temp\dmpfck\051413-18546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*C:\TEMP\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c59e90
Debug session time: Wed May 15 04:48:20.546 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:07.546
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80029868f8, 0, 0}

Probably caused by : GenuineIntel

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

1: kd> !analyze -v
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        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: fffffa80029868f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  
fffff880`02fb96f0 fffff800`02cd7d29 : fffffa80`029868d0 fffffa80`018d7040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fb9c10 fffff800`02bb7217 : fffffa80`029868d0 fffff800`02c31658 fffffa80`018d7040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fb9c40 fffff800`02b1e865 : fffff800`02c933a0 00000000`00000001 fffffa80`02968c20 fffffa80`018d7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fb9c80 fffff800`02a9ea21 : fffff880`01052e00 fffff800`02b1e840 fffffa80`018d7000 00610062`0020002c : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fb9cb0 fffff800`02d31cce : 00730069`00670065 fffffa80`018d7040 00000000`00000080 fffffa80`0184ab30 : nt!ExpWorkerThread+0x111
fffff880`02fb9d40 fffff800`02a85fe6 : fffff880`009e9180 fffffa80`018d7040 fffff880`009f3f40 00200074`0066006f : nt!PspSystemThreadStartup+0x5a
fffff880`02fb9d80 00000000`00000000 : fffff880`02fba000 fffff880`02fb4000 fffff880`03757590 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

Output of !errrec fffffa80029868f8

Read More:

Code:

1: kd> !errrec fffffa80029868f8
===============================================================================
Common Platform Error Record @ fffffa80029868f8
-------------------------------------------------------------------------------
Record Id     : 01ce50f51e631987
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/14/2013 22:48:20 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fd
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : fd 06 00 00 00 08 02 00 - 9d 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  @ fffffa8002986b10

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

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

Hi there, thanks for the response. So this clearly means that the problem is the CPU? and also all of this dmp files states the same? uhm and yah I forgot to post the hardware I got.

core 2 duo e4500 2.20ghz
2gb ddr2 667 RAM
Nvidia Galaxy Geforce GTX 260+
MSI P35 neo3 (motherboard)

According to what you told us, you can boot to OS successfully and only get that BSOD on occasion? If so I suggest you to take my advice from my post and reseat CPU in socket. Check if socket pins are clean from dirt and dust. Be careful though, if you are unexperienced I'd suggest you to take your PC to nearest repair shop.

dmp files showing same error, that indicates problem with accessing internal part of your CPU. In this case (according to this error "BUSL0_SRC_ERR_M_NOTIMEOUT_ERR") main CPU(_SRC_) was unable to access cache memory(_M_) on first processor and first core (Proc 0 Bank 0).
But, this doesn't necessary mean that CPU is to blame, for an example there are many pins in the socket and if one of them periodically looses contact with CPU you will get hardware errors from OS.

divine123 · May 14, 2013

partof said:

divine123 said:

partof said:

Read More:

When do you get this BSOD?
Also having more information about your hardware would be nice.

Try to disable Dual-Core mode in BIOS and see if you can get OS to boot. You can get another BSOD, but with different code, if you do that.
If this doesn't help, I'd try to take out processor from its socket, then place it back and secure it with lever to be sure all its pins are connected with contacts.

Bugcheck clearly states there is hardware problem with your CPU.

Quick dump analysis with !analyze -v

Read More:

Code:

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


Loading Dump File [C:\Temp\dmpfck\051413-18546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*C:\TEMP\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c59e90
Debug session time: Wed May 15 04:48:20.546 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:07.546
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80029868f8, 0, 0}

Probably caused by : GenuineIntel

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

1: kd> !analyze -v
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        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: fffffa80029868f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  
fffff880`02fb96f0 fffff800`02cd7d29 : fffffa80`029868d0 fffffa80`018d7040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fb9c10 fffff800`02bb7217 : fffffa80`029868d0 fffff800`02c31658 fffffa80`018d7040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fb9c40 fffff800`02b1e865 : fffff800`02c933a0 00000000`00000001 fffffa80`02968c20 fffffa80`018d7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fb9c80 fffff800`02a9ea21 : fffff880`01052e00 fffff800`02b1e840 fffffa80`018d7000 00610062`0020002c : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fb9cb0 fffff800`02d31cce : 00730069`00670065 fffffa80`018d7040 00000000`00000080 fffffa80`0184ab30 : nt!ExpWorkerThread+0x111
fffff880`02fb9d40 fffff800`02a85fe6 : fffff880`009e9180 fffffa80`018d7040 fffff880`009f3f40 00200074`0066006f : nt!PspSystemThreadStartup+0x5a
fffff880`02fb9d80 00000000`00000000 : fffff880`02fba000 fffff880`02fb4000 fffff880`03757590 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

Output of !errrec fffffa80029868f8

Read More:

Code:

1: kd> !errrec fffffa80029868f8
===============================================================================
Common Platform Error Record @ fffffa80029868f8
-------------------------------------------------------------------------------
Record Id     : 01ce50f51e631987
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/14/2013 22:48:20 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fd
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : fd 06 00 00 00 08 02 00 - 9d 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  @ fffffa8002986b10

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

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

Hi there, thanks for the response. So this clearly means that the problem is the CPU? and also all of this dmp files states the same? uhm and yah I forgot to post the hardware I got.

core 2 duo e4500 2.20ghz
2gb ddr2 667 RAM
Nvidia Galaxy Geforce GTX 260+
MSI P35 neo3 (motherboard)

According to what you told us, you can boot to OS successfully and only get that BSOD on occasion? If so I suggest you to take my advice from my post and reseat CPU in socket. Check if socket pins are clean from dirt and dust. Be careful though, if you are unexperienced I'd suggest you to take your PC to nearest repair shop.

dmp files showing same error, that indicates problem with accessing internal part of your CPU. In this case (according to this error "BUSL0_SRC_ERR_M_NOTIMEOUT_ERR") main CPU(_SRC_) was unable to access cache memory(_M_) on first processor and first core (Proc 0 Bank 0).
But, this doesn't necessary mean that CPU is to blame, for an example there are many pins in the socket and if one of them periodically looses contact with CPU you will get hardware errors from OS.

Indeed

Ive seen one pin before that is actually flipped differently. I thought its just fine so I just let it like that. there is also no errors for a long time just until now. I havent checked it again though, maybe tomorrow morning. then I'll go update you guys.

Wrench97 · May 14, 2013

If you think there is a bent pin on the CPU now would be the time to try and straighten it.

divine123 · May 14, 2013

Wrench97 said:
If you think there is a bent pin on the CPU now would be the time to try and straighten it.

No. my CPU is pinless, the pin I'm talking about is the one on the motherboard.

usasma · May 14, 2013

Prime95 tests the:
- RAM
- CPU Cache
- memory controller (most likely on your motherboard as you have a Core 2 Duo processor)

Test results:
- you may see errors mentioned on the screen.
- you may see errors mentioned in the results.txt file
- you may see overheating
- you may see crashing

partof · May 14, 2013

divine123 said:

Read More:

partof said:

divine123 said:

partof said:

Read More:

When do you get this BSOD?
Also having more information about your hardware would be nice.

Try to disable Dual-Core mode in BIOS and see if you can get OS to boot. You can get another BSOD, but with different code, if you do that.
If this doesn't help, I'd try to take out processor from its socket, then place it back and secure it with lever to be sure all its pins are connected with contacts.

Bugcheck clearly states there is hardware problem with your CPU.

Quick dump analysis with !analyze -v

Read More:

Code:

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


Loading Dump File [C:\Temp\dmpfck\051413-18546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*C:\TEMP\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c59e90
Debug session time: Wed May 15 04:48:20.546 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:07.546
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80029868f8, 0, 0}

Probably caused by : GenuineIntel

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

1: kd> !analyze -v
ERROR: FindPlugIns 800700a1
ERROR: Some plugins may not be available [800700a1]
*******************************************************************************
*                                                                             *
*                        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: fffffa80029868f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  
fffff880`02fb96f0 fffff800`02cd7d29 : fffffa80`029868d0 fffffa80`018d7040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fb9c10 fffff800`02bb7217 : fffffa80`029868d0 fffff800`02c31658 fffffa80`018d7040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fb9c40 fffff800`02b1e865 : fffff800`02c933a0 00000000`00000001 fffffa80`02968c20 fffffa80`018d7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fb9c80 fffff800`02a9ea21 : fffff880`01052e00 fffff800`02b1e840 fffffa80`018d7000 00610062`0020002c : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fb9cb0 fffff800`02d31cce : 00730069`00670065 fffffa80`018d7040 00000000`00000080 fffffa80`0184ab30 : nt!ExpWorkerThread+0x111
fffff880`02fb9d40 fffff800`02a85fe6 : fffff880`009e9180 fffffa80`018d7040 fffff880`009f3f40 00200074`0066006f : nt!PspSystemThreadStartup+0x5a
fffff880`02fb9d80 00000000`00000000 : fffff880`02fba000 fffff880`02fb4000 fffff880`03757590 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

Output of !errrec fffffa80029868f8

Read More:

Code:

1: kd> !errrec fffffa80029868f8
===============================================================================
Common Platform Error Record @ fffffa80029868f8
-------------------------------------------------------------------------------
Record Id     : 01ce50f51e631987
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/14/2013 22:48:20 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fd
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : fd 06 00 00 00 08 02 00 - 9d 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  @ fffffa8002986b10

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

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

Hi there, thanks for the response. So this clearly means that the problem is the CPU? and also all of this dmp files states the same? uhm and yah I forgot to post the hardware I got.

core 2 duo e4500 2.20ghz
2gb ddr2 667 RAM
Nvidia Galaxy Geforce GTX 260+
MSI P35 neo3 (motherboard)

According to what you told us, you can boot to OS successfully and only get that BSOD on occasion? If so I suggest you to take my advice from my post and reseat CPU in socket. Check if socket pins are clean from dirt and dust. Be careful though, if you are unexperienced I'd suggest you to take your PC to nearest repair shop.

dmp files showing same error, that indicates problem with accessing internal part of your CPU. In this case (according to this error "BUSL0_SRC_ERR_M_NOTIMEOUT_ERR") main CPU(_SRC_) was unable to access cache memory(_M_) on first processor and first core (Proc 0 Bank 0).
But, this doesn't necessary mean that CPU is to blame, for an example there are many pins in the socket and if one of them periodically looses contact with CPU you will get hardware errors from OS.

Indeed

Ive seen one pin before that is actually flipped differently. I thought its just fine so I just let it like that. there is also no errors for a long time just until now. I havent checked it again though, maybe tomorrow morning. then I'll go update you guys.

You can straighten it with a needle, just be careful and do not overdo it, as they are pretty easy to break. Most of the time you can't position it in same position as the others pins, because they bend too easy, but all you need is to restore contact with it and contact pad on CPU. You might need to do that several times if the first time will not fix it.

Search

Search

Windows 7 x64 BSOD - 0x124 - Please Help

divine123

Member

partof

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

divine123

Member

divine123

Member

usasma

Retired Admin

divine123

Member

usasma

Retired Admin

divine123

Member

partof

Member

divine123

Member

Wrench97

Administrator, Hardware Expert

divine123

Member

usasma

Retired Admin

partof

Member

Windows 7 x64 BSOD - 0x124 - Please Help

Member

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Member

Retired Admin

Member

Retired Admin

Member

Member

Member

Administrator, Hardware Expert

Member

Retired Admin

Member

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)