ECS G31T-M7 motherboard RAM problems (get your RAM speeds right!)
I recently got an ECS G31T-M7 motherboard to replace a failed motherboard.
But when I try starting it, I just get a blank screen.
OK, it has an intel E1400 CPU, so I try a different CPU: same problem.
I change power supply: same problem.
I test both power supplies: they are ok.
Maybe the RAM… I replace the 1GB DDR2 with a stick of 512MB DDR2: same problem
I remove the RAM, and I get a series of beeps (motherboard is complaining about no RAM…
So I take it back to my supplier and ask for a refund.
They test it and it works!
Besides the embarrassment, I can’t see what went wrong.
Back at the office, I try again… with the same results!
Is my KVM switch failing? No (I try connecting directly to another monitor).
I try a third stick of 2GB DDR2 RAM… and now it works!
I look more carefully at the RAM I’m using, and I then realise the problem:
I was using some old DDR2-533Mhz RAM (which doesn’t work with this motherboard), while the newer 800Mhz RAM worked.
Another one of those “I’m an idiot” moments 🙁
I had a brain teaser this week as well. Customer has a laptop (small local office of a larger national company) with all of the corporate domain lockdown bells and whistles.
The parent company just rolled out a McAfee whole-drive encryption solution. Now the laptop shuts down cold just after system startup. Their corporate IT guys say there is no way that this is a software problem.
When I get the laptop, I did notice a LSASS error dialog on screen just a split second before the laptop dumps. I saw this a few times so I am sure it has something to do with software. A few google searches send me on the path of a SYSTEM registry hive problem. ok, so it could be software problem caused by bad memory. I replaced their memory with a spare stick I have and the problem persists.
I call their IT guy who links me to an ISO image of a McAfee rescue CD, and they give me the passwords and daily passcode which allows me to view the filesystem from a PE environment. I boot from this, and run a scandisk, but I don’t want to replace the registry with a backup hive since a bunch of software was just added.
Customer (and their IT guys) are reluctant to allow me to decrypt the drive and remove McAfee to see if the problem goes away.
So I insert another drive, and load XP-Pro with a bunch of apps that I think will slow the system down and tax the CPU. The system seems rock-solid.
Then I decided to REALLY tax the system (it is a 4 year old HP NC6220) and load Vista. Sure enough, the laptop just shuts down when Vista installer is decompressing files.
Pull the keyboard, and sure enough, the CPU heat sink had been re-entered at some point recently as I saw a fresh coating of cooling paste. I clean and repaste the heat sink, and reseat it.
Now I try to reload Vista again, and it proceeds much farther into the install.
I put the original HDD in, boot it, run as many apps as I can think of, and the system is now stable.
The lesson here is to be aware of recent changes that might have been a factor, but to stick to trying standard troubleshooting steps before moving on to the new stuff. Had this been a little old lady bringing her 7 year old gateway into the shop with the sane symtoms, I would have gone right to the CPU area and checked the fan / heat sink area.
That an interesting problem Pedro.
To stress a CPU, I use something called cpu burn-in.
On dual core systems, I run it twice, on quad cores, I run it 4 times.
It really stresses the cpu.
I use memtest for RAM, and the hyperspace screen saver (by Terry Welsh) for the video card.
The real problem of ur board is YOU!…. before u install make sure u read the manual of ur board to prevent any problems….. doing without knowing is the very BIG one problem
Hi Independent.
Thats right, the problem is me.
If I had to read the manual, then I’d end up charging $2000 to fix each computer…
Its a lot faster to assume that motherboards will work reasonably (and most do), and not have to worry about CPU types, RAM combinations, video and screen incompatibilities, etc, etc.
Shortcuts: we all take them, but some are more dangerous than others.