Jump to content

gioGats

Member
  • Posts

    26
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

gioGats's Achievements

  1. Stumbled onto this troubleshooting a similar problem on a Z690 Asus ProArt. Under Win11 drivers, Asus only lists the Intel I225 Gigabit (for a port that's supposed to be 2.5Gb, but... after driver install link speed is 2500 Mbps). Installing that did BSOD my system, require a safe mode reboot, and Windows Security is complaining about my memory integrity now... BUT: under Win10 drivers, Asus has both the Win10 and Win11 versions of the Marvell Ethernet Driver. Separate cards for separate ports, and the 10G port showed up as an unknown ethernet in device manager. After installing the driver v3.1.6.0, second ethernet port is recognized and reports link speed 1410 Mbps. Measured speed on iperf3 running client <> Microtik 10G switch <> server is 9.04 Gbps.
  2. Right around what it said in the printout ~750 rpm. This is right around what it had been prior to the issue.
  3. x62 is on the CPU header, and power cables are still in. Is there any way to know if thermal paste has gone bad, other than that the problem goes away after reapplying it? Like a discoloration or texture?
  4. I just tried booting again, to interesting results. BIOS reported correct CPU frequencies and CPU of 50, rising about 1º per second. It topped off at 99, and I managed to get a successful boot into Linux to print the attached sensors report. This time the tubes on the x62 were not warm. No noticeable difference between in and out tubes at all. I'm suspecting a thermal paste issue? Which is concerning because the x62 came with pre-applied paste. Mobo was steady at 30º.
  5. Hey guys, looking for some creative troubleshooting help here. I've got a rig I built last November. i7-6800k cooled by a NZXT x62, Corsair 3000MHz RAM, overclock to 3.9 GHz. It's been running fine on all range of tasks, including some server tasks that would max out all cores for hours on end. I ran it for a few hours on a task that maxed out a single core. Seemed fine. Then it just shut down. Now when I load bios, it's reporting all sorts of weird frequencies: 2.2 GHz, 2.9, etc. It's also reporting CPU temp of 100ºC. I can boot windows but not linux, and even that only lasts for a minute before it shuts down. I removed the overclock, tightened the x62 (it wasn't loose, but worth a try), flashed the bios. All to no avail. The outbound tube on the x62 is warm when it's running, so the x62 is carrying some heat at least. I'm planning to swap in a different cooler tomorrow, but that's not much of a long term solution. What other things can I try to troubleshoot? What happened? And how do I make sure this doesn't happen again?
  6. Hey Guys, First time builder here, and I've got a weird thing going on. Rig is i7-6800k, Corsair 4x8GB 3000MHz, MSI X99A XPower Gaming Titanium and currently testing with an EVGA GeForce 210 refurb. The system will boot fine, both by shorting the case power pins and from the power button on the mobo. But when I try to restart--whether through shorting the reset pins, pressing the reset button on the board, or choosing to save and restart from bios--it shuts off, tries to turn back on, something clicks, and then nothing. Once in this state, it won't reboot unless I discharge the mobo through the button or by cycling the power supply. Anyone experience something similar? Do I have a faulty board on my hands?
  7. Then what? Just buy a whole new board and throw this one in the trash?
  8. Just got the mobo this Wednesday, so yes. I think I might just RMA it on Monday and hope for the best.
  9. Just pulled it from the case and back on the test bench. Still 00. Tried slow mode boot as well, with no luck.
  10. Unfortunately no, but it was working fine with this PSU before I installed it in the case.
  11. Currently there are no hard drives connected. Just CPU and GPU.
  12. Ran fine on the test bench with the updated bios. Tried CMOS.
  13. Unfortunately, tried all of that as well. I'm currently pulling the mobo out of the case to see if it will boot back on the box...
  14. The only thing on that list I haven't tried is the system speaker, because that's the one part I don't have.
  15. All the right power connectors are in... double and triple reseated and checked
×