Windows Vista a reason to buy ECC memory?

WGruener

Distinguished
Feb 1, 2006
48
0
18,530
This morning, we have posted an article about Microsoft's decision to gently recommend ECC memory for computers that come preinstalled with Vista. The benefit, according to Microsoft, is to receive a much more stable operating system.

What do you think? Is Windows XP not stable enough today and is it worth to upgrade to ECC for a more stable OS?
 
I thihk it is a continuation of the recent and quite alarming trend with MS.

In essence, they are extending their OS [virtual] monopoly into the hardware realm, thus really reducing consumer choice.

It began with the insanely steep hardware requirements (most notably, graphics) that would most likely cause people that would like to upgrade the OS upgrade their systems at some significant cost, then it affected teh next gen DVD format war, and now it is expanding into other areas of the system.

Plus, the DRMs that they are pushing are quite insane as well. I think I recall at some point they were proposing monitors with DRM?! So now users need to upgrade that, as well.

I think any shifts in the hardware markets should be driven by the hardware market, and not some OS gimmickry. If there is an argument to be made for natural monopoly in the OS segment, it definitely should not extend to hardware.
 
If it's required, yes. But I think it's actually insane that Microsoft expects us to buy special hardware, just because they're too lazy to finish their software properly.
 
Are you mad??? In what possible way would M$ benefit by forcing (or recommending) that people use ECC memory? Last I checked M$ doesn't make memory nor do they own an significant shares/interests in memory.

Everyone makes ECC memory. The statement that it somehow benefits M$ (both financially and strategically) to make people use ECC memory is insane.

It began with the insanely steep hardware requirements (most notably, graphics) that would most likely cause people that would like to upgrade the OS upgrade their systems at some significant cost, then it affected teh next gen DVD format war, and now it is expanding into other areas of the system.

I think any shifts in the hardware markets should be driven by the hardware market, and not some OS gimmickry. If there is an argument to be made for natural monopoly in the OS segment, it definitely should not extend to hardware.

Hey, last time I checked every single computer sold in the world has some some sort of 3D acceleration. Every computer sold in the past 4 years has 3d acceleration. Explain to me how M$ has made this so! And please show me the "steep hardware requirements" that will be required to run Avalon. Do you even know what the minimum requirements are??? Probably not so I'll post them below.

An AGP or PCI-e video card with 64MB of VRAM. Wow... so steep. And even if some people don't have this, M$ has stated Vista will run in 2D mode w/ a WinXP look just fine. Here is a list of compatible chips/cards from ATI/nVidia/Intel:

http://www.ati.com/technology/windowsvista/index.html
http://www.nvidia.com/page/technology_vista_home.html
http://www.intel.com/business/bss/products/client/vistasolutions/index.htm

The evolution to a 3D accelerated GUI is a natural one. It's a complete waste of talent NOT to use 3D acceleration.

In essence, they are extending their OS [virtual] monopoly into the hardware realm, thus really reducing consumer choice.

Please explain to me how M$ has a vritual monopoly in the hardware realm. Really, I want to know.

-mpjesse
 
I for one see this is a good thing.

Naturally, quality RAM is going to be almost as good as ECC memory. But the problem is the majority of system builders put cheap, crappy memory in the systems they sell. (the exception of course would be Dell, Gateway, and all the big boys- they tend to use name brand stuff)

Since system builders will never voluntarily put good memory in their systems, M$ wants them to use ECC. With ECC you can have it both ways- cheap memory with added stability. The price of ECC will fall as demand and production increases. It appears to me that M$ is trying to make system builders a little more accountable for stability.

Why is that bad?

-mpjesse
 
this make me more...more...hated with Ms/vista. what are they thinking?. forcing people to buy this and that....upgrade this and that. just to load their junk. with all nonsense requirement....is vista worth of upgrade?. can vista run on laptop ?(as they stated "compatible vista laptop"). with the insane requirement, can the laptop run in mobile mode (cpu with 800MHz) while preserving batery?.....I don't think so :evil:
 
This morning, we have posted an article about Microsoft's decision to gently recommend ECC memory for computers that come preinstalled with Vista. The benefit, according to Microsoft, is to receive a much more stable operating system.

What do you think? Is Windows XP not stable enough today and is it worth to upgrade to ECC for a more stable OS?

Interesting how some speculate and act as if the speculation was pure gospel (refering to some of the uninformed replies). Anyways, I am speculating here, but it is my professional opinion that MS is doing this not because Vista needs ECC memory, but because ALL modern memory needs to be ECC. Back when memory modules where 256MB and less, non-ECC memory was fine. Fact is anything 512MB or larger *NEEDS* to be ECC to run stable. Chances are you are getting dozens of memory errors a day but they just go unnoticed as they rarely affect vital data. Memory needs to be ECC because it is getting larger. Even XP is less stable with my two 1GB RAM sticks than it was with a single 512MB stick. Faster, but less reliable. Just my opinion though.
 
I have built about 20 systems with the AMD Athlong 64/Opteron platform and I never found the required ECC on the Opterons to provide any better stability than Corsair Non ECC memory. I have not noticed a difference between buffered and non buffered. NUMA is freaking cool, but programs crash or ignore avalible memory. Getting good code, stil seems like a harder proposition than getting good software. It is as such that I think MS has other reasons for the memory soft requirement.

I think this requirement is for other reasons:
1.)encryption keys stored only in ram
if windows vista is all about security and stability, it would make sense that some of these hardware keys are stored in ram, and they are accessed alot. It is just a guess, but I also think MS might be thinking about storing programs in an encrypted memory space making it really hard to hook code from another application. Things like these are already being done on MS's xbox consoles. It wouldn't suprise me if some of that will filter its way into Vista.

2.)non execute bits
i still kinda wonder how the NX bit works, but from what i know, the NX bit must be stored in memory before being sent to the processor for execution, if an NX bit was set in error or intentionally on a buffer overflow section of memory, I could be used to hook other processes. This could be another step in securing the software of an OS from easy hardware hacking.

3.)quick boots on laptops
it is another guess, but a likely one that as Intel and AMD make the push for INSTANT ON computing, a feature in Vista, they have found that to skip the step of reloading memory from the hard drive requires better memory for maintaining a system state. I still have not gotten a gaming box to work correctly with a suspend mode(its like a ram only hibernate) vs hibernate that writes to the hard drive and then shuts down.

4.)this could be a prerequirement for flash ram
agian, INSTANT ON computing, is a big movement right now and as flash memory merges with other memory types and serves as a cross gap between ram and hard drives, this ECC requirement might be a puch now for the XP version of Vista.

I don't plan on getting Vista at this point, DirectX 10 cards are not yet avalible and all of the new features will take some time to sort out. I will continue to evaluate it as a MSDN developer, but Mac OS X seems like a more usefull OS to learn, as it can bridge the gap between a working gui and linux/bsd platform with suported software on it.
 
I'm sorry, were we reading the same article? Where does it say M$ is forcing anyone to do anything?

They are merely suggesting system builders use ECC.

Sheesh... chill out.

-mpjesse
 
I have built about 20 systems with the AMD Athlong 64/Opteron platform and I never found the required ECC on the Opterons to provide any better stability than Corsair Non ECC memory.

Yes, you are right. Corsair memory (even the cheap stuff) is probably just as good as ECC.

The problem is this: the majority of the computers sold with Windows XP use CRAP, GENERIC, CHEAP memory. Nearly no system builder ships their system with corsair! The only builders who do that are builders like Alienware who make up .001% of the market.

-mpjesse
 
I would REALLY like to see MS make it so I can tell what components are responsible for some random crashes. Granted, crash frequency is infrequent, but diagnosing the cause (Memory, video card mem, other hardware, etc) is still near impossible for some those odd crashes that leave absolutely nothing in the event logs or information that is otherwise useless for me the "user". I can't help but wonder if memory is getting a bad rap here. Its would seem much more likely the more complex components would be more prone to failure than the (relatively) simple memory sticks. (History of failures seem to point to this, too as, generally speaking, complexity fails and simplicity succeeds)

(just a scan through my event log pulled these 2 prime examples)

Event Type: Error
Event Source:
Event Category: None
Event ID: 0
Date: 11/1/2005
Time: 6:27:03 PM
User: N/A
Computer: G
Description:
The description for Event ID ( 0 ) in Source ( ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 6.
Data:
0000: 3f 3f d1 2a e3 ee 92 2d ??Ñ*ãî’-
0008: ae 39 d9 22 ee e9 9a e5 ®9Ù"îéšå
0010: 2e 2f c1 3a f3 f1 82 3d ./Á:óñ‚=
0018: e9 22 8d 32 f9 f9 8a 35 é"?2ùùŠ5
0020: 1f 1f f1 0a af bf f6 0a ..ñ.¯¿ö.
0028: 82 e0 eb 02 d7 c9 ba 05 ‚àë.×ɺ.
0030: 6a 22 b8 f7 63 26 b0 1d j"¸÷c&°.
0038: 06 07 e9 12 cb f4 f3 f8 ..é.Ëôóø
0040: 41 7f 90 6a a3 a1 d2 6d A?j£¡Òm
0048: 76 77 99 62 ab a9 da 65 vw™b«©Úe
0050: 6e 6f 81 7a b3 b1 c2 7d no?z³±Â}
0058: 66 67 89 72 bb b9 ca 75 fg‰r»¹Êu


Ohhhhhh here's another one of my favorites...

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2/5/2006
Time: 12:44:38 PM
User: N/A
Computer: G
Description:
Error code 1000007f, parameter1 00000008, parameter2 f788ed70, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 66 37 38 38 65 64 37 30 f788ed70
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000


Gotta love this:
http://www.anetforums.com/posts.aspx?ThreadIndex=29710

So I should replace my memory AND my video card and if that doesn't fix it AND my sound card and if that doesn't fix it AND my motherboard... jeeze. gimme a break. I prefer MS helping me determine what part is failing. Increase my ability to make educated CHOICES as opposed to baby proofing (aka nerfing) my system.

side note: memtest86 had seven flawless passes (non ECC) and i'm not about to go about buying random parts to replace what may or may not be failing... see my point?
 
Last time I checked you'll aslo need 2 gigs of RAM too, and those graphics will require at least 256mb card. Sounds like a new motherboard and some nice expensive RAM. After service pack 12 though I think I'll look into getting it.
 
I would REALLY like to see MS make it so I can tell what components are responsible for some random crashes. Granted, crash frequency is infrequent, but diagnosing the cause (Memory, video card mem, other hardware, etc) is still near impossible for some those odd crashes that leave absolutely nothing in the event logs or information that is otherwise useless for me the "user". I can't help but wonder if memory is getting a bad rap here. Its would seem much more likely the more complex components would be more prone to failure than the (relatively) simple memory sticks. (History of failures seem to point to this, too as, generally speaking, complexity fails and simplicity succeeds)

The problem with linking between programs is it is sometimes hard to determine what the error is, and what caused it. At the kernel/process/embedded level of programming, program opperations perform executions related to memory addresses and the data that is directly in them. Hardware typically writes to and from memory using a DMA channel and is prompted from another software thread running on another asyncronous hardware element, and so if one piece of hardware or a driver missinforms the hardware, it will write to the wrong memory location without leaving a trail. The memory does not know who wrote the data, and so an exception is thrown. DLLs have the same problem, and as far as the OS is concerned they are asyncronous(event driven). Windows used a shared system memory space for OS and for program execution until windows NT.

In the switch to NT and later to XP(the latest version of the NT kernal) programs are virtualized by the operating system to run in a logical rather than a physical memory structure, meaning that when a program calls for a memory address, it is not a real one, it is one that has been replaced at run time with the actual memory address. All of these moving addresses makes it hard to determine who made an async call that wrote to the wrong memory. The error might have been made along time ago by a program, only to be executed by a program that does not run that often.

Moving to a registerd hardware enviroment(where hardware has encryption certs) will allow MS to restrict memory to legal actions based on hardware that has been certified by MS to work, the only problem being that if your key is transcoded wrong, the hardware will not be allowed to access system memory.

Agian I think this is just an assertion from MS that good memory is critical for windows to not break, I agree, but I don't think ECC is the answer, GOOD memory is. I bought value ram once, and my systems started crashing, I replaced it with Corsair and what do ya know, the computer work flawlessly. These days I would rather skimp on CPU power than on RAM.

Its also a way for MS to pass the buck on to the system builders, by asking "did you use ECC mem?" "oh, no, oh, it must be your problem we will not support it"

In one instance I built a computer with some stability issues and the MB company blamed the PS company, and then the PS company blamed the MB company only to find out that the Memory was the issue.
 
Hey I have a brilliant idea, why not just keep windows XP and not bother with Vista at all? It's not like you really need it, come on now. Why spend all that money when windows XP can do most everything you want it to.

-Mark
 
Another thing to think about is that as memory goes from an average system size of 2GB to 32GB durring the life time of Windows Vista, and a production size of 65nm to 22nm the expected error rate of even good RAM may be an issue.
 
Last time I checked you'll aslo need 2 gigs of RAM too, and those graphics will require at least 256mb card. Sounds like a new motherboard and some nice expensive RAM.

Holy crap are you WAY off base. M$ says this directly from their Vista hardware requirements page:

Memory
To take better advantage of Windows Vista functionality, you should have at least 512 MB of RAM, on your PC. This provides enough memory for both the operating system and a typical application workload. And while 512 MB is great for many scenarios, more advanced users will want 1 GB of memory or more. If your typical workload is heavy, you do a lot of image editing or development, or you run multiple applications all the time, then more memory is good. In general, an investment in additional memory is wise, and you should certainly make sure that the computer you buy has room to add additional memory later.

If you are building or buying PC today, you probably want to avoid the low end of the current GPU range and make sure you get a GPU that supports DirectX 9 and has at least 64 MB of graphics memory.

Why don't actually try READING or googling before making such reckless statements. People in here actually believe what other people say in these forums.

http://www.microsoft.com/technet/windowsvista/evaluate/hardware/vistahardware.mspx

-mpjesse
 
Dear all...

Oh man, 2 sticks of 512 non-ECC PC3200 are already way off lots of people's budget, and if ECC is gonna be more expensive and slower than non-ECC i think i'm gonna stick to XP until everything drops in price.
 
In my humble opinion, Vista is going to be a bit of a disappointment to M$, mainly becuase there isn't a lot of reasons to upgrade until they force you. From what I have seen (And I admit, I haven't been paying much attention, cause I don't plan on buying it), there are only minor improvements that aren't worth the hassle of changing OSes.
 
I know, I always get like this before a M$ OS release, cause I know half of what they say will turn out to be completely inaccurate once the OS is released and the real enthusiasts get their hands on it.

I will probably find a way to evaluate it anyway.
 
Thats not what I was getting at at all. I would have no problem running Vista with what I've got. I am saying that with XP (at least after SP1) we got the best of 98 and 2000 combined. With Vista, I see no reason to upgrade and deal with everything they are dictating, nor the whole new batch of bugs, driver troubles, and general issues associated with it. I am sure I will test it out when its released as my second os, since I will probably be completely on XP x64 by then, I am just not going to spend any additional money on hardware to get it.

Maybe I'll make them get me a new laptop at work when it comes out :wink:
 
"ECC is recommended"
"64/128 MB GPU recommended"
"1GB Ram recommended"
"20 GB HDD recommended"

I wonder what will happen to the "simple PC" you can build today ?
200 250€ Computers sold like Candy in france around christmass.
(60GB / 512 Ram / Sempron or Celeron)

Hell even Dell makes these :
http://www1.euro.dell.com/content/products/features.aspx/dimen_1100?c=fr&cs=frdhs1&l=fr&s=dhs

Why ?
1) Surf / Download
2) DVD / Audio
3) Word / Excel

The only reason for M$ for this arms race is :
- Special deals with hardware manufacturers (very plausible)
(We all know how mass distribution and reverse discout works)
- DRM Management
(No comment needed there)


There have been ZERO improvement from 95 to XP SP2.

ECC ? Gimme a break
 
I don't see this affecting the overcost as much as the basic requirements of vista.

I think that an OS that you can use in a "full bells and whistles" mode is good as a lot of poeple have very powerful computers these days and I see no reason why the OS should not give something to these users.

The fact that Microsoft have included a WinXP style for lower spec systems is a great idea and should help people transition.

Microsoft are in no way forcing people to use ECC but they're saying if you do you can expect a more stable experience. Sounds fair enough to me.

BTW my current main Rig has 2GB ECC corsair RAM :)
 
LOL

Thank god the world isn't controlled by visionless people.

-mpjesse

mpjesse is completely right. I've been reading this forum for a while now and find it quite funny how people post absolute rubbish and try to pass it off as fact.

The company I work for build their own clone machines and sells these alongside the corporate versions of HP/Compaq's. Our machines use cheap crappy RAM whereas the HP's use good quality RAM. Our clones are a fair bit cheaper but use cheap shoddy RAM and break down a lot more....

Guess what most of the problems with our units are.... you guessed it... failed RAM :roll: Personally I wouldn't put anything other than Kingston ValueRam or Corsiar Value Select in a system.

P.S mpjesse I salute you for putting up with people like this and staying civil :wink: At least you recognise that jumping on the M$ bashing bandwagon is not cool unless it's justified.