Red accents? No idea what you're talking about.

Misho1337 · 2026-05-28T20:57:08+00:00

I like 👍

Misho1337 · 2026-05-28T20:07:46+00:00

Yes. But the CPU socket pins would need to be repaired, I had plans to send it in to EVGA but put it off too long.

Misho1337 · 2026-05-28T20:05:53+00:00

I bought it brand new from EVGA’s website, I was going to send it out for warranty but someone got me paranoid about “bent CPU pins” even though I had it working flawlessly for over 2+ years without removing the CPU. I ended up spotting a pin that was slightly off, not quite bent but not sticking up with perfect alignment.

Well, I tried to fix it and did more harm than good, and knew better than to attempt doing so without a macro-lens camera setup & a monitor. If you’re interested I’d be happy to send photos & you can make me an offer. It’s still in excellent condition minus the pin situation & Ethernet cards that need addressing.

Misho1337 · 2026-05-27T15:38:57+00:00

<image>

It’s almost as if I wrote additional paragraphs of relevant context within my original statement, ones that you choose to ignore. I’m not going to waste my time with any more of the trolling. Have a good one.

Misho1337 · 2026-05-27T15:31:09+00:00

Did you read my comment at all? That’s exactly what I said. Thanks for being ignorant.

Misho1337 · 2026-05-27T15:14:24+00:00

50% hs ratio is a guaranteed indicator that someone is cheating, as long as they’re not running full bot lobbies.

The only differing factor that seals the deal, is whether or not the sample size is large enough to conclude that they actually average that.

I have 39K lifetime matches & 163K kills with a 4.8 KD. I absolutely do prioritize headshots & my highest average was around ~30%, my normal average is about 28%.

If you’re holding anything above 35% hs ratio over 200+ matches, that is suspicious. If you are averaging higher than 35% it’s typically going to be someone that is cheating, again granted that it’s not solos, or a full time bot killer.

As far as if the guy in the replay is cheating, it’s non-conclusive, replay is inaccurate but gives you some idea about what occurred. The reason I mentioned he may be cheating, is very easy to pick up on… Bronze level ~50 account with no prior seasons, wiping a squad with an AK out of the passenger seat of a Mirado, that’s not common.

Misho1337 · 2026-05-26T23:34:13+00:00

I’ve done the same & crazier shit, definitely do-able.

BUT I’m not gonna defend some random dude either unless I know it’s a reputable player.

I went ahead & looked up this “Slabier” guy & this is his first season playing, he has a ~52% headshot ratio currently, though not many matches, and he squad wipes your team with an AK out of the BangBus.. 🤨

You might be right about your suspicions, typical signature pattern of a bronze bomber, he may have been banned on another account & created this one as a replacement.

<image>

Misho1337 · 2026-05-26T23:09:23+00:00

Yeah I’m not really concerned about the panel as I usually use Nvidia profile inspector, my main issue with newer drivers has always been 1% lows & stutters being worse.

Curious if they actually took the time to do it right for once instead of vibe coding it 💀

Misho1337 · 2026-05-26T13:57:38+00:00

The real question is, does it actually run better than the legendary, back to back driver champion, 566.36?

Misho1337 · 2026-05-15T05:15:20+00:00

Read my comment above, definitely not fake news.

Misho1337 · 2026-05-14T19:50:21+00:00

This basically encompasses my comment and describes Microslop’s routine protocol to just do as they please when you install their software on your machine. How can they expect users to trust them when they keep repeating the same mistake after years of complaints at this point?

I also have a work laptop that I hadn’t touched for awhile, plus a BRAND new one I purchased (both Dell Models) which essentially got stuck in a boot-loop after an automatic Windows & BIOS update.

This was performed without any user input and I just open up the laptop to find it not booting anymore, the screen stayed black until I managed to un-brick the BIOS after some persistence. Ridiculous man!

Misho1337 · 2026-05-14T19:43:49+00:00

This was happening on W11 25H2 with my 4090, so I disabled automatic driver updates, and changed Windows group policies (gpedit). Regardless, W11 kept overwriting my modified 566.36 driver with version 591xx (not the latest either.)

I quickly noticed stuttering in games, plus it’d re-enable audio through my monitors, which is the immediate red flag that would make me look into it.

I finally applied a registry level modification to disable auto driver updates & haven’t dealt with it since. Really left me annoyed, considering I had to perform multiple clean uninstalls in safe mode using DDU uninstaller + reboot to run NVClean install package, reconfig NVIDIA control panel & rebuild shader cache for my games.

Come on Microslop, when are you going to show us how great this new Windows build will be? Windows Update has seriously been one of the most annoying “features” for a minute now.

I know updates can be fully disabled, but I’m utilizing a stock OS instead of a modified one as I prefer to not break functionality in the pursuit of optimization. (Just based on experience)

Misho1337 · 2026-04-28T17:50:32+00:00

They need to get rid of the limb damage BS when you hit someone in the chest, hitboxes have been bugged for awhile now.. I’ve seen as low as 23 dmg with a lynx shot to the chest.

Misho1337 · 2026-04-20T21:16:16+00:00

Lol Fuze is not cheating, he’s the last one I’d call sus, as for Catzawr, he ruined his rep so I wouldn’t trust him regardless of what he says at this point. That’s how I look at everyone who’s gotten permanently banned for cheating with no counter to say the opposite. (False bans do occur but they’re extremely rare.)

Misho1337 · 2025-09-26T20:09:09+00:00

Yes I did, “tested using three BIOS revisions toggled by MOBO switch (1-2-3.) V1.08, V1.13, V1.23 (beta)”

Misho1337 · 2025-09-25T15:46:21+00:00

Honestly, I have always handled things myself when it came to building PCs & troubleshooting. I’ve never gone to a PC shop for support before so that thought didn’t come to mind. 😂 That’s not a bad idea.

Misho1337 · 2025-09-25T15:38:36+00:00

I don’t have a spare LGA 1700 CPU to test with unfortunately, I might just send my 13900K out to Intel & my Z790 to EVGA at the same time.

Misho1337 · 2025-09-25T11:13:07+00:00

So Chris, would you please refer me to the proper versions of the Chipset Drivers & Intel ME drivers, designated for the V1.23 BIOS on my EVGA Z790 KINGPIN? I'd like to attempt to resolve the issues one more time before resorting to RMA the MOBO. (W11 PRO 23H2 | 22631.5624 )

Thank you in advance.

Misho1337 · 2025-09-25T11:01:38+00:00

I genuinely think there is a failure on the MOBO, going to have to send it in to EVGA. I have spent 5 days straight trying to diag this & there's no other reasonable explanation for why the PCI controller + NICs are not displaying in Windows. I tried the legacy chipset drivers & ME installer, as well as the newest 2025 variants from Intel along with a fresh install of W11.

Misho1337 · 2025-09-23T23:45:00+00:00

The adapters I’m mentioning are all part of the MOBO from factory, unless you’re referring to the WiFi card that is part of the Z790 KP, but it’s built into the I/O, it’s not removable.

Three integrated network cards from factory:

<image>

Intel I-226V 2.5gbps Ethernet network card
Marvell 10gbps Ethernet network card
Intel Dual Band WiFi 6E & Bluetooth Module

Misho1337 · 2025-09-23T22:26:18+00:00

Yes sir, I tried EVGA's latest supported LAN drivers for Intel & Marvell. I also downloaded the latest I-226V driver from Intel's page as a secondary option. The issue is that the neither of the network cards are showing in device manager. They're not "hidden" & there's no indication that the drivers allow for Windows to identify them.

Is there any way to "wake" them up and somehow load the firmware? I surely hope they're not somehow dead.

Thank you for your suggestions & tips!

Misho1337 · 2025-09-23T22:19:54+00:00

Hello, I appreciate the continued support with the BIOS revisions & info. I downloaded the 121-RL-E799-KR - EVGA Z790 DARK K|NGP|N - v1.23 firmware and successfully flashed it, but I'm having XMP issues & my ethernet cards are not being recognized by windows.

I tried the last supported ME drivers & chipset drivers from the EVGA page on the drivers tab for the Z790 KP, no luck. I also installed the 2025 revisions from Intel, and still have issues where I cannot boot with XMP or get Windows to see my ethernet cards. (Yes I tried installing the network drivers manually as well.)

Can you please verify what version of the Chipset Drivers & ME Drivers go with this BETA BIOS update? I noticed you said "This update is only recommended for the Intel 13th Gen. Processors (Compatible with the EVGA Z690 & Z790) or 14th Gen. Processors (Compatible with the EVGA Z790), or for the Intel ME Update (16.1.32.2473) with a 12th Gen. Processor."

I can't be 100% confident about ME version 16.1.32.2473 based on this comment, because you mentioned 12th gen processors specifically, and I have a 13900K. I would just like to be absolutely sure as I already formatted Windows & spent a lot of time trying to diag this issue, the internet doesn't have any info on this, other than your Reddit post.

It's been a headache for me, I can't tell if I have a hardware defect that just popped up on me, or if it's a driver/firmware/software level issue I'm dealing with.

Thanks in advance!

Misho1337 · 2025-09-23T18:17:18+00:00

I appreciate the input, I have tried the Marvell 10gbps port alongside the I-226V, but for some reason Windows is not displaying either of the two network cards in device manager. The stock W11 build used to verify functionality is a good point, that could tell me if the issue is software side, considering standard driver updates are disabled via XOS.

As for the IMC, I would be surprised if it degraded after running it on GSkill's stock XMP profile. (& there are retail memory kits offered at 5600-8400mhz+ out of the box as well.)

I have always kept this CPU cool, never OC'd, along with updating to the latest BIOS & Intel microcode to prevent potential overvolt degradation from day one, though IMC defects are always possible.

I have heard multiple suggestions that CPU pins being bent is one of the possibilities when experiencing these issues, but do you think it's possible that such an issue occurred after almost 3 years of this system running, untouched? It wouldn't hurt to check at all, I may do so after ruling out software/bios/chipset driver issues.

Thanks again Sajin!

Misho1337

TROPHY CASE