Hi,
I'm very new, this is my first attempt at a home network.
Hardware:
Gigabyte motherboard from 2010 - GA-G41M-ES2H rev1.0
CPU - Intel Core 2 Quad Q3800
6GB RAM - I know that's under spec, but it's a network for just me, no other users, hoping that's not the issue.
Windows 7
Device Manager shows all devices operating correctly.
On connection of any of my burned boot devices the computer freezes at the processor stage of the boot
I have done the following all with the same result:
1. Used USB flash drive - made sure it was 2.0
2. Tried numerous USB ports around the machine
3. Re-burned .iso to stick 3 times
4. STarted with Rufus then moved to Etcher for burning
5. switched to external USB HArd Drive that I know works well.
6. redownloaded the iso, and reburned to the known working hard drive using Etcher.
7. my BIOS allows for selection of USB-ZIP, USB-HDD, USB-FDD, USB-CDROM.... I've tried them all.
Note: booting normally into Windows still works, and the external usb hard drive shows as functioning when connected after boot.
Thanks.
I'm very new, this is my first attempt at a home network.
Hardware:
Gigabyte motherboard from 2010 - GA-G41M-ES2H rev1.0
CPU - Intel Core 2 Quad Q3800
6GB RAM - I know that's under spec, but it's a network for just me, no other users, hoping that's not the issue.
Windows 7
Device Manager shows all devices operating correctly.
On connection of any of my burned boot devices the computer freezes at the processor stage of the boot
I have done the following all with the same result:
1. Used USB flash drive - made sure it was 2.0
2. Tried numerous USB ports around the machine
3. Re-burned .iso to stick 3 times
4. STarted with Rufus then moved to Etcher for burning
5. switched to external USB HArd Drive that I know works well.
6. redownloaded the iso, and reburned to the known working hard drive using Etcher.
7. my BIOS allows for selection of USB-ZIP, USB-HDD, USB-FDD, USB-CDROM.... I've tried them all.
Note: booting normally into Windows still works, and the external usb hard drive shows as functioning when connected after boot.
Thanks.