Disk Corruption — Data Altered After Write

Primary C=32 cause — after QB wrote a record and stored its checksum, the disk subsequently altered the stored data (bad sector flip, file system error, or bit rot). When QB reads it back and recomputes the checksum, it doesn't match what was stored, and C=32 is reported. Run chkdsk /f and S.M.A.R.T. disk diagnostics to identify the physical cause.

Incomplete Write — Partial Data on Disk

If QB's write was interrupted (power failure, crash) after writing the checksum but before writing all the data (or vice versa), the stored checksum doesn't match the incomplete data on disk. When QB reads the incomplete record, the checksum check fails with C=32. Rebuild Data can often repair this by reconstructing the record from its component parts.

Failing Hard Drive (S.M.A.R.T. Errors)

A failing HDD with reallocated sectors or pending sectors can successfully write data but then have the underlying storage become unstable, causing the data to degrade between write and read. C=32 recurs even after file repair if the drive is failing. S.M.A.R.T. diagnostics (CrystalDiskInfo, HD Sentinel) reveal drive health and predict failure before data loss occurs.

RAM Errors During Read/Write

Faulty RAM can corrupt data as it passes through memory between disk and QB — the data on disk is fine, but QB computes an incorrect checksum because the RAM introduced bit errors during the read. C=32 from RAM errors recurs randomly and inconsistently. Run Windows Memory Diagnostic (mdsched.exe) or MemTest86 to test RAM.

File System Errors

File system errors (NTFS corruption) can cause QB to read data from the wrong disk location — the file system returns incorrect data for a given file offset, making the checksum check fail. File system errors are repaired by chkdsk /f and, for severe cases, using Windows' built-in file system repair tools.

Network Transmission Error (NAS/Server)

If the company file is on a NAS or network server, data corruption can occur during transmission over the network rather than on the disk itself. Network errors between the file server and QB's workstation cause the data QB receives to differ from what's on disk, producing a C=32 checksum mismatch. Network integrity issues (damaged cables, faulty switches) are the root cause here.

METHOD 1 Run chkdsk + S.M.A.R.T. Diagnostics + Verify/Rebuild Disk-level cause — check hardware first

METHOD 2 Test RAM + Move File to Different Drive RAM errors or failing drive causing C=32

METHOD 3 Restore from Backup C=32 LVL_SEVERE_ERROR or hardware confirmed failing

What is a checksum and why does QB use them?

A checksum is a computed value derived from a block of data — think of it as a fingerprint of the data. When QB writes a record to the company file, it computes a checksum of that data and stores it alongside the record. When QB later reads that record, it recomputes the checksum from the data it reads. If the two values match, the data is intact. If they don't match, the data was altered on disk between the write and the read — this is what C=32 reports. Checksums allow QB to detect silent data corruption that would otherwise go unnoticed. Without checksums, corrupted data could be silently read and used in calculations, producing incorrect financial results without any error message. The C=32 error, while disruptive, is QB's detection mechanism protecting you from using corrupted data unknowingly.