A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » General Hardware & Peripherals » General
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Getting there



 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #19  
Old March 8th 20, 01:28 AM posted to alt.comp.hardware
Norm Why[_2_]
external usenet poster
 
Posts: 114
Default Getting there

*******

You should be able to test the sticks, one stick at a time.
I do tests that way, so the test result ("which DIMM is bad")
is unambiguous.

The following is for "thoroughness of testing".

My favorite way to test, is two sticks in single channel mode,
so that the "upper stick" is 100% tested, while the "lower stick"
is 99% tested. You swap the two sticks and repeat the memtest
single pass, so that the stick now sitting in the high slot
gets 100% tested too. This is mainly for stuck-at faults, to make
sure any 640K reserved locations don't harbor bad RAM.

Don't forget proper etiquette when RAM testing. Power
off, wait 60 seconds (or until the green LED goes out),
before pulling the RAM sticks and pushing them in again.
That's to make sure there is no power in the slot.

*******

This is what I'm running at the moment. I used to have four
sticks of Kingston CAS6 (that failed). All I could find
at the time in a CAS5 was this stuff, so that's what is
in the machine at the moment. Four 2GB sticks. The
Northbridge is probably the flakiest part of the setup now.
I think I was pretty lucky to get this (I might have
asked at the computer store and they still had some). Usually
what happens, is after a memory generation is "Done", all
the CAS5 disappears and only some crappy CAS6 is left.
It's pretty hard to find fancy memory ten years after
the motherboard came out. By crappy, the Kingston I
bought ran abnormally hot, and the voltage wasn't
over stock. I even added a cooling fan over the
RAM just in case, for the Kingston stuff. The Corsair
right now is cooler and isn't scaring me on temps.

It doesn't look like it's still in circulation.

https://www.corsair.com/us/en/Catego...N2X4096-6400C5

Sometimes, the chipset is also a limitation. It's possible
the X48 can't run below CAS4. That's if you could find
some RAM that low. So eventually, the timing inside the
Northbridge doesn't allow "cranking CAS to zero". It has
a limit too (a minimum CAS value).

Paul
Thanks Paul. Upgraded to Q9650 CPU and renewed thermal compound on Intel
heat sink fan. As before, first memtest failed. Now running second
memtest. Samsung 4GB modules are cheap. Time to buy more from eBay for
total 16GB RAM memory.


Q9650 CPU works OK. When I set up the SSDs' SATA and power cables, I ran
into trouble. Win10 tried to boot. It failed because it did not find
GTX950 HDMI display driver, even though those drivers were enabled last
time Win10 booted. Win10 said the PCI VGA was not compatible with Win10.
I may have a troubleshooting CDROM somewhere. Still running Memtest.


This should not stop Windows 10.

Windows (as is traditional) has a built-in VESA driver. All video
cards have a standard legacy interface, which the Microsoft Basic
Display Adapter driver can see. The VESA style driver usually limits
the resolution to a safe value - this avoids lawsuits that happened
during the "non-multisync" era, where monitors were ruined
by OSes using too high a resolution setting. The companies have
never forgotten this, and to this day limit themselves to 1024x768
for example. And yes, a 4:3 resolution looks strange on a
16:9 monitor :-)

Is there more than one display device in the computer ? Would
the second display device be 1024x600 resolution ? There has
got to be some explanation for why the MBDA driver did not
cut in and bring up the system.

I can bring up Windows 10 with an FX5200 in the machine. And
the FX5200 doesn't have a Windows 10 driver.

Paul


Thanks Paul. BartPE is limited by lack of drivers. I think I should make a
bootable Win10 USB stick and use Win10 to update BIOS. Then maybe my copy of
Win10 on SSD will boot.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 02:46 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.