2 scenarios, but I'm not sure if both are possible. I think the first has happened to me. How to interpret and actions to try next to produce error-free, accurate rips.

1) Test & Copy produces matching checksums, but AccurateRip says "Rip not accurate"
2) Test & Copy produces differing checksums, but AccurateRip says "Accurately ripped"

This is for individual tracks, not an entire CD. I'm so bleary-eyed searching through old threads and reading so many posts all over the place.

The first scenario is not unusual and might happen if you have a different CD version than the one stored in the AR database.

The second scenario is impossible (unless AR is comparing only the ripping results against its DB and not the test results and something went wrong during the test copy).

I assume the second pass is the value that is compared to the AccurateRip database. This is possible with a drive or disc producing inconsistent results.

If you get "Accurately ripped" you have nothing to worry about. It was just the first pass that was unreliable.

1)If other tracks are reported as accurate, then the track in question is inaccurate if the confidence is greater then 1 in accuraterip, or you have a different pressing.

2)AccurateRip is correct. AR only seems to check the ripped track and not the test track. So the ripped track is correct.

I just had a track have matching checksums using Secure Mode + Test & Copy but come up Rip Not Accurate with confidence of 1. I'm guessing it's all right then. I think the other tracks were Accurate with confidence of 1.

Most likely the one other submission was wrong for that track. If you have a second drive, try ripping the disc again, in a different drive.