Overclock.net › Forums › Intel › Intel Motherboards › Overclocking gone wrong.
New Posts  All Forums:Forum Nav:

Overclocking gone wrong.

post #1 of 20
Thread Starter 
Not exactly sure where to put this, but if this thread doesn't belong here, please move it to the correct section.

Alright, so I was overclocking my Q6600, because I had PC3-12800 1600MHz ram that I got yesterday. I was trying to match my rams 1600MHz to the FSB Frequency, so I had to increase it. While I increased it, I went onto Windows and stress tested it with Prime95. After a few BSOD's, I get it stable for a few minutes, and my computer completely shuts off. Now, I can't get it show a picture, I took out the battery, and tried a CMOS reset, I plugged the jumper into the right side and middle pin, then plugged it right back into the left side and middle pin. Booted it up, still no picture. I disconnected my power plug from it, then waited and still no picture. Can anyone help? Thanks.

Also, not sure if this has anything to do with it, but I believe I also overclocked the North Bridge to 400MHz, I think, and some other stuff.

-NingZhou.
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
post #2 of 20
If you've reset the CMOS successfully and you still cannot boot, you've corrupted your OS (it's not uncommon when there's a really unstable overclock). Throw the OS disc in and run a repair. If worst comes to worst you're going to have to reformat.
post #3 of 20
Thread Starter 
Quote:
Originally Posted by E-Peen View Post
If you've reset the CMOS successfully and you still cannot boot, you've corrupted your OS (it's not uncommon when there's a really unstable overclock). Throw the OS disc in and run a repair. If worst comes to worst you're going to have to reformat.
No, you're not understanding the problem I'm trying to explain.

No picture at all comes up when I turn on my PC. This has nothing to do with my OS, it's the BIOS that's not booting up.

-NingZhou.
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
post #4 of 20
I blew a quad core by overclocking and not knowing what i did... turns out that i broke the CPU by overvolting
    
CPUMotherboardGraphicsRAM
Core i7 5930k MSI X99S SLI GTX 1080 32GB Crucial DDR4 
Hard DriveHard DriveCoolingCooling
(3x) Crucial 256GB (768gb RAID0) WD 3TB EK Supremacy EVO + D5 Vario GT-AP15 
CoolingMonitorMonitorKeyboard
2X HWLABS GTX360 (2x) 1440p QHD PLS MicroBoard 40" 4k MVA Corsair K70 RGB 
PowerCaseMouseAudio
Corsair RM1000 Custom Build Logitech G900 Yamaha RX-V465 + 5.1 Surround 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Core i7 5930k MSI X99S SLI GTX 1080 32GB Crucial DDR4 
Hard DriveHard DriveCoolingCooling
(3x) Crucial 256GB (768gb RAID0) WD 3TB EK Supremacy EVO + D5 Vario GT-AP15 
CoolingMonitorMonitorKeyboard
2X HWLABS GTX360 (2x) 1440p QHD PLS MicroBoard 40" 4k MVA Corsair K70 RGB 
PowerCaseMouseAudio
Corsair RM1000 Custom Build Logitech G900 Yamaha RX-V465 + 5.1 Surround 
  hide details  
Reply
post #5 of 20
Thread Starter 
Quote:
Originally Posted by iCrap View Post
I blew a quad core by overclocking and not knowing what i did... turns out that i broke the CPU by overvolting
I've pushed my Q6600 harder before, to like 3.8GHz, although it wasn't stable so it shut down, but could boot up again. I also don't think I blew my CPU, since it doesn't get too hot.

-NingZhou.
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
post #6 of 20
Does it seem like your computer is booting? Just with no video? Because you gfx card could have died on you.
post #7 of 20
Quote:
Originally Posted by NingZhou View Post
I've pushed my Q6600 harder before, to like 3.8GHz, although it wasn't stable so it shut down.

-NingZhou.
It's all about voltage, not speed. If you set your processor to 10GHz, it would be fine.. it just wouldn't boot but wouldn't cause any permanent issues. If you set your voltage too high, thats when the damage happens.

If you reset your CMOS and it's still not booting, try other RAM and if that doesn't work.. you probably fried something. It's almost impossible to instantly fry something unless you set the voltage really high. Chances are you set the voltage too high, then let it set in windows for a few minutes. Those few minutes may have fried the CPU, or whatever else you set the voltage too high on.
Edited by Murlocke - 10/3/11 at 3:17pm
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
post #8 of 20
Unplug all power from the Mobo and then remove CMOS battery and then reset.
RIG 1
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD FX 8350 ASUS CH-V 990FX EVGA GTX 980 G-SKILL F3-14900 SNIPER 
Hard DriveHard DriveOptical DriveCooling
Samsung 840 Pro WD Black² PIONEER BDR-205 XSPC Raystorm 
OSMonitorKeyboardPower
WIN 8.1 MCE Nec 463 MX5500 DARK POWER PRO 1200 - P10 
CaseMouseMouse PadAudio
CoolerMaster Cosmos II REVO DIRTY ASUS HDAV 1.3 Deluxe 
  hide details  
Reply
RIG 1
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD FX 8350 ASUS CH-V 990FX EVGA GTX 980 G-SKILL F3-14900 SNIPER 
Hard DriveHard DriveOptical DriveCooling
Samsung 840 Pro WD Black² PIONEER BDR-205 XSPC Raystorm 
OSMonitorKeyboardPower
WIN 8.1 MCE Nec 463 MX5500 DARK POWER PRO 1200 - P10 
CaseMouseMouse PadAudio
CoolerMaster Cosmos II REVO DIRTY ASUS HDAV 1.3 Deluxe 
  hide details  
Reply
post #9 of 20
Thread Starter 
I'm pretty sure nothing is wrong with my GPU, just my CPU. I set my CPU voltage to like 0.5, it says on it. Not sure what that would be, cause my motherboard is a bit odd. Although it was on red text.

-NingZhou.
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
Desktop
(14 items)
 
  
CPUMotherboardGraphicsRAM
Q6600 Asus P5P43TD/USB3 Nvidia 9800GTX+ 8GB 1600MHz 
Hard DriveOptical DriveCoolingOS
Seagate 1TB. DVD Drive. Scythe Yasya Windows 7 Ultimate X64 
MonitorKeyboardPowerCase
ASUS VE246H Thermaltake Meka G1 700W OCZ Cooler Master CM 690 II Advanced 
MouseMouse Pad
Steelseries Xai Steelseries SK Gaming mousepad 
  hide details  
Reply
post #10 of 20
Quote:
Originally Posted by NingZhou View Post
No, you're not understanding the problem I'm trying to explain.

No picture at all comes up when I turn on my PC. This has nothing to do with my OS, it's the BIOS that's not booting up.

-NingZhou.
Oh, I'm sorry. I misunderstood you, my friend. I thought you couldn't boot into Windows, but you were able to POST.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › Overclocking gone wrong.