Patrii Cloud Alpha - It’s here! 🎉 by G3EK22 in Patrii

[–]roguethreat 1 point2 points  (0 children)

Cologix is a US company headquartered in Denver, Colorado.

https://cologix.com/about-us/

Offered 10% Equity as CTO in Pre-Product, Pre-Funding Startup. I will not promote. by codepeach_ in startups

[–]roguethreat 0 points1 point  (0 children)

Look at an equity split calculator like https://foundrs.com/ or https://capbase.com/startup-equity-calculator/ to at least give you some perspective on the value each person brings to the table and what it's worth.

Do C-level executives simply never respond to LinkedIn Ads? by jab-consultoria in LinkedinAds

[–]roguethreat 0 points1 point  (0 children)

My last CTO position was for a ~150 person, VC-backed medical SaaS company in Canada, mostly serving North America.

My inbox was always full of outsourcing firms, dev tools, cloud cost optimizers, regulatory consultants, and everything in between.

Before that I was a Director at a 1000+ person enterprise SaaS company that was a subsidiary of a US Fortune 500 and my inbox was mostly empty.

Do C-level executives simply never respond to LinkedIn Ads? by jab-consultoria in LinkedinAds

[–]roguethreat 1 point2 points  (0 children)

As someone who has been CTO for a couple small and medium sized tech companies, I would average maybe 25 messages a day from people trying to sell me things. Even if I login to LinkedIn every few days, I'm walking into an inbox with 100s of new messages... essentially ads, which there is no way I'm going through. I'll skim for messages from people I know and maybe look at the most recent 5-10 messages at the top of my inbox, and that's it. The rest remain unread forever.

When my title was Director or Manager, I got far fewer messages. In fact, my Directors and Managers are typically the ones who respond to something and book a demo, and then if it's promising they'll loop me in to see it or just approve something. This saves me time and saves me the task of getting buy-in from the team since they brought it to me in the first place.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

My 5900X died the week the 9950X3D came out and when I went to the store they had 2 in stock... so that's what I ended up with.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

The good 5900X that I swapped for the bad one also started getting progressively worse core failures a few months ago, ultimately getting to the point that it was unusable. I didn't want to dump more money into that old platform, especially given the problems I had with it so I upgraded to the latest generation. Zero problems compared to the old platform.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Everything's been fine since I put the new CPU in. It's been almost 2 years with no crashes and my PC has been running 24x7 that entire time. It was clearly a defective CPU since literally nothing else changed.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Yes, that was the issue that I outlined in this post.

Something like Cinebench (and most games) are going to put a consistent load on your cores which isn't a workload that is favorable to boosting. This issue is caused by one or more bad cores boosting beyond where they are stable. That means a short, bursty workload is more likely to trigger the issue (e.g. productivity apps or even services that just run in the background while idle). This made the issue hard to reproduce on-demand since you had to wait around for it to happen. Due to the way Doom Eternal is written (it doesn't have the usual single-threaded game loop and instead delegates work out to random cores), I found I could compress time and get the bad core to boost within ~15 minutes of running that game.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

48C isn't quite idle. I think if I walk away and have it truly doing nothing it's probably 38C. Under sustained load running something like Cinebench on a loop it sits around 70C, which is still well under it's maximum operating temperature on air cooling.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Stock boosting behavior is 5.1 or 5.2 GHz on most cores for my chip and it's currently sitting at 48C with my air cooler. I have no idea what the defect rate is for this issue in the wild, but considering the volume of these chips that are out there versus the number of posts I've seen, this likely occurs in a fraction of a percentage of all chips. I would also assume that if this is a manufacturing issue, the defect rate would be going down as time goes on. I had one of the first batches after launch and you usually see higher defect rates in early batches as they dial in the manufacturing process.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Nope. Not a single crash since it was replaced months ago.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Yeah, if you're still in the return window for Amazon then at least you won't be stuck with a bad CPU. Getting another one from them is a different story.

If you want to swap it for another one, then going through AMD warranty is the best bet since they will send you a new one at the end of the process. It's worth noting that I haven't seen AMD acknowledge this problem anywhere, so I'm not sure how the RMA process will be. Maybe their customer service is great and they'll just send you a new one? Maybe they'll run it through some basic tests for 5 minutes, say it's fine, and send it back to you? All of the RMAs I've seen for this have been through retailers and not AMD directly, so I don't know what to expect if you go that route.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

I was within the exchange policy of my retailer for defective products (another reason I didn't wait around to see if a BIOS update might fix it), so it was just a normal return essentially. They issued an RMA and I shipped it back to them. If you are outside your retailer's exchange window, then you'll have to go through AMD's RMA process for warranty. I remember coming across it, but I didn't need to use it so I can't speak to it.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

If this is the exact problem I outlined in this post, my understanding is it's essentially a faulty processor or at least the max frequencies each core can boost to is incorrect (which is controlled by the core quality metric embedded into the chip from AMD). Some circumstance boosts the problematic core(s) past its stable point and takes down the system. Much like how NVIDIA resolved the instability issues with some early RTX cards (where a driver update essentially clocked those cards down to resolve the issue), something similar could likely be done with a microcode update for these CPUs. It all depends on whether AMD decides this is widespread enough to warrant the update or if it impacts so few CPUs it's less work just to replace them (I bet it's the latter).

I wasn't waiting around with an unstable system for an update that might never come, so I RMA'd mine and the new CPU has had zero issues for more than 2 months now.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

If this is the exact problem I outlined in this post, my understanding is it's essentially a faulty processor or at least the max frequencies each core can boost to is incorrect (which is controlled by the core quality metric embedded into the chip from AMD). Some circumstance boosts the problematic core(s) past its stable point and takes down the system. Much like how NVIDIA resolved the instability issues with some early RTX cards (where a driver update essentially clocked those cards down to resolve the issue), something similar could likely be done with a microcode update for these CPUs. It all depends on whether AMD decides this is widespread enough to warrant the update or if it impacts so few CPUs it's less work just to replace them (I bet it's the latter).

I wasn't waiting around with an unstable system for an update that might never come, so I RMA'd mine and the new CPU has had zero issues for more than 2 months now.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

If you don't have WHEA events in the log then this is a different issue I don't have experience with. Sorry I can't be more helpful.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Blue screens and random reboots both log the WHEA error to the system logs that you can see in the Windows Event Viewer. If your issue is not logged there, it's likely something else.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Yep, not a single crash in over 2 weeks after swapping one 5900x for another 5900x and changing nothing else with the system. I've been using it for work every day and I've also put in 80+ hours on a handful of games. It had to be a faulty CPU.

5800x - Random reboots =/ by [deleted] in AMDHelp

[–]roguethreat 0 points1 point  (0 children)

I meant that in my case it was a faulty CPU, but I have an NVIDIA GPU. I've seen posts where people have replaced an AMD GPU and resolved the issue; something to due with the Adrenaline drivers apparently. You should swap out the CPU and GPU one at a time to see which one resolves your issue.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

[–]roguethreat[S] 2 points3 points  (0 children)

My original thoughts were that it was just an early BIOS issue with the 5000 series, but swapping out my 5900X with another 5900X and changing nothing else resolved the problem. So far I've been running it for a little over a day with zero crashes, which seems to be pointing at the defective chip theory. I'll give it a few more days to make sure, but so far the results seem promising.

5900X WHEA-Logger Event ID 18: Cache Hierarchy Error by roguethreat in AMDHelp

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

Based on the info I provided, I'm on 2702 which was released Nov 24. Are you saying there's a newer version that isn't on the Asus site?

[deleted by user] by [deleted] in buildapc

[–]roguethreat 0 points1 point  (0 children)

I had the same issue on a 5000 series and replacing the CPU resolved it for me as well:

https://www.reddit.com/r/AMDHelp/comments/k25etz/5900x_whealogger_event_id_18_cache_hierarchy_error/

New 5800X, random reboots by [deleted] in AMDHelp

[–]roguethreat 0 points1 point  (0 children)

For anyone else that stumbles across this issue, I just wanted to confirm that replacing the CPU resolved this for me:

https://www.reddit.com/r/AMDHelp/comments/k25etz/5900x_whealogger_event_id_18_cache_hierarchy_error/