WEBVTT 00:00:00.000 --> 00:00:03.960 Hey, it's me, Riley. I've been gone for two weeks because I was on vacation. 00:00:03.960 --> 00:00:07.040 I wasn't dead because I can't die. 00:00:07.040 --> 00:00:09.040 I'm an immortal cyber ghost. 00:00:10.160 --> 00:00:13.520 Intel has admitted that their 13th and 14th gen 00:00:13.520 --> 00:00:18.320 mobile CPUs are crashing, but claim it's a totally different situation 00:00:18.320 --> 00:00:23.280 from their also crashing 13th and 14th gen desktop CPUs. 00:00:23.280 --> 00:00:28.440 The company has stated that they are aware of a small number of instability reports 00:00:28.440 --> 00:00:33.040 on their mobile processors. But they say these are common symptoms stemming 00:00:33.040 --> 00:00:38.040 from a broad range of potential hardware and software issues and not the same issue 00:00:38.040 --> 00:00:42.960 as the desktop chips. Then what Jacob wrote was, that's pretty crazy since Intel doesn't know 00:00:42.960 --> 00:00:49.200 what the root cause of the desktop processor issue is, except we literally just saw that Intel, 00:00:49.200 --> 00:00:52.320 like an hour ago put out a press release 00:00:52.320 --> 00:00:56.920 saying that they had identified the root cause. Breaking news straight from Riley's phone. 00:00:56.960 --> 00:01:00.320 Just hold on, I got the news here, it's inside. 00:01:00.320 --> 00:01:05.040 So Intel's post about this says that there's an error in their microcode that resulted 00:01:05.040 --> 00:01:08.400 in incorrect voltage requests to the processor 00:01:08.400 --> 00:01:15.640 and they're gonna be delivering a microcode patch to fix this later this year in August, mid-August. 00:01:15.640 --> 00:01:20.540 So their original move of blaming motherboard manufacturers and gamers 00:01:20.540 --> 00:01:24.440 for overclocking their processors is sort of valid. 00:01:24.440 --> 00:01:27.760 The overclocking is coming from within the house. 00:01:27.760 --> 00:01:31.520 Now that press release was just talking about the desktop processors. 00:01:31.520 --> 00:01:38.000 So Intel's claim here that that issue is separate from the one that's currently affecting mobile processors, 00:01:38.000 --> 00:01:44.020 might be true, might not. However, Matthew Cassels, CEO of Alderaan Games, 00:01:44.020 --> 00:01:47.880 one of the studios that documented Intel instability in player crash reporting, 00:01:47.880 --> 00:01:51.120 has a different explanation for Intel's denial. 00:01:51.120 --> 00:01:54.160 Cassels believes they are downplaying the mobile concerns 00:01:54.200 --> 00:01:58.240 due to the costs needed to rework the BGA packages 00:01:58.240 --> 00:02:01.240 used to solder their mobile processors to PCBs 00:02:01.240 --> 00:02:05.240 and to reduce harm to OEMs and partners like Razer and MSI. 00:02:05.240 --> 00:02:10.000 Before they announced the patch coming in August, Intel had been trying everything to solve these issues, 00:02:10.000 --> 00:02:15.080 even going so far as to yank out the e-cores in 11 new 14th gen SKUs. 00:02:15.080 --> 00:02:20.680 These new chips for embedded in commercial markets take a page out of your local underfunded public pool 00:02:20.720 --> 00:02:24.440 in that they're entirely full of P-cores, 00:02:24.440 --> 00:02:27.600 P-core, P-core, just go like that one. 00:02:27.600 --> 00:02:31.960 Microsoft has said that about eight and a half million Windows devices were affected 00:02:31.960 --> 00:02:37.360 by the CrowdStrike outage last week as Linux users laughed in superiority, 00:02:37.360 --> 00:02:43.360 seemingly forgetting that CrowdStrike has also caused issues on several Linux distributions. 00:02:43.360 --> 00:02:47.980 Last month, Red Hat reported that booting CrowdStrike's Falcon sensor process 00:02:47.980 --> 00:02:52.680 caused kernel panic, which is more of a Linux analog to Windows blue screens, 00:02:52.680 --> 00:02:58.600 then it is a term for anxious corn. There are even reports of Debian Linux servers crashing 00:02:58.600 --> 00:03:02.120 and refusing to boot after a CrowdStrike update in April. 00:03:02.120 --> 00:03:06.760 While those issues seem to be fixed, some Windows machines may still be affected. 00:03:06.760 --> 00:03:12.680 Microsoft has released a recovery tool meant to help IT admins repair CrowdStrike machines. 00:03:12.680 --> 00:03:15.800 Delta Airlines, though, seems to still not have fully recovered 00:03:15.800 --> 00:03:19.080 since they've canceled 778 flights today. 00:03:19.080 --> 00:03:24.200 I'm sure tired families are excited at the prospect of being forced to spend more time together 00:03:24.200 --> 00:03:27.740 while they're stuck in the airport. Perhaps other airlines should consider 00:03:27.740 --> 00:03:33.700 being a bit more like Southwest, whose entire infrastructure runs off a single Commodore 64. 00:03:34.680 --> 00:03:37.760 Works for them. That's a joke. 00:03:37.760 --> 00:03:43.640 AMD is apparently putting all their efforts into making upcoming RDNA for graphics cards, 00:03:43.640 --> 00:03:47.600 ray tracing beasts. Prominent hardware leaker Kepler 00:03:47.640 --> 00:03:51.880 tweeted out some alleged new features coming to the RDNA 4 platform. 00:03:51.880 --> 00:03:56.800 A lot of the leaked text is about as readable as the black speech of Mortor, 00:03:56.800 --> 00:04:01.080 but the double-intersect ray tracing engine raises some eyebrows. 00:04:01.080 --> 00:04:05.440 According to PC Gamer, it implies that either RDNA 4 will have double 00:04:05.440 --> 00:04:11.120 the number of RT units that RDNA 3 has, or these units are able to process twice the number 00:04:11.120 --> 00:04:14.880 of ray triangle intersection calculations. 00:04:14.880 --> 00:04:22.100 Just calm down guys, I know it's exciting. The point is this, number go up, Gamer Brain happy. 00:04:22.100 --> 00:04:25.560 But Gamer Brain no happy with performance rumors. 00:04:25.560 --> 00:04:31.100 Kepler also claims that while the ray tracing may be improved, the strongest RDNA 4 card 00:04:31.100 --> 00:04:34.160 will perform somewhere between this generation's 00:04:34.160 --> 00:04:38.560 RX 7900 XT and 7900 XTX. 00:04:38.560 --> 00:04:43.440 As for when we'll see these cards, Kepler alleges they will be unveiled early next year. 00:04:43.440 --> 00:04:49.080 That may mean they'll be launching alongside NVIDIA's RTX 50 series GPUs, 00:04:49.080 --> 00:04:54.420 as yet another leaker, our old pal, Copight 7 Kimmy, believes that Team Green 00:04:54.420 --> 00:04:57.440 is delaying the Blackwell launch from fall this year 00:04:57.440 --> 00:05:01.800 to CES next year. I'm not sure why, but I'm guessing they lost 00:05:01.800 --> 00:05:07.060 their prototype cards under a pile of money, and it's gonna take them months to check all those piles. 00:05:07.060 --> 00:05:12.360 They've just been, they keep coming in. We don't know where to put it. As an undying, ageless being, 00:05:12.360 --> 00:05:16.160 I don't understand quick bits. Millennia are mere minutes to me, 00:05:16.160 --> 00:05:21.200 but I hear you like them, so here you go. The ROG Ally X is out and reviews are hitting 00:05:21.200 --> 00:05:25.320 every place that cares about reviewing the Ally X. 00:05:25.320 --> 00:05:31.880 Along with the handheld, ASUS has released an update to the Armory Crate app to turn the AirSats game launcher 00:05:31.880 --> 00:05:35.880 into something players should dislike using slightly less. 00:05:35.880 --> 00:05:39.960 As for the new handheld itself, praise has been levied at the improved battery life 00:05:39.960 --> 00:05:46.280 and increased RAM, but some reviewers have complained of difficulty reaching certain buttons with smaller hands. 00:05:46.280 --> 00:05:50.120 Jacob's writing, I don't have that problem because my hands are so big, 00:05:50.120 --> 00:05:54.640 like you wouldn't even believe it if you saw them, just crazy big hands, but that's not true. 00:05:54.640 --> 00:05:57.720 I have their average of best. 00:05:57.720 --> 00:06:00.800 Normal hands. I'm immortal, normal hands. 00:06:00.800 --> 00:06:06.760 It's trade-offs. NVIDIA is working on a new variant of the company's B200 flagship AI accelerator. 00:06:06.760 --> 00:06:11.440 It could sell to the Chinese market without violating U.S. export restrictions. 00:06:11.440 --> 00:06:16.040 I mean, they gotta get their AI chips from somewhere. Let them sell the chips, Joe. 00:06:16.040 --> 00:06:21.960 They're stepping down anywhere. I mean, who cares? You're not gonna be there. It is officially over. 00:06:21.960 --> 00:06:26.840 There's a chance NVIDIA is wasting their money though. According to courts, analysts think the U.S. 00:06:26.840 --> 00:06:31.320 is highly likely to ban NVIDIA's last gen H20 chip, 00:06:31.320 --> 00:06:36.280 which was designed for the same purpose. It's kind of rude. Who are we to restrict Chinese access 00:06:36.320 --> 00:06:42.360 to the Scarlett Johansson we have at home? Reddit has signed deals with several major sports leagues 00:06:43.320 --> 00:06:45.440 in the greatest crossover of all time 00:06:46.640 --> 00:06:50.160 between redditors and sports. Anyway, they signed deals with sports leagues 00:06:50.160 --> 00:06:53.400 such as the NFL, NBA, and MLB. 00:06:53.400 --> 00:06:58.720 The sports leagues will post game highlights behind the scenes videos and AMAs with players, 00:06:58.720 --> 00:07:02.960 which sounds kind of cool until you realize it'll lead to more ads. 00:07:02.960 --> 00:07:06.760 Advertisers will show ads within these videos and the revenue will be split 00:07:06.760 --> 00:07:11.400 between Reddit and the sports leagues. This means Reddit is now the place 00:07:11.400 --> 00:07:15.760 where you can watch a worse version of TV while your data is being scraped for AI training. 00:07:15.760 --> 00:07:19.520 Rivian CEO RJ Sc... Oh no, I don't know. 00:07:19.520 --> 00:07:22.680 Scaringy? Scaring. Scringe. 00:07:22.680 --> 00:07:25.840 Sc... Scrimmage. Leave all those in. 00:07:25.840 --> 00:07:30.880 Has told the Verge that the company will not be adopting carplay for its vehicles. 00:07:30.880 --> 00:07:38.240 Oh no, I have to say it again. Oh, Scaringy, the CEO, not a scary orange. 00:07:38.240 --> 00:07:40.160 Okay, so I guess it's Scaringy. 00:07:41.320 --> 00:07:46.440 Said that his reasoning for not using Apple carplay is ironically similar to Apple's desire 00:07:46.440 --> 00:07:51.040 to control their own ecosystem. Scaringy also points out that if, that can't be right. 00:07:51.040 --> 00:07:54.960 Scrooge also points out that if Rivian instituted carplay, 00:07:54.960 --> 00:08:00.200 users would have to leave the app on the dashboard to do things like open the car's front trunk. 00:08:00.240 --> 00:08:03.440 Or hear me out, you give opening the front trunk 00:08:03.440 --> 00:08:09.080 a separate f***ing button. The controls for a vehicle that can easily take a human life 00:08:09.080 --> 00:08:13.400 if you drop your attention for a moment shouldn't really be relegated to a bargain bin iPad. 00:08:13.400 --> 00:08:18.640 That's what, you know, that's what we think. And a 700 Hertz refresh rate has been achieved 00:08:18.640 --> 00:08:23.240 on a CRT monitor. YouTuber Retro Gaming Base has been putting 00:08:23.240 --> 00:08:27.600 a 22 year old Ilyama Vision Master Pro 512 00:08:27.600 --> 00:08:33.520 through the paces over the past couple of months by overclocking it to hit refresh rates of 255 Hertz 00:08:33.520 --> 00:08:37.680 and above. Their latest attempt got the monitor to 700 Hertz, 00:08:37.680 --> 00:08:40.900 much higher than the highest commercially available gaming monitor. 00:08:40.900 --> 00:08:46.120 There is a small downside. The maximum resolution the CRT monitor could achieve 00:08:46.120 --> 00:08:50.240 at this refresh rate was 320 by 120. 00:08:50.240 --> 00:08:53.800 But you don't need to see your enemies to feel superior to them. 00:08:53.800 --> 00:08:57.700 I mean, but hopefully we'll be able to see you on Wednesday 00:08:57.700 --> 00:09:00.860 because you'll have come back for more tech news at that point, right? 00:09:00.860 --> 00:09:04.180 Cause that's what you're gonna do. 00:09:06.900 --> 00:09:07.740 Right?