Cannot create a Boot Camp Partition In High Serra

I took the following steps.

Downloaded High Sierra from Apple

Installed the clean High Sierra on a USB drive.

• booted from the USB,
• erased Mac HD and formatted as APFS
• reinstalled High Sierra from the USB onto the cleaned HD
• Used BCA to partition a windows drive
• failed same error message
• Your disk could not be partitioned
• An error occurred while partitioning the disk. Please run Disk Utility to check and fix the error
• ran sudo fsck_apfs -n -l /dev/rdisk1
• result

warning: Overallocation Detected on Main device: (1769475+2) bitmap address (135c5)

warning: Overallocation Detected on Main device: (2401950+1) bitmap address (134ba)

warning: Overallocation Detected on Main device: (12256641+1) bitmap address (118aa)

warning: Overallocation Detected on Main device: (86951436+1) bitmap address (12fb9)

warning: Overallocation Detected on Main device: (87467036+1) bitmap address (13009)

warning: Overallocation Detected on Main device: (101365176+1) bitmap address (138c5)

How do I address Overallocation- is this what is preventing BCA from creating a Windows partition?

If I can't get this problem fixed I will have to switch to a windows machine, just can't justify the time wasted on this issue.

Frustrated in the snow.

i installed Mojave on an external USB. Booted from the USB and ran first aid on the Macintosh HD then ran

sudo fsck_apfs -n -l /dev/rdisk1

output was the same warnings

overallocation

should I erase the internal drive and then install Mojave.

The overallocations persist after reformatting in High Sierra. Are sectors on the disk preserved during formating, if so how can the overallocations be eliminated?

thanks for your effort in solving this problem

Erased disk1 in Disk Utility,

in terminal ran sudo fsck_apfs -n -l /dev/disk1

geting the same overallocation warnings

it does seem that sectors of the disk must be preseved by OSX.

the allocation warning iD’s change slightly.

eg first warning

(1769475+1)bit address (

become after erasing

(1769475+

First allocation warning before erasing

(1769475+1) bit address (12272)

after

(1769475+2) bit address (1178c)

These change after every fsck

tried running fsck on disk1 with

-o option and it appears to have worked all overallocationn removed!.

thanks Loner1 for helping me resolve this problem fun to deal with Unix commands again been a long time.

Thanks I will try.

here is the console out put.

Thanks for you assistance, ran the commands and results as posted.

The error still persists after running the commands.

By running Mojave from an external disk what action would I perform on the Mac's ssd? How will I correct the over allocations? Thanks for your help, there may yet be light at the end of this tunnel.