"Volume hash mismatch" error on Monterey

Well, the worst part is that even after installing new os twice, one time just re-installing and one time totally wiping and instating clean, the error still comes back. I honestly think its an apple hardware fault, something with bad memory or ssd and they just don't want to accept that, since the memory and SSD modules are of course now all soldered on and not replaceable (Great Apple !!!- Well done). So now - after going into apple store and sending the 2019 MacBook Pro in they tell me I need to replace motherboard for 680 bucks :-(. If you run more and more disk tests you will see that they randomly come back with errors and checksum problems, so honestly the same issue I have with a 6 year old SSD, slowly going bad, only that I can replace it and all is happy. But not with apple - you need to swap motherboard if either your RAM or SSD go bad. BRAVO - brilliant engineering APPLE.

The issue has appeared elsewhere and come to find out the Issue is a Bad RAM Module

This would require the user to have the computer Evaluated by an Apple Authorized Service Centre for an Extend overnight Hardware Test performed by them

The issue has appeared elsewhere and come to find out the Issue is a Bad RAM Module

This would require the user to have the computer Evaluated by an Apple Authorized Service Centre for an Extend overnight Hardware Test performed by them

How do you come up with that statement? Which software update has solved that? Read through the discussion and see that tons of people have installed multiple versions of OS starting from Big Sur all the way to the latest Monterey. None of the softwares that I ever installed on my MacBook Pro solved the issue. Only service and replacing ram module actually solved the problem. Really interesting to see which software update you are referring to - please elaborate. thanks

1.- The ram module being defective had no sense since my machine ran heavy gaming in windows and never presented any issue at all no mater how long I left my mac in that operative system.

2.- I had this issue with Monterrey 12.0, and in every single session that ended up with the hash mismatch there was a mds crash at the startup registered in the console

3.- In macOS 12.1 (21C52) the problem disappeared, no mds crash at the startup and no hash mismatch no matter how long I left the macOS running

4.- Out of concern I ran ram test that never came back with negative results

While I was having this issue, I heavily suspected it to be a firmware related issue

I recommend you to check the macOS 12 Monterey on Unsupported Macs Thread in MacRumors where this issue was more studied and dissected, some fixes where suggested but for me the permanent solution was that update mentioned until 12.4 (21F79) were I had the issue again, now Im testing 12.5 (21G5037d) but no mds crash so Im positive it is also free of the problem at least for me

1.- The ram module being defective had no sense since my machine ran heavy gaming in windows and never presented any issue at all no mater how long I left my mac in that operative system.

2.- I had this issue with Monterrey 12.0, and in every single session that ended up with the hash mismatch there was a mds crash at the startup registered in the console

3.- In macOS 12.1 (21C52) the problem disappeared, no mds crash at the startup and no hash mismatch no matter how long I left the macOS running

4.- Out of concern I ran ram test that never came back with negative results

While I was having this issue, I heavily suspected it to be a firmware related issue

I recommend you to check the macOS 12 Monterey on Unsupported Macs Thread in MacRumors where this issue was more studied and dissected, some fixes where suggested but for me the permanent solution was that update mentioned until 12.4 (21F79) were I had the issue again, now Im testing 12.5 (21G5037d) but no mds crash so Im positive it is also free of the problem at least for me

Hi After heaven, that sounds all good for your case and you might not have a bad RAM module or are having a different issue altogether, but you are referring to quite some subjects that are not really related to these issues the rest is encountering.

First issue is that you are referring to a Thread for Monterey on Unsupported Macs, which is clearly not the issue we are encountering, since we are are all on Monterey supported machines.

Second you are referencing updating and installing different versions of Monterey on your machine - again, none of the other users are even able to update without crashing, so your issue is most likely unrelated.

Third, you are saying a RAM module being defective makes no sense, since you are running heavy gaming in windows, without any issues?? How is that related - my 2019 MacBook Pro ran tons of compute intense calculations and 3D software for 2 years without any issues??? RAM doesn't come bad, but goes bad, so you can have a perfectly working laptop that one day starts acting up and then become more and more unstable (Which is typical for a bad ram problem).

Fourth, you said that you ran a memtest that came back negative - again it was established in multiple threads that they bad memory problem did never show up on apples build in memory test, but that you have to run a third party memtest, like the standard Memtest86, which pretty much showed a memerror on most machines that are affected.

A lot of community members have spend months with the problem and finally come to the conclusion that this is in most case RAM related. So to just tell everyone thats wrong is somewhat misleading and might get people onto the wrong path and spend weeks trying to go through upgrade cycles that take days to complete, due to them crashing 90% and sometimes taking 2-3 days to finally complete.

I hope you understand,

Thanks

On forums about macOS in unsupported machines theres usually more in depth information regarding the whole software involved in mac machines, I mentioned it because of that, but you're right

I was unaware of machines being unable to successfully update, my bad for not reading the whole article first

While on macOS, the hash mismatch would always appear after a certain time, but in Windows there was never an issue even when I was playing heavy games, the relation was that if ram were the issue, both operative system would be unstable not just macOS and games would crash

I didn't ran any build up ram test, I always used third party ones. But I didn't knew people had actually found ram errors, again Im sorry

I was mostly in the wrong here, but it's really important that people searching online for this problem that don't have the money to do an expensive replacement know that there is another side of the problem that points to a fixable firmware error.

Apple being apple trying to make you replace the whole chasis for broken key is what led me to a first bad impression on this

Im sorry, and tank you for showing me where I was wrong

Volume hash mismatch, cannot reinstall MacOS

My bad , omitted to supply linked article earlier

You are referring to something like in this article https://osxdaily.com/2021/11/10/volume-hash-mismatch-error-in-macos-monterey/

Sorry but this I am aware of this issue but do not know the solution.

It is not a Bad ram module at all, it is a software issue that was already solved in some macOS updates.

In this person's specific case it was the RAM Module.

Volume hash mismatch, cannot reinstall MacOS

Is misleading to attribute the issue to a bad ram module when all points out to a firmware error.