Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Gigabyte Z97X Gaming 7 occasional cold boot failure




  1. #11
    lemjello is offline Junior Member
    Join Date
    Aug 2012
    Location
    USA
    Posts
    13

    Default Re: Gigabyte Z97X Gaming 7 occasional cold boot failure

    Your board is in there. Itís just many pages in the thread.
    But, as far as M2 drive, no, never had that running. Not till I got a z370 board did I even think about it.
    Iím not sure if the mod bios add support for the drive or not. Could be worth the search. That thread goes on for days. Youíll see, it might be on page 100 or something crazy like that. You gotta go way past all the old chipsets, where people start requesting bios mods. Thatís where you will eventually find the one for your board. I found one using search. There are just so many pages on that thread that I didnít have time to find and link the exact page.

  2. #12
    deadlock0345 is online now Junior Member
    Join Date
    Jan 2020
    Location
    new jersey
    Posts
    16

    Default Re: Gigabyte Z97X Gaming 7 occasional cold boot failure

    i have the gigabyte z170x gaming 7 4x8gb 3000 mhz trident z rgb ram o.c too 3200mhz and cl14 the motherboard is touchy with ram over clocks on the non k 6700 i caN TELL YOU FROM PERSONAL EXPERIENCE. sorry hit caps but dont want to retype that at all, so i wouldn't be able too boot whats so every over 2666 until i turned my ref clock too 133 instead of 100...and as mentioned i have all 4 slots full. i recommend you update your bios honestly.but clearly if your trying too bclk o.c on a non k cpu than im sure you may or may not need that bios your on rite now too do soo and if its overclocked but this happens when you turn the pc on i wouldnt consider that as stable...yes it may work once you go through your daily ritual to get it on...but it seems like theres a problem somewhere if you ask me...if your solely doing the ram o.c than i find that all you should need too do is increase the ram channel voltage to 1.36v i did not have to increase vcco or system agent in order to get my ram overclock but im only overclocking my ram, not bclk at all, i will mention though that even though i did not have too add voltages too those things too get my pc too boot i did add a little voltage too them because i feel it just made my pc run a little little bit better and i have a cooler thats able too deal with the extra heat. have you tried seeing if your pc will boot normally with no overclock going at all? if not could you? and let me know what happens? im interested in trying too help in what ever way i can if im able too. ill also try re reading your issue too make sure im understanding correctly and try looking more into it too see if others are also having this issue...but i for one say i always been an msi mobo type of guy, but once i went to gigabyte and got things steady i really really love their products...before i knew anything about computers i felt like gigabyte was a cheap crappy company but their products have proven my nonfactual bias opinion otherwise. i also dont think that these types of issues only happen in gigabyte motherboards...i think it happens all the way across the board with every and any company that manufactures any types of electronics, everyone's motherboard is different with different combinations of cpus, ram ect installed soo noone can know for certain how they will react and it comes down to trial and error too fine tune yours to work properly...but that should be half the fun of all of this :) its not alll about gaming and work!

  3. #13
    deadlock0345 is online now Junior Member
    Join Date
    Jan 2020
    Location
    new jersey
    Posts
    16

    Default Re: Gigabyte Z97X Gaming 7 occasional cold boot failure

    these are the different types of error codes that can or will pop up on the debug l.e.d on the motherboard.. just incase you didn't have them i just wanted too share them with you
    10 | PEI Core is started
    11 | Pre-memory CPU initialization started
    12~14 | Reserved
    15 | Pre-memory North Bridge Initialization started
    16~8 | Reserved
    19 | Pre-memory South Bridge initialization started
    1A~2a | Reserved
    2B~2F | Memory Initialization
    31 | Memory installed
    32~36 | CPU PEI initialization
    37~3A | IOH PEI initialization
    3B~3E | PCH PEI initialization
    3F~4F | Reserved
    60 | DXE Core is started
    61 | NVRAM initialization
    62 | Installation of the PCH runtime services
    63~67 | CPU DXE initialization started
    68 | PCI host bridge initialization started
    69 | IOH DXE initialization
    6A | IOH SMM initialization
    6B~6F | Reserved
    70 | PCH DXE initialization
    71 | PCH SMM initialization
    72 | PCH devices initialization
    73-77 | PCH DXE initialization (module specific)
    78 | ACPI Core initialization
    79 | CSM initialization started
    7A~7F | Reserved for AMI use
    80~8F | Reserved for OEM use
    90 | Phase transfer to Boot Device
    91 | Issue event to connect drivers
    92 | PCI Bus initialization Started
    93 | PCI Bus hotplug initialization
    94 | PCI Bus Enumeration for detecting how many resources are requested
    95 | Check PCI device requested resources
    96 | Assign PCI device resources
    97 | Console Output devices connect
    98 | Console input devices connect
    99 | Super IO initialization
    9A | USB initialization started
    9B | Issue reset during USB initialization process
    9C | Detect and install all currently connected USB devices
    9D | Activated all currently connected USB devices
    9E~9F | Reserved
    A0 | IDE initialization is started
    A1 | Issue Reset during IDE initialization process
    A2 | Detect and install all currently connected IDE devices
    A3 | Activated all currently connected IDE devices
    A4 | SCSI initialization is started
    A5 | Issue reset during SCSI initialization process
    A6 | Detect and install all currently connected SCSI devices
    A7 | Activated all currently connected SCSI devices
    A8 | Verify Password if needed
    A9 | BIOS setup is started
    AA | Reserved
    AB | Wait user command in bios setup
    AC | Reserved
    AD | Issue Ready to Boot event for OS Boot
    AE | Boot to legacy OS
    AF | Exit Boot Services
    B0 | Runtime AP installation Begins
    B1 | Runtime AP installation ends
    B2 | Legacy option ROM initialization
    B3 | System reset if needed
    B4 | USB device hot plug-in
    B5 | PCI device hot plug
    B6 | Clean up of NVRAM
    B7 | Reconfigure NVRAM settings
    B8~BF | Reserved
    C0~CF | Reserved

    S3 Resume




    E0 | S3 Resume is started
    E1 | Fill boot script data for S3 resume
    E2 | Initializes VGA for S3 resume
    E3 | OS S3 wake vector call

    Recovery

    F0 | Recovery mode will be triggered due to invalid firmware volume detection.

    F1 | Recovery mode will be triggered by user decision.

    F2 | Recovery firmware image is found.

    F4 | Recovery firmware image is loaded.

    F5-F7 |Reserved for future AMI progress codes.

    Error

    50-55 | Memory initialization error codes.

    56 | Invalid CPU type or speed.

    57 | CPU mismatch.

    58 | CPU self test failed or possible CPU cache error.

    59 | CPU micro-code is not found or micro-code update is failed.

    5A | Internal CPU error.

    5B | Reset PPI is failed.

    5C-5F | Reserved.

    D0 | CPU initialization error.

    D1 | IOH initialization error.

    D2 | PCH initialization error.

    D3 | Some of the architectural Protocols are not available.

    D4 | PCI resource allocation error. Out of resources.

    D5 | No Space for Legacy Option ROM initialization.

    D6 | No Console Output Devices are found.

    D7 | No Consoles Input Devices are found.

    D8 | Flash update has failed.

    D9-DA | Can't load boot option.

    DB | Flash update has failed.

    DC | Reset protocol is failed.

    DE-DF | Reserved.

    E8 | S3 Resume is failed

    E9 | S3 Resume PPI is not found.

    EA | S3 Resume Boot Script is invalid.

    EB | S3 OS Wake call is invalid.

    EC-EF | Reserved.

    F8 | Recovery PPI is invalid.

    <F9> | Recovery capsule is not found.

    FA | Invaild recovery capsule.

    FB-FF | Reserved.

  4. #14
    Join Date
    Jan 2015
    Location
    Ireland
    Posts
    14

    Default Re: Gigabyte Z97X Gaming 7 occasional cold boot failure

    Quote Originally Posted by deadlock0345 View Post
    i have the gigabyte z170x gaming 7 4x8gb 3000 mhz trident z rgb ram o.c too 3200mhz and cl14 the motherboard is touchy with ram over clocks on the non k 6700 i caN TELL YOU FROM PERSONAL EXPERIENCE. sorry hit caps but dont want to retype that at all, so i wouldn't be able too boot whats so every over 2666 until i turned my ref clock too 133 instead of 100...and as mentioned i have all 4 slots full. i recommend you update your bios honestly.but clearly if your trying too bclk o.c on a non k cpu than im sure you may or may not need that bios your on rite now too do soo and if its overclocked but this happens when you turn the pc on i wouldnt consider that as stable...yes it may work once you go through your daily ritual to get it on...but it seems like theres a problem somewhere if you ask me...if your solely doing the ram o.c than i find that all you should need too do is increase the ram channel voltage to 1.36v i did not have to increase vcco or system agent in order to get my ram overclock but im only overclocking my ram, not bclk at all, i will mention though that even though i did not have too add voltages too those things too get my pc too boot i did add a little voltage too them because i feel it just made my pc run a little little bit better and i have a cooler thats able too deal with the extra heat. have you tried seeing if your pc will boot normally with no overclock going at all? if not could you? and let me know what happens? im interested in trying too help in what ever way i can if im able too. ill also try re reading your issue too make sure im understanding correctly and try looking more into it too see if others are also having this issue...but i for one say i always been an msi mobo type of guy, but once i went to gigabyte and got things steady i really really love their products...before i knew anything about computers i felt like gigabyte was a cheap crappy company but their products have proven my nonfactual bias opinion otherwise. i also dont think that these types of issues only happen in gigabyte motherboards...i think it happens all the way across the board with every and any company that manufactures any types of electronics, everyone's motherboard is different with different combinations of cpus, ram ect installed soo noone can know for certain how they will react and it comes down to trial and error too fine tune yours to work properly...but that should be half the fun of all of this :) its not alll about gaming and work!
    {PLEASE}

    Edit this, it is unreadable...

    So many orthography errors and no punctuation...
    show some respect not only hardware...

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •