Windows 7 x64 BSOD - 0x124 - Please Help

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:

Output of !errrec fffffa80029868f8

Read More:
 
Hi -

Same findings here - hardware failure.
-
Code: 
[FONT=Lucida Console]FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV[/FONT]

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: 
[font=lucida console]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[/font]

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: 
[font=lucida console]
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

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  [/font]
 
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:

Output of !errrec fffffa80029868f8

Read More:
Click to expand...

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)
 
jcgriff2 said:
Hi -

Same findings here - hardware failure.
-
Code: 
[FONT=Lucida Console]FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV[/FONT]

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: 
[FONT=lucida console]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[/FONT]

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: 
[FONT=lucida console]
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

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  [/FONT]
Click to expand...


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.
 
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
 
Last edited:
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
Click to expand...

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.
 
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!
 
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!
Click to expand...


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?
 
divine123 said:
partof said:
Read More:
Click to expand...

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)
Click to expand...

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.
 
partof said:
divine123 said:
partof said:
Read More:
Click to expand...

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)
Click to expand...

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.
Click to expand...


Indeed :eek: 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.
 
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
 
divine123 said:
Read More:


Indeed :eek: 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.
Click to expand...

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.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top