• 1 Post
  • 48 Comments
Joined 1 year ago
cake
Cake day: March 4th, 2024

help-circle






  • Honestly it might still just be the SOC failing - when I worked in hardware repair most laptops had separate chips for each but now tech has progressed to have them both on one “system on a chip”. So back in my day if it was gpu the cpu might keep humming along while the gpu was fried, but that’s less relevant now-a-days.

    Sorry bro, I’d say back anything you give a shit about up because she’s probably on the way out. If my experience holds, even with the single chip boards - eventually it’ll artifact like this every boot and you’ll be digging out the hard drives to get at your files.

    In your shoes I’d recommend fucking with the drivers and your OS, it’s still possible that it’s the drivers are interacting with the hw wrong and causing the issues, but in reality that’s a long shot. Also run memtest86 overnight one night and see if maybe its the ram?

    If it does die and you’re feeling hack-y, the dude who suggested an oven reflow is not wrong. If you manage to figure out getting the motherboard out (make sure no plastic that could melt!!) and put it in the oven at reflow temp, you might revive it. If picking the laptop up and twisting the body slightly can cause the crash, it’s almost definitely soldier joint issues.

    Are the fans doing anything under normal load? If it’s not moving air at all that’s cause for concern too. Dead fans mean thermal issues, which can cook chips.

    Oh one last edit, check how long the warranty is - fucky soldier is a manufacturing defect.

    Best of luck brother, sorry for the shitty news.




  • I don’t know about other materials so make that decision first but I’ll say opaque PETG will do better with UV than translucent.

    But honestly just paint the top that’ll be getting hit by the sun.

    Make sure it’s not like, going to get crazy hot in the summer and melt to the opening and seal it, could be a nightmare.




  • I know it’s not totally relevant but I once convinced a company to run their log aggregators with 75 servers and 15 disks in raid0 each.

    We relied on the app layer to make sure there was at least 3 copies of the data and if a node’s array shat the bed the rest of the cluster would heal and replicate what was lost. Once the DC people swapped the disk we had automation to rebuild the disks and add the host back into the cluster.

    It was glorious - 75 servers each splitting the read/write operations 1/75th and then each server splitting that further between 15 disks. Each query had the potential to have ~1100 disks respond in concert, each with a tiny slice of the data you asked for. It was SO fast.