motherboard revival? suitable for Win 7?

Did you extract all the file from the zip file into one older of its own? It has config settings that are needed for the app to run. Then Right click the .exe file and choose Run as Admin.

Odd, will it run on your Win 7 machine?

Hmm. it may be a compatibility issue. Try Speccy - System Information - Free Download I used it on XP before.

EDIT: The Hardware monitor says it is for XP and all x86 systems

The free Open Hardware Monitor software runs on 32-bit and 64-bit Microsoft Windows XP / Vista / 7 and any x86 based Linux operating systems without installation.

Is this your motherboard: Asus M2N68-AM
If it is you can download the manual from there.

gemini2010 said:

Dave,
I think this is the information I needed to acccess?

CPU Ratio and Voltage:

• Processor Frequency Multiplier [Auto]
  (Options are Auto or x8.0 1600Mhz through to x13.0 2600Mhz)
• Processor Voltage [Standard]
  (Options are Power Saving Mode, Standard, +50mv, +100mv)

Memory Timing and Voltage:

• Memory Clock Mode [Auto]
  (Options are Auto or Manual)
• DRAM Timing Mode [Auto]
  (Options are Auto or DCT 0)
• Memory Over Voltage [Auto]
  (Options are *Min = 1.85000V, Max = 2.24375V, Standard = 1.8500V, Increment = 0.00625V)

Chipset Voltage:

• Chipset Voltage [Auto]
  (Options are Auto, +50mv, +100mv, +150mv)

These are the right place to adjust the DRAM and Chipset voltages. Page 2-8 in your motherboard manual.

Memory Over Voltage [Auto]
(Options are *Min = 1.85000V, Max = 2.24375V, Standard = 1.8500V, Increment = 0.00625V)

Set to 'Manual' and change the DRAM voltage to 1.950v.

Chipset Voltage [Auto]
(Options are Auto, +50mv, +100mv, +150mv)

Set to 'Manual' and change the Chipset voltage +100mv.

Post the voltage of the chipset, after the increase.

With the 'Bad' RAM installed, run memtest86+ again, for 7 full passes.
If you get any errors, stop the test and let us know the results.

Let us know if you have any questions.


Are you installing the hardware monitoring apps with the good or bad RAM installed?
You might need to try it with the good RAM installed.
We need to know the CPU temps, as this could be the cause of the problems.

Britton30 said:

Yes, you can't get Core temp directly, it uses some flaky installer and will add toolbars and other crapware if you're not on your toes.

Not entirely true. It is possible to download CoreTemp directly. Instead of clicking on the main download (currently Core Temp 1.0 RC3), click on More downloads... instead. Here you can download a standalone 32-bit or 64-bit version, plus language packs. Click on the appropriate version, either 32 Bit or 64 Bit, to download it. Once downloaded, extract the contents of the zip file/folder. Core Temp may now be run directly from the extracted folder. It does not require installation.

Dwarf said:

Britton30 said:

Yes, you can't get Core temp directly, it uses some flaky installer and will add toolbars and other crapware if you're not on your toes.

Not entirely true. It is possible to download CoreTemp directly. Instead of clicking on the main download (currently Core Temp 1.0 RC3), click on More downloads... instead. Here you can download a standalone 32-bit or 64-bit version, plus language packs. Click on the appropriate version, either 32 Bit or 64 Bit, to download it. Once downloaded, extract the contents of the zip file/folder. Core Temp may now be run directly from the extracted folder. It does not require installation.

Thanks Guy! I saw no More Downloads on the page I linked to, just Download, but indeed that worked with no finessing around bumware.

Set to 'Manual' and change the DRAM voltage to 1.950v
Set to 'Manual' and change the Chipset voltage +100mv

Hi Dave, thanks for the post,
That is my motherboard yes.
I adjusted the setting in the BIOS as described above, but as soon as I booted with the bad RAM I got blue screen error flash up briefly followed by a restart.

EDIT - I've been trying the hardware monitoring apps with the good RAM

Dwarf,
Thanks for that, I did quickly view that section, I'll go back and look a little more carefully for it.