Motherboard shows wrong model in windows

[maxiwee]

I have a Z790M pg lightning d4 but windows detects it as a MSI H510M-A pro(MS-7D22). First thought would be that I just got scammed, but we have to keep a few things in mind; I bought it from a legit website(galaxus), it arrived in a real box, it looks exactly like the one the ASRock website and has all the feature from there, it had the ASRock bios installed and I even reflashed the one from the official website multiple times. Also I am using the official raid driver from the official ASRock website of my motherboard. My bios also says what's it supposed to be. Another thing I've already did was install basically all drivers from the motherboards official website. What could be the reason for this? How could I fix this?

In case it matters, here's my full pc config;
12700K
Z790M pg d4
4x8gb Corsair Vengeance LPX DDR4 3200
Arctic Liquid freezer III 240
KFA2 3060 12gb
be quiet! system power 10 550W
2x1tb crucial p3 as raid 0

If you need any other info's just ask and I'll try to provide them.

 

[Bill_Bright]

I have a Z790M pg lightning d4 but windows detects it as a MSI H510M-A pro(MS-7D22).

The brand and model number (and revision number) should be printed on the motherboard itself. What does it say?

 

[maxiwee]

says what its supposed to say

 

[Macro Device]

You wouldn't have been able to run a 12700K on an RKL motherboard. If your benchmarks results are about the same as the averages for your CPU/RAM/GPU then why do you even care. Just report the bug to Microsoft and call it a day.

 

[r00tcz]

Wouldn't be first time MSI botched up DMI or ACPI strings in their BIOS... or ASrock? Probably leftover from previous BIOS image build or some configuration file they used.
In general all these strings are completely freely editable in BIOS image, you can even change them if you really care about it. But it's just that, vendor string that doesn't affect anything else. It would be very hard to mistake H510 for Z790 board. hardware and feature wise.

 

[Marcus L]

Does it say this under system properties and device manager also? Have you tried any other apps like hwinfo? Definitely strange it's reporting as a completely different vendor board though if it's working fine then I wouldn't pay too much attention to it, could be hard to explain if you ever come to sell the system however, maybe a clean windows install if all else fails?

Maybe worth putting in a support ticket to Asrock

 

[Bill_Bright]

Why so quick to blame Microsoft?

I don't see this as Microsoft's fault here. CPU-Z shows it as an MSI too so this appears to be what the chipset is reporting.

says what its supposed to say

You mean the board says Z790 PG Lightning/D4?

Maybe try HWiNFO64 to verify and then I would contact ASRock to ask them. You can also run systeminfo from a command prompt.

What I am assuming is both ASRock and MSI use the same OEM maker her.

 

[maxiwee]

my motherboard doesnt say Z790 PG Lightning/D4 but Z790M PG Lightning/D4. hwinfo64, systeminfo, cpu-z and some other tools ive tried all reported the same again, msi h510m-a pro. i have contacted them and will update the thread

 

[Caring1]

@W1zzard what's your take on CPU-z reading this incorrectly?

 

[ShrimpBrime]

Why so quick to blame Microsoft?

I don't see this as Microsoft's fault here. CPU-Z shows it as an MSI too so this appears to be what the chipset is reporting.


You mean the board says Z790 PG Lightning/D4?

Maybe try HWiNFO64 to verify and then I would contact ASRock to ask them. You can also run systeminfo from a command prompt.

What I am assuming is both ASRock and MSI use the same OEM maker her.

Probably hot swapped the drive and the 510 was the old motherboard. He could try just uninstalling the old chipset drivers. Can also change the device names in registry, but thats pretty complicated for most people. The simplest solution is a clean windows installation if all else fails. At least thats my take on it.

 

[Bill_Bright]

Probably hot swapped the drive and the 510 was the old motherboard.

Good thought.

@maxiwee - Is that what you did? That is, was your boot drive previously used with that MSI board?

 

[EarthDog]

I don't think CPUz reads from/stores any data like this on your HDD, peeps. This is a question for the CPUz devs, not M$ (maybe W1z could shed some light on it tho).

 

[ir_cow]

does your motherboard look like a ASRock Z790M pg lightning d4 or MSI H510M-A pro. The Lighting has a VRM heatsink and saying Lighting on it. The MSI one does not have a VRM heatsink at all.

 

[maxiwee]

Good thought.

@maxiwee - Is that what you did? That is, was your boot drive previously used with that MSI board?

i've never used a different mobo. all parts got bought brand new and built, the only parts i swapped are the cooler and some fans, i.e nothing relevant.

oh and actually this wouldn’t have been possible, because when configuring a RAID array using Intel RST (the tool used by my BIOS), you have to either format the drive or rebuild the GPT using something like WinRE or SystemRescue (which is what I used). But how I know that is a different story…

Probably hot swapped the drive and the 510 was the old motherboard. He could try just uninstalling the old chipset drivers. Can also change the device names in registry, but thats pretty complicated for most people. The simplest solution is a clean windows installation if all else fails. At least thats my take on it.

look above. have already done a clean install, checked it also accross some of the other os ive used on this pc(loads of debian based distros, arch, fedora, some others and macos at some point) and all i can remember is that it always displayed the msi one. the registry method works for windows ig but the real issue is still there, my bios seems to be the only software that recognizes it as what it is.

does your motherboard look like a ASRock Z790M pg lightning d4 or MSI H510M-A pro. The Lighting has a VRM heatsink and saying Lighting on it. The MSI one does not have a VRM heatsink at all.

it looks like ASRock Z790M pg lightning d4, attached some images but its hard to properly get my phone in there.

EDIT: i saw the ssd in the first image, fixed.

 

[ShrimpBrime]

look above. have already done a clean install, checked it also accross some of the other os ive used on this pc(loads of debian based distros, arch, fedora, some others and macos at some point) and all i can remember is that it always displayed the msi one. the registry method works for windows ig but the real issue is still there, my bios seems to be the only software that recognizes it as what it is.

Look where? You did not state this until this very post. That said NVM it then.

I even reflashed the one from the official website multiple times.

And how exactly was the procedure performed??

___________

To clear DMI data, is simply a cmos reset. The long way. turn off PSU, pull the battery and jumper on the pins for 30 seconds.

Then Flash the bios. (Through the bios or strictly using AsRock windows flash tool, but I suggest bios)

Then do the clear cmos again after the flash.

Change no bios settings, post straight to windows.

Does it still report the wrong information? Yes? Then try a different earlier bios. No, you cannot roll back Management engine firmware. You can uninstall the management engine software however and use an earlier version, but may have conflicts with up to date firmware.

OR, do nothing. Use the PC and be happy it posts and works normal. Sometimes a bad DMI pool prevents the board from posting.

HFGL!!

 

[Bill_Bright]

Look where? You did not state this until this very post.

I think he meant "just above" - as in the same post as the reply to me. The point, he did a clean install. His boot drive was not used with a previous motherboard.

I am a strong proponent of, "if it ain't broke, don't fix it." While this seems seem to be working fine (it ain't broke), I don't believe I would be able to ignore this issue. Something seems fishy here. I see no reason why programs report this motherboard to be an MSI motherboard when the BIOS correctly reports it as an ASUS.

Something ain't right. Does it need to be "fixed"? Not necessarily. But it needs to be explained.

 

[maxiwee]

Look where? You did not state this until this very post. That said NVM it then.

I meant the the part of above your quoted comment, sorry if i was unclear.

And how exactly was the procedure performed??

By downloading the bios rom file and placing onto a fat32 formatted usb stick and then using the flash utility in the bios itself.

To clear DMI data, is simply a cmos reset. The long way. turn off PSU, pull the battery and jumper on the pins for 30 seconds.

If I remove my cmos battery it basically nukes my raid config. No data gets deleted, just the config gets corrupted and I'd have to reconfigure it and then rebuild the gpt and still wouldn't fix it(or at least hasn't in the past).

I am a strong proponent of, "if it ain't broke, don't fix it." While this seems seem to be working fine (it ain't broke), I don't believe I would be able to ignore this issue. Something seems fishy here. I see no reason why programs report this motherboard to be an MSI motherboard when the BIOS correctly reports it as an ASUS.

Something ain't right. Does it need to be "fixed"? Not necessarily. But it needs to be explained.

I totally get it, but one thing that may is related but don't think so tbh is that my gpu is weirdly only using pcie4x4.0 even it could run on 16x4.0 but it's a far fetch I'd say. I mean we will see what the support will say about this, haven't got a response yet.

 

[ShrimpBrime]

I meant the the part of above your quoted comment, sorry if i was unclear.

By downloading the bios rom file and placing onto a fat32 formatted usb stick and then using the flash utility in the bios itself.




If I remove my cmos battery it basically nukes my raid config. No data gets deleted, just the config gets corrupted and I'd have to reconfigure it and then rebuild the gpt and still wouldn't fix it(or at least hasn't in the past).


I totally get it, but one thing that may is related but don't think so tbh is that my gpu is weirdly only using pcie4x4.0 even it could run on 16x4.0 but it's a far fetch I'd say. I mean we will see what the support will say about this, haven't got a response yet.

You forgot the last part.

OR, do nothing. Use the PC and be happy it posts and works normal.

@Bill_Bright
The bios might have some corruption in the DMI pool. May be best ro just leave it alone. Or its something really stupid and simple we haven't thought of yet. If it where me, Id leave it alone at this point.

 

[maxiwee]

You forgot the last part.

OR, do nothing. Use the PC and be happy it posts and works normal.

@Bill_Bright
The bios might have some corruption in the DMI pool. May be best ro just leave it alone. Or its something really stupid and simple we haven't thought of yet. If it where me, Id leave it alone at this point.

If support isn't able to fix it(i don't count sending me a new one as a fix as it would be a waste of electronics), I will likely just use some real dmi entries of my board(or at least of asr and then I guess my boards strings) and use something like dmiedit or afuwin. Just need some legit dmi entries from the same board or at least a similar one.

 

[ShrimpBrime]

If support isn't able to fix it(i don't count sending me a new one as a fix as it would be a waste of electronics), I will likely just use some real dmi entries of my board(or at least of asr and then I guess my boards strings) and use something like dmiedit or afuwin. Just need some legit dmi entries from the same board or at least a similar one.

That's the problem. It is highly likely the DMI pool in the bios file is accurate, but they bios chip its self may have corruption in which there usually isn't a repair for. Its extremely rare a modern bios file would contain inaccurate DMI pool.

 

[maxiwee]

That's the problem. It is highly likely the DMI pool in the bios file is accurate, but they bios chip its self may have corruption in which there usually isn't a repair for. Its extremely rare a modern bios file would contain inaccurate DMI pool.

I mean if I edit it and it still doesn't hasn't changed, I'll just live with it. Maybe the unexpected happens and support actually fixes it, but I don't have high hopes.

 

[Ruru]

Sorry for being lazy and not going through the whole thread, but does other software recognize it properly? Could be just a CPU-Z bug.

 

[maxiwee]

Sorry for being lazy and not going through the whole thread, but does other software recognize it properly? Could be just a CPU-Z bug.

it's the same across every tool I've tried and most os's I've had on this pc, mostly debian based distros but also other classic ones

 

[Bill_Bright]

As I noted above, for me, it does not necessarily needs to be fixed, but it needs to be explained, because at this point, it really makes no sense. If MSI and ASUS were subsidiaries of the same company (like Chevrolet and Buick are of GM), then I might understand as they share many components. But MSI and ASUS have no corporate relation - AFAICT.

 

[EarthDog]

If you want to correct it.......use an app called "DMIEDIT".

Was this board bought used...................wonder if the previous owner was banned in games and changed all the info mobo info, LOL!


Also, isn't it CIM these days, not DMI? I thought DMI was dated and replaced by CIM.