BSOD 124 on Intel Burn test start

Kalidor · 27 Jun 2012

Hi everyone,

I recently built a new system (like a month ago) and everything seemed fine at first and then I suddenly got random BSOD mostly while playing Diablo...

In the event viewer I got a WHEA-Logger warning that happen from time to time :

Source: WHEA-Logger EventID: 19

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 6

I decided reinstall windows and now I only have the ASUS drivers and ASUS utility tools installed. I managed to pass 3 hours of prime95 torture test and then I decided to try Intel Burn test which BSOD immediately everytime

Here's what in the system:
- EVGA GeForce GTX 550 Ti Superclocked
- Corsair CMZ16GX3M4A1600C9 16GB
- ASUS P8Z77-V Pro
- Intel Core i5 3570K
- Corsair TX750 V2
- Windows 7 ultimate x64

Drivers are up to date, BIOS is the latest.
I am not overclocking and I don't think I will, BIOS is all set to default settings I tried to disable Turbo Mode and it didn't change anything!

I am starting to think my CPU or motherboard might be defect

Any help will be greatly appreciated
Thanks!!!

James7679 · 27 Jun 2012

Hello Kalidor! Welcome to Seven Forums.

If you would like for us to be able to effectively help you, we will need you to follow the https://www.sevenforums.com/crashes-d...tructions.html Please be sure to do each step, as outlined in the tutorial. By doing this, we will have the necessary information to help you.

Thank you,

James

Kalidor · 30 Jun 2012

Hi James thanks for the reply,

It took me a bit of times to do as you asked because I tried a bunch of stuff on my parts since now I can run Intel Burn test but I still get random BSOD. BSOD so far can happen anytime but those inside my attached zip file happened while browsing the web and watching video online.

Here's what I did so far, ran 8 hours of memtest86+, ran 3 hours of prime95, ran 5 passes of Intel Burn test. Intel burn test now pass since I reseated my ram ( wanted to be sure they were installed properly...). I also reinstalled Windows and afterward my computer seemed more stable since I could pass Intel Burn test but I still have random BSOD

I am not sure where to go next, only clue I have is pretty much that WHEA-logger warning...

I will wait for your reply
Thanks a lot!!!

usasma · 02 Jul 2012

Only 58 updates since SP1 - most systems have 75 to 130. Please visit Windows Update and get all available updates.

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

IMO this is most likely caused by the SSD (or the controller drivers that it's using).
If it's not that (or the Windows Updates), then we've gotta start with the hardware diagnostics here: Hardware Diagnostics
Since this is a fresh install, you may want to try installing Win7 on a platter based hard drive to help rule out the SSD.

If these don't show anything, then post back for further suggestions.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


AsIO.sys        Mon Aug 23 21:53:02 2010 (4C7325FE)
AsUpIO.sys      Mon Aug 02 22:47:59 2010 (4C57835F)
HECIx64.sys     Wed Nov 09 19:52:25 2011 (4EBB2049)
ICCWDT.sys      Wed Aug 18 04:27:45 2010 (4C6B9981)
MpFilter.sys    Fri Mar 09 06:05:26 2012 (4F59E3F6)
NuidFltr.sys    Fri Apr 08 18:58:16 2011 (4D9F9308)
RTKVHD64.sys    Tue Jan 03 05:51:09 2012 (4F02DD9D)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asahci64.sys    Thu Jan 05 00:08:19 2012 (4F053043)
asmthub3.sys    Wed Nov 02 23:00:32 2011 (4EB203D0)
asmtxhci.sys    Wed Nov 02 23:00:22 2011 (4EB203C6)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
dc3d.sys        Wed May 18 04:07:24 2011 (4DD37E3C)
dump_iaStor.sys Tue Nov 29 22:39:19 2011 (4ED5A567)
e1c62x64.sys    Wed Jul 20 12:37:53 2011 (4E270461)
iaStor.sys      Tue Nov 29 22:39:19 2011 (4ED5A567)
iusb3hcs.sys    Thu Jan 05 06:56:40 2012 (4F058FF8)
iusb3hub.sys    Thu Jan 05 06:54:43 2012 (4F058F83)
iusb3xhc.sys    Thu Jan 05 06:54:45 2012 (4F058F85)
nvhda64v.sys    Wed Apr 18 13:07:54 2012 (4F8EF4EA)
nvlddmkm.sys    Tue May 15 03:35:36 2012 (4FB20748)
point64.sys     Wed May 18 04:07:20 2011 (4DD37E38)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\063012-7472-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jun 30 14:58:10.057 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:14.900
BugCheck 124, {0, fffffa800f3d1028, b2000000, 10005}
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0f3d1028 00000000`b2000000 00000000`00010005
BiosVersion = 1206
BiosReleaseDate = 06/05/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\063012-8080-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jun 30 14:55:29.771 2012 (UTC - 4:00)
System Uptime: 0 days 2:36:56.004
BugCheck 124, {0, fffffa800d101028, b2000000, 10005}
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0d101028 00000000`b2000000 00000000`00010005
BiosVersion = 1206
BiosReleaseDate = 06/05/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Kalidor · 02 Jul 2012

One of the first thing I tried when I started experiencing random BSOD was to unplug the SSD and use a normal hard drive instead. I still had the same BSOD without the SSD so I am pretty sure this is not my issue.

I haven't done everything here Hardware Diagnostics but I have tested memory, stress the cpu, made sure temp are ok and everything seem fine. So the only thing I have right now is the WHEA-logger warning that you probably saw already.

The research I did online on this warning suggest that it might be a defective cpu and I decided to give it a shot so I contacted Intel for a RMA about an hour ago. I am still not 100% sure on this but it's worth a try...

I will keep you updated when I receive my new cpu

Thanks for your help

usasma · 02 Jul 2012

It's great that you can get an RMA for the CPU - it's much easier than fussing around trying to prove it's a CPU problem! I've argued at great length with people about the significance of the STOP 0x124 errors - so the new CPU will save you a lot of time

Good luck!

Kalidor · 01 Aug 2012

I have received my new CPU and I have been using my computer for 2 weeks without any issues at all. :)
So yes my problem was definitely my CPU and everything is working great now!

Thank you for your support