I have a serious problem with my Fatal1ty P67 Professional motherboard. Suddenly it failed to boot to POST screen after restart. There was error code 59 shown on Dr. Debug, and the board always restarted itself automatically a few seconds after the code was shown. Then the board repeated the boot/restart process over and over again with no sign to boot to POST screen. I did contact ASRock regarding this issue but have yet to receive an answer. Here's what I can share so far:
1. All the hardwares like processor, RAM and graphics card found to be not faulty. I've checked everything and every single hardware that was installed on the P67 Professional was performed normally on another P67 motherboard (Asus P8P67 Deluxe). No faulty hardware or problem were shown or detected during test, meaning all the hardwares I used on P67 Professional are fine.
2. I never done any kind of overclocking. I'm not familiar with it and I always stay away from it. I've changed boot priority (HDD, ODD, USB) and enabled Intel XMP profile for my RAM and nothing else.
3. I've been using this motherboard since late 2011 and I never had any problem with it. Not even once.
4. I've tried clearing CMOS to no avail. Removing/swapping the battery didn't fix anything too.
5. I've tried to boot the board using only core hardwares (processor, a single RAM module and a graphics card) but it didn't fix anything.
6. The code shown on Dr. Debug before the board automatically restarted itself was 59 (it has something with CPU micro-code, if I recall it correctly).
7. The same PSU used to power the board were using to power the test board (ASUS P8P67 Deluxe) and there was nothing wrong or strange happened, meaning the PSU performed normally.
8. The issue happened so suddenly. There was no power failure nor BSOD.
According to all my friends who once used ASRock boards, they claimed it has something to do with the BIOS chip. The ones that used P67 Professional before suggested me that the faulty BIOS chip might caused it and recommended me to ask ASRock for a replacement. My board's still under warranty, at least according to ASRock claim. It was Rev. B3 board and ASRock provides 3-year (or 5-year?) warranty for it. But so far I've received no reply from ASRock regarding this issue. So what should I do now? Can anybody help me with this issue?
1. All the hardwares like processor, RAM and graphics card found to be not faulty. I've checked everything and every single hardware that was installed on the P67 Professional was performed normally on another P67 motherboard (Asus P8P67 Deluxe). No faulty hardware or problem were shown or detected during test, meaning all the hardwares I used on P67 Professional are fine.
2. I never done any kind of overclocking. I'm not familiar with it and I always stay away from it. I've changed boot priority (HDD, ODD, USB) and enabled Intel XMP profile for my RAM and nothing else.
3. I've been using this motherboard since late 2011 and I never had any problem with it. Not even once.
4. I've tried clearing CMOS to no avail. Removing/swapping the battery didn't fix anything too.
5. I've tried to boot the board using only core hardwares (processor, a single RAM module and a graphics card) but it didn't fix anything.
6. The code shown on Dr. Debug before the board automatically restarted itself was 59 (it has something with CPU micro-code, if I recall it correctly).
7. The same PSU used to power the board were using to power the test board (ASUS P8P67 Deluxe) and there was nothing wrong or strange happened, meaning the PSU performed normally.
8. The issue happened so suddenly. There was no power failure nor BSOD.
According to all my friends who once used ASRock boards, they claimed it has something to do with the BIOS chip. The ones that used P67 Professional before suggested me that the faulty BIOS chip might caused it and recommended me to ask ASRock for a replacement. My board's still under warranty, at least according to ASRock claim. It was Rev. B3 board and ASRock provides 3-year (or 5-year?) warranty for it. But so far I've received no reply from ASRock regarding this issue. So what should I do now? Can anybody help me with this issue?
Comment