Invalid regions

While viewing my ramsav.bin in PKHeX I did an integrity check of my Checksums and came back with these errors;

Invalid: 03 @ region 06600

Invalid: 0A @ region 07400

Invalid: 32 @ region 27200

1st SAV: 55/58

Any idea what these are or how to correct them?

Thanks.

EDIT: Issue clarified. Thanks.

From a chat I had with Alpha in IRC;

[11:11] <Ceveth> Any here able to shed some light on my inquiry? http://projectpokemon.org/forums/showthread.php?44878-Invalid-regions

[11:11] <+Nene> Ceveth's URL: Invalid regions [ text/html ]

[11:16] <~Alpha> mine is 52/58 and seems perfectly fine

[11:16] <~Alpha> there are some hashes that just aren't always updated in RAM

[11:16] <~Alpha> that feature is more for when the files are actually saved

[11:17] <Ceveth> Yeah I'm not experiencing any issues in-game at all. I'm not not too familiar with what they are & why they're being flagged.

[11:18] <~Alpha> like I said, they aren't all that important in volatile memory

[11:19] <~Alpha> because when you import the RAM and save the game itself will fix those checksums

[11:19] <~Alpha> save the game, the game itself*

[11:19] <Ceveth> Ah, ok.

[11:19] <Ceveth> I'll try to ignore them then. Thanks for clearing it up.

[11:20] <Ceveth> Just me being anal retentive I suppose.

[11:20] <~Alpha> actually, pkhex will even fix most, if not all of them, up

[11:20] <~Alpha> so a simplified version of a checksum is like: how many pokemon are in my party?

[11:21] <~Alpha> well, if you have 5, it should be 5

[11:21] <~Alpha> but what if you just catch another pokemon?

[11:21] <~Alpha> well, the number of pokemon in your party is now 6, but the value still says 5 until it decides it wants to update it

[11:22] <~Alpha> when you save, there's no doubt that number will have been updated to 6

[11:22] <~Alpha> but while in RAM, it can just kinda go at its own pace

[11:22] <Ceveth> That makes sense. So if I export the romsav with PKHeX then re-import it & check the checksums again they should be fixed? Or am I misunderstanding?

[11:23] <~Alpha> the only way to get the save in a state where it's not RAMlike is to use other hardware

[11:24] <~Alpha> PKHeX was built before the web exploit and being able to pluck saves out of RAM when this was more critical

So it seems these invalid regions are simply a byproduct of the romsav being imported in a RAMlike state.

Most, if not all, of the errors will be fixed by themselves after exporting the SAV from PKHeX & saving in-game.

Apparently they aren't anything to worry about if you happen to come across something similar.