Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Results 1 to 10 of 10

Thread: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

  1. #1
    cohibaman is offline Junior Member
    Join Date
    Aug 2011
    Location
    Vancouver,Canada
    Posts
    9

    Default (Solved)Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30?

    Hi I have purchased a new board, and set it up with a new 2600k CPU, using manufactured set of 16GB sticks of 4x4 Corsair Vengence 1600 ram, with a Kuhler 920 HS. Also the PSU is a new Corsair AX850. I have a monitor attached with onboard MB VGA. I am checking the board and CPU for post before installing in case,. When I power on, the fans on HS are working, the monitor doesn't display and the there is no startup beep. The only thing displaying is Dr.Debug code 30. I have checked the power connetions, tried changing ram sticks around instead of using 4 I have tried with using 2 sticks in differnt slots 2 in red or 2 in black. I have powered off reset the CMOS, and I am still getting error code 30 and it is kind of vague for the description in the manual. Any help would be appreciated, thanks in advance.

    Solved by changing 8 pin cable on that came with PSU. Hopefully helps for somebody else
    Last edited by cohibaman; 08-08-2011 at 06:51 AM.

  2. #2
    moordare is offline Junior Member
    Join Date
    Oct 2011
    Location
    texas
    Posts
    2

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    Can you tell me specifically what you did? I'm having same issue. I have my 8 pin coming out of cm 1000 gold and plugged into the 8 pin extender that came with psu. I route behind mobo to plug into 8 pin Power on mobo

  3. #3
    moordare is offline Junior Member
    Join Date
    Oct 2011
    Location
    texas
    Posts
    2

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    I'm also having a hell of a time getting an led to fire. I have 2 others working, but the stock one with have started to fry.

  4. #4
    ASRock TSD - Emily is offline ASRock Tech Support Staff
    Join Date
    Mar 2011
    Location
    Taiwan
    Posts
    562

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    Dear all,

    Debug code shows "30", it maybe related to your memory.

    Please kindly refer to below suggestions for testing.
    1. Please insert your memory module in the black DRAM slot then try again.
    2. Please unplug your memory and replug in then make sure your memory module is installed properly.
    3. Please only install a stick memory by turns to check your memory are fine.
    4. If possible, please kindly change other memory for testing.

    If the problem still cannot be solved, please kindly contact your local dealer to check your system.
    Thanks!

    Have a nice day
    ASRock TSD
    Emily

  5. #5
    londoncalling is offline Junior Member
    Join Date
    Nov 2011
    Location
    London
    Posts
    4

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    Hi,

    I've just started on my first PC build with an ASROCK Extreme 7 mobo which I've put together with CPU i5 2500K and Corsair Vengeance RAM as a test rig. but sadly am also seeing the Debug Code 30 that cohibaman reported. I do suspect that the RAM might be a problem as when the package arrived it was badly damage and had been re-bagged by the Post Office. However, before I go out and buy more I'd like to try the power supply fix that was mentioned; can someone explain in more detail what this fix is?

    I'm slightly reeling from all the stories of problem builds I'm now seeing on forums, I thought, maybe naively that it was all going to slot together quite simply... !!!

    Any help or support would be most welcome.

    Robert.

  6. #6
    cohibaman is offline Junior Member
    Join Date
    Aug 2011
    Location
    Vancouver,Canada
    Posts
    9

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    Quote Originally Posted by moordare View Post
    Can you tell me specifically what you did? I'm having same issue. I have my 8 pin coming out of cm 1000 gold and plugged into the 8 pin extender that came with psu. I route behind mobo to plug into 8 pin Power on mobo
    I also reseated the ram moduals quite a few times, and had to really push down to get them seated, tried with 2 sticks first and got to post and then added the other 2 sticks of ram with having to reseat them so that they were recongnised

  7. #7
    cohibaman is offline Junior Member
    Join Date
    Aug 2011
    Location
    Vancouver,Canada
    Posts
    9

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    Quote Originally Posted by londoncalling View Post
    Hi,

    I've just started on my first PC build with an ASROCK Extreme 7 mobo which I've put together with CPU i5 2500K and Corsair Vengeance RAM as a test rig. but sadly am also seeing the Debug Code 30 that cohibaman reported. I do suspect that the RAM might be a problem as when the package arrived it was badly damage and had been re-bagged by the Post Office. However, before I go out and buy more I'd like to try the power supply fix that was mentioned; can someone explain in more detail what this fix is?

    I'm slightly reeling from all the stories of problem builds I'm now seeing on forums, I thought, maybe naively that it was all going to slot together quite simply... !!!

    Any help or support would be most welcome.

    Robert.
    Check with Asrock website to make sure your ram is compatible for your MB and also check to see if your board is listed with Corsair's site for the ram you have, then just have a monitor (a video card if no onboard graphic card is available) connected with 2 sticks of ram installed, reseat the ram a few times, as it takes a lot of pressure to seat them, and try the 2 slots recomended in the manual and if this does not work try the other 2 slots. Once you get to post then you can add more ram, making sure it is the same as the installed sticks. It took me awhile but I got pass the "Code 30" with 4 sticks of ram seated, went to post then into Bios and never had any other problem. Also I read, if pins got bent when CPU got installed it could also cause this code....hopefully that isn't the problem but you might have to check it out!!

  8. #8
    londoncalling is offline Junior Member
    Join Date
    Nov 2011
    Location
    London
    Posts
    4

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    Quote Originally Posted by cohibaman View Post
    Check with Asrock website to make sure your ram is compatible for your MB and also check to see if your board is listed with Corsair's site for the ram you have, ...... Also I read, if pins got bent when CPU got installed it could also cause this code....hopefully that isn't the problem but you might have to check it out!!
    Thanks for getting back so quickly. I remember reading somewhere about using this RAM with MB but cannot find reference now. I checked the sites like you suggested and guess what, Corsair lists it as compatible but it's not listed as supported on the ASRock site!! I will try reseating memory like you suggest although I thought I was pressing down pretty hard already... I sure hope it's not the CPU pins as I guess this means MB is wrecked... Yes?

    Thanks,
    Robert.

  9. #9
    mhanna is offline Junior Member
    Join Date
    Nov 2011
    Location
    Exeter UK
    Posts
    1

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    The AMI Debug code 30 is normal for a system waking up from the S3 sleep state - check the THE ACPI/ASL Checkpoints at the bottom of the list below.

    This is the part that is missing from the ASROCK user manual. 30 is what I get from S3 with AA from a cold Boot.

    List of Debug Codes

    For your reference, here's a list of debug codes used by AMI for Sandy Bridge. Codes in this list correspond with the onboard Debug Led codes. Applies to Maximus IV Extreme, P8P67 series, Asrock P67 boards etc.

    Progress Codes

    00 - Not used
    01 - Power on. Reset type detection (soft/hard)
    02 - AP initialization before microcode loading
    03 - System Agent initialization before microcode loading
    04 - PCH initialization before microcode loading
    05 - OEM initialization before microcode loading
    06 - Microcode loading
    07 - AP initialization after microcode loading
    08 - System Agent initialization after microcode loading
    09 - PCH initialization after microcode loading
    0A - OEM initialization after microcode loading
    0B - Cache initialization

    SEC Error Codes

    0C - Reserved for future AMI SEC error codes
    0D - Reserved for future AMI SEC error codes
    0E - Microcode not found
    0F - Microcode not loaded

    PEI Phase

    10 - PEI Core is started
    11 - Pre-memory CPU initialization is started
    12 - Pre-memory CPU initialization (CPU module specific)
    13 - Pre-memory CPU initialization (CPU module specific)
    14 - Pre-memory CPU initialization (CPU module specific)
    15 - Pre-memory System Agent initialization is started
    16 - Pre-Memory System Agent initialization (System Agent module specific)
    17 - Pre-Memory System Agent initialization (System Agent module specific)
    18 - Pre-Memory System Agent initialization (System Agent module specific)
    19 - Pre-memory PCH initialization is started
    1A - Pre-memory PCH initialization (PCH module specific)
    1B - Pre-memory PCH initialization (PCH module specific)
    1C - Pre-memory PCH initialization (PCH module specific)
    1D - OEM pre-memory initialization codes
    1E - OEM pre-memory initialization codes
    1F - OEM pre-memory initialization codes

    20 - OEM pre-memory initialization codes
    21 - OEM pre-memory initialization codes
    22 - OEM pre-memory initialization codes
    23 - OEM pre-memory initialization codes
    24 - OEM pre-memory initialization codes
    25 - OEM pre-memory initialization codes
    26 - OEM pre-memory initialization codes
    27 - OEM pre-memory initialization codes
    28 - OEM pre-memory initialization codes
    29 - OEM pre-memory initialization codes
    2A - OEM pre-memory initialization codes
    2B - Memory initialization. Serial Presence Detect (SPD) data reading
    2C - Memory initialization. Memory presence detection
    2D - Memory initialization. Programming memory timing information
    2E - Memory initialization. Confi guring memory
    2F - Memory initialization (other)

    30 - Reserved for ASL (see ASL Status Codes section below)
    31 - Memory Installed
    32 - CPU post-memory initialization is started
    33 - CPU post-memory initialization. Cache initialization
    34 - CPU post-memory initialization. Application Processor(s) (AP) initialization
    35 - CPU post-memory initialization. Boot Strap Processor (BSP) selection
    36 - CPU post-memory initialization. System Management Mode (SMM) initialization
    37 - Post-Memory System Agent initialization is started
    38 - Post-Memory System Agent initialization (System Agent module specific)
    39 - Post-Memory System Agent initialization (System Agent module specific)
    3A - Post-Memory System Agent initialization (System Agent module specific)
    3B - Post-Memory PCH initialization is started
    3C - Post-Memory PCH initialization (PCH module specific)
    3D - Post-Memory PCH initialization (PCH module specific)
    3E - Post-Memory PCH initialization (PCH module specific)
    3F - OEM post memory initialization codes

    40 - OEM post memory initialization codes
    41 - OEM post memory initialization codes
    42 - OEM post memory initialization codes
    43 - OEM post memory initialization codes
    44 - OEM post memory initialization codes
    45 - OEM post memory initialization codes
    46 - OEM post memory initialization codes
    47 - OEM post memory initialization codes
    48 - OEM post memory initialization codes
    49 - OEM post memory initialization codes
    4A - OEM post memory initialization codes
    4B - OEM post memory initialization codes
    4C - OEM post memory initialization codes
    4D - OEM post memory initialization codes
    4E - OEM post memory initialization codes
    4F - DXE IPL is started

    PEI Error Codes

    50 - Memory initialization error. Invalid memory type or incompatible memory speed
    51 - Memory initialization error. SPD reading has failed
    52 - Memory initialization error. Invalid memory size or memory modules do not match
    53 - Memory initialization error. No usable memory detected
    54 - Unspecifi ed memory initialization error
    55 - Memory not installed
    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 not available
    5C - Reserved for future AMI error codes
    5D - Reserved for future AMI error codes
    5E - Reserved for future AMI error codes
    5F - Reserved for future AMI error codes

    DXE Phase

    60 - DXE Core is started
    61 - NVRAM initialization
    62 - Installation of the PCH Runtime Services
    63 - CPU DXE initialization is started
    64 - CPU DXE initialization (CPU module specific)
    65 - CPU DXE initialization (CPU module specific)
    66 - CPU DXE initialization (CPU module specific)
    67 - CPU DXE initialization (CPU module specific)
    68 - PCI host bridge initialization
    69 - System Agent DXE initialization is started
    6A - System Agent DXE SMM initialization is started
    6B - System Agent DXE initialization (System Agent module specific)
    6C - System Agent DXE initialization (System Agent module specific)
    6D - System Agent DXE initialization (System Agent module specific)
    6E - System Agent DXE initialization (System Agent module specific)
    6F - System Agent DXE initialization (System Agent module specific)

    70 - PCH DXE initialization is started
    71 - PCH DXE SMM initialization is started
    72 - PCH devices initialization
    73 - PCH DXE Initialization (PCH module specific)
    74 - PCH DXE Initialization (PCH module specific)
    75 - PCH DXE Initialization (PCH module specific)
    76 - PCH DXE Initialization (PCH module specific)
    77 - PCH DXE Initialization (PCH module specific)
    78 - ACPI module initialization
    79 - CSM initialization
    7A - Reserved for future AMI DXE codes
    7B - Reserved for future AMI DXE codes
    7C - Reserved for future AMI DXE codes
    7D - Reserved for future AMI DXE codes
    7E - Reserved for future AMI DXE codes
    7F - Reserved for future AMI DXE codes

    80 - OEM DXE initialization codes
    81 - OEM DXE initialization codes
    82 - OEM DXE initialization codes
    83 - OEM DXE initialization codes
    84 - OEM DXE initialization codes
    85 - OEM DXE initialization codes
    86 - OEM DXE initialization codes
    87 - OEM DXE initialization codes
    88 - OEM DXE initialization codes
    89 - OEM DXE initialization codes
    8A - OEM DXE initialization codes
    8B - OEM DXE initialization codes
    8C - OEM DXE initialization codes
    8D - OEM DXE initialization codes
    8E - OEM DXE initialization codes
    8F - OEM DXE initialization codes

    90 - Boot Device Selection (BDS) phase is started
    91 - Driver connecting is started
    92 - PCI Bus initialization is started
    93 - PCI Bus Hot Plug Controller Initialization
    94 - PCI Bus Enumeration 32
    95 - PCI Bus Request Resources
    96 - PCI Bus Assign Resources
    97 - Console Output devices connect
    98 - Console input devices connect
    99 - Super IO Initialization
    9A - USB initialization is started
    9B - USB Reset
    9C - USB Detect
    9D - USB Enable
    9E - Reserved for future AMI codes
    9F - Reserved for future AMI codes

    A0 - IDE initialization is started
    A1 - IDE Reset
    A2 - IDE Detect
    A3 - IDE Enable
    A4 - SCSI initialization is started
    A5 - SCSI Reset
    A6 - SCSI Detect
    A7 - SCSI Enable
    A8 - Setup Verifying Password
    A9 - Start of Setup
    AA - Reserved for ASL (see ASL Status Codes section below)
    AB - Setup Input Wait
    AC - Reserved for ASL (see ASL Status Codes section below)
    AD - Ready To Boot event
    AE - Legacy Boot event
    AF - Exit Boot Services event

    B0 - Runtime Set Virtual Address MAP Begin
    B1 - Runtime Set Virtual Address MAP End
    B2 - Legacy Option ROM Initialization
    B3 - System Reset
    B4 - USB hot plug
    B5 - PCI bus hot plug
    B6 - Clean-up of NVRAM
    B7 - Confi guration Reset (reset of NVRAM settings)
    B8 - Reserved for future AMI codes
    B9 - Reserved for future AMI codes
    BA - Reserved for future AMI codes
    BB - Reserved for future AMI codes
    BC - Reserved for future AMI codes
    BD - Reserved for future AMI codes
    BE - Reserved for future AMI codes
    BF - Reserved for future AMI codes

    C0 - OEM BDS initialization codes
    C1 - OEM BDS initialization codes
    C2 - OEM BDS initialization codes
    C3 - OEM BDS initialization codes
    C4 - OEM BDS initialization codes
    C5 - OEM BDS initialization codes
    C6 - OEM BDS initialization codes
    C7 - OEM BDS initialization codes
    C8 - OEM BDS initialization codes
    C9 - OEM BDS initialization codes
    CA - OEM BDS initialization codes
    CB - OEM BDS initialization codes
    CC - OEM BDS initialization codes
    CD - OEM BDS initialization codes
    CE - OEM BDS initialization codes
    CF - OEM BDS initialization codes

    DXE Error Codes

    D0 - CPU initialization error
    D1 - System Agent 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
    D6 - No Console Output Devices are found
    D7 - No Console Input Devices are found
    D8 - Invalid password
    D9 - Error loading Boot Option (LoadImage returned error)
    DA - Boot Option is failed (StartImage returned error)
    DB - Flash update is failed
    DC - Reset protocol is not available

    S3 Resume Progress Codes

    E0 - S3 Resume is stared (S3 Resume PPI is called by the DXE IPL)
    E1 - S3 Boot Script execution
    E2 - Video repost
    E3 - OS S3 wake vector call
    E4 - Reserved for future AMI progress codes
    E5 - Reserved for future AMI progress codes
    E6 - Reserved for future AMI progress codes
    E7 - Reserved for future AMI progress codes

    S3 Resume Error Codes

    E8 - S3 Resume Failed
    E9 - S3 Resume PPI not Found
    EA - S3 Resume Boot Script Error
    EB - S3 OS Wake Error
    EC - Reserved for future AMI error codes 31
    ED - Reserved for future AMI error codes 31
    EE - Reserved for future AMI error codes 31
    EF - Reserved for future AMI error codes 31

    Recovery Progress Codes

    F0 - Recovery condition triggered by firmware (Auto recovery)
    F1 - Recovery condition triggered by user (Forced recovery)
    F2 - Recovery process started
    F3 - Recovery firmware image is found
    F4 - Recovery firmware image is loaded
    F5 - Reserved for future AMI progress codes
    F6 - Reserved for future AMI progress codes
    F7 - Reserved for future AMI progress codes

    Recovery Error Codes

    F8 - Recovery PPI is not available
    F9 - Recovery capsule is not found
    FA - Invalid recovery capsule
    FB - Reserved for future AMI error codes
    FC - Reserved for future AMI error codes
    FD - Reserved for future AMI error codes
    FE - Reserved for future AMI error codes
    FF - Reserved for future AMI error codes

    ACPI/ASL Checkpoints

    01 - System is entering S1 sleep state
    02 - System is entering S2 sleep state
    03 - System is entering S3 sleep state
    04 - System is entering S4 sleep state
    05 - System is entering S5 sleep state
    10 - System is waking up from the S1 sleep state
    20 - System is waking up from the S2 sleep state
    30 - System is waking up from the S3 sleep state
    40 - System is waking up from the S4 sleep state
    AC - System has transitioned into ACPI mode. Interrupt controller is in APIC mode
    AA - System has transitioned into ACPI mode. Interrupt controller is in APIC mode

  10. #10
    londoncalling is offline Junior Member
    Join Date
    Nov 2011
    Location
    London
    Posts
    4

    Default Re: Asrock Z68 Fatal1y Pro Gen3 Dr.Debug Code 30

    Hi all, just a quick update. Tried reseating the ram but same so ordered some new, different ram... Kingston - KHX1600C9D3K2/4GX - Which is on the ASRock site as compatible. Arrived today and guess what... POST... I am happy!

    So, I don't know if it's the corsair was not compatible or was wrecked by the Post Office, my guess is the PO but you may want to check, double check with Corsair. But, I would say the Kingston feels far more solid, better made... The heatsink fins on the corsair are pretty flakey. The other thing is that my BeQuiet Dark Rock will now fit, the Vengence fins were too high.

    No time to get any further today... Work :( but hopefully put it all together tomorrow... Will keep yo posted...

Thread Information

Users Browsing this Thread

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

Bookmarks

Posting Permissions

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