Asus P5E3 deluxe

mididoc

Well-Known Member
Hi,

we have a Asus P5E3 deluxe.

1) in sensors the 4th chassis fan is not listed.

2) the manufacturer and device name of our rams is not displayed.

3) the voltage of the ram is not displayed

4) the motherboard slots are complete false
hw says: 2xPCI, 5xPCI Express x1, 1xPCI Express x4, 1xPCI Express x16
we have: 2xPCI, 2xPCI Express x1, 1xPCI Express x4, 2xPCI Express x16

5) is there a way to pass this dialog at program start promting for "RUN" ?

thanks for assistance

M.T.R

;)
 

mididoc

Well-Known Member
hi martin,

thanx for answering.

btw. point 1: fan4 has been detected today by surprise.
so this is out of the head.

the listing of voltages, speeds, temps etc. is really impressing.
it's quite more listed all together than at the competing tools like hw monitor of cpuid.

here is the file you want attached.

;)
 

Martin

HWiNFO Author
Staff member
Thanks for the additional data.
2) I see the modules report a part number (OCZ3G16002G), and I think this is displayed in HWiNFO64. Can you please attach the Report File too so I can see if it's really not reported?
3) You mean the nominal voltage per specification, or the measured voltage in Sensors? I don't think your mainboard is capable of monitoring the DRAM voltage. Is there any other tool or the BIOS reporting it?
4) That's what the system reports as available slots..
5) Put/change "ShowRegDialog=0" into the HWiNFO64.INI file in the last section [Settings]
 

mididoc

Well-Known Member
ok here it is

;)

4) That's what the system reports as available slots..
how can the system reports not existing slots?
this is a misreading.

see the attached picture:

5) Put/change "ShowRegDialog=0" into the HWiNFO64.INI file in the last section [Settings]
thanks for the tip, great.

btw
why does the main program not save window size?

the sensor page saves the size fine.



i don't see the ocz rams reported,
no manufacturer, no partnumber.


3) You mean the nominal voltage per specification, or the measured voltage in Sensors? I don't think your mainboard is capable of monitoring the DRAM voltage. Is there any other tool or the BIOS reporting it?
cpu-z reports the ram voltage.
if you report what cpu-z reports this is exellent.

see the attached picture.
 

mididoc

Well-Known Member
sorry about the ram readings,
stupid me.

:oops:

i was searching in motherboard memory ...
sometimes don't see the trees in the forest.

ok so this is resoved and also the voltage is visible.

the question is, which voltage is right.

are the 1.5 v the voltage setup in bios?
is this the rel voltage delivered? (measured)
or is this the voltage the ocz modul needs?

in fact the ocz would need 1.7 volt.

we do not know if the computer delivers the right voltage.

thanks for a tip.

;)
 

mididoc

Well-Known Member
concerning the slots:

they are RIGHT displayed in: SM BIOS/System Slots

see attached picture




but they are wrong listed in: Motherboard

Motherboard Slots: 2xPCI, 5xPCI Express x1, 1xPCI Express x4, 1xPCI Express x16
 

Martin

HWiNFO Author
Staff member
The 1.5V DRAM voltage in the memory section (JEDEC/SPD) is just what the module reports that it needs/supports.
Real DRAM voltage monitoring should be visible in the Sensors, but your mainboard doesn't support measuring of this rail.

The slots reported come from enumerating the complete PCI bus and sometimes might not be absolutely correct. I'll check to see how this can be fixed..
 

mididoc

Well-Known Member
The 1.5V DRAM voltage in the memory section (JEDEC/SPD) is just what the module reports that it needs/supports.
Real DRAM voltage monitoring should be visible in the Sensors, but your mainboard doesn't support measuring of this rail.

The slots reported come from enumerating the complete PCI bus and sometimes might not be absolutely correct. I'll check to see how this can be fixed..
the ocz modules report 1.5V DRAM voltage although they need 1.7 DRAM voltage, this is written on.
strange though.

anyway we will go corsair.

yeah with the slots should be repaired.

btw.
first time i complained, that fan 4 is not reported.
next time run it was reported for surprise.
today it is not reported anymore.

do you have an idea?
is there a way to update, say rescan?
or what could be the problem?

this program is great.

what is On Semi ADP4000 listed in sensors?

picture attached.
 

Martin

HWiNFO Author
Staff member
As I already said, the ADP4000 is misidentified here and thus all the values reported are invalid. I'll remove it in the next build.
As for the 4th fan, is it possible that it's stalled?
 

mididoc

Well-Known Member
As for the 4th fan, is it possible that it's stalled?
the 4th fan is new and works fine (12cm papst)

sometimes it's listed, sometimes not.
in speed fan 4.43 it's always listed.
 

Martin

HWiNFO Author
Staff member
Are you running any other monitoring tool concurrently with HWiNFO? If yes, please close the other tool(s) to see if that changes the situation.
 

mididoc

Well-Known Member
Martin said:
Are you running any other monitoring tool concurrently with HWiNFO? If yes, please close the other tool(s) to see if that changes the situation.
of course not.

if i monitor HWiNFO64 there is nothing else active.

;)
 

Martin

HWiNFO Author
Staff member
What's the original name of the 4th fan reported by HWiNFO ? Chassis4 or Chassis2 ?
Can you please attach a Debug File when you launch sensors and that fan is not present ?
 

Martin

HWiNFO Author
Staff member
Thanks. Please try the following:
Do a reboot or shutdown, then run the current version of HWiNFO64 that you have if you see the fan. If not, run SpeedFan, close it and then try HWiNFO64 again if the fan appears. I think that SpeedFan might reconfigure the fan controller to proper settings which are not used by default. Let me know about the results..

As the second step, here's a new build of HWiNFO64 which tries to reconfigure the fans too:
<!-- w --><a class="postlink" href="http://www.hwinfo.com/beta/hw64_382_1318.zip">www.hwinfo.com/beta/hw64_382_1318.zip</a><!-- w -->
If the first test has proven SpeedFan to be correctly reconfiguring fans, then I assume this new HWiNFO64 build should do the same (test after reboot).
 

mididoc

Well-Known Member
ok,
I
reboot
run HWiNFO64
Chassis4 is not visible
run speedfan
run HWiNFO64
Chassis4 is visible

install new built 1318

reboot
run HWiNFO64
Chassis4 is visible
run speedfan
run HWiNFO64
Chassis4 is visible

great.
let see if it rests like this.

btw
does HWiNFO64 display anywhere the actual cpu multiplier?
did not find it yet.



;)
 

Martin

HWiNFO Author
Staff member
Ok, so that proves my assumption.
What about the new build of HWiNFO64, does it work now after reboot (without running SpeedFan) ?
 
Top