Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Dalork on November 19, 2014, 06:23:47 am
-
Got windows 8.1 on a crucial M500 SSD, i5 4690k on a Gigabyte z97x gaming 7 MB with 16GB (4x4), has got slow to boot for some reason. During post check the computer seems to sit on code 64 for a while before booting windows, it's getting longer and once or twice seemed as though it may have hung at this point.
Running BIOS F6, any ideas? I see there are many more beta BIOS versions, does anyone know if they might be to help with a issue such as this? GB's website lists the current official BIOS still as F6. Have not overclocked it and windows boots fine and system doesn't seem to fail memory or CPU stress tests etc.
-
Seemed to hang or did hang at boot?
What is your boot time from pressing power button to desktop?
Please unplug your system
Carefully reseat all 4 memory modules
Retest
If same
***Try reseating CPU as well. If you perform this step, be sure to inspect the socket carefully for bent or mis-aligned pins.
-
Thanks for the help Shadowsports,
Last 2 days it appears to hang, I let it sit for 5 mins or so and it just sits there showing code 64. I don't know if it eventually boots into windows, saw no reason for leaving it that long to test. The system was working fine for months, so I doubt it's bent cpu pins or that should have presented itself much earlier wouldn't it?
I already tried reseating everything except the cpu only because I don't have any TIM handy, will have to buy some more.
Boot time from pressing power button used to be less than a minute to desktop, it's been getting slower for a month or so taking about 3 mins showing it sitting on code 64 and then it would finish going through post and windows would load.
Last 3 start-ups now it has just stopped at code 64 and that's it for 5 mins, if I restart the computer it will post and boot up into windows.
Nothing new has been fitted or changed to hardware or software, only changes to the system over past few months would be software updates I guess.
I ran stress tests and memory seems fine and cpu seems ok, no fault and max cpu temps were 48-50 Celsius with a rather hot ambient room temp of 34 degrees. idle temps are 18-22.
I'll get some TIM and try reseating CPU and checking pins anyway next pay.
-
Before moving forward please remove 2 sticks of RAM, reconnect power and retest. Try alternating the sticks as well. first 2, then second 2. If there is no change, continue. Check CPU socket. If you get a clean/fast boot by pressing the power or reset button after this Qcode 64 hang, You may also want to look at your power supply as another possible cause.
-
OK here is a shot. Strip it down to cpu, 1 stick ram, hard drive. If you have onboard graphics use it instead of a video card. If not then you have to use video card also. Keyboard and mouse only. Now that it is stripped down take the power cord off and battery out and leave it out for 10 minutes. Then put battery back in and start it up. Does it still hang after that.
If so you might try flashing the bios and then start it stripped down. If this solves it add 1 piece of ram at a time till everything is back as it should be.
Code 64 is a CPU code.
-
Thanks for the help guys, I will strip it down to the basic min and test it soon as thermal paste turns up. Takes about 8 days for it by post so I'll have a week to wait.
ATM I'm just leaving the system powered up, everything in the computer is still under warranty (think is only 6 months old). I suspect it's the MB starting to fail or maybe the PSU (RM750), might see if I can borrow a working PSU though the week and check that side of it. Ram is couple years old but worked without a hick-up so far in previous system and this one till now.
Yes code 64 is a cpu error code, it's the driver execution environment start-up point I think.
-
Well pulled the system down then put cpu, 1 stick of ram and ssd back in, all worked as it should and booted fine. Then added each item 1 thing at a time and booted computer. All works fine and I have everything plugged back in, all seems to be as it should.
Then after a day or two it gets slow again sitting at the debug code 64, but does then load windows. Hasn't stopped on the 64 and not booted up yet but I suspect it will over the next few days/weeks again just as before.
I'm running Bios F6, most current listed as official on Gigabytes website for this board. There is several more beta versions though now up to F7, so I wonder if they are having issues. Should I try the latest beta version or stay with the official version F6 (which is the minimum I can use for this board with a i5 4690K).
I'm at a loss as to what's wrong though, seems to run fine for weeks to several months and then starts having issues again. I think windows 8.1 is loaded as MBR (not GPT). Doesn't seem to be a hot or cold boot/running issue, cpu is running cool (13 degrees Celsius is the lowest idle on a cool day and on a extremely hot day running prime 95 it hits high 40's) at idle and even fairly cool being stress tested.
-
Tried flashing the latest beta bios F7, didn't seem to help either. Still the same as before.
-
update:
After seeing no improvement from the latest Beta BIOS (F7) I re-flashed back to BIOS F6 and things have improved. I timed start-ups with a stop watch, initial time for it to go through post is lightening fast (as it used to be) takes 3 seconds.
Then it sits at code 64 for 22 to 25 seconds, then it proceeds with a few more codes very quickly (too fast to read most of them) finishing post and boots windows. This part is working as it should very quickly taking a total of about 8 to 12 seconds to reach desktop (windows loaded).
So from pressing power button to reaching desktop takes 38 to 41 seconds in total, so under 1 minute and everything is loaded and computer is good to go for normal use. Seems to have stayed that way for quite a few start-up/restarts (warm boots) and also was the same after sitting all night and then having a fresh cold boot.
Strange but seems ok now (did not try reseating or touching any hardware, just reverting back to BIOS F6) but will see what happens over the next few days/weeks. I have no idea of what timing is normal for post to sit at code 64 (CPU driver execution) but I think total boot time to desktop of under 1 minute is very good and I'm happy.
I have been told/suggested that some of the newer Gigabyte motherboards and Corsair power supplies don't go together so well for some reason but I don't think that is the issue here. I also just wanted to give thanks Shadowsports and Autotech for their time, help and input.
-
One guy over on tom's hardware said he did this: fixed my mine, with one ram stick on the far left slot. Then once you get it to boot add the other sticks one at a time.
-
Yo, sorry for the bump, but i'm having the same issue as Dalork. My Z97X Gaming 7 board will randomly get code 64 when powering on, especially when it's been off for several hours. It's got an i5-4690k, 2x4GB RAM, and is running Windows 7 on an Intel 730 SSD. It'll power on and run through several codes, then hang up on 64 until I manually cycle the power. I'm not overclocking any components aside from adjusting my RAM, but I still get the code even when the CMOS is reset to default.
I've tried re-seating all of my components, upgraded and downgraded the BIOS, and exchanged my RAM and motherboard at Micro Center, the issue still persists. It only happens 1 out of every 5 times I power it on, every other time, it boots properly and runs exactly as it should, very quick and responsive. What's more, if I power it off and on repeatedly to test it, it always passes, it only throws the code if it's been powered off for a while.
The only thing that comes to mind could be my power supply (Corsair CX750M) or the CPU, I've gotten the code running with just the CPU and one RAM module in slot 0, so I know it's not any drives or the GPU. I'd try exchanging them, but yesterday was the end of my 30-day return period, so I don't have that net to fall back on. Maybe if I see the same dude behind the customer service counter, he'll hook me up.
Once again, i've tried a completely new motherboard and RAM, re-seated every other component twice, and tried every fix on the first page of Google. I've just been leaving it on and suspending it in the meantime, it's not a critical issue, but an issue nonetheless. Anyone else having this issue?
-
Somehow, my is related to USB3 ports.
Empty USB3 ports....post code 64 for almost 60 seconds.
Anything plugin (USB stick, Samsung S5,....etc) booting normal.
-
Somehow, my is related to USB3 ports.
Empty USB3 ports....post code 64 for almost 60 seconds.
Anything plugin (USB stick, Samsung S5,....etc) booting normal.
Interesting, as i'm only using my USB 2.0 ports on the back for my mouse and keyboard. I switched them both to 3.0 and haven't noticed an immediate difference, but once again, it won't hang up if i'm resetting it repeatedly to test it. I'll keep posted, though.
-
Resetting is always OK for me......just cold boot are affected.
Do you have any USB flash drive?
-
Sorry for the late reply, been busy with work and school. I still receive code 64, with seemingly increasing frequency. Last week I encountered it three times in a row, after a routine reboot (the computer had been on for about 5 hours). A few hours ago, I took my i5-4690k to Micro Center and they swapped it out for an i7-4790k, but I still get the issue.
I might have an extra return period for the exchanged motherboard, so I may swap it out for another model, this board's given me a bad experience. When my old man and I built our first computer back in the day, we used a gigabyte board, and i've used gigabyte boards since, just sucks that this one's giving me so much trouble.
Resetting is always OK for me......just cold boot are affected.
Do you have any USB flash drive?
I'd thought that cold-booting was the only way to generate the code, but I received it three times in a row after a reboot last week. I've got a drawer full of USB drives, but the only devices I have plugged into the computer on boot are my mouse and keyboard.
-
It's not CPU related, I tried stacks of different models. I wonder if it's to do with this MB and Corsair PSU's some how
-
It's not CPU related, I tried stacks of different models. I wonder if it's to do with this MB and Corsair PSU's some how
That's the only thing I can think of now, aside from yet another faulty board. The majority of other people that had this issue RMA'd their boards and that fixed it, so it's got to be the power supply somehow. Micro Center's probably tired of seeing me by now, so i'll see if I can't use a buddy's employee discount at Fry's to grab another PSU sometime this week, and return it if the issue persists.
-
What make of PSU are you currently using?
-
What make of PSU are you currently using?
It's a Corsair CX750M, matches the description. I've noticed that on occasion, my K70 RGB and/or my M95 mouse stay illuminated even while the computer is fully shut down, wonder if it's related, as I didn't see any BIOS settings related to USB power while off.
-
So after almost a week without encountering the code, I got it again this morning. What's odd is that this time, it sat on code 64 for about 30-40 seconds, then it cleared POST and gave the all-clear beep, but then it hung on the Gigabyte splash screen for another 30 seconds, and after that, the good old flashing cursor stayed in the top-left corner until I restarted it manually. After restarting it, of course, it powered on and fully booted in under 20 seconds.
Haven't gotten a new power supply to test it with yet, probably will go with a cheap Thermaltake one to determine if it's the PSU causing this issue or not, and if it is, i'll invest in a higher-end PSU.
-
Got windows 8.1 on a crucial M500 SSD, i5 4690k on a Gigabyte z97x gaming 7 MB with 16GB (4x4), has got slow to boot for some reason. During post check the computer seems to sit on code 64 for a while before booting windows, it's getting longer and once or twice seemed as though it may have hung at this point.
Running BIOS F6, any ideas? I see there are many more beta BIOS versions, does anyone know if they might be to help with a issue such as this? GB's website lists the current official BIOS still as F6. Have not overclocked it and windows boots fine and system doesn't seem to fail memory or CPU stress tests etc.
I used the Old Case to Rebuild a customers PC, The new Motherboard is a Z97X Gamming 7, I plugged in his old camera SD card Reader into the motherboard because it was part of the case. System would hang on code 64 and take 2 minutes or longer before I would get the Gigabyte screen then boot to windows, once I unplugged the old card reader it would boot fast, so here is what I found out, if you have an old front side usb 1.1 or 2.0 and it is plugged into the 3.0 front side connectors it can and will case the board to hang on code 64. Hope this helps all who reads this. Rick
-
I used the Old Case to Rebuild a customers PC, The new Motherboard is a Z97X Gamming 7, I plugged in his old camera SD card Reader into the motherboard because it was part of the case. System would hang on code 64 and take 2 minutes or longer before I would get the Gigabyte screen then boot to windows, once I unplugged the old card reader it would boot fast, so here is what I found out, if you have an old front side usb 1.1 or 2.0 and it is plugged into the 3.0 front side connectors it can and will case the board to hang on code 64. Hope this helps all who reads this. Rick
Thank you, for me this was it.
I use a front panel with combined 4 x USB 2.0 hub, various card readers and 2 x USB 3.0, connected to F_USB2 and F_USB30.
The system ran fine for almost 9 months now, last week it startet to show the same behaviour as reported by different users: Stuck at '64', then at 'AE', before booting to the OS. Once I DID have the impression it might be USB releated, since the keyboard driver would load only after 10 seconds after the login screen was shown, but I dropped the idea.
I switched RAM modules, updated the BIOS, even tried other RAM modules - no good.
Then - after a week - it worked again, I had no idea why. I was happy for a few days until I wanted to boot from a USB stick on the fron panel. There it was again and it remained that way since.
Yesterday I read your post, removed the card reader/USB HUB and now everything works fine.
I'll see if I can still use it if I play around with the legacy support in the BIOS.