Jump to content

Welcome to ExtremeHW

Welcome to ExtremeHW, register to take part in our community, don't worry this is a simple FREE process that requires minimal information for you to signup.

 

Registered users can: 

  • Start new topics and reply to others.
  • Show off your PC using our Rig Creator feature.
  • Subscribe to topics and forums to get updates.
  • Get your own profile page to customize.
  • Send personal messages to other members.
  • Take advantage of site exclusive features.
  • Upgrade to Premium to unlock additional sites features.

maddangerous

Members
  • Posts

    61
  • Joined

  • Last visited

  • Feedback

    0%

Reputation

41 Is on the right road

Personal

  • Location
    A Cozy Office
  • Interests
    Cars, Computers, Motorcycles, Mountain BIking
  • Occupation
    IT

Recent Profile Visitors

1,310 profile views

My Awards

  1. Edit: failed to read, disregard lol
  2. Thanks, I hope as well! I really didn't want to take this thing apart *
  3. Alright, so far I haven't had any stability issues or general weirdness, so hopefully it was just conflicting memory settings in the BIOS or something. I've passed all the stress tests so far, and I've also configured Buildzoids timings and run the tests, so far so good.
  4. Normally the setting would be right there, to select the band. what exactly are you trying to accomplish? Are you trying to wirelessly connect two devices directly, like plugging an Ethernet cable directly into two computers?
  5. ok, so the host specs are as follows: Intel NUC11TNHi50L Intel i5-1135G7 (4c/8t) bsae clock 2.4 GHz, turbo is 4.2GHz 32 GB (2x16GB) Mushkin Redline DDR4 3200MHz, CL16 1TB Samsung 970 Evo Plus 2x 2.5Gb Intel i225-LM NIC I'm currently using ESXi v8.0U1a, but I'm considering moving to Proxmox (working on getting a test system up with Proxmox). OPNsense is running as a VM. Originally I had it running with 2 vCPU, 512 MB RAM, and 30 GB HDD space. Recently I bumped it up to 4vCPU, and 1 GB RAM, due to using openvpn and having several concurrently connected users, I was seeing higher utilization and wanted more headroom. I may need to assign more RAM still, I'm at 60% utilization there still. Having this as a VM is nice, because: Resource assignment changes are easy. shut down the VM, add/remove CPU/RAM, power up. Rolling back from a failed upgrade is easy. Take a snapshot of the VM, install update(s), test, roll back to snapshot if needed. Delete snapshot if everything works fine. My favorite part... the VM reboots in ~23 seconds. I don't do anything too crazy right now in OPNsense, here's what it's doing: OpenVPN setup for some friends to connect to game servers. VLANs are routed here so I can use firewall rules instead of switch ACLs to manage traffic. QoS to manage bufferbloat is in place. Everything in my home that uses NTP syncs to OPNsense as the local time server (for now). I've got netflow setup, but that really needs to be ingested elsewhere instead of it running on the firewall. Basically I need to setup another stack for monitoring and export netflow data from the firewall. DDNS configured to update cloudflare for my domain GeoIP filtering In progress project is getting Wireguard configured for my phone, as OpenVPN, while nice, dstroys battery life on mobile devices in my experience.
  6. holy crap, life got in the way and I totally forgot about this. I’ll have something in here later this afternoon. especially since the NUC is actually in prod now.
  7. we'll see, getting to those stress tests finally I ran the OCCT Memory benchmark for an hour earlier, and that passed successfully. I suppose I'll run linpack in OCCT tonight or tomorrow. OCCT Memory was auto instruction set and threads, 80% memory
  8. Nope, no SATA drives. All NVME. I too am stumped. although, I'm not all the way through testing, so there's the possibility I'm on the right track here. going to put this through some stress testing later today and see where that gets me. hoping it's stable, fingers crossed. I'd like to get this kit running the speed/timings it should be running
  9. Alright I've been kinda bad at keeping this updated. I've got the BIOS reset, and set these settings: I'm not running the speed and timings this kit is capable of at the moment. After settings were changed I was able to boot. I reinstalled Windows 11 Pro, ran all windows updates and installed all of my motherboard drivers (Several reboots during this time.) I went to install the Corsair iCue software, as I have an HX1000i PSU and Virtuoso XT RGB. After that installed, I almost immediately got a BSOD for MEMORY_MANAGEMENT, and when I rebooted from that, another BSOD IRQL_NOT_LESS_OR_EQUAL, and the system fails to get past initial Windows boot stages. I got one more MEMORY_MANAGEMENT BSOD, and another BSOD IRQL_NOT_LESS_OR_EQUAL. All caused by ntoskrnl.exe, none have anything corsair indicated in the bugcheck files. Even the same memory address for them. Keep in mind that this is a ~20 minute old Windows install, from a known good USB stick that I made on a separate working computer. When I booted into the BIOS, and reset to factory default settings, rebooted back into the BIOS immediately and set those same settings as in my screenshot above, computer seems to be fine since, the little bit I've used it. This is very strange. I'll be running stress tests before moving on to buildzoids timings and getting this kit off JEDEC speeds. I haven't run any stress tests yet, that's on the list for this weekend.
  10. Wow, that sounds like an adventure lol Honestly, i have a warranty, and if I'm getting it to the point where I'm checking the socket... I'm RMA'ing it. It's been rock-solid until wednesday, so I'm doubting bent pins. At this point, I'm honestly unsure what happened.
  11. well.. I didn't get the change to run a full system stress test. reinstalled windows since that was corrupted, and it froze. Upon reboot, intermittantly, I'll get the CPU and MEM debug LED's on the board turning on and it fails to boot. If it doesn't fail to boot, windows bluescreens, and back to the debug LEDs again. I don't have another AM5 CPU to test with, and moving DIMMs around didn't help. Looks like I'm going to Microcenter tomorrow, hopefully whatever the hell happened didn't damage all 5 of my NVMe drives too.
  12. agreed. However, why furmark? Isn’t that GPU?
  13. Aight so, I had to reset the BIOS twice, but I was able to get into windows. First reset, post code checker was stuck on 00 for a few minutes, and one of the debug LEDs was on (CPU I think?) Power cycled the machine, same thing, so I did a BIOS reset again and I was able to POST + load windows. First thing I did, was make a backup of my stuff. It wasn't time for my weekly backup yet, so I had some stuff I'd lose if I didn't do that, so I'm good there. I'm going to grab the latest BIOS and flash that, see what happens. Oddly, the whole machine does feel snappier overall, so something funky was definitely happening. I didn't change any BIOS settings, prioritized getting my data before messing around.
  14. That's in the cards to try, and yeah it was released oct 17th as a beta bios. Just have to get the time to get to it.
×
×
  • Create New...

Important Information

This Website may place and access certain Cookies on your computer. ExtremeHW uses Cookies to improve your experience of using the Website and to improve our range of products and services. ExtremeHW has carefully chosen these Cookies and has taken steps to ensure that your privacy is protected and respected at all times. All Cookies used by this Website are used in accordance with current UK and EU Cookie Law. For more information please see our Privacy Policy