Signature done.
Signature done.
Any sort of burn mark on CPU should be enough IMO.
well trust me when i tell u if u have the same problem after replacing the cpu..its something else. look at everyone else here who has the same hardware. other than swapping out parts...i dont know what else to suggest as i dont think it could be a corrupt windows install. u have 7 64 bit? if u do i had to reinstall mine once due to it not booting after a bios update. im just trying to shoot from the hip here with suggestions
to help...sorry ur having to go through this i know how frustrating it can be
You could always just exchange he board and CPU to be done with it, you'd just have to live with the fact you'll never know what the fault really was :p:
The thing is, my old chip had no problems overclocking. It's this cpu I have now that I am have a hard time with. I am running windows 7 x64. I can boot into windows no problem, it's once I try oc. past 4300mhz, is where I run into problems. That's why it's hard for me to say whether it's the board, or the chip?
Since you probably have the best relation with ASrock, maybe you could help. Before I knew it was the chip originally, I thought the board was at fault. I contacted Asrock via email and told them my issues, and mentioned that I have owned the board for 2 months. They were very quick responding which is a plus, and gave me some troubleshooting to try. None were successful, I notified them of this, and they told me to contact the vendor for a replacement. I was unsure of this but, I contacted the place I purchased it from, and they won't replace anything that is over 30 days, and told me to try and contact ASrock again. It seems like I am just running circles. What would you recommend?
AFAIK the vendor is primarily responsible for replacing the board for the first year of warrenty. I'd get back onto them.
yes...its not like they eat the cost of the board as they send it back to asrock..total bull crap! where did u buy this board?
Never did get my system stable past 4.5ghz :(
Turns out that previous "success" was short lived.
I also noticed that I happen to have the same memory as Mean6. I *NEVER* got it stable @ 2133 (advertised speed and timings). Funny thing is that the G.Skill folks on the forum blame the motherboard. :rolleyes:
u can de-tune the ram to run at 1600 and u have xmp enabled? i would put the ram at 1600 or loosen the timings on the ram..u have all four slots or 2? if only 2 slots which ones u have filled?
i suggest backing off the timings...also running them at 1600 or 1866..you dont need 2133 ram
Sure you do. 4.5GHz and 2133 vs 1600 is the difference of 45secs per pass in IBT and 36secs. For my purposes thats a huge time saving when it all mounts up.
im running gskill 1600mhz at 1866 speed with cl8 timings and im at 5 ghz and can push it further if needed...u do not need,meaning have to have...2133 ram.
Somebody told me the exact opposite (might have been in this thread); I'm using the blue slots, haven't tried the white ones. Guess it wouldn't hurt to try... :shrug:
What are your BIOS settings, if you don't mind...? Extreme6 or 4? 2500 or 2600 cpu?
I would *LOVE* to get to 5ghz. I feel like my cooler is overkill for the paltry temps I'm getting...
I've got a 2600K with the Extreme4 board and I seem to be having some issues that are similar to what I'm hearing other people say here. When I first started overclocking this rig, I could get up to the 4.4 automatic turbo overclock in the UEFI to boot into Windows, but 4.6 just gave me the black screen with blinking cursor. I could get 4.5 to load windows by setting the multiplier myself, but 4.6 wouldn't boot Windows no matter what I tried.
Then, I came across a post by blacksun1942 that linked to some foreign site that had some settings that blacksun1942 said allowed him to get into Windows at 4.8. The link is http://ts2peca.no-ip.info/?p=604
When I used those same settings I was suddenly able to get into Windows at 4.8 as well, but any kind of stress test would either blue screen or freeze up the system. I wasn't willing to give it any more Vcore for stability so I backed the voltage down to 1.35v and was trying to get 4.6 stable in Prime95. I actually had it stable with small FFTs overnight for 8 hours without a single error. I then rebooted the system because I was going to try one notch down with the voltage so I could get better temps and decided to shut the system down completely to make sure it would cold boot properly because prior to using those settings I could never get 4.8 to boot Windows before. After shutting off the system completely and turning it back on, sure enough it was back to the black screen with a blinking cursor. Keep in mind I had changed nothing at this point from when it was 8 hours stable in Prime95 small FFT, but now it would not even boot Windows. It got past POST, but no further. This makes no sense to me. Since then I've tried every combination of settings I can think of and I can't get into Windows at anything higher than 4.5 even if I use the settings from that site again.
I'm no expert about this kind of thing, but it doesn't seem like a CPU limit to me. If it was the CPU, then why would it fail to load Windows at the exact settings where Prime95 had run for 8 hours previously without errors? I've considered doing an RMA of the board, but I'm hesitant because I don't know if it's actually the board or the CPU. I was hoping a future BIOS version might help but I just flashed 1.70 earlier this morning and nothing has changed.
At this point I'm not sure what to do. I've got 4.5 stable at 1.3v and the system is certainly fast enough, but the fact that I had it stable at a faster speed that I can no longer boot into is really bothering me.
extreme 4...2500k...this ram....http://www.newegg.com/Product/Produc...82E16820231445
bios setting are left alone..i mean i didnt change anything but these settings
cpu ratio=50
turbo boost=255,255
cpu voltage1.38-1.4
llc=3
ram=xmp,1866,1.6 volts
bios 1.61..no dual boot
reboot and everything is stable
i run core temp.precision pro and extreme tuning
By any chance, did you have anything plugged into the front USB2 ports? I've had this happen to me literally once or twice and both times I had a USB pen drive in the front USB2 ports, took the device out, Ctrl+Alt+Del restarted and no problem. My guess would be the system tried to read from the USB device thinking it was the OS drive for some reason.
I'm afraid I'm at a total loss on that one then :confused: