To elaborate, this CRC also takes an additional 32-bit parameter value, which I suspect is the initial value or related to it somehow. The behavior I mentioned with even-odd xor is when that parameter is non-zero.
For generating checksums it only accepts data that is sized as a multiple of 32 bytes, of which the last 8 bytes are always unused and don't affect the result.
An example of some results appearing online that I mentioned is the value 0xc5b9cd4c, which is the result when the parameter value is 0 and the input is the byte 0x01 followed by 31 null bytes. This number returns various CRC-related results in google, in one of which this value seems to be in a lookup table of CRC remainder values.

All include some more results below, all with the parameter value I mentioned at zero, and an input of 32 bytes, all unmentioned bytes are null:
All null bytes: 0
Byte 0 as 0x01: 0xc5b9cd4c
Byte 1 as 0x01: 0xf382b7f2
Byte 2 as 0x01: 0x64c29d0
Byte 3 as 0x01: 0x56af9db2
Byte 4 as 0x01: 0x17d3315d