"Mad at the Internet" - a/k/a My Psychotherapy Sessions

[Slav Power]

The Windows-Linux flip-flopping will continue until the real culprit finally gives up for good.

@Null Check. Your. System. There is no good reason for both Linux and Windows failing in unexplainable ways at random. Use OCCT to stress your shit. CPU, RAM, GPU, push it to it's breaking point, OCCT was designed for testing hardware stability. Better yet, use Memtest86+ to check your RAM sticks, because it's most likely that they're the ones dying and causing instabilities.

Time spent on diagnosing potential hardware issues will be better than having to constantly switch from Arch to Windows in hopes one of them will be stable.

Windows 10 never BSOD'd for me for no good reason. The only one time it did was due to faulty drivers, where after their removal it never had any instabilities. It never had a crash because of it being Windows. And if both Arch and Windows shits itself this badly at random, it has to be the issue with the hardware.

 

[Good Night Knight]

Any MATI experts out there able to recognize which episode this clip came from?

Victory Lap - Mad at the Internet (August 14th, 2020)

Spoiler: 7 steps to find it

- Play the video
- Intro music lyrics heard: "Don't call your mother, don't call your priest, don't call your doctor, call the police"
- Googling... Ween - It's Gonna Be a Long Night
- No date on screen, so it's an older stream.
- JCM Archives on youtube has old streams and the description usually says what songs are played.
- Search "It's Gonna Be a Long Night" on their page.
- Video found.

 

[R00T]

View attachment 5721181
The Windows-Linux flip-flopping will continue until the real culprit finally gives up for good.

@Null Check. Your. System. There is no good reason for both Linux and Windows failing in unexplainable ways at random. Use OCCT to stress your shit. CPU, RAM, GPU, push it to it's breaking point, OCCT was designed for testing hardware stability. Better yet, use Memtest86+ to check your RAM sticks, because it's most likely that they're the ones dying and causing instabilities.

Time spent on diagnosing potential hardware issues will be better than having to constantly switch from Arch to Windows in hopes one of them will be stable.

Windows 10 never BSOD'd for me for no good reason. The only one time it did was due to faulty drivers, where after their removal it never had any instabilities. It never had a crash because of it being Windows. And if both Arch and Windows shits itself this badly at random, it has to be the issue with the hardware.

But if he fixes the problem I dont get to laugh at Cobes’s face burned into the windows blue screen like his computer just got hit by a missile.

 

[Null]

The Windows-Linux flip-flopping will continue until the real culprit finally gives up for good.

listen you aggravating piece of shit, the issue with windows as a loose ram stick. I fixed that. I don't know what I'm doing that pops it out every so often, but Windows runs without issue. OBS on Windows runs without issue. The driver issues on Linux have been a persistent issue and they got worse recently after updating my system.

 

[Crocodylus Acutus]

> muh mentals

It was a reference to the MATI stream, smh not a real fan

 

[Anti Snigger]

listen you aggravating piece of shit, the issue with windows as a loose ram stick. I fixed that. I don't know what I'm doing that pops it out every so often, but Windows runs without issue. OBS on Windows runs without issue. The driver issues on Linux have been a persistent issue and they got worse recently after updating my system.

Is there any consistent pattern of what drivers are causing problems?

 

[Null]

the video drivers. OBS's rendering freezes, browser tabs on brave crash during Kick streams with SIGKILL that do not happen on FireFox. The latter apparently happens to a lot of people though.

 

[Anti Snigger]

Is your graphics card nvidia by chance?

 

[Slav Power]

Is your graphics card nvidia by chance?

Yeah he has a 4090 lmfao

 

[Null]

yes

 

[WelperHelper99]

listen you aggravating piece of shit, the issue with windows as a loose ram stick. I fixed that. I don't know what I'm doing that pops it out every so often, but Windows runs without issue. OBS on Windows runs without issue. The driver issues on Linux have been a persistent issue and they got worse recently after updating my system.

You vill like Windows and you VILL be happy

 

[Anti Snigger]

I'd poke around with nividia-smi and try manually downgrading some of the drivers. One of my computers has an nvidia card and it's been less than cooperative at times. Even when I dual boot into windows on it, I get similar issues with WSL and specifically Cuda. Nvidia has historically been the nigger of the hardware vendors in the linux space, and something might have happened between their recent driver updates and kernel updates.

 

[Null]

When I have space I might just have a completely separate computer for streaming using Windows and NVIDIA and then set up AMD and Linux for dev.

 

[Jotch]

Most linux distros are extremely stable out of the box. If it crashes without you changing any settings it is always a hardware compatibility or functionality problem.
Ie my PC ran Ubuntu 20.04, but I had a pretty new graphics card. My PC crashed and I had video driver issues, fortunately AMD put out their own drivers.

It kept crashing however, and after so many reinstalls and screwing around I ran memtest, which should have been my first thing. My ram failed the bit fade test... sometimes. So programs loaded into ram would have tiny parts clear to zero over time. Definitely the type of thing that slowly crashes system.
New ram, fixed!
(please Noolean run memtest all the way through I know it takes a while but you really should do it)

@Null, I am fairly sure you missed this, please give it a try. If you have tried it I have no way of knowing since you have never mentioned memtest.
Also I recommend disabling hardware acceleration on browsers, they usually fuck it up on linux.

I was not kidding when I said that subtly bad ram like bit-fading is very insidious. It slowly poisons, on occasion, your entire system and every file that is written. Every file that gets read, stored in memory, then written again is slowly corrupted. Every file to be written spends time in memory, such as during updates and installs. This means that after a particularly unlucky install or update part of a program, driver, or even kernel can be corrupted. This is incredibly hard for the system to detect, since the assumption is generally made that ram is reliable for the sake of memory usage and speed. The best indication is when programs randomly SEGFAULT, but the OS can't tell if it is because of the program's code has failed or because the copy of the program in memory got fucked. It could even be that the program is fine but made a specific system call that happened to access a corrupted part of a driver file. The consequences of this simple ram fault are terrible, and they compound.

I challenge you to keep your system running for a long time, see if it starts to crumble apart (or just randomly crash for no reason after some hours) as the drivers and kernel in ram slowly get corrupted.
I also challenge you to run UEFI level memtest, all tests enabled with at least 1 full loop. Pay special attention to the bit fade and hammer tests.

 

[Rei is Shit.]

Imagine being a mother in the future and having your children bear the unimaginable weight of their mother bragging about how many dicks she sucked. This is why adults of today are dickless and posting BBC porn in kids spaces.
View attachment 5718893

'ew 'oss

 

[Anti Snigger]

The only redeeming quality of Nvidia cards that I've found is Cuda/CuDNN, aside from that I have very little positive to say about them

 

[Slav Power]

You vill like Windows and you VILL be happy

And Windows is good. Even Windows 11 is good and the hate comes from superfluous bloat. Under the hood it's a damn fine OS. But the fact that Null has such shit luck that even Windows BSOD's at random I suspect some hardware issue.

RAM sticks that go bad can cause all kinds of weird instabilities even when the OS seems to be running fine, so if I were him I'd at least run Memtest86+ once to make sure that it's definitely not the RAM sticks going bad.

Then there's OCCT as the nuclear verification option. Makes your PC do insanely tough work on CPU, GPU and RAM, and if any of those goes bad, it will catch it. A proper system can do an OCCT stress test with zero issues.

Of course this is in case it is a deeper hardware issue than just a loose RAM stick. It can be one RAM module starting to fail and causing weird shit, or much like any instability, an issue with drivers. Null had issues with Arch over Nvidia drivers, I had Windows BSOD's because of faulty Nvidia driver versions.

BSOD causes can sometimes be diagnosed since Windows leaves a minidump when it happens. That's how I figured out the Nvidia drivers were at fault. Under Windows there is a tool called NVCleanInstall that can be used to do a proper Nvidia driver reinstall, and there's Display Driver Uninstaller that goes scorched earth on GPU drivers.

I gave my two cents on what I'd do to pinpoint the issue. Sorry if trying to be helpful and giving pointers is this much of an issue.

 

[Crocodylus Acutus]

'ew 'oss
View attachment 5721314

Piker can't help but open his mouth when the conversation involves dicks.

 

[WelperHelper99]

And Windows is good. Even Windows 11 is good and the hate comes from superfluous bloat. Under the hood it's a damn fine OS. But the fact that Null has such shit luck that even Windows BSOD's at random I suspect some hardware issue.

RAM sticks that go bad can cause all kinds of weird instabilities even when the OS seems to be running fine, so if I were him I'd at least run Memtest86+ once to make sure that it's definitely not the RAM sticks going bad.

Then there's OCCT as the nuclear verification option. Makes your PC do insanely tough work on CPU, GPU and RAM, and if any of those goes bad, it will catch it. A proper system can do an OCCT stress test with zero issues.

Of course this is in case it is a deeper hardware issue than just a loose RAM stick. It can be one RAM module starting to fail and causing weird shit, or much like any instability, an issue with drivers. Null had issues with Arch over Nvidia drivers, I had Windows BSOD's because of faulty Nvidia driver versions.

BSOD causes can sometimes be diagnosed since Windows leaves a minidump when it happens. That's how I figured out the Nvidia drivers were at fault. Under Windows there is a tool called NVCleanInstall that can be used to do a proper Nvidia driver reinstall, and there's Display Driver Uninstaller that goes scorched earth on GPU drivers.

I gave my two cents on what I'd do to pinpoint the issue. Sorry if trying to be helpful and giving pointers is this much of an issue.

I actually really like Windows 11 at this point. Yes I kind of had to upgrade the ram in my beater laptop to 16 gigs, but now it's fucking smooth. And it's integrated well with the new Copilot. I think the hate for the most popular os isn't warranted, all I'm saying.

You've given good tips, thing is Josh might have tried that shit and is kinda pissed hearing it again. Don't worry, he'll fix it, he always does.

 

[Slav Power]

I actually really like Windows 11 at this point. Yes I kind of had to upgrade the ram in my beater laptop to 16 gigs, but now it's fucking smooth. And it's integrated well with the new Copilot. I think the hate for the most popular os isn't warranted, all I'm saying.

You've given good tips, thing is Josh might have tried that shit and is kinda pissed hearing it again. Don't worry, he'll fix it, he always does.

Give Windows 11 Education a try. Not "Pro Education", just "Education". It's the closest to a non-bullshit LTSC-like Windows 11 install you can get now. It's possible that Win11 LTSC will come out at some point this year, but before that Win11 Education is the best option. You can just add a domain account hassle-free, Windows Settings won't nag you to add a MS account, and all the regular bloat like shortcuts to install Spotify or news getting shoved in your face is off by default.

And Null really needs to run Memtest at least once, to rule out failing RAM once and for all. Just because your OS seems to be booting and working fine doesn't mean that your RAM is 100% fine. A failing RAM stick is very insidious, and the only way you can check it is by using Memtest, which requires you to boot into it rather than into your regular OS.