I'm afraid you've gotten off to a pretty bad start here. Please read the PHD2 User Guide and the Best Practices document to better understand what you need to do.
https://openphdguiding.org/documentation/
https://openphdguiding.org/phd2-best-practices/
The first thing to do is to fix the hardware-related problem that is creating the camera timeouts. Those problems are probably coming from the USB connection to the camera assuming that you are running the latest version of the ZWO drivers (not an old version from the Windows 7 system). If all of your camera-related gear works correctly on Windows 7, then the place to start looking is the USB subsystem of the new computer. There is an extensive trouble-shooting section in the User Guide that provides suggestions on what to look for. All of the testing can be done during the daytime simply by looping camera exposures. Until you can run for several hours, at least, continuously taking 1-2 second camera exposures, you won't make any progress with guiding.
Once you have resolve the timeout problems, you need to follow the correct procedures in PHD2:
1. Create a new configuration profile using the new-profile-wizard
2. Plan on using 1-2 second exposures, nothing smaller
3. Build a dark library for your guide camera. You can do this as the last step in the new-profile-wizard
4. Increase the guide speed setting in the mount to 0.9x sidereal. This is done using the hand-controller or the ASCOM driver configuration, not PHD2.
5. Use multi-star guiding by clicking on the auto-find icon. Don't try to select stars manually
6. Use the Calibration Assistant to complete a calibration, following all of its suggestions including a correct pointing location in the sky
7. Run the Guiding Assistant for at least 2 minutes, then follow its recommendations
Regards,
Bruce