Discipulus1

Go into Task Manager, and check each drive. It should say the manufacturer and model on top of the activity graph:

so.. steve is making a stink over something an LMG employee said, without the context of what they were talking about, and the environment they were talking in...
 
i feel like there's a strong vibe of "everyone is handling this the wrong way" here...
 
this is the point where i watch the entire GN video to make sure the above statement is correct...
 
there's a lot of truth here.. but the general tone of the video seems.. unnecessarily nitpicky and vindictive?
 
steve ripping on the framework investment being conflict of interest for doing laptop reviews.. is also just unnecessary. linus is aware of the potential conflict of interest, it has been brought up to the community at the time of him considering it, and is mentioned in each laptop review he hosts.
also this:
is a very important distinction. you cant talk about the budgets of a corporation, and then talk about someone's personal investment as if they are one and the same.
 
i'm actually at the point where i'm getting annoyed at steve putting far too many out of context quotes into his video. it seems almost purposefully disingenuous on his part to cut things to make them seem worse.. when the full story is already less than favourable.
 
yes.. LMG makes a lot of mistakes, too many mistakes.. but saying that a "100 million dollar company" should not do this, is just factually inaccurate. that cash does not exist at LMG, and steve knows this. why make this argument if not to purposefully make LMG seem evil, rather than just careless.
 
it *could* have been a wakeup call for LMG, but instead the entire video just feels like steve going as hard as he can without openly hard cutting his own ties with LMG in case he needs linus to call someone at youtube for him.
 
actually.. this has been an issue i've had with steve's videos in general. i like steve, i love what he stands for, but every time i bump into a video of his he seems to be unnecessarily vindictive about everything. it's just exhausting at this point. steve's usually right, but he loses so much credibility to me by inflating facts almost into the field of alternative truths... life is crazy enough as it, let's not inflate things any more and try to fix things for once.
 
PS: a TL:DR here in case someone is gonna pop in to call me an LMG shill.. i 87% agree with steve on the topic, i just also 99% disagree with the way he voices his opinion on said topic.

Billet sent us a quote. I don't know or care how they arrived at the value. If they're good, I'm good.

As for what steps we're taking, you're talking about an outlier issue that has happened once in 10+ years of operation. There won't be a new SOP to ensure we don't accidentally auction stuff. We just need to tighten up some documentation.

There won't be a big WAN Show segment about this or anything. Most of what I have to say, I've already said, and I've done so privately.

To Steve, I expressed my disappointment that he didn't go through proper journalistic practices in creating this piece. He has my email and number (along with numerous other members of our team) and could have asked me for context that may have proven to be valuable (like the fact that we didn't 'sell' the monoblock, but rather auctioned it for charity due to a miscommunication... AND the fact that while we haven't sent payment yet, we have already agreed to compensate Billet Labs for the cost of their prototype). There are other issues, but I've told him that I won't be drawn into a public sniping match over this and that I'll be continuing to move forward in good faith as part of 'Team Media'. When/if he's ready to do so again I'll be ready.

To my team (and my CEO's team, but realistically I was at the helm for all of these errors, so I need to own it), I stressed the importance of diligence in our work because there are so many eyes on us. We are going through some growing pains - we've been very public about them in the interest of transparency - and it's clear we have some work to do on internal processes and communication. We have already been doing a lot of work internally to clean up our processes, but these things take time. Rome wasn't built in a day, but that's no excuse for sloppiness.

Now, for my community, all I can say is the same things I always say. We know that we're not perfect. We wear our imperfection on our sleeves in the interest of ensuring that we stay accountable to you. But it's sad and unfortunate when this transparency gets warped into a bad thing. The Labs team is hard at work hard creating processes and tools to generate data that will benefit all consumers - a work in progress that is very much not done and that we've communicated needs to be treated as such. Do we have notes under some videos? Yes. Is it because we are striving for transparency/improvement? Yeah... What we're doing hasn't been in many years, if ever.. and we would make a much larger correction if the circumstances merited it. Listing the wrong amount of cache on a table for a CPU review is sloppy, but given that our conclusions are drawn based on our testing, not the spec sheet, it doesn't materially change the recommendation. That doesn't mean these things don't matter. We've set KPIs for our writing/labs team around accuracy, and we are continually installing new checks and balances to ensure that things continue to get better. If you haven't seen the improvement, frankly I wonder if you're really looking for it... The thoroughness that we managed on our last handful of GPU videos is getting really incredible given the limited time we have for these embargoes. I'm REALLY excited about what the future will hold.
 
With all of that said, I still disagree that the Billet Labs video (not the situation with the return, which I've already addressed above) is an 'accuracy' issue. It's more like I just read the room wrong. We COULD have re-tested it with perfect accuracy, but to do so PROPERLY - accounting for which cases it could be installed in (none) and which radiators it would be plumbed with (again... mystery) would have been impossible... and also didn't affect the conclusion of the video... OR SO I THOUGHT...
 
I wanted to evaluate it as a product, and as a product, IF it could manage to compete with the temperatures of the highest end blocks on the planet, it still wouldn't make sense to buy... so from my point of view, re-testing it and finding out that yes, it did in fact run cooler made no difference to the conclusion, so it didn't really make a difference.
 
Adam and I were talking about this today. He advocated for re-testing it regardless of how non-viable it was as a product at the time and I think he expressed really well today why it mattered. It was like making a video about a supercar. It doesn't mater if no one watching will buy it. They just wanna see it rip.  I missed that, but it wasn't because I didn't care about the consumer.. it was because I was so focused on how this product impacted a potential buyer. Either way, clearly my bad, but my intention was never to harm Billet Labs. I specifically called out their incredible machining skills because I wanted to see them create something with a viable market for it and was hoping others would appreciate the fineness of the craftsmanship even if the product was impractical. I still hope they move forward building something else because they obviously have talent and I've watched countless niche water cooling vendors come and go. It's an astonishingly unforgiving market.
 
Either way, I'm sorry I got the community's priorities mixed-up on this one, and that we didn't show the Billet in the best light. Our intention wasn't to hurt anyone. We wanted no one to buy it (because it's an egregious waste of money no matter what temps it runs at) and we wanted Billet to make something marketable (so they can, y'know, eat).
 
With all of this in mind, it saddens me how quickly the pitchforks were raised over this. It also comes across a touch hypocritical when some basic due diligence could have helped clarify much of it. I have a LONG history of meeting issues head on and I've never been afraid to answer questions, which lands me in hot water regularly, but helps keep me in tune with my peers and with the community. The only reason I can think of not to ask me is because my honest response might be inconvenient. 
 
We can test that... with this post. Will the "It was a mistake (a bad one, but a mistake) and they're taking care of it" reality manage to have the same reach? Let's see if anyone actually wants to know what happened. I hope so, but it's been disheartening seeing how many people were willing to jump on us here. Believe it or not, I'm a real person and so is the rest of my team. We are trying our best, and if what we were doing was easy, everyone would do it. Today sucks.
 
Thanks for reading this.

Old xmp profile might be causing instability, reset the bios either with the pins and/or removing the cmos battery and let it sit for a minute without the power cable.
 
Then put in the cable and cmos battery and power it up and go into the bios.
 
Make sure the xmp profile is off initially, if it starts acting up enable the xmp profile.

I asked F@H for a new passkey (I think they just sent the same?).  I re-entered it into the client.  It reset the the client, and appears to have fixed the problem.
 
Thank you.

My educated guess would be that you either did not actually put passkey (or you mistyped it) or you just dumped a lot of WUs and now QRB has been stripped away from you until you reach 80% of successfully returned assigned WUs.
Try deleting F@H (data as well), restarting your pc, installing F@H again and then use Afterburner to downclock it a bit and then try again.
Or you can skip first and third step, just restart pc, and downclock. Also, my AMD cards actually liked to dump some WUs like that even if they were 100% stable on same WUs before. Happens from time to time...
 
Also, are you running any expert flags?

I added a Passkey at first.  I even looked into re-entering it.
 

Yeah, I could have replied to him with a dose of critical negativity, but with this being a good cause, why not just keep everything positive.  Cheers.