New Build - Problems

Page 1 of 2 12 LastLast

  1. Posts : 58
    Win10 Pro x64 [22H2 19045.2604]
       #1

    New Build - Problems


    Specifications: System Builder - Ryzen 5 2600 3.4 GHz 6-Core, GeForce GTX 960 4 GB SSC ACX 2.0+, Focus G ATX Mid Tower - PCPartPicker

    EVGA GTX 960 was used (tested, working, in my old FX-8350 system [2nd system] = no problems there).
    TP-Link Archer T5E PCIe WiFi NIC was "Renewed" (Amazon).

    This build started with a Ryzen 5 1600 (YD1600BBAFBOX). Swapped for the 2600 because of no bona fide Win11 support.

    I will now admit to a very embarrassing mistake. I initially set the RAM to 1600MHz (assuming all Ryzen 5's could take it; I admit I was wrong, own my foolishness in full). As you can guess, crashes, crashes, crashes (BSODs for everything under the sun). As soon as I figured out my mistake, I immediately set it back to JEDEC 2133MHz.

    Reinstalled Win11, all that, verified no corruption etc. all good.
    ___
    Too, Win10 installed as MBR the first time. I tried MBR2GPT. I wound up reinstalling Win10 instead after (which did install GPT that time). I have also *disabled* CSM and *enabled* TPM 2.0 and Secure Boot EFI Windows. Just mentioning in case, for some wildly bizarre reason, any of this has any relation to...
    ___

    THE REAL PROBLEM NOW: Intermittently, I am getting what I'm pretty sure is one long and three short beep codes (I have installed a warning speaker). I am given to understand, on AMI (ASUS) motherboards this is pointing towards a GPU problem. But it's POSTing. No outright apparent VGA problems are presenting themselves.

    So far, this has happened twice. Both times after I'd switched the PSU off to move it elsewhere, this happens after booting again.

    Anyone have any ideas what's going on here?

    Building this for my mom (wanted her to stop getting robbed by OEM's on unusable garbage beyond 2 years) . I feel just absolutely horrible about this (if it's something I can't resolve). Please help?

    I should now mention that I have run two 1x4 (8 passes total) of Passmark's Memtest86. The RAM is good. (I am also assuming my mistake, given that, hasn't damaged the CPU's IMC. Those problems would pop up there too, wouldn't they?).

    EDIT: Dug this up... (obviously not a RTX but... interesting): Is this dangerous? 4 beeps but boots fine | Overclockers UK Forums
      My Computers


  2. Posts : 23,255
    Win 10 Home ♦♦♦19045.4355 (x64) [22H2]
       #2

    @Mortiferon

    Your troubleshooting has been on the money.
    There is something wrong with either the power supply or the vid card, or "between" the two.

    Things to try...

    1. Have the power supply tested. (Best Buy can do this, or get a power supply tester on Amazon)
    2. Make sure the video card is properly "seated", and that there is no dust, etc., in the PCIe slot.
    3. Make sure the 8 pin cable to the vid card is properly attached (both ends).
    4. Make sure you used the correct connector on the power supply end.
    5. Try a different vid card in that computer.


    Example power supply tester: Amazon.com
      My Computer


  3. Posts : 58
    Win10 Pro x64 [22H2 19045.2604]
    Thread Starter
       #3

    Thank you so extremely much, Ghot! You've likely just saved this build.

    The 12v is reading 10v and the 5v less according to HWiNFO64.

    New Build - Problems-psucropped.png

    I'm going to formally diagnose dying PSU.

    I've shut it down and will be aiming for a replacement. Ugh. I checked that, too (first thing I do when I get into BIOS) it had been fine, then.

    Now, to hope it's not damaged the GPU already... would be a real tearjerker.
      My Computers


  4. Posts : 23,255
    Win 10 Home ♦♦♦19045.4355 (x64) [22H2]
       #4

    Mortiferon said:
    Thank you so extremely much, Ghot! You've likely just saved this build.

    The 12v is reading 10v and the 5v less according to HWiNFO64.

    I'm going to formally diagnose dying PSU.

    I've shut it down and will be aiming for a replacement. Ugh. I checked that, too (first thing I do when I get into BIOS) it had been fine, then.

    Now, to hope it's not damaged the GPU already... would be a real tearjerker.

    Use a few other programs to check PSU voltage. Check also in the BIOS.
    Keep in mind, that the Asus M5A99FX Pro R2.0 motherboard is getting long in the tooth as well.
    Might be a problem with the PCIe socket also.

    IF you have to get a new power supply, go with Seasonic. Something like this...



    Good deal at Newegg... SeaSonic FOCUS Gold 750 W 80+ Gold Certified Semi-modular ATX Power Supply (SSR-750FM) - PCPartPicker

    Promo code...great deal at Newegg... SeaSonic FOCUS Plus Platinum 650 W 80+ Platinum Certified Fully Modular ATX Power Supply (SSR-650PX) - PCPartPicker


    At PCpartpicker you can choose your country (if not the US), at the top right.
    Always a good idea to put your country at least, in your profile. Makes it a lot easier when parts recommendations are needed.





    Most important... my assumptions here, are based on the beep code.
    Like I said... triple check the PSU voltages before replacing.
    IF the 12v rail is actually at 10.x volts... then a new power supply is needed.
      My Computer


  5. Posts : 58
    Win10 Pro x64 [22H2 19045.2604]
    Thread Starter
       #5

    This is all new with exception to the GPU and WiFi NIC. Not using the M5A99FX Pro R2.0 for any of this (that is the system that the GPU was tested in, no issues, before we pulled the trigger on the rest).

    I've checked my X570-E Gaming with HWiNFO64 and it's reading my RM 750 correctly:

    New Build - Problems-mypsu.png

    I'd think it very strange it would read accurate on mine, but inaccurate on the other (so similar). Thank you very much once again; I'd have missed it. I feel that it is most likely PSU, given the GPU worked in my old build (that old RM 750 power supply has also never been misread by any sensor monitoring software either).
      My Computers


  6. Posts : 2,549
    Windows 11
       #6

    Mortiferon said:
    This is all new with exception to the GPU and WiFi NIC. Not using the M5A99FX Pro R2.0 for any of this (that is the system that the GPU was tested in, no issues, before we pulled the trigger on the rest).

    I've checked my X570-E Gaming with HWiNFO64 and it's reading my RM 750 correctly:

    New Build - Problems-mypsu.png

    I'd think it very strange it would read accurate on mine, but inaccurate on the other (so similar). Thank you very much once again; I'd have missed it. I feel that it is most likely PSU, given the GPU worked in my old build (that old RM 750 power supply has also never been misread by any sensor monitoring software either).
    Beep codes are Hardware related but PSU's doesn't do that you either crash a ton or just can't boot
    Chances are your card is dying or has issues take it out re-seat it and use a different VGA power cable from the same PSU chances are a weak rail or what not but all signs point to the GPU having issues you probably never seen it on the other build but it could of been artifacting on you and you just didn't notice it
      My Computers


  7. Posts : 58
    Win10 Pro x64 [22H2 19045.2604]
    Thread Starter
       #7

    Argh. Well, voltages registering within tolerance in BIOS. And GPU-Z is saying it's getting 12v too. (Still suspicious of PSU anyway).

    I have attempted to induce this by shutdown + PSU switch toggle 20-some times and it hasn't done it again so far.

    Ran Unigine's Heaven benchmark, ultra, many times. There is nothing apparently wrong with this GPU.

    Re-re-checked absolutely everything. Everything is where it ought to be, and firmly seated.

    I'm pretty sure the two times I heard this, it was after unplugging and having physically moved it. (Which since I have done yet again; this time, no beep code sequence after). Perhaps it simply just wasn't seated right. Or there in fact is a problem with it and it's sneaky, no other telltale signs than this (which I'd never have even known about save I prefer a warning speaker in place; wahey, maybe why they're not included anymore lol)... I dunno. I'm out of ideas.

    Thanks for your help, guys. Always appreciated.
    Last edited by Mortiferon; 19 Aug 2021 at 00:15.
      My Computers


  8. Posts : 23,255
    Win 10 Home ♦♦♦19045.4355 (x64) [22H2]
       #8

    Mortiferon said:
    Argh. Well, voltages registering within tolerance in BIOS. And GPU-Z is saying it's getting 12v too. (Still suspicious of PSU anyway).

    I have attempted to induce this by shutdown + PSU switch toggle 20-some times and it hasn't done it again so far.

    Ran Unigine's Heaven benchmark, ultra, many times. There is nothing apparently wrong with this GPU.

    Re-re-checked absolutely everything. Everything is where it ought to be, and firmly seated.

    I'm pretty sure the two times I heard this, it was after unplugging and having physically moved it. (Which since I have done yet again; this time, no beep code sequence after). Perhaps it simply just wasn't seated right. Or there in fact is a problem with it and it's sneaky, no other telltale signs than this (which I'd never have even known about save I prefer a warning speaker in place; wahey, maybe why they're not included anymore lol)... I dunno. I'm out of ideas.

    Thanks for your help, guys. Always appreciated.


    Just keep an eye on it. There are many times when a GPU is not seated properly.
    Re-seating it, might be all that's necessary to solve a problem.
    I had a similar problem once... a teeny bit of dust down in the vid card slot. I had to use a tiny artists paint brush to remove the dust.

    As for those tiny speakers... I use them too. They don't come with motherboards, anymore, but you can still buy them on Amazon.

    Anyway, I'm glad it working now. If the problem surfaces again, just update this post.


      My Computer


  9. Posts : 2,549
    Windows 11
       #9

    Mortiferon said:
    Argh. Well, voltages registering within tolerance in BIOS. And GPU-Z is saying it's getting 12v too. (Still suspicious of PSU anyway).

    I have attempted to induce this by shutdown + PSU switch toggle 20-some times and it hasn't done it again so far.

    Ran Unigine's Heaven benchmark, ultra, many times. There is nothing apparently wrong with this GPU.

    Re-re-checked absolutely everything. Everything is where it ought to be, and firmly seated.

    I'm pretty sure the two times I heard this, it was after unplugging and having physically moved it. (Which since I have done yet again; this time, no beep code sequence after). Perhaps it simply just wasn't seated right. Or there in fact is a problem with it and it's sneaky, no other telltale signs than this (which I'd never have even known about save I prefer a warning speaker in place; wahey, maybe why they're not included anymore lol)... I dunno. I'm out of ideas.

    Thanks for your help, guys. Always appreciated.
    Good Job lucky for you it was only the GPU needed to be re-seated it happens to the best of us
    I myself tend to forget to even plug the GPU power in at times and look stupidly why it isn't showing anything lol
      My Computers


  10. Posts : 58
    Win10 Pro x64 [22H2 19045.2604]
    Thread Starter
       #10

    Aye, I feel a right heel for my initial colossal mistake with the RAM. It does happen though. I'm actually still lost in the woods there a bit (not been rich enough to mess with manual OC before). There's only a 3200MHz D.O.C.P profile available (not officially supported by R5 2600). Right now it's still JEDEC but I'd like to at least get that to 2993MHz. Ought I just to select "Auto" but force 2993MHz, you reckon?

    Technically my R5 5600x only officially supports 3200MHz but I have it stable at 3600MHz... (actually be curious to know if, over time, that could somehow degrade/damage my CPU on that one, going so much over what it's officially rated to handle; definitely don't want that).
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:20.
Find Us




Windows 10 Forums