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

[clookoo2]

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]

Welcome to the forums clookoo2,

[COLOR="Red"]BugCheck 124[/COLOR], {[COLOR="Blue"]0[/COLOR], [COLOR="SeaGreen"]fffffa800e593748[/COLOR], 0, 0}

Probably caused by : AuthenticAMD

4: kd> [COLOR="SeaGreen"]!errrec fffffa800e593748[/COLOR]
===============================================================================
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         : [COLOR="Red"]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  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:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[clookoo2]

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]

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]

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]

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]

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]

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]

Of course, Here it is.

 

[x BlueRobot]

Have you completed MemTest86+ yet?

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=Blue]0[/COLOR],[COLOR=SeaGreen] fffffa800d9bb8f8[/COLOR], 0, 0}

Probably caused by : AuthenticAMD

2: kd> [COLOR=SeaGreen]!errrec fffffa800d9bb8f8[/COLOR]
===============================================================================
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         : [COLOR=Red]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000e0100460
  Misc.       : 0xc00a0fff01000000

 

[clookoo2]

Oh, got another BLOD, this ones different. This is the first time this ones happened,



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: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: 0000000000000000
BCP3: FFFFF8800317F338
BCP4: FFFFF8800317EB90
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

And I don't think I gave memtest enough passes, I'm going to run it again tonight, and all day tomorrow.

 

[x BlueRobot]

[COLOR=Red]BugCheck 1000007E[/COLOR], {[COLOR=SeaGreen]ffffffffc0000005[/COLOR], 0, fffff8800317f338, fffff8800317eb90}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : [COLOR=Red]MijXfilt.sys[/COLOR] ( MijXfilt+2033 )

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

4: kd> [COLOR=SeaGreen]lmvm MijXfilt[/COLOR]
start             end                 module name
fffff880`09953000 fffff880`09975000   MijXfilt T (no symbols)           
    Loaded symbol image file: MijXfilt.sys
    Image path: MijXfilt.sys
    Image name: MijXfilt.sys
    Timestamp:        [COLOR=Red]Sat May 12 05:27:12 2012[/COLOR] (4FADE6A0)
    CheckSum:         00022009
    ImageSize:        00022000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your MotioninJoy simulate Xbox 360 controller (virtual Xinput device) driver seems to be a possible cause and causing problems, it is very well known to cause BSODs with Windows 7, as a result I would suggest you check for a update - MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy

 

[clookoo2]

I installed a new version of Motion Joy, so lets hope I never get that BSOD again. Also, I havent had any other BSOD's today, but my CPU temp freaked out and again went to around 220 Degrees Celsius, so I'm still thinking that is a hit or miss problem, and I'm probably not going to play games at high settings, I'll probably tone it down until I get a new case and proper cooling systems. I'll be sure to let you know if anymore BSOD's happen, thank you for all the support.

 

[clookoo2]

Okay, it happened again, the same recurring BSOD that I've been having since the beginning, but I think I've isolated as to what the problem is.

I have this wireless receiver for my 360 controller, it isn't genuine (meaning not made by Microsoft), and after I plugged it in and installed the drivers, then reset my system, it began it's cycle again of logging in for a few seconds then rebooting continuously. Now, I'm not 100% positive this is the only thing causing the problem as I haven't tried logging in again, but I'll find out soon enough.

 

[x BlueRobot]

Are you able to boot normally without it plugged in?

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=Blue]0[/COLOR], [COLOR=SeaGreen]fffffa800e5a24b8[/COLOR], 0, 0}

Probably caused by : AuthenticAMD

Stop 0x124's are usually always hardware, but can be caused by corrupted or incompatible drivers sometimes.

2: kd> [COLOR=SeaGreen]!errrec fffffa800e5a24b8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa800e5a24b8
-------------------------------------------------------------------------------
Record Id     : 01ce7d46e66bf2e5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/10/2013 8:24:45 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e5a2538
Section       @ fffffa800e5a2610
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    @ fffffa800e5a2580
Section       @ fffffa800e5a26d0
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  @ fffffa800e5a26d0

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

Error         : [COLOR=Red]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000e0100520
  Misc.       : 0xc00a0fff01000000

 

[clookoo2]

Yes, when the wireless receiver is not plugged in, I can log in normally, however, today the same BSOD happened even when it wasn't plugged in. Though, when it was plugged in, the reboot cycle was continuous, and never stopped, sometimes Blue Screening ten times before I gave up, where as when it isn't plugged in, it only Blu Screens once, then everything is fine. There was also a minor issue that happens every now and then where the screen freezes up when I'm playing a game, and has a buzzing, glitchy noise emanating from the speakers, but I think that is probably a overheating issue.

I also noticed that it says "Probably caused by : AuthenticAMD" above, and the only AMD thing that I have in my computer is my processor, so maybe that is the source of the problem. I'm going to try re-seating and re-applying thermal paste to the processor to see if maybe that will solve the problem. I was just hoping that that wasn't the problem earlier, 'cause that can be a bit of a pain sometimes, and messy.

 

[x BlueRobot]

Every Stop 0x124, BSOD will either say AuthenticAMD or GenuineIntel, since usually the CPU finds the hardware error with a Machine Check Exception.

The Xbox 360 Wireless driver is causing the boot cycles, but there' still another underlying problem, hence the BSOD Stop 0x124's still, it is worthwhile reapplying thermal paste to eliminate any CPU overheating issues.

I would also suggest stress testing the graphics card for any issues:

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

   Warning

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components

Use the following program to monitor your hardware temperatures during the stress test:

• GPU-Z Video card GPU Information Utility

 

[clookoo2]

I have already done a few stress tests on my graphics card, and under maximum load it performs quite well, not going over temperatures of around 78 degrees Celsius, and not causing any slow down. But, I really am stuck on thinking it may be my CPU. The thermal paste that was already on the stock heat sink was relatively small compared to the size of the CPU itself, and upon inspection, it doesn't seem to cover all of the surface area of the CPU, and that is mostly due to the space that is slotted out for the CPU on the heat sink being too small to cover the surface area of the CPU. So, after noticing that, I figured why bother replacing the thermal paste, I'm just going to buy a new CPU Cooler and some new thermal paste for it. And if I'm not explaining the situation well enough, I can give you a photo of it if you need one just so that it's easier to visualize how the heat sink interacts with the surface area of the CPU.

 

[x BlueRobot]

I understand what you mean, overheating can be cause, and if the heatsink is too small, then you'll need to get one which fits. Be wary though, since some hardware vendors will state that replacing the stock cooler etc. will void the warranty of the device.

 

[clookoo2]

Yeah, and in this case it does state that the warranty will be void. I'm planning on contacting AMD though and seeing if maybe I can keep my warranty because it's not really my fault that the heat sink sucks.

Also, I guess the wireless receiver wasn't the issue of the re-boot cycle, or now it's something else, because last night a never ending reboot cycle happened without the receiver plugged in, I really don't know what to do at this point, I have pretty well every USB port empty besides the mouse and keyboard, so there isn't any external hardware causing an issue. I'm just at a complete loss now. So the only place I feel that I can look is the processor.

Also, I did end up re-seating the processor and re-applying new thermal paste to the CPU and really made sure to cover the whole surface area of it. But, when I fired the PC up, it blue screened 3 times, then now its fine so far. This is only the first time I've logged in since I re-applied the thermal compound, so I'm crossing my fingers.