Cold booting problem

[Stevetank1130]

I seem to be at a loss on this one.... I would say 75 percent of the time when I start from a cold boot using Windows 8 x64 pro everything posts and I get an "AA" code (my understanding that's when everything is turned over to the OS) I get to the desktop and it's blank. My mouse and keyboard are lit but have no functionality (there both usb). Sometimes it goes to blue screen after a few minutes, sometimes the icons eventually load. On a rare occasion I manually restart by holding the power button and I'll get the bios message saying my overclock failed. If that happens all I do is F10 at the bios and it'll load fine. I've tried throwing 0.005 more offset voltage at it and no effect, I've bumped my PLL to 1.75 (it was 1.65), I've adjusted the VCCSA up by 0.01 and the problem still happens. It's like my dad's old Chevy you have to start it a couple of times before it gets to runnin right. Any thoughts guys??

Thanks

[Stevetank1130]

I don't know if this matters but I've been having a heck of a time with razers synapse program and my Logitech mouse software fighting it out could that be of any consequence?? I may try uninstalling them and see what happens. I'm grasping at the same straws lol

[HiVizMan]

Er Logitec keyboard with a USB hub by any chance?

[Stevetank1130]

It's a G110 keyboard, it does have a usb slot but nothings plugged in.....however my Samsung S27B970D monitor has the Razer keypad and the logitech keyboard plugged into it's hub. My G700 Logitech mouse is plugged into the back of the mobo...

[HiVizMan]

Could find a generic mobo and see if plugging that into the back of your case sorts out the issue please.

[Stevetank1130]

Well I did some digging and tracked down the error code from windows which is a timing error. The OS is either waiting on a process thread to complete or the processor is waiting on instruction set from the OS, anywho something times out and for what I can understand it's usually driver related. So I reset to F5 defaults....booted to windows and ran the install DVD. It said there was a driver incompatability with Intel PROset so I uninstalled it. Rebooted after removing the DVD and so far at default settings in the bios it's booted up fine. Do you think one of the clock gen settings in bios could be causing the issue?? I've set windows to give me an error report next time it crashes so I'll have something to look over.

I appreciate any thoughts on this as always!

HiVisMan: do you think it could still be Mobo related??

[HiVizMan]

I am blushing here. I typed mobo when what I was trying to say was generic keyboard. So sorry dude. Must have been a blonde day for me. If only I had any hair.

[Stevetank1130]

Haha don't worry man, I was feeling rather embarassed to ask you to explain!! And don't worry about the hair it's over rated, I think i lost mine to and LGA 775 processor :)... I'll try the keyboard this evening and let you know. This is def an unusual problem.

[Stevetank1130]

Well after removing the incompatable (for whatever reason) intel winpro driver it seems that everything is stable again at default speeds. I've restarted a ton of times and no errors or BSOD or lockups. I'm gonna try a mild OC and see what happens. Maybe I just didn't have enough vCore or something and it was aggravating the issue.