News Posts matching "issue"

Return to Keyword Browsing

Newegg Confirms Limited Availability of Intel Core 8th Gen Processors

A user from [H]ardOCP has posted on the website's forums an exchange he had with the customer service over at Newegg. If availability of Intel's latest 8th Gen CPUs was rumored to be limited before, this seems to bring some more credence to those reports. Case in point: over at Newegg, orders for the Core i5 8600K processor are currently being put on back-order, with estimated shipping dates of 15 to 20 days. Pore over the i7 8700K processor, though, and you'll find it currently out of stock.

Newegg has apparently ordered over 3000 units of the Core i7 8700K CPU alone, in order to keep pace with demand (these have been well-received chips as you can see on TPU's own reviews). Newegg expects these to come in at around a "3 to 5 weeks" time-frame. What separates this particular availability problem from being simply an issue of overly high demand is that Intel's Coffee Lake processors were already expected to be limited in availability even before they were launched. Remember that while Intel probably had such six-core processors as these taped out well in advance already, they did pull up their launch window so as to better compete with current AMD Ryzen offerings.

Sources: HardOCP, Newegg 8600K, Newegg 8700K

Microsoft Acknowledges Gaming Performance Issues Under Win 10 Creators Update

Microsoft made considerable noise on their vaulted Game Mode, a Windows feature which made its appearance in their latest Creators Update version of Windows 10. Game Mode was one of the foremost features in the latest Windows update, which was supposed to deliver improved performance in gaming or other full-screen 3D applications, by enabling more of the available CPU and GPU resources to be tapped into by specific applications. Specific CPU (through winding down of non-crucial processes) and GPU (through prioritization of game-related graphics memory allocation) improvements were baked into this latest version; supposedly, only performance improvements should result from this effort on Microsoft's part.

Latest Gigabyte X370 K7 Motherboard BIOS Broken Dynamic vCore, up to 1.7v

Update: It seems that the vCore voltage can go up to 1.7v, which has resulted in at least one claim of a fried Ryzen CPU on Gigabyte's forums. Multiple users are reporting this issue, and apparently the problem isn't limited to Gigabyte's K7 motherboard: users on the Gaming K5 motherboard are also reporting similar issues with the latest BIOS for their respective motherboard.

A warning to users of Gigabyte's X370 K7 motherboard: the most recent F5 BIOS version, which was posted as a stable release on the company's BIOS support page, has been originating reports from users as having increased the dynamic voltage applied towards stratospheric values (from a "healthy CPU vCore baseline.) The problem appears to be related to the usage of Gigabyte's Dynamic vCore functionality, where users that were seeing vCore values of around 1.2v started seeing those dynamic values, as set by the motherboard, being set to a crispy 1.55v instead, at the same clocks as before the BIOS update. If you have such a motherboard, and have recently updated your BIOS to revision F5 or planned on doing so, please do yourself a favor and set vCore manually to your value of choice, compensating with LLC (Load Line Calibration) so that your CPU isn't shocked to death with additional vCore.

AMD Resolves Linux Marginality Performance Issue on Newly Shipped Ryzen CPUs

We've brought to your attention how AMD's Ryzen architecture was encountering a bug that prevented it from successfully performing certain tasks under Linux. The issue, to which Phoronix was the first website to call attention to, was later confirmed by AMD, with a further remark from the chip designer that EPYC and ThreadRipper weren't affected by it.

AMD has now solved the Ryzen issue at a silicon level, and new revisions of the CPUs should be clear of the problems. Phoronix's Michael Larabel has confirmed that the new processor passes the previous insurmountable, crash-prone workloads with flying colors, so all in all, AMD delivered a swift response to the issue. The company is also doing good for itself in that it is open to replacing previous-batch CPUs that are affected by the issue, through a contact to its Customer Care department.

Source: Phoronix

AMD Issues Official Statement on RX Vega 64 Pricing Woes

Update: Related to this story, feast your eyes on Newegg's deal of the day, with a reference, standard Sapphire RX Vega 64 for $689.99 with two "free" games. I don't think I've ever seen such a conturbated launch as this. Also, considering the scope and content of the article, I will be updating the tag for this piece as an Editorial.

There has been somewhat of an uproar in recent times regarding AMD's lack of clarity on pricing of their newly-launched Vega 64. While AMD themselves told reviewers and consumers that their RX Vega graphics cards would be available for $399 (Vega 56) and $499 (Vega 64), recent events have, at the very least, cast some doubts on Vega's supposedly clean-cut pricing. Some popular reviewers and YouTubers have even gone so far as to say they won't be accepting any more samples from AMD due to a perceived slight at the erroneous information provided by the company; when someone reviews and analyses a product based on a fixed price-point advanced by a company, and then that pricing seems to have turned out nothing more than smoke and mirrors... People's work is put out the window.

Now, AMD has come out to put rumors of false Vega pricing announcements to rest. Except the skeptic in me remains, well... skeptic. Here's what AMD has said: "Radeon RX Vega 64 demand continues to exceed expectations. AMD is working closely with its partners to address this demand. Our initial launch quantities included standalone Radeon RX Vega 64 at SEP of $499, Radeon RX Vega 64 Black Packs at SEP of $599, and Radeon RX Vega 64 Aqua Packs at SEP of $699. We are working with our partners to restock all SKUs of Radeon RX Vega 64 including the standalone cards and Gamer Packs over the next few weeks, and you should expect quantities of Vega to start arriving in the coming days."

Noctua's Alleged Manufacturing Discrepancies Put to the Test, Found Lacking

A recent maelstrom has hit Noctua in social forums due to a then unverified, reported issue with manufacturing differences between fans of the company that have been built on Taiwan or China factories. The issue, first brought about by Reddit user Kendalf, left open some questions on cooling and noise deltas between Taiwan and China-made Noctua fans, while admitting that the issue could be with a particular batch/testing conditions/other unidentified variables. But the Internet is fantastic, and what was posted as a legitimate question was quickly turned into a pitchfork-handling mob crying "Noctua never again" and "Down to Noctua" (which really are one of the most innovative companies in the cooling space...)

AMD Confirms Ryzen Marginality Performance Issue Under Linux, TR and EPYC Clear

An issue on AMD's Ryzen performance under certain Linux workloads, which caused segmentation faults in very heavy, continuous workloads on the Ryzen silicon (parallel compilation workloads in particular) has been confirmed by AMD. Tests like Phoronix's Test Suite's stress run quickly bring the Ryzen processors to their knees with multiple segmentation faults. While this problem is easy to cause under very heavy workloads, the issue is virtually absent under normal Linux desktop workloads and benchmarking,

AMD also confirmed this issue is not present in EPYC or Threadripper processors, but are isolated to early Ryzen samples under Linux (AMD's testing under Windows has found no such behavior.) AMD's analysis has also found that these Ryzen segmentation faults aren't isolated to a particular motherboard vendor, but are problems with the processors themselves. AMD encourages Ryzen customers who believe to be affected by the problem to contact AMD Customer Care. Some of those who have contacted customer care about the segmentation faults have in turn been affected by thermal, power, or other problems, but AMD says they are committed to working with those encountering this performance marginality issue under Linux. AMD will also be stepping up their Linux testing/QA for future consumer products.

Sources: Phoronix, AMD Confirms Ryzen Issue - Phoronix

AMD Crimson ReLive 17.7.2 Presents Some Issues to Users

Users running AMD's latest 17.7.2 driver package are running into issues - which, let's face it, is somewhat understandable, considering all the new features AMD has crammed into this latest driver release. All driver releases ship with a bug here or there - there is even a "Known Issues" checklist on almost all of them - so unless bugs are widespread enough, they don't ever reach the critical mass to be noted by most users. However, users in both our forums and Reddit have been reporting issues after they install their 17.7.2 driver package: namely, the absence of the ReLive tab on the Radeon Control Panel.

The issue persists even after a full DDU (Display Driver Uninstaller) cleanup, and appears to be inconsistent in that users with the same hardware and on the same OS have mixed results upon installation. This issue has been confirmed by the Director of AMD's Corporate Strategy, Terry Makedon, on Reddit, who said that "Windows 7 being identified as beta and missing DVR is now reproduced in here and we will issue an update later today to address that. Sorry for that, hopefully we fixed it fast enough." For now, and until AMD releases a fix, there seems to be a workaround, as our own VSG has reported on an update to our Crimson ReLive 17.7.2 Preview: "One potential fix reported is to disable all security components (Antivirus, Malware protection etc) and to use the AMD Web Installer instead (Windows 10 64-bit here, replace 10 with 7 and 64 with 32 in the URL for other options)."Sources: Forums @ TPU, AMD Reddit, Thanks @ user Nabarun for first reporting this

Intel Clover Trail-based Systems Won't Receive Creators Update - Ever

We recently covered how users with systems powered by Intel's Clover Trail CPUs were having issues with a "Windows 10 is no longer supported on this PC" error when trying to update their machines to Microsoft's latest Windows 10 Creators Update. The systems in question - built around Intel's Clover Trail Atom processors - are generally low-cost, low-power machines (mainly 2-in-1) released between 2012 and 2015 under Windows 8 and 8.1. These systems were deemed ready to receive Windows 10; however, now it looks as if they won't ever be able to support it.

In our last piece, we wondered if this problem was only temporary; now it seems it's permanent. Microsoft has however announced that Clover Trail-based systems will still receive security updates (just not feature updates) until 2023. The issue seems to lay with Clover Trail's integrated GPU drivers; Clover Trail Atoms use GPU technology licensed from Imagination Technologies. Ars Technica's Peter Bright says that "Imagination appears unwilling, and Intel appears unable, to update the GPU drivers to meet the demands of the Creators Update. So systems built with such hardware will never be upgradable beyond the Anniversary Update."

On Cryptocoins: I think I know why Satoshi Nakamoto Hides

To all you out there wondering why you can't get a GPU for gaming at a reasonable rate, or why we are using record numbers in energy usage to mint so called "toy money," depleting our planets energy in the process, I have a bit of a statement to make as a former miner and "part of the problem" so to speak.

I'm sorry, it wasn't supposed to be this way. None of it was supposed to go down like this.

That probably requires some justification, yes? I mean mining is an inherently energy expensive operation, right? Well, yes and no, respectively. Yes, it requires justification, and that's precisely because mining is NOT an inherently energy expensive operation, despite public perception. It has become that way due to human greed, and nearly everything bad to come from cryptocurrency has decidedly come from that group: humans. Cryptocurrency is not inherently responsible. The inventors, pioneers, and early miners such as myself never anticipated what was to come, and we did not intend it to be this way. Bitcoin was intended to do good, and in the end, it wasn't cryptocurrency that screwed it all up, it was humans. Human greed, particularly.

Update on the Intel X299 Platform "VRM Disaster"

We have some updated information on the X299 Platforms VRM issues from the same overclocker who initially discovered the issue, renowned overclocker der8auer. In an updated YouTube video, der8auer first updated his viewers with new information on his testing techniques, and basically concluded that all issues initially detected (throttling included) are still is an issue even after extensive testing, only in some instances it is difficult to detect not only if you are throttling, but even specifics such as what precisely is throttling. He goes into extensive detail, but a brief summary of the videos main points can be found below for your consumption.

NVIDIA's 384.76 Drivers Crash Watch Dogs 2 on Startup

Users beware: if you've updated your NVIDIA drivers to the recently released 384.76 version and intend to play Watch Dogs 2, you might have a hard time doing so. Reports have surfaced that the latest NVIDIA drivers, which bring support to the "Rise Up" open-beta of "Lawbreakers" as well as support for "Spiderman: Homecoming - a VR Experience.", break startup on Ubisoft's game.

The issue doesn't appear to be listed on NVIDIA's 384.76 release notes (not even on the PDF), so it seems this issue largely flew under NVIDIA's radar. But if you've had problems with Wash (sorry, Watch) Dogs 2, be sure to check if you have the latest 384.76 drivers installed. That could be the source of the problem. Our own resident W1zzard himself ran into this problem, but no amount of steampunk wand waving was able to fix the issue. However, a fresh install of NVIDIA's previous driver release (382.53) should let you go out to San Francisco again.

Edit: The issue is related to Ansel and can be fixed by starting C:\Program Files\NVIDIA Corporation\Ansel\Tools\NvCameraConfiguration.exe and selecting the "disabled" option at the bottom of the window.Source: Ubisoft Forums
Return to Keyword Browsing