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.

 

[abysal]

...

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).

...

So the RAID config on most consumer boards will be stored on the drives. You can clear / reset the BIOS, and to get your RAID config back you just need to enable RAID function for your NVME or SATA ports. Do not recreate or do anything with the individual drives. Reboot back to BIOS and you should see your prior RAID volume. I've moved my RAID 1 this way across multiple systems (AMD AM4 to another AM4, and then to an AM5, and another AM5; my RAID 1 volume remained intact after each move. However as with anything involving irreplaceable data, have a few good backups just in case something goes wrong.

But your overall issue with the hardware / DMI data being reported as an MSI board is really odd. The board is clearly an ASRock Lighting series as seen and identified physically. Was this board brand new when bought? Perhaps it was repaired with a transplanted BIOS chip or flashed with a programmer incorrectly at some point with an MSI BIOS image, which left traces of it? Those are my theories.

If you are not worried about potential warranty questions, and it flashes and shows an ASRock BIOS, I would just keep on using it, otherwise perhaps do an RMA... but thats probably more hassle then its worth.

 

[maxiwee]

So the RAID config on most consumer boards will be stored on the drives. You can clear / reset the BIOS, and to get your RAID config back you just need to enable RAID function for your NVME or SATA ports. Do not recreate or do anything with the individual drives. Reboot back to BIOS and you should see your prior RAID volume. I've moved my RAID 1 this way across multiple systems (AMD AM4 to another AM4, and then to an AM5, and another AM5; my RAID 1 volume remained intact after each move. However as with anything involving irreplaceable data, have a few good backups just in case something goes wrong.

Could be the case usually, but my motherboard is either an exception or I was just unlucky multiple times before. When I try to do it like you said my volume would just be marked as non bootable and one of the drives would just always be marked with failed. Trust me I tried a lot and the way I did it wasn't my first idea.

But your overall issue with the hardware / DMI data being reported as an MSI board is really odd. The board is clearly an ASRock Lighting series as seen and identified physically. Was this board brand new when bought? Perhaps it was repaired with a transplanted BIOS chip or flashed with a programmer incorrectly at some point with an MSI BIOS image, which left traces of it? Those are my theories.

It was bought brand new(like the rest of the system).

otherwise perhaps do an RMA... but thats probably more hassle then its worth.

Same thing I am thinking + it would also just be a waste as they would likely just trash a fully functional board instead of looking into the problem.

 

[EarthDog]

Change it yourself with the program I mentioned and never think about it again.

 

[maxiwee]

Change it yourself with the program I mentioned and never think about it again.

As said before in this thread, if I decide to change it I would want to have some legitimate entries from a similar mb by asr or maybe even the same. The actual changing isn't a problem.

And just noticed something odd, in 3d mark results it shows me the following:

 

[meatwar]

Sir... this is an issue with an old OS installation/mb swap, this cannot be such a ridiculous mistake from Asrock/MSI.
If you tell me, you tested a clean OS installed on a spare disk, then yes, we have a major ISSUE...

 

[maxiwee]

Sir... this is an issue with an old OS installation/mb swap, this cannot be such a ridiculous mistake from Asrock/MSI.
If you tell me, you tested a clean OS installed on a spare disk, then yes, we have a major ISSUE...

All parts got bought brand new. I've used several different os's on this pc and as far as I can remember all of them reported the same...

 

[EarthDog]

As said before in this thread, if I decide to change it I would want to have some legitimate entries from a similar mb by asr or maybe even the same. The actual changing isn't a problem.

You can do that manually, too. Just follow the formatting you see.

 

[meatwar]

"I've used several different os's on this pc and as far as I can remember all of them reported the same..."

Then share your current mb bios FULL DUMP (Intel FPT tool is enough)... i want to see if you're making fun of all of us here on the forum or if the rest of system components have a new kind of "memory trace" that the world of technology still doesn't know the existence...

EDIT: FPT v16.1 of course...

 

[maxiwee]

Asrock support doesn't seem to care about my ticket so I gave that up, I just used dmi edit to change it, all looks normal now. Somehow I even had completely different serial numbers... Got the real one from my box.

i want to see if you're making fun of all of us here on the forum

Interesting thought. Don't even know what else to say.

Error 201: [FPTw64.exe] cannot be run on the current platform.

"I've used several different os's on this pc and as far as I can remember all of them reported the same..."

Then share your current mb bios FULL DUMP (Intel FPT tool is enough)... i want to see if you're making fun of all of us here on the forum or if the rest of system components have a new kind of "memory trace" that the world of technology still doesn't know the existence...

EDIT: FPT v16.1 of course...

I uploaded it, did it work?

 

[meatwar]

Asrock support doesn't seem to care about my ticket so I gave that up, I just used dmi edit to change it, all looks normal now. Somehow I even had completely different serial numbers... Got the real one from my box.

Interesting thought. Don't even know what else to say.

Error 201: [FPTw64.exe] cannot be run on the current platform.


I uploaded it, did it work?

DMI on bios region is OK as Z790M PG Lightning/D4, bios tag also matches current Asrock bios update file 15.04 (5.27)
Ok, file verified, its NVRAM residuals, you have to do a "COLD" reset to the mb, these can be inject by an app used/still used in OS...no wizzard here to guess it, sry.
Unplug PSU, take out CMOS battery (also check mb jumper), leave it to drain about 15m.
On restart load defaults, save and exit, reboot and set any specific settings again to bios if needed to boot current OS.

Later on you can update the CSME v16.1.30.2264 to the latest 16.1.35.2557

 

[maxiwee]

View attachment 404590
DMI on bios region is OK as Z790M PG Lightning/D4, bios tag also matches current Asrock bios update file 15.04 (5.27)
Ok, file verified, its NVRAM residuals, you have to do a "COLD" reset to the mb, these can be inject by an app used/still used in OS...no wizzard here to guess it, sry.
Unplug PSU, take out CMOS battery (also check mb jumper), leave it to drain about 15m.
On restart load defaults, save and exit, reboot and set any specific settings again to bios if needed to boot current OS.

Later on you can update the CSME v16.1.30.2264 to the latest 16.1.35.2557

Did that, now the pc doesn’t boot anymore. I put in the cmos, try to boot but nothing happens. Fans run, no display output, no usb power and for some reason the debug leds on my motherboard tell me there’s an issue with my cpu.

 

[meatwar]

Sorry, but for sure that anyone here will tell you, that a simple clear CMOS WON'T KILL A SYSTEM... i would be in a great trouble with my customers if I KILLED a system of them, every time i need to perform a reset...no more comments and start using those "brain" mass...

Oh and dont tell me that you used a screwdriver to take out the CMOS battery (damage done to pcb is omitted from this conversation...shhhh)

 

[maxiwee]

Sorry, but for sure that anyone here will tell you, that a simple clear CMOS WON'T KILL A SYSTEM... i would be in a great trouble with my customers if I KILLED a system of them, every time i need to perform a reset...no more comments and start using those "brain" mass...

Oh and dont tell me that you used a screwdriver to take out the CMOS battery (damage done to pcb is omitted from this conversation...shhhh)

calm down, I don’t blame you. I am sure something else must have happened while I used it but I just don’t know what it could’ve been. It’s not that big of an issue, I have 2 options rn, spi flashing or sending it back(it’s under 2 years old, so it’s still covered).

No I didn’t use a screwdriver, I just used my finger nail to trigger the release thing.

no more comments and start using those "brain" mass

Also, just why? I never said you’re at fault, nor did I ever say I thought it was me removing the cmos battery what caused this. I just told you what happened.

I still wanna say thanks to you @meatwar and everyone else that contributed to this thread. I mean the problem kinda got fixed but the board had it coming tbh. 1 usb port was broken and something just felt off, I can’t tell you what it was, my head just told me