You have dout and count assigned in both processes. Neither are resolved signals.
From IEEE Std 1076-1993:
12.6.1 Drivers
Every signal assignment statement in a process statement defines a set of drivers for certain scalar signals. There is a single driver for a given scalar signal S in a process statement, provided that there is at least one signal assignment statement in that process statement and that the longest static prefix of the target signal of that signal assignment statement denotes S or denotes a composite signal of which S is a subelement. Each such signal assignment statement is said to be associated with that driver. Execution of a signal assignment statement affects only the associated driver(s).
This essentially means you are duplicating both count and dout.
There are many ways to model the behavior of dout and count you desire. Bifurcating their operation across two processes based on starting and ending events isn’t one of them. That would require three processes, one for the making event, one for the breaking event and one for the clocked storage. You’d likely need separate events for operating count.