Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Erroneus ROW number DDR3 RAM 2-ch reading
#1
Hi!
So I used to update your program to vers 4.00.xx (latest) and I opened the program and i observed that om Memory parameters in tree are only ROW 1, 2, 3 is missing ROW 0 despite my system reports 4 DDR3 ram slots occupied with each 2GB DDR3 2-ch Muskin Radioactive Frosty-Bite at 1600Mhz in SMBIOS DMI > Memory Devices branch of HWiNFO tree all slots from 0 to 4 appear occupied and running, Windows 7 64birs SP1 reports 8GB ram, Piriform Speccy reports also 4 slots of ram all running an occupied, AIDA64 also having trouble seeing all 4 row's in their three Motherboard >SPD so whats happening on another computer your program same vers. also 8GB DDR2 1066Mhz 2-ch Corsair Dominator are visible all 4 row's from 0 to 4 ???? My system is an AMD Phenom II x4 965 BE, MB Gigabyte GA-770TA-UD3, bios v.4b (latest) ????
Reply
#2
I need additional information to check this problem.
Please see this about submitting a bug report: http://www.hwinfo.com/forum/Thread-IMPOR...g-a-report
Reply
#3
I attach some *'.jpg's     ,     with print-screens of the situation in that PC (pointed with red arrows in files) in comparison with *.jpg's     ,     archive of a 2nd PC where HWiNFO shows the situation correctly 4row's instead 3row's as in first PC ???
Reply
#4
Thanks for the images. But I need the HWiNFO Debug File as mentioned in the post above.
Reply
#5
Hallo. Habe genau das gleiche Problem. Nach dem "Energiesparmodus" abgestürzt, wurde ein RAM nicht mehr erkannt.
Wenn ich die RAM vertausche, wird immer der der nicht mehr angezeigt wird, auch in einem anderen Steckplatz nicht erkannt.
Wenn man den RAM mit einem neuen ersetzt, werden wieder alle vier angezeigt?
(Row0-Row3).


Attached Files Thumbnail(s)
   

.dbg   HWiNFO32.DBG (Size: 646.59 KB / Downloads: 1)
Reply
#6
First, please post all communication in English language, so all users can understand it.
Indeed, it seems that the 1st memory module in your system is not properly read out, especially its identification.
Does the same happen, even after a complete power off and reboot ? I assume yes, since you say you have exchanged the module position.
Do other tools (like CPU-Z for example) not show this module as well ?
Reply
#7
(11-22-2013, 10:28 AM)Martin Wrote: First, please post all communication in English language, so all users can understand it.
Indeed, it seems that the 1st memory module in your system is not properly read out, especially its identification.
Does the same happen, even after a complete power off and reboot ? I assume yes, since you say you have exchanged the module position.
Do other tools (like CPU-Z for example) not show this module as well ?

I have the same Probleme. After grash for "SuspendMode" not Show One RAM Modul? In CPU-Z Show all Moduls 1-4 see Pictures. Excuse me , my english is not good.

This is in HWinf32 and HWiNFO64.


Attached Files Thumbnail(s)
               
Reply
#8
In CPU-Z, please click the "Tools" button on the bottom of window, then "Save Report as .TXT". Please attach the file here.
Reply
#9
(11-22-2013, 10:55 AM)Martin Wrote: In CPU-Z, please click the "Tools" button on the bottom of window, then "Save Report as .TXT". Please attach the file here.

Here the file.
Thank you

PS.: Change the Module with a new other Module then Display all Modules. I have Change the Modules 6* in shop. This is not good. The think i am silly.


Attached Files
.txt   ULTIMATE.txt (Size: 105.87 KB / Downloads: 1)
Reply
#10
CPU-Z also sees this erratic information in that module, though it seems to ignore it. HWiNFO is more strict.
Reply
#11
(11-22-2013, 11:21 AM)Martin Wrote: CPU-Z also sees this erratic information in that module, though it seems to ignore it. HWiNFO is more strict.

Why is this? after grash from suspendmode? a new modul is OK? a new modul indicates HWiNFO correct.

Thank You
Michael
Reply
#12
I can't tell you exactly how that happened, but it might be related to what you say. I seems a part (only 1 byte) of the module configuration data was lost. Though it's not a critical data part, depends mostly on how the BIOS is sensitive about this. If your BIOS and system recognizes this module and uses it, all should be well. If there are issues, you might want to RMA this module.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)