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

Thread: New build getting 45 Dr.Debug code




  1. #1
    Join Date
    Jul 2011
    Location
    Illinois
    Posts
    4

    Default New build getting 45 Dr.Debug code

    Just finished putting together the comp and go to turn it on for the first time. The fans run fine but I get no signal on the monitor. On the Dr Debug LED display I get the code 19 then 56 then 49 then 45 and then it hangs on 45. I connected the little speaker that was included and nothing outputs from that. I removed the CPU Cooler and double checked that the CPU was inserted properly. I'm not sure what 45 means or what I should do?

    Specs:
    CPU: i5 2500K LGA 1155 Unlocked (stock)
    CPU Cooler: CPU Cooler Hyper 212 Plus
    RAM: 2x4GB DDR3 G.Skill Ripjaws (7-8-7-24)
    GPU: MSI N560GTX-Ti Hawk
    HDD: Western Digital Caviar1TB
    MoBo: Asrock P67 Extreme4
    PSU: Corsair TX750
    Case: CoolerMaster HAF 922
    OS: 64-bit Windows 7
    Bios: P1.70-15B
    Last edited by Oblivionslol; 07-15-2011 at 12:38 PM.

  2. #2
    Join Date
    Mar 2011
    Location
    Taiwan
    Posts
    562

    Default Re: New build getting 45 Dr.Debug code

    Dear Oblivionslol,

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

    Please kindly refer to below suggestions for testing.
    1. Please insert your memory module in the white 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 two stick 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

  3. #3
    Join Date
    Jul 2011
    Location
    Illinois
    Posts
    4

    Default Re: New build getting 45 Dr.Debug code

    ASRock TSD Emiy,

    I followed your instructions and it was indeed 1 of the sticks of memory that was the root of the problem, when only 1 is plugged into the white DRAM slot it runs fine.
    This has saved me a bit of a headache. Thanks! :)

    -Oblivionslol

  4. #4
    Join Date
    Jul 2011
    Location
    Brantford, Ontario, Canada
    Posts
    5

    Default Re: New build getting 45 Dr.Debug code

    I too am having error code 45. I have tested both modules by themselves in the #1 slots of A and B. But when set into dual channel it won't boot. I bought this brand new board on Ebay, therefore I have no dealer to go too. Neither of the #A-B2 slots will boot anything. Only way I can even boot - is with both modules in A1 and B1 in single channel. I think it may be possible that those slots are dead. Even if I stick them in those slots by themselves it gives #45.

    Any ideas? Everything is brand new in the system. Including memory.

  5. #5
    Join Date
    Jul 2011
    Location
    Illinois
    Posts
    4

    Default Re: New build getting 45 Dr.Debug code

    What are your system specs. Additionally, I came across this and it may be helpful to you

    Condition Beeps Code Debug Code
    Normal 1 short beep after POST With goodnight LED enabled, debug code will disappear after the beep.
    Bad CPU No beep No debug code
    Bad memory No beep 45
    Without memory 3 long beeps 53
    Without CPU No beep(No Power) No debug code
    Without VGA card 5 long beeps Beeps atd6, then show "0d"

  6. #6
    Join Date
    Jul 2011
    Location
    Brantford, Ontario, Canada
    Posts
    5

    Default Re: New build getting 45 Dr.Debug code

    Specs:
    CPU: i5 2500K LGA 1155 Unlocked (stock)
    CPU Cooler: CPU Cooler Corsair H70
    RAM: 2x4GB DDR3 Corsair Vengence (Low profile) 9-9-9-24
    GPU: PNY Geforce 460
    HDD: Western Digital Green 2TB
    HDD2: WD Digital 500GB
    HDD3: WD Digital 250GB
    MoBo: Asrock P67 Extreme4
    PSU: Corsair TX750
    Case: CoolerMaster HAF-X
    OS: 64-bit Windows 7
    Bios: P1.90-15B (Updated it myself) was a 1.70

    I also checked for the beeps and nothing beeps.

    I just bought this ram and it's brand new, but so is everything else. So I want to make sure that it's not the board. Maybe I've been out of the game to long, maybe you can answer me this, will a pc boot if a single channel is placed in a #2 slot? Because I can boot in any of the A1-B1 slots, but not a A1 B2 kinda deal. So it gave no beep with the 45 code. Should I call for RMA with Corsair then?
    Last edited by whitepyro; 07-17-2011 at 03:44 AM.

  7. #7
    Join Date
    Jul 2011
    Location
    Illinois
    Posts
    4

    Default Re: New build getting 45 Dr.Debug code

    I assume you've connected the mini speaker to the motherboard to test for beeps? Not that it matters, as I did that and obviously didn't get any beeps. If you're getting 45 it's definitely a memory problem. If both memory sticks aren't defective (only 1 of mine was) a single stick in the #2 channel should allow for a boot. I was able to boot using my non - defective stick.

    I've already RMA'd my memory and it appears that may be what you need to do as well.

  8. #8
    Join Date
    Jul 2011
    Location
    Brantford, Ontario, Canada
    Posts
    5

    Default Re: New build getting 45 Dr.Debug code

    Well neither of the modules will boot in A2 or B2, which has me thinking, maybe the board itself is to blame..

  9. #9
    Join Date
    Jul 2011
    Location
    Brantford, Ontario, Canada
    Posts
    5

    Default Re: New build getting 45 Dr.Debug code

    Had a friend come over and try another set of dual channel memory.. Same result, next idea? B2 And A2 are defective???

  10. #10
    Join Date
    Jul 2011
    Location
    Brantford, Ontario, Canada
    Posts
    5

    Default Re: New build getting 45 Dr.Debug code

    So I've tried 3 different pairs of DDR3, nothing will post in A2/B2 ram slots, cleared CMOS, reset timings, set manual voltage, so on and so forth. There is no way it's the ram, but more likely the ram slots on the board. So what can I do about this? All result in code 45.

Page 1 of 2 12 LastLast

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
  •