I get a BSOD if I try to OC my i5 2500k after 30 minutes on the comp.

Well to start off, I'm going to post my specs:

ASUS P8Z68 DELUXE/GEN3 LGA 1155 Intel Z68 SATA 6Gb/s USB 3.0 ATX Intel Motherboard with UEFI BIOS
G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
Western Digital Caviar Black WD1001FALS 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5"
Intel Core i5-2500K Sandy Bridge
Coolmaster Extreme at 600 watts
HIS HD 5870 Turbo

I had a GIGABYTE GA-Z68XP-UD3P LGA 1155 Intel Z68 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard and I could overclock my cpu to 4.5 without any problems, but with this new motherboard which cost more btw... which doesn't have intergrated graphics... which means it's a performance mobo... doesn't let me OC my cpu and I get a blue screen of death which doesn't last long enough for me to even read the error code. I downloaded all of the drivers from the website and I still get that BSOD.
20 answers Last reply
More about bsod 2500k minutes comp
  1. hi, you say your current mobo doesnt have integrated graphics but its a z68 chipset which does have igpu .anyway i have an i5 2500k with an asus p8z68-v mobo and basically has the same overclocking power as yours does and are some of the best mobos for sandybridge imho. im no expert in this field but have you checked to see if your bios needs updating as the gen3 boards are pretty new. just a thought.
  2. ive just noticed that there are no bios updates as yet for your mobo so it could just be teething problems until a new bios update is released i would keep an eye on some forums to see if others are having the same problem !!!! hope this helps
  3. It doesn't have a plug for vga dvi or hdmi. But that doesn't solve my problem :(
  4. Sounds like an unstable OC. Tell us the settings you changed. You can also look a the the bsod log to see what caused it. Just in case, make sure all cables are connected correctly.

    Not having video outputs does not mean it's a performance mobo, the igpu is on the cpu.
  5. I just change the multiplier from 33 to 40, 42, 45, etc I prefer to have 45, but I change nothing else. How do I look at the bsod log?
  6. I mean which program do I use to view the log?
  7. You can look in the reliabilty monitor, find the event, view details, you'll find the stop code there. Kind of irrelevant when you incorrectly OCed (not a smart thing to do) but you can check anyways. OCing is simple on SB but not that simple. You are supposed to stability test, checking vcore and temps for at least 1 hour, how else would you know it's safe? Unless you like to throw away money.

    I'll just give you the quick and newbie way to oc. First, get cpuz, hwmonitor, and prime95. Now in bios, keep your multi at 45, change the vcore to offset, set it to +.05. Now in windows, open all 3 programs, in prime run large fft. Tell me core temps and vcore. Temps need to stay below 72C and vcore should be around 1.3v (over 1.4v will cause more degradation than one would like). If not, you can stop prime and adjust the offset. You will need to run prime for at least 1 hour without errors or bsods.
  8. ^+1 overclocking requires you to adjust more then the multiplier, more then likely on your gigabyte board the vcore was set to auto and it cranked itself up as your increased your clock. I have a gigabyte board and my first increamental increases did similar, then i realised and changed the voltage manually. As you increase the clock you need to up the vcore to increase stability. Try reading the overclocking sticky in this forum and follow it as best you can.
  9. My Asus motherboard is also set to auto, but I put in those values and the vcore was already in offset and I got a bsod before I could even type in my password.
  10. At the end it said 019
  11. 0x19 is a software caused bsod. Try to go to stock and get more info on the other bsods.
  12. Which other BSODs?
  13. Any before today.
  14. Doesn't show more past 11/3/11 but i remember getting a 0x0000003b but I fixed that by switching a switch to disable that was on my motherboard that was near the ram.
  15. It should, dumb question, did you click the left arrow? Check what file caused the 0x19.
  16. Description
    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffffa8006f93340, 0xfffffa8006f93340, 0xfffffa8006f93340). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 112211-36098-01.
    Only button I see was the OK button after I clicked on the View technical details in the action column.
  17. Found this error also...The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8009a93028, 0x00000000f2000000, 0x0000000000000014). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111811-24585-01.
  18. mistatwista said:
    My Asus motherboard is also set to auto, but I put in those values and the vcore was already in offset and I got a bsod before I could even type in my password.

    0x124 is vcore. So back to vcore, what did you mean by "is also set to auto" if you said vcore was offset. Set your llc to high and try again.
  19. But I got the 019 message after I did all that you told me, I got the 124 message after I just raise the multiplier to 45
  20. The values in my uefi bios were all set to auto and only the multiplier was raised and then after I put those specific values to manual and changed them how you instructed me, I recieved the 0x00000019 error.
Ask a new question

Read More

CPUs Intel Motherboards Overclocking