BIOS Occasionally Hangs at Splashscreen

[gidgiddonihah]

I have had several issues with the system these past few months forcing me to replace my Kingston SSD with a Samsung 840 Pro, my CX500 with a Rosewill Capstone 750W, and my G. Skill Ripjaw DDR3 RAM with some Corsair Vengeance sticks.

Anyways something that has plagued the system since I first built it is that the BIOS occasionally (maybe 1 in ever 15-30 posts) hangs at the slashscreen. When this happens the HDD light is solid and a simple press of the reset button does the trick, posting and booting just fine. It is more annoying than anything but I am sick if it doing it. Any thoughts on the cause?

My Build
And, as always: Thanks Ahead!

 

[Roland Of Gilead]

I have had several issues with the system these past few months forcing me to replace my Kingston SSD with a Samsung 840 Pro, my CX500 with a Rosewill Capstone 750W, and my G. Skill Ripjaw DDR3 RAM with some Corsair Vengeance sticks.

Anyways something that has plagued the system since I first built it is that the BIOS occasionally (maybe 1 in ever 15-30 posts) hangs at the slashscreen. When this happens the HDD light is solid and a simple press of the reset button does the trick, posting and booting just fine. It is more annoying than anything but I am sick if it doing it. Any thoughts on the cause?

My Build
And, as always: Thanks Ahead!

Being honest, the only thing that I can think of that would have such an effect, would be an unstable overclock. Given you've unlocked your CPU, maybe that's why? Suggestion would be to put your CPU to stock, leaving the locked cores as they are, and just see if you continue to experience the issue. Presumable you've set your ram timings, voltages manually?

 

[gidgiddonihah]

I posted this when I thought my new RAM was stable, so I am doing some messing around with the system. I have taken the unlock off the system to ensure easy RAM diagnosis and updated the BIOS so we will see. I will try unlocking again after a week of being stable with the RAM and see if it happens again. I'll post my results here.

 

[Roland Of Gilead]

I posted this when I thought my new RAM was stable, so I am doing some messing around with the system. I have taken the unlock off the system to ensure easy RAM diagnosis and updated the BIOS so we will see. I will try unlocking again after a week of being stable with the RAM and see if it happens again. I'll post my results here.

cool, ill watch out, and see if I can be of any help.

Cheers

 

[gidgiddonihah]

It crashed again but I am not sure it's the RAM. I may have to ditch this question for longer than I want. I have made some changes and I hope that fixed it but I really don't think I did. If it crashes again I will take it to a local guy who is pretty sure it is some form of RAM problem.

 

[Roland Of Gilead]

It crashed again but I am not sure it's the RAM. I may have to ditch this question for longer than I want. I have made some changes and I hope that fixed it but I really don't think I did. If it crashes again I will take it to a local guy who is pretty sure it is some form of RAM problem.

fair enough. Sure if you have any update be sure to post.

 

[gidgiddonihah]

Looked at Windows Event Viewer and apparently since I started having issues this past month I have been getting NTFS and drive errors (on a brand new Samsung 840 Pro that runs benchmarks like a champ and passes SMART without a single error). I have also been getting a lot of SATA controller resets and errors. This afternoon it booted to a black screen and when I walked back after giving it a few minutes it was on a BIOS warning screen telling me the last boot had a "Hypertransport Sync Flood Error". Windows gave me this error when I booted successfully the next time:

A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: HyperTransport Watchdog Timeout Error
Processor ID: 0

With all of the errors I am pretty much calling this a dead or dying motherboard as it boots most of the time and has a crapload of different errors pointing different ways. I also looked at this Tom's thread and he had an eerily similar set of problems: pulling the fans fixed it for a couple of days, then when it stopped working again replacing different hardware got it to boot and then when it had problems again changing the SATA port got it to boot but several days later he got the same error I got. Swapping motherboard was his fix.

Edit: Also on track with this thread, either stopping the unlock or updating the BIOS fixed the hanging on the splashscreen problem as I haven't had it since I updated the BIOS and removed the unlock.