GrandNebSmada

If card was new and problems started when you got it why didn't RMA the card?

Even now it's still under warranty.

Can you test that removing GPU the problems?

Your first problem is that the microphone is not physically isolated from your desk. The vibrations in your desk are being transferred physically through the body of the microphone and getting picked up by the capsule. A good way to solve this would be to get a boom arm and shock mount for the microphone.
 
The second thing you need to do is to make sure the back of the microphone is aimed directly towards the things you wish to not hear.
 
If you wish to upgrade your microphone, I suggest buying an Audio Technica AT2020 or Lewitt LCT240. Make sure that whichever you buy you get the pack that also has the shock mount. For getting the audio into your computer I recommend the Behringer UMC202HD. Be sure to look up the audio drivers for that. It's called an ASIO driver. 

Since you have both, how about you test them both and decide that way?

So, LMG content is rushed, inaccurate and focus more on being "funny" rather than accurate?
 
I guess there's no news here lol

I hate to break it to you, but all tech journalism has plenty of factual errors, especially those that go for the video format. To avoid falling into the what-aboutism category, let me just say that as someone who works in related industries, GN has plenty of bad takes as well, the difference being that they're not nearly as good about going "my bad". LTT doesn't get needlessly defensive over the fact that they make errors, and they often include the bad takes in videos with corrections, which I appreciate because it does tend to show the initial genuine reaction - something which is useful for myself as someone that's tangentially related with product design on various occasions. This is far more useful than a boring line that might get missed from my point of view.
 
I would imagine it's actually more than 500 USD, having an actual person with some training and a college/university degree work in a building tends to cost around $90-100 an hour. So you need someone doing the work, someone on the camera, someone doing sound, and preferably some sort of director present, so the shoot alone would probably end up costing around $2000, if you then need to manufacture a new mounting bracket, etc. you could easily lose an entire day and now you're looking at somewhere around $4000 to $5000. It also doesn't account for the fact that you might have a deal with sponsors that require the video to come out on a certain date, availability of working and recording spaces, etc.; which is to say that I understand not wanting to do another take. But it's indicative of general communication problems between billet labs and LTT, which compounds further with the block being sold at auction. The real question is how they respond after the screw up becomes known. I experienced this type of communication breakdown at both small start-ups and multi-billion dollar corporations, so I can totally see it happening at LTT as well.
 
Accuracy of information is actually my main grievance with Gamers Nexus. Every time they dove into electronics manufacturing I just cringed and wanted to start bashing my head on my desk to make it stop.
 
Asking the manufacturer for input when you have unexpected results is quite desirable when dealing with complex and new products, it's quite possible a single setting could make all the difference in the world. I just wish this would be done consistently across all products if unexpected results pop up.
 
I wouldn't be surprised if the recent increase in error rate is caused by the large volume intake of new employees.

Calling people delusional is just going to reinforce their belief that this is a hit piece and not something borne out of genuine concern for the community.
 
That said, there's definitely a lot of takes in here where people are acting personally attacked and that's a little out of touch.
 
The video is good natured. The message isn't an attack, it's a concern. And after trust me bro, Steve said point blank he was no longer treating ltt as an individual but the corporation that it is.
 
Corporations don't care about your feelings. Corporations aren't people. Corporations don't get handled with kid gloves.
 
They get publicly discussed, and allowed to make their own decision on how to respond to that discussion.

First of all, the whole Billet Labs stuff is completely absurd if true. I don't think they would intentionally sell something they couldn't, probably some massive fuck up in communications happened between the team responsible for sending it back and the people choosing the items to be auctioned, but it's still a huge issue and 100% LTT's responsibility to fix it and make sure something like this never ever happens again. 
 
About the rushed content, it's something that a lot of times crosses the border of "fun jank" to being just frustrating. Every single project they do seems to be rushed, unfinished, untested and plagued with issues and oversights. And that could be their content "brand", seems like many people enjoy the jank. But if they now want to present themselves as serious testers, someone the community can look up for reliable data with Labs, that mindset needs to change, FAST. How the hell can I trust someone who has to correct themselves almost every video? And makes errors that a basic review of the content could catch? 
 
You need to pump out 7 videos a week? Sure buddy, but maybe allow more time sensitive projects to be properly planned, executed and reviewed and throw some "here's 10 fun crap we found on aliexpress" videos to make up for it.

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.

Steve vs Linus cage match when?????

Relevant videos
 
 
 

Short answer: no.
 
Long answer: there are technically two different versions of the 1151 socket, one that supports 6th and 7th gen CPUs, another that support 8th and 9th gen chips. I blame Intel for not giving the 2nd one a suffix like 1151-v2. It just creates unnecessary confusion, as evidenced by here.
 
The sockets are actually mechanically compatible, so you can get that board and install the CPU in it. However, there is no BIOS support for it. Some people have modded in BIOS support for the older CPUs, same with the other way around, it's just that you're likely to run into weird issues since your modifying the BIOS. 

Heck yeah it could. If you threw it hard at someone's head, it'd probably knock them out cold and cause a severe haemorrhage. 

It really amazes me how people still choose to live in that state.

It really amazes me how people still choose to live in that state.

It really amazes me how people still choose to live in that state.

It really amazes me how people still choose to live in that state.

It really amazes me how people still choose to live in that state.

It really amazes me how people still choose to live in that state.

It really amazes me how people still choose to live in that state.

Linux doesn't have a concept of drives (C:, D:) like Windows does. Instead you have a directory tree that starts at / and all directories beneath it contain your files. If you add an additional drive, that drive needs to be mounted somewhere in that directory tree. So e.g.the  /home/5Beans6 and /home/Eigenvektor directories could actually be on different drives. Most applications can's access the raw drive below /dev, since that require root permissions and is not a real directory.
 
In addition to the answer @EDK Tech gave you, here's a link explaining how to permanently mount the additional drive by configuring it in /etc/fstab:
https://confluence.jaytaala.com/display/TKB/Mount+drive+in+linux+and+set+auto-mount+at+boot
 
Ok, then you can probably ignore what I said above 😅 You probably need to set the permissions on the directory so that it is readable by your user without e.g. sudo. What do the current permissions look like?

It doesn't unfortunately. My hard drive is mounted perfectly fine and I can access all the files on it through my file explorer. The problem is with other applications being able to access the files. They can see the drive, but there is a permission issue.

I would imagine it's because the amount of views they would get relative to the amount of effort they'd have to invest makes it a bad business decision to do so. 

I am running a minecraft server on a separate computer in my home and have it setup with No-IP for the dynamic DNS service. I have always been able to connect to the server from my main computer using the domain name I have assigned to it from my local network, but recently I have not been able to and can only connect using the local IP. The issue is not isolated to these two computers either. I can setup a server on a completely separate computer and try to connect the same way from another unique computer and it still doesn't work, which leads me to believe it's an issue with my router settings. I have found people saying to edit my host files but this is not an acceptable method for me and should not be necessary since I have used this setup before in the past and it worked with no issues.
 
Things I have already tried:
Verified outside users can connect using the domain name with no issues. Verifying the port forwarding is correct Verified the public IP associated with the domain names is up to date Made sure that my NAT type is appropriate Set the NodeType settings on the computers' network adapters to "hybrid"  
I'm really stumped here, any help would be greatly appreciated!!!

Thanks, i figured it out. Idk why I didnt realize i was inside the home folder within the root directory. Just a brain fart moment

The "NvContainerLocalSystem" (NVIDIA LocalSystem Container) service was the only process on my system causing this.
 
Here is a more general workaround that should work for everyone:
- In the Mionix Software click on "Apply" (it will freeze)
- Open task manager
- Select tab "Details"
- Right-click on "NAOS3200_Config.EXE" and click "Analyze wait chain"
- A dialog opens up showing all processes preventing the Mionix Software from saving
- Close all those processes cleanly or force end/kill them
- The Mionix Software should no longer be frozen