16GB Memory Modules Coming from Samsung


Recommended Posts

16GB-Memory-Modules-Coming-from-Samsung-2.jpg

Samsung Electronics Co., Ltd., the world leader in advanced memory technology, has recently announced having started the sampling of 50nm DDR3 memory modules. According to the company, this new advance will allow it to fabricate more power efficient memory modules, enabling it at the same time to produce devices with capacities of up to 16GB.

According to Samsung, the new 50nm samples are DDR3 modules featuring 2Gb capacity. The devices have been said to offer two times the density of the current 1Gb chips while also delivering 40 percent power efficiency over their predecessors. The company announced at the same time that the manufacturing of the 2Gb modules allows it to mark a 60 percent productivity gain.

“We have focused on maximizing density alternatives and power savings to make our 2Gb DDR3 solution as flexible as possible for designers,” said Jim Elliott, Vice President, Memory, Samsung Semiconductor, Inc. The 2Gb module is up to 1.6 times faster than an 800Mbps 1Gb-based dual-die package and also reduces heat emissions due to the smaller number of DDR3 chips.

The new form factor allows leveraged configurations, said the company. This way, registered in-line memory modules (RIMMs) can be configured with capacities of up to 8GB, while small outline dual in-line memory modules (SODIMMs), which are mainly designed for notebook usage, can rise to 4GB configurations. Desktop and server applications can gain even more capacity through the use of dual-die packages, which enables their densities to be leveraged to 16GB.

The new 2Gb devices are able to support data rates of up to 1.3 Gb/s at 1.5 or 1.35 volts, announced Samsung. The company stated that the mass production of the new 2Gb chips is planned to start by the end of this year, and also said that the 2Gb DDR3 should become its primary DRAM process technology in 2009. It is worth noticing that Samsung brought innovations to the industry starting with the introduction of the 150nm-class DRAM technology in 2000 and going to the mass volume production of 1Gb DDR2 under the 50nm-class process technology last April.

Samsung's announcement sounds more than attractive to enthusiasts, yet there are little chances for the mainstream computers to have the new 8GB or 16GB memory modules as an affordable option. Currently, 8 GB DDR3 devices are not too popular, and, at the same time, the similar DDR2 modules have prices well over $1,000.

source

x32 is fading away, and the Trend is going higher, was quite slow with XP, and got faster with vista, i think and hope Win 7 Will flip the bowl over with over 50% 64bit, this will help support. and everyone and let the tech advance

It's "32-bit x86," not "x32." By that token, it's also "x86_64," "amd64," "EM64T" or "IA64," or numerous others (PPC, SPARC), but not "x64." There was never an architecture called "x64," it's pure marketroid BS.

It's "32-bit x86," not "x32." By that token, it's also "x86_64," "amd64," "EM64T" or "IA64," or numerous others (PPC, SPARC), but not "x64." There was never an architecture called "x64," it's pure marketroid BS.

Interesting :)

It's "32-bit x86," not "x32." By that token, it's also "x86_64," "amd64," "EM64T" or "IA64," or numerous others (PPC, SPARC), but not "x64." There was never an architecture called "x64," it's pure marketroid BS.
Windows Vista / XP X64

You had better tell the rest of the Net this. It is used as such everywhere.

Meh even my 8GB ram is not utilised beyond 30% under Vista64 after several days photo editing, gaming, video encoding etc :p upside is I can leave those apps minimised all day long and not worry whilst gaming!

Meh even my 8GB ram is not utilised beyond 30% under Vista64 after several days photo editing, gaming, video encoding etc :p upside is I can leave those apps minimised all day long and not worry whilst gaming!

Supercomputers need lots of RAM, though :whistle:

Meh even my 8GB ram is not utilised beyond 30% under Vista64 after several days photo editing, gaming, video encoding etc :p upside is I can leave those apps minimised all day long and not worry whilst gaming!

wow that's really cool, with that amount of memory you can basically put the most demanding 3D application and run at the same time in the background Crysis and you don't have to worry about it, Unless that you have a crappy Core duo 2 processor.

Meh even my 8GB ram is not utilised beyond 30% under Vista64 after several days photo editing, gaming, video encoding etc :p upside is I can leave those apps minimised all day long and not worry whilst gaming!

Now thats what I want to hear. In the Hi-Fi world we would call the extra excessive amounts of ram "head room" :p

It's "32-bit x86," not "x32." By that token, it's also "x86_64," "amd64," "EM64T" or "IA64," or numerous others (PPC, SPARC), but not "x64." There was never an architecture called "x64," it's pure marketroid BS.

The official term/spec is "x86-64" (a 64-bit superset of the x86 instruction set architecture). The rest are just vender specific addons to the original spec.

The 64-bit only version is officially called now the Intel Itanium architecture.

You had better tell the rest of the Net this. It is used as such everywhere.

I'd be glad to, because the rest of the Net is wrong. But I think a better person or group of people to tell them would be the engineers at Intel and AMD who actually built the chips and called them many various things, none of which was "x64." "x64" was, as I said, created by idiot marketers possessed of insufficient neurons to grasp the concept that these architectures all had/have their own distinctive characteristics and decided to lump them together under the made-up term "x64."

If they had called it "*64" or "*64*" that might be a little more acceptable, as "*" is accepted in the technology world as a wildcard character, but "x64" just sounds flat-out stupid. And, again, actually happens to be flat-out factually incorrect.

Mmmmmmm...super RAM! :D For the time being, its overkill...but its still nice to see it coming out! :)

Edit: 100th post! Whoohoo! :woot:

i doubt it even intended for HD computers , not even next gen ultra high ended skull trail rig :p

servers need rams like this , very useful in this case :D

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!