ASRock P67 Fatal1ty Pro mobo issues

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

dementedleo

Distinguished
Jul 13, 2010
21
0
18,510
HI all I am having an issue with this new board I bought as title shows it is the ASRock p67 Fatal1ty board.
here is list of everything in build:
I5-2500k @4.7ghz
2 MSI GTX 460 TwinFrozr 2 SOC SLI
4x2g Gskill ECO 1600 CL7
Corsair 750 HX psu
H50 cooler
Antec 902 case
3 antec 120mm in push pull config w/ 200mm on top
Spinpoint F3 1tb
hp dvd-rw


ok problem is in the new bios thing I try to set ram to 1600mhz as should be. I get DR Debug code 45 and pc stalls and I have to manually shutdown.
I can only run ram at 1333mhz and with auto settings.
I have ran prime95 for 36 hours so I have a stable system.
I have ran memtest on every stick of ram and all passed.
I am currently running bios 1.70 for mobo.
I have clean install of win 7 64 pro.
Please help cause I am at wits end.
Before you ask yes the ram is on site saying it is compatible.
I have tried everything I can think of ex: running cpu at stock and then trying to switch timings of ram. negative ; ;help........
 
I have the same issue using the Gskill RipjawsX F3-12800CL6D-4GBXH. I populated all 4 slots and would only get error code 45 but when I pulled them and only populated the furthest white slot from the CPU I got it to post. From there I got it to post with the 2 furthest slots populated, no other combination worked. I am hoping that AsRock is working on this as I would like to have all the memory working. Any suggestions are welcome.

Thanks Chris.
P.S my board is the P67 Extreme4
 
Solved - ASRock extreme4 P67 / code 45

I have gotten in my new MB and CPU. This time it was plug & play and smooth as butter. No issues whatsoever.
The memory is accepted and works under specifications. XMP worked great.

I have sent the new findings with the new serial number to ASRock (nl). They will send it to Taiwan for further reference.
One would assume that my problem can be reduced to the motherboard or CPU.
The old MB was stepping B3, but I don't know the BIOS version.


My current config:
MB: ASRock Extreme4 P67 / Stepping B3
BIOS: 1.60a
CPU: i7-2600K (Sandy Bridge) / batch 3103B323
Memory: Patriot Viper 2X 4GB DDR3 1866 Model PXD38G1866ELK / blue slots
Timing: 9-11-9-27 / f=933 / FSB=1:7/ CR=1T
Voltage: 1.65V
HD: WD velociraptor 300B
Graph: X1950Pro / 256
PS: ANTEC NeoPower Blue 650W
Cool: Zalman CPS9900A

Temps: CPU 31C / MB 29C (idle)

I have yet to perform some stress tests, but the system looks stable with comfortable temperatures. I have done some gaming that caused the system to crash, but that seems to be a driver issue. Within days I will get in my new graphic card PowerColor PCS+ AX6970.

I hope this will be of help to any of you out there struggling with this problem.
 


Chris,
See my posting ....

From the memory support list on the ASRock site, the G-Skill brand seems quite prominent.
http://www.asrock.com/mb/memory.asp?Model=P67%20Extreme4

Contact ASRock. They have helped me well, though did not directly solved it through support. I did share my findings, so the problem should be known with them.
Hope you get it solved ...
 
Thanks djwave28,

I called them and they told me to return the board as the memory should work fine (as it does in two of the slots). Hopefully the next board will fire up without a hitch.

Chris.
 


Wish you luck. Let me know. I am still interested in the cause of the problem. Although with you having the same problem, I am pretty sure that the mobo is the culprit.
 
Got the same problem here, code 45, and I've tried other memory - same thing. So now I know, that is the MB. Today I`ll try another same MB, but should I?

100% that it`s a mistake of ASRock`s engineers or factory.

I like this MB, couse it`s comfortable to use and OC, but this problem...

It happened after three days of use and when I take out the CPU and Mem to another MB (MSI) and then return it back to ASRock, this problem appear. I`m sure, that when I install this CPU and Mem to new ASRock P67 PROFESSIONAL FATAL1TY it will work fine, but how long? Until that moment when I take out the CPU/Mem from this MB for some reason again? 😱
 
So, in the company where I bought this board told that MB is OK, but there was my cousin, so he just said that wants another MB and now I have a new one.

Of course new MB have BIOS 1.70 and MB works (no code 45). But now I want agaon to unpgade BIOS to 1.80, like it was on my last (cause my hands).
 


The BIOS upgrade should not cause problems. The feature comes with the mobo. However, don't fix what is not broke and that is basically what ASRock warns users about on their site.

We don't recommend users to update BIOS while the system is running well. For any damages caused by improper operation of downloading or updating BIOS, ASRock® assumes no responsibility.

If you need it for a feature that is not working correctly then make sure you follow the proper operation and you should be fine. I do suggest that you leave things running for a bit to see if you're system is stable, before applying upgrades.
 
djwave28
The BIOS upgrade should not cause problems.
After BIOS update, my first MB worked fine (OC, LinX, Prime95 and games).

This note only for security reason. I need MB that not just work properly, I need MB that overclocks good and after all can work OK. And first of all, I need fresh BIOS form manufacturer. I have followed this principle from Socket 462.
 
hello from Poland

I've just got brand new computer with P67 PRO3 and also have same problem - monitor in idle and not posting MB with 45 code on DR Debug. I have 2x4gb of polish RAM producer GoodRAM which was recommended everywhere.

I pulled out one stick and MB posted correctly and I have installed Win7 correctly and without problems. So it seems it's sth with dual-channel. I have to try two sticks with crossed colours in single-channel

and still I don't know it's worth to complain because it works well with one slot and on the other hand I bought two sticks to have dual
 
hi,

i have the same issue on code 45. my mobo is newly replace but i got the same issue. still code 45. i bought a new ram gskill 2x2gb 1600 ripjaws x gskill.
it means new mobo, new ram but i have an issue in code 45. any 1 can help me with this?

here's my specs:
Asrock Fatal1ty Professional
Intel Core i5 2500k
2x2gb 1600 Ripjaws X Gskill
GTX 460 palit
700 watts OCZ Modextream.

Thanks
 
You need to contact warranty department again :) Or try to install only one ram-stick and to flash BIOS. But carefully, if you fail due to MB bug, it will stop work completely.
 
Problem solve Debug Code 45 in Asrock Fatality Pro.

Its Processor problem, i tried other processor from my friend and its works fine!

its not the memory issue base on my experience. 🙂

thanks to this thread.
 
I've run into the same code 45 problem on an ASRock P67 Extreme6, Intel Core i7 2600K, and DDR3-1600 8GB (2x4GB) G.Skill Sniper Low Voltage Series RAM.

When I tried booting with only one of the sticks, in single channel mode, my PC boots fine. Just to be sure, I tried the same stick in all four slots on the mobo. It boots fine everytime.

When I tried using the 2nd stick in each slot, I get Dr. Debug code 45.

When I try booting with both sticks in dual channel mode, I get the code 45 again.

So it sounds like one of my sticks is bad?


Any opinions? I don't exactly have access to spare CPUs or parts sitting around my house to troubleshoot.
 
Well that did it. You'd think that was something they could include in big letters with the RAM. Thanks for the tip!

Edit: Nevermind. Not 30 seconds later the BIOS froze, and I get code 45 on the next boot.
 


Hey you are not alone. I just had to RMA an Asus Z68 Pro V board because it would not post. I loaded windows 7 on the drive and started to install the ATI XFX 6950 drivers and nothing....... The board would not post at all. Nothing I could do would help.

From what you are saying I don't think that it is your motherboard or your PSU. Unfortunately, many people blame the PSU because it is convenient, not because it has really be trouble shooted in a systematic way.


I am sorry that you are having problems - I definitely can feel your pain. Glad you got it fixed 🙂