[ftsteven]

I bought gigabyte GA-MA78G-DS3HP with AMD 5200+ 6 mouth ago and kept running everest when start up,then the problem came:

the computer will self crash after starting windows,maybe after 5 hours,maybe just 5 minutes.

I've try many ways like changing the bios setting or closing the windows power managment,even changing the memery, the power and the mainboard,the problem still could not be solve.

but one day I closed the everest after booting up,the problem did not appear again!

I try to keet running everest on another computer,unika U690GM with AMD 3800+,the problem comes again.

Is there some one have the same problem like me?

[Fiery]

1) What version of EVEREST are you using?

2) Are you running any hardware monitoring, overclocking or tweaking utilities in the background? E.g. SpeedFan, EasyTune6, Rivatuner, ATITool, HWMonitor?

3) Are you using Windows XP, Vista or Win7?

4) What video adapter do you have in the two computers you mentioned? Or they both use the onboard integrated video controller?


Thanks,
Fiery

[ftsteven]

1) What version of EVEREST are you using?

2) Are you running any hardware monitoring, overclocking or tweaking utilities in the background? E.g. SpeedFan, EasyTune6, Rivatuner, ATITool, HWMonitor?

3) Are you using Windows XP, Vista or Win7?

4) What video adapter do you have in the two computers you mentioned? Or they both use the onboard integrated video controller?


Thanks,
Fiery

1) I allways use EVEREST Ultimate Edition with EXE package,and I've try 5.00,5.01 and 5.02,all have the same problem.

2) I can sure I just running EVEREST,anyother software like core temp,SpeedFan is not installed.I only install AMD Catalyst Display Driver,the gigabyte one is 9.4,unika is 8.9.

Both BIOS is set to default,no overclocking software is installed.

3) both have XP SP3 with all patches.

4) both use the onboard integrated video controller.

What's more,I once though it may cause by Cool'n'Quiet,but same problem came even I disabled it on both computer.

Thanks for your reply.

[Fiery]

Thank you. Please try to run EVEREST, and disable the GPU part of the Hardware Monitoring module by right-clicking on the bottom status bar of EVEREST main window --> HWMon Modules --> GPU.

FYI, that setting is not remembered or saved, so if you restart EVEREST or restart Windows, you gotta disable it again.

Let me know if disabling the GPU layer solves the issue or not. If it's possible, please try it on both AMD chipset based systems you have.


Thanks,
Fiery

[ftsteven]

Thank you. Please try to run EVEREST, and disable the GPU part of the Hardware Monitoring module by right-clicking on the bottom status bar of EVEREST main window --> HWMon Modules --> GPU.

FYI, that setting is not remembered or saved, so if you restart EVEREST or restart Windows, you gotta disable it again.

Let me know if disabling the GPU layer solves the issue or not. If it's possible, please try it on both AMD chipset based systems you have.

Thanks,
Fiery

thanks for your attention,

Could you show me a photo where is the GPU settings and how to disable it?

EVEREST main window-->File-->Preferences-->HWMon,I did not find such setting named GPU.

I can find GPU in EVEREST main window-->Menu-->Display,but it just show me information on the graphics.

I can sure my gigabyte and unika mainboard both can not detect the GPU(north bridge) temperature.

here is the snapshot picture of HWMon settings

[Captain Face-Plant]

thanks for your attention,

Could you show me a photo where is the GPU settings and how to disable it?

EVEREST main window-->File-->Preferences-->HWMon,I did not find such setting named GPU.

I can find GPU in EVEREST main window-->Menu-->Display,but it just show me information on the graphics.

I can sure my gigabyte and unika mainboard both can not detect the GPU(north bridge) temperature.

here is the snapshot picture of HWMon settings

this is where you right-click:

 click.png (10.53K)
Number of downloads: 0

[Nils]

Hy,

I have the same problem. Two Mainbords with ATI chipset (MSI-K9A2 Platinum and MSI-KA780GM).
Another Notebook with Intel chipset (Mobile Intel Alviso-G i915GM) runs without problems.
I try the workaround above without any result.

Gruß

Nils

This post has been edited by Nils: 02 July 2009 - 07:01 AM

[Nils]

Hi,

are there any news about this problem?

[Fiery]

Nils, on 05 November 2009 - 12:20 AM, said:

Hi,

are there any news about this problem?

We've performed several test runs with different AMD chipset based motherboards, but couldn't reproduce the issue. However, it's always recommended to try the latest beta, maybe we "accidently" managed to fix the crash meanwhile

http://www.lavalys.c...s1dmyn4wcxr.zip

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.