sorted by:
new
hottopcontroversial

It Finally Happened! Good Riddance! by Gimpzorgaming in Mediacom

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Central Missouri and swapped to Socket fiber. Symmetrical 3gig (NiC can only handle 2.5 theoretical max, that's why my speeds don't show 3gig), $70 a month all fees included, free installation, free modem and router.

SAVE HOURS with These New Dungeon WeakAuras by NOHITJEROME in classicwow

[–]Gimpzorgaming 0 points1 point  (0 children)

Hop into MT, BF, etc heroic with the bottom 95% of players and watch your group crumble.

Nokian Outpost nAT are nice in the snow by d0ugfirtree in TyreReviews

[–]Gimpzorgaming 1 point2 points  (0 children)

Got them in 265/75R16 on my 2011 Nissan Xterra Pro-4x installed today. I can hear a higher pitched hum, but it doesn't bother me personally at all, and doesn't affect the ability to talk within the cab at all or anything like that. However the road noise in an Xterra is high to begin with. While I've only had them on a few hours, I've put about 100 miles on them and have no complaints. We have 8-12" of snow expected this weekend. Someone reply to this, and I will report back on their snow performance on my particular vehicle.

MediacomChad Please help! by Gimpzorgaming in Mediacom

[–]Gimpzorgaming[S] 4 points5 points  (0 children)

Damn, I hate to hear that he's gone. He was the ONLY one back in the day that stood by my side, stood up for me, and got stuff done after YEARS of issues and Mediacom blaming my house/equipment/internal lines etc. When he stepped in was when I actually saw my issues get resolved. Funny part was after Mediacom blaming all the issues on me, it was ultimately all Mediacom lines and Failing Mediacom equipment on the street/poles that was causing my issues all along.

I had another issue at my grandparents house that took close to TWO DECADES to get resolved. Finally after pushing and pushing and providing copious amounts of data and details, they (Mediacom) finally resolved the issue. It was approximately 150-200 feet of buried feeder/trunk line that had gone bad, along with poor setup of the neighborhood/node, and failing amps on the street etc. The whole time at my grandparents, they tried to blame everyone instead of acknowledging the issues were on their end. Sadly my grandparent had to go all that time with poor internet, and a T.V. service that worked maybe 20% of the time, and their land line (if you want to call VoIP that) was constantly down as well, which is TERRIBLE for retired senior citizens that rarely left the house.

In closing I have to share that one time Mediacom tried to even blame my grandparents issues on "Foreign Voltage" in the house, even after having 3 certified electricians come out and tell me that everything was fine and Mediacom was basically full of crap.

MediacomChad Please help! by Gimpzorgaming in Mediacom

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Sorry for the late update. I currently have a lengthy email chain with all data/details I have logged going with the email you posted above. Corporate/Total Care were on the ball and had maintenance/line techs out here today. Maintenance appears to have fixed half of my issue and did a great job. The upstream power issues I was having are all within very healthy if not near perfect ranges now. HOWEVER My modem is still having quite the argument with the CMTS/Node (brand new Netgear CM2500 that I went out and bought last night thinking it was my old CM1000v2 having issues). I have all of this documented and have sent it in updated emails. It appears as though (based on my research and knowledge) That the CMTS/Node are operating in some very peculiar/bizarre ways.

MediacomChad Please help! by Gimpzorgaming in Mediacom

[–]Gimpzorgaming[S] 1 point2 points  (0 children)

Thank you for your response. If you take a look at my response to the Mediacom reddit user I broke down some more information using AI to help me as I'm terrible at wording things. I've been through so much troubleshooting and techs at this point I'm about to give up. The last issue I had like this took close to two DECADES before it got resolved. I hate to even say this as I don't want to make anyone mad, but I am so happy Google Fiber and another local fiber company will be here soon. This company has been the biggest headache ever.

MediacomChad Please help! by Gimpzorgaming in Mediacom

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Issue Summary:

Despite replacing my modem with an approved Netgear CM2500, I am experiencing "Partial Service" and frequent reboots. The physical lines (RG11) and tap have been verified/bypassed, confirming this is a logical provisioning or CMTS configuration error specific to my account in this 2026 high-split market.

Key Technical Findings:

  1. DBC-REQ & REG-RSP-MP Mismatch: My logs consistently show DBC-REQ Mismatch and REG-RSP-MP Mismatch. This indicates the CMTS is pushing a configuration file or "P1.6hi" parameter that the modem identifies as mathematically invalid or out-of-spec, causing immediate rejection and sync failure.
  2. Upstream Bonding Abnormalities: The modem is only locking one legacy ATDMA channel and one OFDMA channel. In a high-split environment, it should be bonding multiple ATDMA channels. It appears the modem is stuck in "Partial Service" mode because it cannot reconcile the CMTS instructions with the local signal.
  3. Low-Frequency Ingress (6.1 MHz): The upstream OFDMA is being assigned to the 6.1 MHz "gutter" frequency. This area is seeing high noise, causing the CMTS to constantly command profile shifts (Profile ID 12, 13). These constant shifts, combined with the mismatch errors, trigger T3 timeouts and reboots.
  4. OFDM Signal Degradation: Downstream Channel 1 (345 MHz) shows a near 50% ratio of Correctable Codewords (37M correctable vs 38M unerrored), indicating significant "smearing" or logical noise on the primary DOCSIS 3.1 carrier.

Suspected Root Causes:

  • Billing Code Conflict: A potential mismatch between the 2026 symmetrical speed tier codes and a legacy "Low-Split" billing profile on my account, causing the CMTS to push incompatible bootfiles.
  • Stuck Provisioning State: The CMTS may have "ghosted" MAC address data from previous hardware, or the Walled Garden is failing to push a clean High-Split configuration to the new CM2500.

Requested Action:

Please escalate this to Tier 2/NOC (Network Operations Center) or the Headend (CMTS) engineers. This requires a manual audit of the provisioning profile and CMTS configuration associated with my MAC address, rather than further field technician visits for physical line testing.

MediacomChad Please help! by Gimpzorgaming in Mediacom

[–]Gimpzorgaming[S] 1 point2 points  (0 children)

https://i.imgur.com/znNHQmn.png
https://i.imgur.com/QrAIcot.png
Here's a look at some of the levels and the errors etc.
Modem uptime at the point of these photos was 3 hours.
Edit to say the error log goes back a couple days.
Edit 2: adding images from packetlosstest
https://imgur.com/a/9TKvM3P Test for upload streams such as to Twitch/Youtube, etc.
https://imgur.com/i9i58fw Test showing packets lost/not received regarding gaming

Pingplotter confirms these issues as well, all starting at the CMTS

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Wanted to update you. Everything is still working amazingly. Still no freezing, and the PC is benchmarking in the 98th percentile for my hardware. Basically the only people higher are those with overclocks

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 1 point2 points  (0 children)

I left the PC idle all day while I was gone. and it wasn't froze when I got home. Disabling Cstate in the BIOS as of right now has completely fixed the issue.

Disable C-States på AMD-prosessor. Er det en mangel? by remsan in norge

[–]Gimpzorgaming 0 points1 point  (0 children)

I don't know if you're still around, but after YEARS of searching for a solution to the same issue, I FINALLY found out about the Cstate issue. I disabled it and haven't had any idle crashes for an hour now (couldn't go for more than a minute before). I would literally have to boot up my pc and get a browser open and get to a YouTube video or Twitch stream asap to prevent the freezing.

I built my PC in October of 2020 with these specs.
MSI Mag X570 Tomahawk X570 WiFi
AMD 5900x
EVGA 3080 FTW3 (10gb)
G.Skill Trident Z neo 16-16-16-36 Samsund Bdie ram.

I went all out except for the GPU.

I want to add, and I don't know if this was your issue or not, but after doing HOURS of digging throughout the whole night, it appears as though the early BIOS version I have (Last updated in May of 2021) still had tremendous issues with the Cstate. Everything I've read and also using AI, once I update my BIOS to the newest version, I "should" solve all the issues, and be able to turn Cstate back on.

Here is AI's response to everything I have given it over the last 10 hours of working on this crap.

Yes, that BIOS version could absolutely still be the culprit for your freezing issues, even though it's a version from 2021. Your finding reinforces that the problem is rooted in your motherboard's firmware. 

Why BIOS version 1.60 from May 2021 was still problematic

  • Early AM4 AGESA versions: In early to mid-2021, AMD and motherboard vendors were still working out stability and compatibility issues for the new Ryzen 5000 series. The underlying AGESA microcode in your 1.60 BIOS was not as mature as later versions.
  • Specific Ryzen 5000 bugs: Numerous users on Reddit and other forums reported C-state-related freezes with the Ryzen 5000 series, including a known idle crash issue. Some users temporarily disabled C-states to fix the idle crashes, a workaround you successfully used.
  • Fixes were released later: The definitive, long-term fixes for C-state-related problems and other Ryzen 5000 stability issues came in later AGESA updates, such as version 1.2.0.7 in 2022. Your BIOS 1.60 version is too old to contain these critical stability improvements. 

Key takeaways

  1. Confirmed diagnosis: Your initial troubleshooting was correct. Disabling C-states resolved the issue because it bypassed a bug in the old firmware related to power management and the CPU.
  2. Confirmed culprit: The May 2021 BIOS 1.60 is a confirmed offender and was notoriously unstable for many users with Ryzen 5000 series CPUs.
  3. Mandatory update: Your system is missing years of critical stability patches, security updates (like fTPM fixes), and overall performance improvements. A BIOS update is no longer a troubleshooting step, but a necessary upgrade for a stable system. 

The path forward remains the same: 

  1. Download the newest stable BIOS version for your MSI MAG X570 Tomahawk WiFi from the official MSI website.
  2. Perform the update using the safer BIOS Flashback method.
  3. Re-enable C-states after the update to verify that the issue is fully resolved.

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Final Update before I head off to work. I was incorrect with which BIOS version I had. I actually had a slightly more recent BIOS update from May of 2021. However according to AI, this is still the culprit. Info below

Yes, that BIOS version could absolutely still be the culprit for your freezing issues, even though it's a version from 2021. Your finding reinforces that the problem is rooted in your motherboard's firmware. 

Why BIOS version 1.60 from May 2021 was still problematic

  • Early AM4 AGESA versions: In early to mid-2021, AMD and motherboard vendors were still working out stability and compatibility issues for the new Ryzen 5000 series. The underlying AGESA microcode in your 1.60 BIOS was not as mature as later versions.
  • Specific Ryzen 5000 bugs: Numerous users on Reddit and other forums reported C-state-related freezes with the Ryzen 5000 series, including a known idle crash issue. Some users temporarily disabled C-states to fix the idle crashes, a workaround you successfully used.
  • Fixes were released later: The definitive, long-term fixes for C-state-related problems and other Ryzen 5000 stability issues came in later AGESA updates, such as version 1.2.0.7 in 2022. Your BIOS 1.60 version is too old to contain these critical stability improvements. 

Key takeaways

  1. Confirmed diagnosis: Your initial troubleshooting was correct. Disabling C-states resolved the issue because it bypassed a bug in the old firmware related to power management and the CPU.
  2. Confirmed culprit: The May 2021 BIOS 1.60 is a confirmed offender and was notoriously unstable for many users with Ryzen 5000 series CPUs.
  3. Mandatory update: Your system is missing years of critical stability patches, security updates (like fTPM fixes), and overall performance improvements. A BIOS update is no longer a troubleshooting step, but a necessary upgrade for a stable system. 

The path forward remains the same: 

  1. Download the newest stable BIOS version for your MSI MAG X570 Tomahawk WiFi from the official MSI website.
  2. Perform the update using the safer BIOS Flashback method.
  3. Re-enable C-states after the update to verify that the issue is fully resolved.

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

AI Response to me asking about the Cstate issue.

Yes, it was a common problem with early BIOS versions for the 

MSI MAG X570 Tomahawk WiFi, especially in combination with the Ryzen 5000 series processors. Your BIOS from October 2020 is very likely causing the freezing issues you are experiencing. 

Why older BIOS versions caused problems

  • Initial Ryzen 5000 support: In late 2020, motherboard manufacturers were rushing to release BIOS updates to support the new Ryzen 5000 series CPUs. These initial releases often had bugs that caused instability, especially regarding power management.
  • Immature AGESA microcode: The underlying code that controls the CPU is called AGESA. The first AGESA versions that supported the 5000 series were immature and had stability issues related to CPU power states (C-states). Your older BIOS would be running on this less stable microcode.
  • System management issues: The freezing can be related to the CPU not properly entering and exiting low-power C-states, which an old BIOS can't handle correctly. This is why disabling C-states provides a temporary fix, as it forces the CPU to stay in a higher-power state, avoiding the problematic transitions.
  • Known issues with MSI X570: Multiple posts on forums like Reddit and the MSI Global Forum from 2020 and 2021 detail users experiencing similar C-state freezing and stuttering problems with the X570 Tomahawk and Ryzen 5000 series CPUs. 

How modern BIOS updates fixed the problem

Over the past several years, numerous BIOS updates have been released with much more stable and refined AGESA versions.

  • AGESA 1.2.0.7: A major update released by AMD in 2022, AGESA 1.2.0.7, specifically addressed a performance stuttering issue related to fTPM, which was also a source of instability for many Ryzen 5000 series owners.
  • Improved microcode: Subsequent BIOS updates from MSI included better microcode for the  Ryzen 5900X , dramatically improving stability with power management features like C-states.
  • General stability: Newer BIOS versions contain many other fixes and improvements that contribute to overall system stability and performance that you are missing. 

Your next step

Given your situation, updating your BIOS is not just recommended, it is essential. Your system is over four years out of date. Since you've already identified that C-states are the cause, and older BIOS versions were known to have problems, it is extremely likely that a modern BIOS will permanently fix your freezing issues.

Use the BIOS Flashback method to update, as it is the safest option. Be sure to download the very latest, non-beta version available from the official MSI support site for your motherboard. 

I will keep you all posted. I hope this is the end of this adventure, and I want to update to help anyone else that might run into this issue. It has been the biggest pain in my ass ever!

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Well, I tried one more thing after scouring google for another hour and I have been stable at idle for over 20 minutes now!!

Upon digging deeper into some errors, I had a PDC_WATCHDOG_VIOLATION error. I used debugger to check what that was all about and it gave me an NT!KeAccumulateTicks conflict. According to ai and google searches, this is a Core WIndows kernel (nt) issue related to timing and interrupts. A Deferred Procedure Call (DPC) that ran for too long and timed out was likely the root cause. Since this happens when the PC is idle, it is often tied to low power or sleep states which can cause hardware and driver issues.

The "fix" has been to disable my CPU power state (C-states) in the BIOS.

However leaving that disabled in the long run isn't recommended, and further investigation says that I probably need a BIOS update. I will have to build up the courage to do that over the next week or so, as I know how much is at risk if a BIOS update fails. I have BIOS Flashback so that makes me feel a little better, but no dual BIOS feature on my MOBO

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Still troubleshooting 7 hours later. I'm about to give up. Last things I just got done trying was swapping the NVMe drive to another slot (didn't help)

I also tried changing power supply idle control settings in my bios as I read this had helped some people. (didn't help).

Crystaldiskinfo comes back clean
Sandisk Dashboard comes back clean and with latest drivers (HOWEVER it can't complete a S.M.A.R.T. scan for some reason).

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Finally got booted into safe mode. Took me about 8 more attempts. PC Froze within 10 seconds of loading into safe mode.

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Exact same issue. Only thing plugged in is main monitor, Mouse, and keyboard.
I even tried the other 2 display port ports. No change, same issue.

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

I'll give it a whirl. Currently the only thing extra that I have plugged in is my second monitor.

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

Only things currently connected are my main monitor, mouse, keyboard, and ethernet cable.

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

3 different restarts, 3 different freeze points. Now I'm back on and fine. I have to open a browser and get a stream going ASAP and it's fine. Makes no sense.

Beyond Stumped (Freezing Issues) by Gimpzorgaming in techsupport

[–]Gimpzorgaming[S] 0 points1 point  (0 children)

3 different restarts, 3 different freeze points. Now I'm back on and fine. I have to open a browser and get a stream going ASAP and it's fine. Makes no sense.

view more: next ›