HWInfo showing over temp on RAM

[Kez]

Just a heads up to anyone running the latest bios that supports AGESA 1.0.8.0 (7D69v1B1)

Keep an eye on your memory/motherboard sensors.

I decided to update to this bios version this morning and since my new memory had just arrived I installed it right after the bios update.
I began noticing the memory was pulling a lot of power (Almost 4V to everything, even on the 1.8V and 1.0V) and pulling almost 32W of power and the temperature sky rocketing to almost 3,600C before my PC began acting crazy.

At first I assumed the memory was faulty but then I swapped it out for my old kit and noticed the exact same thing happening and while doing that I noticed that some of my motherboard sensors were reading 160C+

After this I decided to flash 7D69v19 and it appears to have immediately fixed the issue, so for anyone running that bios I'd advice you keep an eye on your components via HWInfo

I'm still kind of worried though because since this happening some of my sensors on my motherboard aren't even working now and I am wondering whether it's damaged anything or if it was simply just an incorrect reading.

Unsure if others have had/are having this issue and I have no clue where to report it so I'm just posting it here..

 

[Kez]

With EXPO and default BIOS settings? I am using the BIOS 7D70v18, and after leave SoC to 1.25V, everything its ok (1 week, gaming, virtualizing, etc), but without EXPO the system was stable in my testing of the last week.

EXPO Enabled and pretty much default bios, the only things I ever change in bios is disabling my iGPU and then I enable Wake up via USB so that I get continuous power via USB to charge my mouse/keyboard over night and then I also disable MSI's auto installer stuff.

Memory was basically fine and was showing the correct voltages but as I watched in HWInfo I keep constantly seeing the voltages spike massively and along with the massive spikes came big heat increases before eventually just killing itself, lasted maybe ~5 minutes at most.

Since flashing 7D69v19 it appears to be fine.

I suspected it was faulty memory but I went back and reinstalled my old memory and it did exactly the same thing the only reason I even suspected the bios is because I also seen the motherboard sensors sky rocketing along side it but I didn't get a chance to check the actual motherboard sensors but I do kind of remember it saying that the CPU Socket was at 160C and I think I also seen the chipset at 160C, I didn't get much chance to actually check and as soon as I seen those numbers I immediately flashed back to a different bios and it all seems fine now but some of my motherboard sensors don't appear to be reporting at all now.

I just don't know if it was purely a visual issue (Once the memory failed iCue also failed and began showing the memory sensors as nothing) or if it's actually hit those temperatures
I kind of want to say it's probably visual because Memory hitting almost 3600C would be insane.. that's like above the melting point of titanium but I'm guessing it's more of a spike because as soon as the temps sky rocket it just died and then restarting resulted in it working again (sometimes) until it decided to happen again.

Safe to say I ain't running that bios again anytime soon lol

Here are the dimms on 7D69v19 after running for ~15 minutes

(If you compare with the previous image you can see that the Minimum sensors are basically the same as the min/max of above, because at first it was running fine and then as you can see by max sensors in the previous image it would slowly spike before killing itself)

 

[Alan J T]

Just a heads up to anyone running the latest bios that supports AGESA 1.0.8.0 (7D69v1B1)

Keep an eye on your memory/motherboard sensors.

I decided to update to this bios version this morning and since my new memory had just arrived I installed it right after the bios update.
I began noticing the memory was pulling a lot of power (Almost 4V to everything, even on the 1.8V and 1.0V) and pulling almost 32W of power and the temperature sky rocketing to almost 3,600C before my PC began acting crazy.

At first I assumed the memory was faulty but then I swapped it out for my old kit and noticed the exact same thing happening and while doing that I noticed that some of my motherboard sensors were reading 160C+

After this I decided to flash 7D69v19 and it appears to have immediately fixed the issue, so for anyone running that bios I'd advice you keep an eye on your components via HWInfo

I'm still kind of worried though because since this happening some of my sensors on my motherboard aren't even working now and I am wondering whether it's damaged anything or if it was simply just an incorrect reading.

Unsure if others have had/are having this issue and I have no clue where to report it so I'm just posting it here..

List all your hardware and Photos of the Memory modules Sticker, please See the posting guide
Will pass this on to our Contact on the odd chance it is hardware related conflict so please include part numbers if possible
>>Posting Guide<<

 

[Kez]

Board: MSI MEG X670E ACE
BIOS: 7D69v19 (Currently) - 7D69v1B1 (Causes the issues)
VGA: Asus Radeon RX 6650 XT ROG Strix OC 8GB
PSU: Seasonic VERTEX GX-1200 1200W
CPU: Ryzen 9 7950X3D
MEM: DOMINATOR® TITANIUM RGB 32GB (2x16GB) DDR5 DRAM 6000MT/s CL30 (CMP32GX5M2B6000Z30)
HDD/SSD: 1x 1TB Samsung 990 Pro, 2x 1TB Samsung 980, 1x 500GB Crucial P5 Plus
COOLER: Corsair H170i Elite LCD
Keyboard: Razer Blackwidow V3 Pro
Mouse: Razer Basilisk Ultimate
OC: None
OS: Windows 11 Pro
Display: 1x MSI Optix G272 & 1x LG UltraGear 27GP850
- Is it a TV?: [No]
- How display is connected to the GPU?: [DP]

I don't believe it has a serial number to protect sooo..

Edit:

Here are my other memory too which had the exact same issue -DOMINATOR® PLATINUM RGB 32GB (2x16GB) DDR5 DRAM 6000MT/s C30 (CMT32GX5M2B6000Z30K)

 

[Alan J T]

Board: MSI MEG X670E ACE
BIOS: 7D69v19 (Currently) - 7D69v1B1 (Causes the issues)
VGA: Asus Radeon RX 6650 XT ROG Strix OC 8GB
PSU: Seasonic VERTEX GX-1200 1200W
CPU: Ryzen 9 7950X3D
MEM: DOMINATOR® TITANIUM RGB 32GB (2x16GB) DDR5 DRAM 6000MT/s CL30 (CMP32GX5M2B6000Z30)
HDD/SSD: 1x 1TB Samsung 990 Pro, 2x 1TB Samsung 980, 1x 500GB Crucial P5 Plus
COOLER: Corsair H170i Elite LCD
Keyboard: Razer Blackwidow V3 Pro
Mouse: Razer Basilisk Ultimate
OC: None
OS: Windows 11 Pro
Display: 1x MSI Optix G272 & 1x LG UltraGear 27GP850
- Is it a TV?: [No]
- How display is connected to the GPU?: [DP]

I don't believe it has a serial number to protect sooo..
View attachment 179760


Edit:

Here are my other memory too which had the exact same issue -DOMINATOR® PLATINUM RGB 32GB (2x16GB) DDR5 DRAM 6000MT/s C30 (CMT32GX5M2B6000Z30K)
View attachment 179759

Serials covered the first four digits of are manufacture year and the Week and the rest is the serial number

 

[Kez]

Serials covered the first four digits of are manufacture year and the Week and the rest is the serial number

Ah I see, well thanks for covering them haha (Although they're probably publicly on imgur now anyway)

Edit: Nevermind, I put in a deletion request to Imgur, all guuud.

 

[vilius15ed02ee]

Just a heads up to anyone running the latest bios that supports AGESA 1.0.8.0 (7D69v1B1)

Keep an eye on your memory/motherboard sensors.

I decided to update to this bios version this morning and since my new memory had just arrived I installed it right after the bios update.
I began noticing the memory was pulling a lot of power (Almost 4V to everything, even on the 1.8V and 1.0V) and pulling almost 32W of power and the temperature sky rocketing to almost 3,600C before my PC began acting crazy.

At first I assumed the memory was faulty but then I swapped it out for my old kit and noticed the exact same thing happening and while doing that I noticed that some of my motherboard sensors were reading 160C+

After this I decided to flash 7D69v19 and it appears to have immediately fixed the issue, so for anyone running that bios I'd advice you keep an eye on your components via HWInfo

I'm still kind of worried though because since this happening some of my sensors on my motherboard aren't even working now and I am wondering whether it's damaged anything or if it was simply just an incorrect reading.

Unsure if others have had/are having this issue and I have no clue where to report it so I'm just posting it here..

Hi, same thing- X670E ACE MOBO, 7D69v1B1 BIOS running for a couple of days. After I have read your post - noticed the same thing in HWinfo! I am thinking that this is definitely a readout error, as I am not sure that my pc would have survived for 3 days with such readings? Almost 3600 degrees C, lol... anyway, rolling back to the previous BIOS right now. Anyone else have the same problem?

 

[Alan J T]

Hi, same thing- X670E ACE MOBO, 7D69v1B1 BIOS running for a couple of days. After I have read your post - noticed the same thing in HWinfo! I am thinking that this is definitely a readout error, as I am not sure that my pc would have survived for 3 days with such readings? Almost 3600 degrees C, lol... anyway, rolling back to the previous BIOS right now. Anyone else have the same problem?

Can you list your full build, please
>>Posting Guide<<

 

[vilius15ed02ee]

Can you list your full build, please
>>Posting Guide<<

Board: MSI MEG X670E ACE
BIOS: 7D69v19 (Currently) - 7D69v1B1 (Causes the issues)
VGA: Gigabyte Aorus Master 4090
PSU: Seasonic VERTEX GX-1200 1200W
CPU: AMD 7800X3D
MEM: Trident Z5 Neo RGB DDR5-6000 CL30-40-40-96 1.40V 64GB (2x32GB) AMD EXPO (F5-6000J3040G32GX2-TZ5NR)
HDD/SSD: 2x WD_BLACK SN850X NVMe SSD 4TB
COOLER: iCUE H150i ELITE LCD XT Display Liquid CPU Cooler
Keyboard: Corsair K95
Mouse: Logitech G903 HERO
OC: None
OS: Windows 11 Pro
Display: 1x AW3821DW
- Is it a TV?: [No]
- How display is connected to the GPU?: [DP]

 

[vilius15ed02ee]

Got any ideas, Alan?

 

[Alan J T]

Got any ideas, Alan?

Nope have sent it to our contact for a look but likely just a bug that needs to be fixed

 

[jonggg2163b02f4]

Hey all!

Recently got a new setup, which includes the MPG B650 Edge, G.Skill Trident Z5 Neo RGB 64GB (2 x 32GB) DDR5-6000 CL30, and Ryzen 7 7800X3D.

Been having an issue where HWInfo shows the RAM very shortly spiking in voltage and temperature. Insane numbers like 3.8V+ and 3,500+ Celsius. I've only ever found it to be happening to this one stick. It is extremely brief and random as far as I can tell. Nearly all the rest of the time the voltages and temps look to be normal even when under load. Should I be concerned about this or could it just be false readings? I imagine if this was real, my system would be crashing?

Maybe it's unrelated, but with this same stick, I would have an issue where the LED would turn off when MSI Center started up during the Windows boot. However, I could go in and apply the RGB again and the LED would turn on to what I set. I just bring it up because it seems maybe more than coincidental that this same stick is being weird in other ways.

 

[Alan J T]

Hey all!

Recently got a new setup, which includes the MPG B650 Edge, G.Skill Trident Z5 Neo RGB 64GB (2 x 32GB) DDR5-6000 CL30, and Ryzen 7 7800X3D.

Been having an issue where HWInfo shows the RAM very shortly spiking in voltage and temperature. Insane numbers like 3.8V+ and 3,500+ Celsius. I've only ever found it to be happening to this one stick. It is extremely brief and random as far as I can tell. Nearly all the rest of the time the voltages and temps look to be normal even when under load. Should I be concerned about this or could it just be false readings? I imagine if this was real, my system would be crashing?

Maybe it's unrelated, but with this same stick, I would have an issue where the LED would turn off when MSI Center started up during the Windows boot. However, I could go in and apply the RGB again and the LED would turn on to what I set. I just bring it up because it seems maybe more than coincidental that this same stick is being weird in other ways.

Starting to look like a BIOS BUG or it is HWInfo that is at fault MSI has been made aware of this and I will include your info once you supply full system details as per the Posting guide please see the link below


>>Posting Guide<<

 

[jonklevje165102ee]

I got the same bug x670 ACE, 7800x3D, F5-6000J3038F16GX2-FX5 and latest bios

Readings for ddr temp and voltages are all over the place and then Hwinfo loses connection to the sensors and stops reporting, eventually the dimms disappear from hwinfo.

It’s a reporting bug for sure, as hwinfo also shows 3600v being showed into the dimms…which deff. isn’t happening with out some sparks

But it is super annoying as I can’t really keep am eye on temps or voltages

Also ddr high voltage mode keeps resetting for ever boot, so I need to enter bios everytime the pc is restarted, and if I forget to set it while in bios pc crashes and I need to preform a clear cmos and set up everthing from scratch….suuuuuuuper annoying and this shouldn’t happen on any mobo….let alone on a 700 usd mobo

 

[Alan J T]

@Kez
@jonklevje165102ee
@jonggg2163b02f4
@vilius15ed02ee
I need a bit more info MSI is unable to replicate the problem
Can you submit a HWInfo Log report, please

See below on how to do a bug report with HWInfo

IMPORTANT - Read this before submitting a report

In order to submit a bug report, please include the following information: HWiNFO32/64 Report File (HTM or TXT preferred) HWiNFO32/64 Debug File (HWiNFO32.DBG or HWiNFO64.DBG) In case the application crashes or you are not able to create a Report File, please submit only the Debug File. This...

www.hwinfo.com

In order to submit a bug report, please include the following information:

1. HWiNFO32/64 Report File (HTM or TXT preferred)
2. HWiNFO32/64 Debug File (HWiNFO32.DBG or HWiNFO64.DBG)

In case the application crashes or you are not able to create a Report File, please submit only the Debug File. This will help to find the reason of crash.
In order to create the Debug File, HWiNFO32/64 needs to be run in Debug Mode. This can be enabled: right after starting HWiNFO32/64 click the Settings button and navigate to the "Safety" tab.

Then continue with the scan process. After the scan is finished, please close the application (in case of a crash or freeze, reboot the system).
You can find the Debug File in the HWiNFO32 installation folder, the filename is: HWiNFO32.DBG (on HWiNFO32) or HWiNFO64.DBG (on HWiNFO64)

Note:

• Running HWiNFO32/64 in Debug Mode might be considerably slower than in normal mode (especially running from a flash drive or certain sensor scanning).
• In case you would like to report an issue with sensors, please don't forget to open the Sensor window prior to creating the Report File and closing application.
• If you experience a system crash, hang or BSOD, make sure that the "Debug Write Direct" option is enabled too, otherwise the resulting DBG file might not contain all information.
• If the welcome screen of HWiNFO is disabled, so it's not possible to reach the Settings screen, Debug Mode can be enabled by editing the HWiNFO32.INI or HWiNFO64.INI and changing "DebugMode=0" to "DebugMode=1".

 

[jonklevje165102ee]

I’ll create a report when Im back home on Friday

 

[pnrxtx]

same thing with spd sensor, vdd, vddq reading errors in 1.0.8.0.

b650 tomahawk
2x16gb f56000j3038f16g
I did report this in ticket to msi and in my post here.
Flashed to previous stable bios which dont have this sensor reading errors.
In bios voltage readings are correct.

edit: i saw today new 1.0.9.0 agesa bios up for this board. Not tested yet.

 

[Kez]

@Kez
@jonklevje165102ee
@jonggg2163b02f4
@vilius15ed02ee
I need a bit more info MSI is unable to replicate the problem
Can you submit a HWInfo Log report, please

See below on how to do a bug report with HWInfo

IMPORTANT - Read this before submitting a report

In order to submit a bug report, please include the following information: HWiNFO32/64 Report File (HTM or TXT preferred) HWiNFO32/64 Debug File (HWiNFO32.DBG or HWiNFO64.DBG) In case the application crashes or you are not able to create a Report File, please submit only the Debug File. This...

www.hwinfo.com

In order to submit a bug report, please include the following information:

1. HWiNFO32/64 Report File (HTM or TXT preferred)
2. HWiNFO32/64 Debug File (HWiNFO32.DBG or HWiNFO64.DBG)

In case the application crashes or you are not able to create a Report File, please submit only the Debug File. This will help to find the reason of crash.
In order to create the Debug File, HWiNFO32/64 needs to be run in Debug Mode. This can be enabled: right after starting HWiNFO32/64 click the Settings button and navigate to the "Safety" tab.

Then continue with the scan process. After the scan is finished, please close the application (in case of a crash or freeze, reboot the system).
You can find the Debug File in the HWiNFO32 installation folder, the filename is: HWiNFO32.DBG (on HWiNFO32) or HWiNFO64.DBG (on HWiNFO64)

Note:

• Running HWiNFO32/64 in Debug Mode might be considerably slower than in normal mode (especially running from a flash drive or certain sensor scanning).
• In case you would like to report an issue with sensors, please don't forget to open the Sensor window prior to creating the Report File and closing application.
• If you experience a system crash, hang or BSOD, make sure that the "Debug Write Direct" option is enabled too, otherwise the resulting DBG file might not contain all information.
• If the welcome screen of HWiNFO is disabled, so it's not possible to reach the Settings screen, Debug Mode can be enabled by editing the HWiNFO32.INI or HWiNFO64.INI and changing "DebugMode=0" to "DebugMode=1".

I'm currently not running that bios but I guess if no one else posts logs I'll try flash it and do it when I get some time

Edit: I also don't believe I mentioned but it doesn't appear to just be a read out issue.

iCUE eventually starts detecting issues with the memory too and starts erroring within the app and flashing the memory modules showing there is an error (typically white or red - I experienced white) and the memory eventually completely locks down and iCUE can no longer detect it at all, obviously reverting back to the previous bios fixed all these issues and I've had zero issues with my memory since

Edit #2: Had time so decided to do it anyway.. unsure how to create a HTM/TXT "Report File" so I enabled logging which is a CSV file..?

It's too large to upload direct to the forums so here is a link to google drive.. hopefully it works - https://drive.google.com/file/d/1XfdMl3zXHyGEtkBQzbW3jrgSCObVcTVs/view?usp=sharing

May be worth noting as well along with the Memory Sensors getting killed off the chipset 1 (xHCI) sensor does too it seems? It grays out like the memory only difference is restarting HWInfo results in it being detected again and immediately grays out while the memory is no longer detected at all

I'm swapping back to my old bios now.

 

[Alan J T]

I'm currently not running that bios but I guess if no one else posts logs I'll try flash it and do it when I get some time

Edit: I also don't believe I mentioned but it doesn't appear to just be a read out issue.

iCUE eventually starts detecting issues with the memory too and starts erroring within the app and flashing the memory modules showing there is an error (typically white or red - I experienced white) and the memory eventually completely locks down and iCUE can no longer detect it at all, obviously reverting back to the previous bios fixed all these issues and I've had zero issues with my memory since

Edit #2: Had time so decided to do it anyway.. unsure how to create a HTM/TXT "Report File" so I enabled logging which is a CSV file..?

It's too large to upload direct to the forums so here is a link to google drive.. hopefully it works - https://drive.google.com/file/d/1XfdMl3zXHyGEtkBQzbW3jrgSCObVcTVs/view?usp=sharing

May be worth noting as well along with the Memory Sensors getting killed off the chipset 1 (xHCI) sensor does too it seems? It grays out like the memory only difference is restarting HWInfo results in it being detected again and immediately grays out while the memory is no longer detected at all

I'm swapping back to my old bios now.

Thanks will grab the log and email it contact

 

[lionfire]

I have the same issue with CPUid and HWmonitor.
MSI B650 Tomahawk Wifi, 7950x3d with Viper Patriot Memory 6000MHz 40-40-40-86
CPUid shows wrong memory info and HWmonitor shows temps around 255 degrees Celsius!!!!!!!!!!
I have opened a ticket with MSI and they told me that the problem is with the program and not with the bios.

As we can see here, this is not correct. Also with the latest bios, 7D75v1A , it is still the same wrong info.

I am one step before i sell everything and go intel. Very pissed since March i bought the system.