[–] [S] 1 point 9 months ago (2 children)

PSU is 750. Heck, with the exception of the GPU it's the second most expensive part in the old girl. I upgraded it a few years back when I installed a more powerful fan for cooling.

its been more than enough for this setup for the last few years since then. Which basically confirms my suspicion that the PSU has crapped the bed.

Thanks for the assist.

  • source
  • parent
  • context
  • [–] 3 points 9 months ago* (3 children)

    Your PSU is too weak. All your devices are struggling to keep power, and the onboard power management is turning all your interfaces on and off.

    Easiest test would be to remove the GPU and use on-board graphics if you have that option. If not, try underclocking your GPU, and use your BIOS to underclock your memory and turn off everything else you aren't using.

    If you're not using SATA, disable it.

    It's a stretch, but might get you some stability. Otherwise, I'd get a bigger PSU, because the GPU you're running seems to be a power hog.

  • source
  • parent
  • context
  • [–] [S] 1 point 9 months ago* (4 children)

    dmesgg posted: (Edited to clean it up)

    [ 2958.891985] NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.

    [ 2958.892004] nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5

    [ 2958.892647] nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5

    [ 2958.892661] nvidia 0000:01:00.0: PM: failed to suspend async: error -5

    [ 2958.914133] sd 2:0:0:0: [sdb] Synchronizing SCSI cache

    [ 2958.914134] sd 0:0:0:0: [sda] Synchronizing SCSI cache

    [ 2958.914214] sd 7:0:0:0: [sdd] Synchronizing SCSI cache

    [ 2959.095302] PM: Some devices failed to suspend, or early wake event detected

    [ 2959.095899] rtlwifi: rtlwifi: wireless switch is on

    [ 2959.198925] ata6: SATA link down (SStatus 0 SControl 300)

    [ 2959.198971] ata4: SATA link down (SStatus 0 SControl 300)

    [ 2959.199015] ata5: SATA link down (SStatus 0 SControl 300)

    [ 2959.340791] usb 4-2: reset full-speed USB device number 2 using ohci-pci

    [ 2959.347379] usb 1-1: reset full-speed USB device number 4 using ohci-pci

    [ 2960.680797] Bluetooth: hci0: command 0xfc20 tx timeout

    [ 2960.680830] Bluetooth: hci0: RTL: download fw command failed (-110)

    [ 2960.682885] Bluetooth: hci1: unexpected event for opcode 0xfc20

    [ 2960.683184] OOM killer enabled.

    [ 2960.683191] Restarting tasks ... done.

    [ 2960.685177] random: crng reseeded on system resumption

    [ 2960.685186] PM: suspend exit

    [ 2960.744103] Bluetooth: hci1: RTL: examining hci_ver=06 hci_rev=0e2f lmp_ver=06 lmp_subver=a041

    [ 2960.794398] Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)

    [ 2960.980858] r8169 0000:02:00.0 enp2s0: Link is Down

    [ 2961.076932] Bluetooth: hci1: RTL: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821

    [ 2961.078903] Bluetooth: hci1: RTL: rom_version status=0 version=1

    [ 2961.080916] Bluetooth: hci1: RTL: btrtl_initialize: key id 0

    [ 2961.080927] Bluetooth: hci1: RTL: loading rtl_bt/rtl8821a_fw.bin

    [ 2961.081266] Bluetooth: hci1: RTL: loading rtl_bt/rtl8821a_config.bin

    [ 2961.081297] Bluetooth: hci1: RTL: cfg_sz 10, total sz 17438

    [ 2961.940974] Bluetooth: hci1: RTL: fw version 0x0e2fa041

    [ 2962.080210] Bluetooth: MGMT ver 1.23

    [ 2963.452055] r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control rx/tx

    [ 3024.508246] usb 4-2: reset full-speed USB device number 2 using ohci-pci

    [ 3033.432024] Bluetooth: hci1: Opcode 0x0402 failed: -110

    [ 3033.432041] Bluetooth: hci1: command 0x0402 tx timeout

       ~ 

  • source
  • parent
  • context
  • [–] 1 point 9 months ago*

    something made on paper

    On one paper write out the times in whatever increments you want to measure, like every 15 minutes.

    Then another piece of paper, start at 0 and count up in the same increment.

    To us it put the "clock" paper down, then line up the "stop watch" paper to have zero at the start time, and look to see what it says for the end time.

    You can literally make it into a slide rule and use different materials to make it more durable, but I think that's a quick and dirty way to do what you want.

    But really, the mental math isn't that hard, but this would help people who are unable but still need to track time.

    Quick edit:

    You could just let them use a 24 hr clock too, that makes the math way easier unless working overnight. Then you convert it back if necessary, which is also easy

  • source
  • parent
  • context
  • [–] 1 point 9 months ago

    Print a paper ruler, replace inches with hours, mark time with clips or pencils, use a second ruler to measure, 1/4in = 15 mins. Should be easy math for most people to convert 2.5in to 2.5 hours etc.

  • source
  • [–] [S] 2 points 9 months ago

    I've spent so much time testing RAM, using DISM, and scanning drive health...its nauseating. Considering the machine is good with the old GPU (which I want to rehousing in a different machine), I feel comfortable ruling out other peripherals (mouse, keyboard, audio interface). But correct me if I'm wrong here

    I ran MSI Afterburner for a while too, forgot to mention that. Even under load, none of the components went over 30°. I stress tested the CPU and GPU for a long time just to see if it made the system more unstable, but it didn't seem to make a difference

  • source
  • parent
  • context
  • [–] 1 point 9 months ago (1 child)

    Have you tried to reinstall windows? Or at least run a repair? Sometimes this can be a OS problem.

    You can also use a wattage meter where you plug the computer in and measure it through the meter. You could see if there is a abnormally high power draw and begin to narrow things down.

    Unplug everything that isn't necessary to see if it's a accessory issue.

    One last thing you can do is grab a pen and paper, and setup a software CPU temp monitor and write down everything that happens when it goes black. Especially sounds the computer makes.

    Also try and replicate it with another monitor.

  • source
  • [–] [S] 1 point 9 months ago

    No other USB issues

    The motherboard is becoming my concern. Before I disassemble my computer again and buy yet another part, I'd like to make absolutely sure that this is the problem and not (for example) a simple setting change

    Different cable as in HDMI? In that case no, and I don't have a different DP cable to try. I'm using the one that came with my display

  • source
  • parent
  • context
  • [–] 1 point 9 months ago (1 child)

    Do you have issues with other usb devices?

    If two GPUs have had the issue would it not be a problem with the motherboard?

    Have you tried a different cable to the monitor?

  • source
  • [–] 4 points 9 months ago* (last edited 9 months ago)

    How did you clean it? The schmoo gets jammed in the bottom of the port and after 10 years of insertion cycles it gets really stuck down there. If you can find one get a thumb tack with a really tiny (but still pointy) tip and use that to scrape it out. Do multiple cycles of cleaning, blowing compressed air, inserting/removing cable repeat.

    The pins are only on one side of the receptacle so figure out where that is, and keep the metal thumb tack to that side so you don't short/damage the pins. Also while you're at it inspect the pins. They should be gold. If they're brown then maybe the gold coating got wiped out somehow. I destroyed a cable (not the phones end thankfully) by having some water in there and it shorted some of the pins.

    They also make kits for cleaning ports. I have a USB C one that looks like an asterisk that I like. The dingus is plastic and soft so you shouldn't be able to short the pins with it, but it's not as good at scraping out the really nasty stuff.

    Oh also try a stiff plastic bristle brush.

  • source
  • parent
  • context
  • [–] 2 points 9 months ago* (last edited 9 months ago)

    Because apples lightning is a shitty connector standard and they refused to switch to USB, because people will buy a new device more often when it breaks quickly.

    If its actually the socket thats dead then its kinda hard to do anything, but maybe its the cable? You could also try hotgluing the cable in place if you just wanna experiment.

  • source
  • [–] 6 points 9 months ago (4 children)

    It likely has debris in the charging port, often lint from living in pockets or purses. Get a bright flashlight and take a look. Be careful not to damage the connections if you see something and try to remove it

  • source
  • view more: ‹ prev next ›