Mismatch between NIST SP800-90A test vectors and CTR_DRBG output

I am testing my Python implementation of NIST SP800-90A CTR_DRBG https://csrc.nist.gov/publications/detail/sp/800-90a/rev-1/final (AES-256, no df) with the CAVP test vectors (https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation-Program/documents/drbg/drbgtestvectors.zip), and have been stuck for the past couple of days.

The challenge I face is related to the CTR_DRBG_Generate function as specified in Section 10.2.1.5.1 (Generating Pseudorandom Bits When a Derivation Function is Not Used) of the above mentioned NIST SP800-90A standard.

[AES-256 no df]
[PredictionResistance = True]
[EntropyInputLen = 384]
[NonceLen = 0]
[PersonalizationStringLen = 0]
[ReturnedBitsLen = 512]

COUNT = 0
EntropyInput = faf346c9c8afbc5ab6e33ce492247fac6db9a7ba4297557f587a42563ddf56c90e41c6afb56233815b74e091bac7d8e5
Nonce =
PersonalizationString =
** INSTANTIATE:
Key = a9fccc320fea8ae31f80881556ef0c27a31ee7870ff73e115f348785872ccbd1


This works, the Key and V values are correct after a call to my CTR_DRBG_Generate function.

AdditionalInput =
EntropyInputPR = dfc111252d7146922713720ae1e348a07ae403b5238fefb4e8592f6f6cc4a61c94828db84c6faecd1502261008011f2c
** GENERATE (FIRST CALL):
V   = 9ac50e38805dab58baf6429436e00b39


This does not work, the resulting Key and V values from my implementation are different; so my first instinct was to look for an error in the design of my CTR_DRBG_Generate function. As a side note, would you agree that the EntropyInputPR is redundant and not needed at all?

AdditionalInput =