Computer Restarts Every 2 Minutes After Fresh Install of Windows 10

kaityf · 05 Mar 2017

I have additional info, but I don't know if it will make any difference.

I had changed the boot order in bios so that the flash drive would boot first, then the CD Rom, and then the hard drive. When I removed the flash drive and start the computer again, it actually booted from the CD Rom drive! I had made that the second option after the flash drive. That means it can run Seatools. (There was a Seatools disk in the drive that I had tried to use before.)

Now here's the new and interesting information (to me anyway). The screen resolution is off. It's magnified about 125%, which is actually one of the problems we had with the computer when it first started messing up. It's impossible to see what's on the far left of the screen. I looked up Seatools tutorials to find some screenshots to know what I was missing. What I can't see is the "Bas" in "Basic Tests." I also see an arrow on the screen like you would see for moving a cursor around with a mouse - but the mouse doesn't work. I tried a different mouse. That didn't work either.

Using cntrl/alt I was able to make selections and start running a long test. However, I'm not sure how I'm going to be able to read the log when it finishes as I can see the far left of the screen.

I find that resolution thing odd as well as the mouse thing. Does this narrow down any problems? I figure I still have to take the computer in for repairs, but it would be nice to have an idea of the problem.

kaityf · 07 Mar 2017

I thought everyone would like to know that the problem with the computer was a bad graphics card. New card was installed and everything seems to be working okay.

ArazelEternal · 07 Mar 2017

Bad video card was my thought. The fact that it would do the restart loop when it would connect to the internet was what told me that the video hardware was bad. The drivers for it were coming in through an update somehow, and that would cause the crash loops. You wouldnt get a blue screen because the card would cut out and not display anything so there wasnt anything to see.

The crashing would only start after the install of drivers because before the drivers are installed only the most basic functions of the card were active. The card during this time was mostly inactive so whatever about it that was bad and causing the issues wasnt active so it wouldnt fail.

Now I could be wrong about that, but Ive repaired a number of computers in my time, including my own. When ever I would see something like this, that was the cause.

Ive also seen faulty processors and mobos cause issues like this too.

Good to hear that it seems to be fixed though. Come back in a few days and let us know if it stays working.