Overclock.net › Forums › AMD › AMD - General › Uh oh... I think I killed it
New Posts  All Forums:Forum Nav:

Uh oh... I think I killed it

post #1 of 43
Thread Starter 
Well the day I never thought would come is here. Just to let you know I'm no noob when it comes to overclocking. I've been tinkering with this particular system for about 15 months.

Last night I was overclocking with the fsb to see how high I could get it. The highest was about 238 with 1.45v cpu and 1.35 nb and it test 5hrs prime stable so I thought I would up it to 240 and test it again and that's when it stopped booting. No big deal I thought I will just reset the cmos and work on the OC when I wake up.

When I booted this morning the display would not come up. I get one long beep and 2 short beeps which my mobo manual indicates is a monitor or graphics card error. I tried to reset the cmos again with no luck. I then pulled out the battery and test the voltage, it was 2.94v. I checked for leaks around the gpu, none. I then sprayed some air around the pcie because there is no way to pull out my gpu with my watercooling set up unless I want to bleed and disassemble it. BUT I don't think it's the gpu acting up at all.

So, when I go to boot up I get one long beep and 2 short and I get nothing on the display. Now, when I reset the cmos I get one normal short beep and the computer goes to post, almost. After the logo screen it goes to a safe mode and gives me three options, boot from default settings boot from last know good config and hit f1 to continue boot. When I try the first two options the computer will restart and then give me one long beep and 2 short beeps and not display anything on the screen. BUT if I clear the cmos again and when I get the boot option screen I hit f1 to continue it will actually boot up into windows just fine. BUT when I go to restart it's the same problem all over again.

I've run into problems overclocking before where I set something too high but all I had to do was reset cmos and everything was fine and dandy. I've never had a problem that stays persistent. I even turned the computer off reset cmos and left it off for an hour while I went out and did some errands. I tried to be as detailed as possible so sorry about the long post. Any idea's?
post #2 of 43
Wait wait so you oc your cpu and then your gpu died?
mission3
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 980x Asus sabertooth x58 2x ASUS GTX 480 SLI 6GB corsair DDR3-1600 
Hard DriveOSMonitorPower
Crucial M4 128Gb + 1TB seagate HD Windows 7 ultimate 64-bit ASUS VG236 23" 120hz + 3d vision, Acer H233H 23" Corsair AX1200 
Case
coolermaster haf 932 
  hide details  
Reply
mission3
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 980x Asus sabertooth x58 2x ASUS GTX 480 SLI 6GB corsair DDR3-1600 
Hard DriveOSMonitorPower
Crucial M4 128Gb + 1TB seagate HD Windows 7 ultimate 64-bit ASUS VG236 23" 120hz + 3d vision, Acer H233H 23" Corsair AX1200 
Case
coolermaster haf 932 
  hide details  
Reply
post #3 of 43
OCing the FSB raises the freq of the PCIe slot too. Be very careful with that. I thought it shouldn't cause any permanent damage, but who knows..
My Rig
(14 items)
 
Ex-wife's Rig
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 4460 AsRock H81M-DG4 Sapphire Rx470 Platinum KVR 1600 16Gb 
Hard DriveHard DriveCoolingOS
2x Seagate 3Tb Samsung 850 EVO 120 Scythe Ninja 3 Rev.B Windows 10 Pro 
MonitorKeyboardPowerCase
Fujitsu Siemens A17-2A Logitech K280e SuperFlower SF-550K12XP Thermaltake Versa H25 
MouseAudio
Logitech G402 Sony MDR XD150 
CPUMotherboardGraphicsRAM
Athlon 750K 4.0Ghz AsRock FM2A75 Pro4+ Sapphire R9 270X Dual-X Kingston 2x4Gb 1600 
Hard DriveHard DriveOptical DriveCooling
Samsung 850 EVO 120  Western Digital 320Gb LiteON DVD-RW CoolerMaster Hyper Z600 
OSMonitorKeyboardPower
Windows 7 Pro x64 Toshiba 32" FullHD TV Logitech FSP Hexa 550 
CaseMouse
DeLUX Logitech 
  hide details  
Reply
My Rig
(14 items)
 
Ex-wife's Rig
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 4460 AsRock H81M-DG4 Sapphire Rx470 Platinum KVR 1600 16Gb 
Hard DriveHard DriveCoolingOS
2x Seagate 3Tb Samsung 850 EVO 120 Scythe Ninja 3 Rev.B Windows 10 Pro 
MonitorKeyboardPowerCase
Fujitsu Siemens A17-2A Logitech K280e SuperFlower SF-550K12XP Thermaltake Versa H25 
MouseAudio
Logitech G402 Sony MDR XD150 
CPUMotherboardGraphicsRAM
Athlon 750K 4.0Ghz AsRock FM2A75 Pro4+ Sapphire R9 270X Dual-X Kingston 2x4Gb 1600 
Hard DriveHard DriveOptical DriveCooling
Samsung 850 EVO 120  Western Digital 320Gb LiteON DVD-RW CoolerMaster Hyper Z600 
OSMonitorKeyboardPower
Windows 7 Pro x64 Toshiba 32" FullHD TV Logitech FSP Hexa 550 
CaseMouse
DeLUX Logitech 
  hide details  
Reply
post #4 of 43
Thread Starter 
Quote:
Originally Posted by ilglavmvm View Post
Wait wait so you oc your cpu and then your gpu died?
Not quite. I can boot into the system if I clear cmos and hit f1 on the boot selection screen (which only comes up when there is a problem) I'm actually on the computer right now and the gpu is working just fine. Once I restart the pc though it's going to give me one long beep and 2 short and wont show any display. If I clear the cmos it will then try to post and give me the boot selection screen as if something is wrong.

Funny thing is I can go into the bios after I clear the cmos, set everything to default and save and it will still give me the one long beep and 2 short after I go to restart to apply changes to bios and it won't show the display again that is, until I clear the cmos again.

It's frustrating.
post #5 of 43
Thread Starter 
Quote:
Originally Posted by ronnin426850 View Post
OCing the FSB raises the freq of the PCIe slot too. Be very careful with that. I thought it shouldn't cause any permanent damage, but who knows..
You are very correct. Because of this whenever I go into the bios to tinker with settings I always take it off "auto" and set it to 100.

I don't leave any settings on auto.
post #6 of 43
Almost as "new cpu installed" glitch. If it's somehow similar, it's mobo.
Skylake
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 6700k Asus Maximus VIII Gene GTX 970 Kingston hyperx Savage  
Hard DriveCoolingOSMonitor
Samsung 850 PRO NH-D14 Win 7 Philips 60 
KeyboardPowerCaseMouse
Ducky SHine 4 TX950 Air 540 G502 
  hide details  
Reply
Skylake
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 6700k Asus Maximus VIII Gene GTX 970 Kingston hyperx Savage  
Hard DriveCoolingOSMonitor
Samsung 850 PRO NH-D14 Win 7 Philips 60 
KeyboardPowerCaseMouse
Ducky SHine 4 TX950 Air 540 G502 
  hide details  
Reply
post #7 of 43
Quote:
Originally Posted by thx1138 View Post
You are very correct. Because of this whenever I go into the bios to tinker with settings I always take it off "auto" and set it to 100.
Mm, yes But that doesn't solve your problem. Auto = 100 generally, it's like the RAM setting- it sets the divider rather than the frequency.
So Auto PCIe = 100 PCIe @200 Ref clock.
And Auto PCIe = 120 PCIe @240 Ref clock.

So it's inevitable, unless the mobo supports some sort of freq lock which I haven't seen before
My Rig
(14 items)
 
Ex-wife's Rig
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 4460 AsRock H81M-DG4 Sapphire Rx470 Platinum KVR 1600 16Gb 
Hard DriveHard DriveCoolingOS
2x Seagate 3Tb Samsung 850 EVO 120 Scythe Ninja 3 Rev.B Windows 10 Pro 
MonitorKeyboardPowerCase
Fujitsu Siemens A17-2A Logitech K280e SuperFlower SF-550K12XP Thermaltake Versa H25 
MouseAudio
Logitech G402 Sony MDR XD150 
CPUMotherboardGraphicsRAM
Athlon 750K 4.0Ghz AsRock FM2A75 Pro4+ Sapphire R9 270X Dual-X Kingston 2x4Gb 1600 
Hard DriveHard DriveOptical DriveCooling
Samsung 850 EVO 120  Western Digital 320Gb LiteON DVD-RW CoolerMaster Hyper Z600 
OSMonitorKeyboardPower
Windows 7 Pro x64 Toshiba 32" FullHD TV Logitech FSP Hexa 550 
CaseMouse
DeLUX Logitech 
  hide details  
Reply
My Rig
(14 items)
 
Ex-wife's Rig
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 4460 AsRock H81M-DG4 Sapphire Rx470 Platinum KVR 1600 16Gb 
Hard DriveHard DriveCoolingOS
2x Seagate 3Tb Samsung 850 EVO 120 Scythe Ninja 3 Rev.B Windows 10 Pro 
MonitorKeyboardPowerCase
Fujitsu Siemens A17-2A Logitech K280e SuperFlower SF-550K12XP Thermaltake Versa H25 
MouseAudio
Logitech G402 Sony MDR XD150 
CPUMotherboardGraphicsRAM
Athlon 750K 4.0Ghz AsRock FM2A75 Pro4+ Sapphire R9 270X Dual-X Kingston 2x4Gb 1600 
Hard DriveHard DriveOptical DriveCooling
Samsung 850 EVO 120  Western Digital 320Gb LiteON DVD-RW CoolerMaster Hyper Z600 
OSMonitorKeyboardPower
Windows 7 Pro x64 Toshiba 32" FullHD TV Logitech FSP Hexa 550 
CaseMouse
DeLUX Logitech 
  hide details  
Reply
post #8 of 43
Thread Starter 
Quote:
Originally Posted by ronnin426850 View Post
Mm, yes But that doesn't solve your problem. Auto = 100 generally, it's like the RAM setting- it sets the divider rather than the frequency.
So Auto PCIe = 100 PCIe @200 Ref clock.
And Auto PCIe = 120 PCIe @240 Ref clock.

So it's inevitable, unless the mobo supports some sort of freq lock which I haven't seen before
Ah, I wasn't aware of that but it makes sense now. I always thought it locked it to a certain speed. Hmmm so I probably f-ed something up somewhere between my nb and my pcie.

This gets me a little closer to figuring out how to solve it, unless I caused some permanent damage. Only voltage increase was to the cpu and the cpu nb vid.
post #9 of 43
Quote:
Originally Posted by ronnin426850 View Post
Mm, yes But that doesn't solve your problem. Auto = 100 generally, it's like the RAM setting- it sets the divider rather than the frequency.
So Auto PCIe = 100 PCIe @200 Ref clock.
And Auto PCIe = 120 PCIe @240 Ref clock.

So it's inevitable, unless the mobo supports some sort of freq lock which I haven't seen before
He just said he locked it at 100. What do you meant here's no lock? It's been on all mobos I've used.. Don't AMD boards have this?
M1XN
(18 items)
 
Study Zenbook
(5 items)
 
 
CPUMotherboardGraphicsRAM
i7 4770K @ 4.2 GHz ASUS Maximus VI Impact MSI GTX 970 Gaming 4G 2x8 GB Kingston HyperX DDR3 @ 2400 MHz 
Hard DriveHard DriveHard DriveOptical Drive
Crucial M4 64 GB Crucial M4 128 GB SAMSUNG Spinpoint M9T 2 TB LiteOn DL-8ATSH 
CoolingOSMonitorKeyboard
Noctua NH-C14 Windows 10 64-bit ViewSonic VP2770 Vortex Pok3r 
PowerCaseMouseMouse Pad
Corsair SF600 NCASE M1 V2.5 Logitech G502 SteelSeries QcK+ 
AudioOther
HiFiMan HE-400 Logitech C920 
CPUGraphicsRAMHard Drive
i5-3317 GT 620M 2 GB soldered + 8 GB Corsair OCZ Vertex 3 120 
OS
Windows 7 Home Premium 64-bit 
  hide details  
Reply
M1XN
(18 items)
 
Study Zenbook
(5 items)
 
 
CPUMotherboardGraphicsRAM
i7 4770K @ 4.2 GHz ASUS Maximus VI Impact MSI GTX 970 Gaming 4G 2x8 GB Kingston HyperX DDR3 @ 2400 MHz 
Hard DriveHard DriveHard DriveOptical Drive
Crucial M4 64 GB Crucial M4 128 GB SAMSUNG Spinpoint M9T 2 TB LiteOn DL-8ATSH 
CoolingOSMonitorKeyboard
Noctua NH-C14 Windows 10 64-bit ViewSonic VP2770 Vortex Pok3r 
PowerCaseMouseMouse Pad
Corsair SF600 NCASE M1 V2.5 Logitech G502 SteelSeries QcK+ 
AudioOther
HiFiMan HE-400 Logitech C920 
CPUGraphicsRAMHard Drive
i5-3317 GT 620M 2 GB soldered + 8 GB Corsair OCZ Vertex 3 120 
OS
Windows 7 Home Premium 64-bit 
  hide details  
Reply
post #10 of 43
Quote:
Originally Posted by B!0HaZard View Post
He just said he locked it at 100. What do you meant here's no lock? It's been on all mobos I've used..
Are you sure? Like when you set your RAM @667 instead of Auto and then get very surprised it runs @740 after the OC?
My Rig
(14 items)
 
Ex-wife's Rig
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 4460 AsRock H81M-DG4 Sapphire Rx470 Platinum KVR 1600 16Gb 
Hard DriveHard DriveCoolingOS
2x Seagate 3Tb Samsung 850 EVO 120 Scythe Ninja 3 Rev.B Windows 10 Pro 
MonitorKeyboardPowerCase
Fujitsu Siemens A17-2A Logitech K280e SuperFlower SF-550K12XP Thermaltake Versa H25 
MouseAudio
Logitech G402 Sony MDR XD150 
CPUMotherboardGraphicsRAM
Athlon 750K 4.0Ghz AsRock FM2A75 Pro4+ Sapphire R9 270X Dual-X Kingston 2x4Gb 1600 
Hard DriveHard DriveOptical DriveCooling
Samsung 850 EVO 120  Western Digital 320Gb LiteON DVD-RW CoolerMaster Hyper Z600 
OSMonitorKeyboardPower
Windows 7 Pro x64 Toshiba 32" FullHD TV Logitech FSP Hexa 550 
CaseMouse
DeLUX Logitech 
  hide details  
Reply
My Rig
(14 items)
 
Ex-wife's Rig
(15 items)
 
 
CPUMotherboardGraphicsRAM
Core i5 4460 AsRock H81M-DG4 Sapphire Rx470 Platinum KVR 1600 16Gb 
Hard DriveHard DriveCoolingOS
2x Seagate 3Tb Samsung 850 EVO 120 Scythe Ninja 3 Rev.B Windows 10 Pro 
MonitorKeyboardPowerCase
Fujitsu Siemens A17-2A Logitech K280e SuperFlower SF-550K12XP Thermaltake Versa H25 
MouseAudio
Logitech G402 Sony MDR XD150 
CPUMotherboardGraphicsRAM
Athlon 750K 4.0Ghz AsRock FM2A75 Pro4+ Sapphire R9 270X Dual-X Kingston 2x4Gb 1600 
Hard DriveHard DriveOptical DriveCooling
Samsung 850 EVO 120  Western Digital 320Gb LiteON DVD-RW CoolerMaster Hyper Z600 
OSMonitorKeyboardPower
Windows 7 Pro x64 Toshiba 32" FullHD TV Logitech FSP Hexa 550 
CaseMouse
DeLUX Logitech 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD - General
Overclock.net › Forums › AMD › AMD - General › Uh oh... I think I killed it