kaka Software

As we wave linux, said to share my last “experience” with Windows XP.
A little background: my computer was until recently with a modest 384MB RAM. It was divided into two modules - one 128MB DDR333, and the other 256MB DDR400. I decided to add another module - 256MB DDR400.
It was no designer - and the other 256. Only this is 128MB of Spectec. So, I bought it and put the last remaining free DIMM slot. I put my PC-to. YES! Launched first time … ups, mistake. At present, which would make login screen XP, I rejoice with a blue screen with error message “PAGE_FAULT_IN_NONPAGED_AREA”. “Well - you yell, I am not sure it set right. But unfortunately after place, the result was the same again. Unsettle the three modules in different slots - zip. Each sample separately - work without error. Sample each in combination with any of the other two - yet their work. Only when the three together had a blue screen. There is no mention that the majority of blue screens that make Windows, receive and errors in MFT any of the units most often BOOT drive, and after any such error had to walk into Recovery console of XP to handle them alone calculate … How long does it take the whole experiment. But this is not important.
Anyway - is that the truce will get 128-itsata so at least I have working 512MB.
But before you pull out, I decided to see how Linux will react to it. I am a fan of minimalizma, Slax Linux use in live-install version (on that later). Sistemata launched into Slax, and a miracle! Welcomed me Console login (and should). root, ******, and hop inside us. startx and runner - I started dekstopa (Xfce). Tsak, tsak, I started and 3D environment (Beryl). Everything worked. poraztsakah little - file manager, etc. … Several times bipkaniya heard from PC-speaker-a, meaning that there was still kernel errors (in dmesg | tail came that there). But the system worked. Even put a game under Wine - quite starichkata Shadowman (because no other handy at the moment). Left. I thought that’s enough, and left to leave the X session. Only then hang the system and had to restart.

Or briefly:
Windows a conflict between memory modules:
blue screen at startup fucking a file system boot partition

Linux a conflict between memory modules:
work their places are 3D environment, games and occasionally bipka error, and thrust down leaving the system

Appendix: Memory healthy. All three modules. Test them with memtest86 , and under normal frequencies and taymingi (ie without ovarklokl) no one module gave no errors.

The findings leave you.