BSOD Problem on start-up, begins a reboot cycle continuously.

clookoo2 · 07 Jul 2013

I've been having this problem when I built this PC. I'm not quite sure exactly what is causing it, but when it does, my computer gets hung up in a continuous reboot cycle at the welcome screen, and sometimes it logs in for a total of about 2 minutes, then freezes up, and crashes.

When I do get a chance to log in, I'm presented with the exact same BSOD error every time. It looks like this,

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800E593748
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

In advance, I attached the SF_07-07-2013.rar file.

So, if anyone can help me fix this issue as I have no idea where to start, It would be very appreciated. Thanks in advance.

x BlueRobot · 07 Jul 2013

Welcome to the forums clookoo2,

Code:

BugCheck 124, {0, fffffa800e593748, 0, 0}

Probably caused by : AuthenticAMD

Code:

4: kd> !errrec fffffa800e593748
===============================================================================
Common Platform Error Record @ fffffa800e593748
-------------------------------------------------------------------------------
Record Id     : 01ce7b390e83a584
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/7/2013 17:40:36 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e5937c8
Section       @ fffffa800e5938a0
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         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                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  @ fffffa800e593960

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

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000e0100528
  Misc.       : 0xc00a0fff01000000

The error reported to WHEA, seems to be a generic timeout error originating as a Machine Check Exception from the CPU, firstly since your not able to boot into Windows, I would suggest testing the RAM first:

RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

clookoo2 · 08 Jul 2013

Thank you for replying so quickly, I have been able to log into windows normally through allot of luck and trial an error. But I'm finally in, and I'm going to let it run for a long amount of time and then do the Memtest. Another worrying issue I get is when I play any hardware demanding game such as Crysis 3 or Farcry 3, my processor gets to very dangerous temperatures, in a very short amount of time and I'm not too sure as to why. The program I'm using to detect my CPU temperature is Core Temp. I don't really know what is causing this issue, I was thinking that this may have something to do with the BSOD, but just for a reference, when I was playing Farcry 3 earlier today, my CPU hit temperatures of 200 Degrees Celsius as detected by core temp, which is quite worrying.

x BlueRobot · 08 Jul 2013

There may be some genuine overheating issues too, but temperatures reported at that level, is most likely either a bad motherboard sensor or a bug in the software. I use CoreTemp too, and don't get temperature readings like that, what's the version?

Have you checked inside the case for any dust accumulation? Checked if all the fans are working?

clookoo2 · 08 Jul 2013

The version of Core Temp I'm using is 1.0 RC5, and there is no possible chance of too much dust, but I do need a proper case with much better ventilation, that is for sure, but since the computer I built was built no less then about five days ago, there is no dust within the case. And the cores on the CPU only reach temps like that when I'm playing games that are hardware demanding, but it is a six core processor and maybe core temp has a hard time accurately reading the temperatures of the processor. Just for reference, it is a AMD FD6300WMHkBOX FX-6300 Six-Core 3.5GHz the black edition. Also, as far as the fans are working, they are, but like I said, I definitely do need a way better case that supports more case fans. I currently have a generic HP case that only supports a rear exhaust fans and no front or side fans. So, yeah, a new case is definitely on the top of my list, next to a more powerful CPU cooler, cause the one I'm using is the one that came with the CPU, and it's not that great.

x BlueRobot · 08 Jul 2013

I've got that version of CoreTemp and don't have any problems.

Okay, let's see if CoreTemp is giving the wrong temperatures, install and check the temperatures along with HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

A HP case most likely is causing very poor ventilation, since it's not designed for gaming purposes etc.

clookoo2 · 09 Jul 2013

Mem test didn't find any problems, and I'm still getting,

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800E593748
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

And as far as my CPU temps go, I didn't go over 42 degrees Celsius when I was playing Crysis 3 earlier today, so it seems to be a hit or miss problem, that or Core Temp wasn't reading the right temperatures. Thank you for all the help you've given so far, I hope you can help me more to resolve the BSOD problem, Thanks again.

x BlueRobot · 09 Jul 2013

CoreTemp must have had a hard time reading the temperatures then, and could you please upload the latest dump file using the same method as before?

clookoo2 · 09 Jul 2013

Of course, Here it is.

x BlueRobot · 09 Jul 2013

Have you completed MemTest86+ yet?

Code:

BugCheck 124, {0, fffffa800d9bb8f8, 0, 0}

Probably caused by : AuthenticAMD

Code:

2: kd> !errrec fffffa800d9bb8f8
===============================================================================
Common Platform Error Record @ fffffa800d9bb8f8
-------------------------------------------------------------------------------
Record Id     : 01ce7c26f2609365
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/8/2013 22:03:28 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800d9bb978
Section       @ fffffa800d9bba50
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         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                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  @ fffffa800d9bbb10

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

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000e0100460
  Misc.       : 0xc00a0fff01000000