Overclock.net › Forums › Components › Memory › Failed Mem OC Attempt - Now No Keyboard
New Posts  All Forums:Forum Nav:

Failed Mem OC Attempt - Now No Keyboard

post #1 of 10
Thread Starter 
Hello, tied to oc memory for the 1st time in long time and now even after clearing battery and switching ram slots - i have no keyboard though it says it detects 1 keyboard, 1 mouse on the startup screen - the one telling me to hit F1 to go into Bios.

for a while it said 'no Keyboard detected' but whether it says it or not, no keyboard. Heres a possible caveat, my kid spilled coffee ontop my tower the other day which had honey in it, no noticeable effects but now i see the usb cable ends are indeed sticky. Doubt its that tho cause its worked for 3 days until my failed try.

What can I do at this point? My mobo is Asus z97-e and my cpu is 4690k @4.7. memory is 1333/1600 ddr3 and was trying for 1866 at 1.7 dram voltage.

MY mobo does not have the standard jumper that you manually move but says to short the pins with a screwdriver which is just bizarre and dont understand. Ive never done a flash - can i even do this without keyboard?
post #2 of 10
Did you try using a different keyboard? Or did you try this keyboard on a different computer to see if it really works?

EDIT:

Those two pins where you have a missing jumper, you can connect them through touching them with the tip of a screwdriver instead of a jumper. You then wait half a minute or so, while keeping the screwdriver there. You do this with the PC off and the power cable disconnected (or the power switch of the PSU on off if your PSU has a switch).
Edited by deepor - 10/6/16 at 12:21pm
post #3 of 10
Thread Starter 
Thanks for reply. Ok just bought a cheap $10 keyboard and I'll try it tonight afterwork. So basically just make contact with those 2 pins with metal and that'll do it ? Weird but OK,hope this works.
Edited by froggyluv - 10/6/16 at 2:56pm
post #4 of 10
Thread Starter 
New crappy keyboard works -so my old Corsair did bite the dust i guess frown.gif Prolly only 2 years old max and cost a good $100

Strange timing that it would die on a failed reboot tho eh..?
post #5 of 10
Quote:
Originally Posted by froggyluv View Post

New crappy keyboard works -so my old Corsair did bite the dust i guess frown.gif Prolly only 2 years old max and cost a good $100

Strange timing that it would die on a failed reboot tho eh..?

I'm not too familiar with the electrical design of computers, but it's possible that with a failed OC, the mobo might go a little bit crazy before it manages to lock itself down and reboot safely. If the keyboard was on the brink of life, a voltage spike or something to that effect might have killed it. Also, its possible that the spill might be shorting something in the USB port/cable (its unclear to me where exactly it spilled from your post).

Regardless, just be happy that you're only out of a 2 year old keyboard, and not your whole system.
Fractal Fury
(9 items)
 
TJ08-e Reborn!
(12 items)
 
CPUMotherboardGraphicsRAM
i7-5930k ASRock X99m Killer AMD Radeon Fury X G-Skill Ripjaws 4 32Gb 
Hard DriveCoolingKeyboardPower
Kingston Hyper-X Predator M.2 Corsair H100i GTX Ducky Shine III (MX Blue) EVGA Supernova 750 G2 
Case
Fractal Node 804 
  hide details  
Reply
Fractal Fury
(9 items)
 
TJ08-e Reborn!
(12 items)
 
CPUMotherboardGraphicsRAM
i7-5930k ASRock X99m Killer AMD Radeon Fury X G-Skill Ripjaws 4 32Gb 
Hard DriveCoolingKeyboardPower
Kingston Hyper-X Predator M.2 Corsair H100i GTX Ducky Shine III (MX Blue) EVGA Supernova 750 G2 
Case
Fractal Node 804 
  hide details  
Reply
post #6 of 10

You tried different USB ports?  Usb 2.0 one or something?  Sucks such a nice keyboard don't work, does it have a warranty?

Beast
(16 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k/5.0Ghz/1.37vBios Gigabyte z97x gaming 5 EVGA 1080 FTW HYBRID(2164core-12,012mem) Mushkin 8x2 16gb 2133mhzOC 
Hard DriveOptical DriveCoolingOS
840 evo 250g and 1tb None Cpu:H100i--Gpu:Hybrid Windows 10 Pro 64bit 
MonitorKeyboardPowerCase
Acer Predator x34 Logitech wirless Dell 875.  On a table 
MouseMouse PadAudioOther
Razor Naga Chroma Powercolor Full table pad Onboard Liquid PRO 
  hide details  
Reply
Beast
(16 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k/5.0Ghz/1.37vBios Gigabyte z97x gaming 5 EVGA 1080 FTW HYBRID(2164core-12,012mem) Mushkin 8x2 16gb 2133mhzOC 
Hard DriveOptical DriveCoolingOS
840 evo 250g and 1tb None Cpu:H100i--Gpu:Hybrid Windows 10 Pro 64bit 
MonitorKeyboardPowerCase
Acer Predator x34 Logitech wirless Dell 875.  On a table 
MouseMouse PadAudioOther
Razor Naga Chroma Powercolor Full table pad Onboard Liquid PRO 
  hide details  
Reply
post #7 of 10
Thread Starter 
Thanks for replies guys. Sadly, there is something much larger at hand and I cant really get a grip on what it is. After replacing keyboard, noticed I was getting a lot of BSOD with a WATCHDOG_CLOCK error. (LoL just happened now while typing this!)

So yesterday bought some new memory as I had seen a few messages during gaming regarding memory -went from Corsair 8gb 1600cl8 to Corsair 16gb 2400cl10. Came home, still crashing with even the slightest of overclocks. Now I had been running this system very stable at 4.7 and only a 1.35v with temps remaining very cool -high 40's low 50's under load. But now even an overclock to 4.0 with the slightest voltage bump kills the pc.

Looking in that specific error last night I seen that its either generally the CPU itself or a bad driver so after much attemted cleaning finally just wiped windows for a fresh install -ran 95prime before bed and woke up to a hung PC -again had left it on a very mild AUTO Overlock run from BIOS.

So yeah, now I'm in that state of high anxiety because this cpu/mobo are relatively new build -only 4 months plus I'm not really sure where the source of the problem is. Could it be Power Supply, CPU or MObo? Or all AAAGHHHH biggrin.gif

Problem is all my expendable PC income is out so I cant freely buy them all just to test out like I used to.\

Edit: Guess what I'm saying is - it seems stable with absolutely zero overclock but to me that's like going to a washi washi massage parlor and walking out with *cough* just a standard massage.. I play mostly Arma 3 exclusively and the game realy only responds to a high cpu frequency as well as really speedy ram. Had I actually done my research I would have built a 6600k/1151 mobo but alas went impulse shopping.

Is it possible I damaged the cpu somehow with the high overclock even tho temp were always very low?? Probably this is all a result of that fateful coffee spill by my kids...sigh
Edited by froggyluv - 10/10/16 at 8:11am
post #8 of 10

WATCHDOG bsod is not enough Vcore

Beast
(16 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k/5.0Ghz/1.37vBios Gigabyte z97x gaming 5 EVGA 1080 FTW HYBRID(2164core-12,012mem) Mushkin 8x2 16gb 2133mhzOC 
Hard DriveOptical DriveCoolingOS
840 evo 250g and 1tb None Cpu:H100i--Gpu:Hybrid Windows 10 Pro 64bit 
MonitorKeyboardPowerCase
Acer Predator x34 Logitech wirless Dell 875.  On a table 
MouseMouse PadAudioOther
Razor Naga Chroma Powercolor Full table pad Onboard Liquid PRO 
  hide details  
Reply
Beast
(16 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k/5.0Ghz/1.37vBios Gigabyte z97x gaming 5 EVGA 1080 FTW HYBRID(2164core-12,012mem) Mushkin 8x2 16gb 2133mhzOC 
Hard DriveOptical DriveCoolingOS
840 evo 250g and 1tb None Cpu:H100i--Gpu:Hybrid Windows 10 Pro 64bit 
MonitorKeyboardPowerCase
Acer Predator x34 Logitech wirless Dell 875.  On a table 
MouseMouse PadAudioOther
Razor Naga Chroma Powercolor Full table pad Onboard Liquid PRO 
  hide details  
Reply
post #9 of 10
Thread Starter 
Yep, but problem is even very large increases in vcore (1.4) to very conservative OC like 3.9 I just tried now hang into crash -not always with that exact message mind you. The system can literally not handle ANY overclocks anymore and I'm not sure why because it was outstanding before the above events.
post #10 of 10
Thread Starter 
Here is the WhoCashedMe report:


On Mon 10/10/2016 1:37:03 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFF810139E6C180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Memory
Overclock.net › Forums › Components › Memory › Failed Mem OC Attempt - Now No Keyboard