x
PC in "booot loop"
posted in
Hardware
Takes like 5 mins to take the gfx card out and test so you may aswell, but I highly doubt its the source of your problem.
I had a similar issue when I built my pc, where it would power off straightaway. The problem for me was power related unsurprisingly, with a small bit of the metal from the I/O shield touching the inside of a port and short-circuiting the mobo (not easy to spot). The fact your pc had been working means this is probably not your problem though.
An easy thing to check would be that there are no loose cables/connections inside your case aswell.
If its not posting it could also be mobo/cpu which are pretty hard to test unless you've got a spare mobo laying around.
Doesn't Setsul live in Germany? just summon him with the ritual
Takes like 5 mins to take the gfx card out and test so you may aswell, but I highly doubt its the source of your problem.
I had a similar issue when I built my pc, where it would power off straightaway. The problem for me was power related unsurprisingly, with a small bit of the metal from the I/O shield touching the inside of a port and short-circuiting the mobo (not easy to spot). The fact your pc had been working means this is probably not your problem though.
An easy thing to check would be that there are no loose cables/connections inside your case aswell.
If its not posting it could also be mobo/cpu which are pretty hard to test unless you've got a spare mobo laying around.
Doesn't Setsul live in Germany? just summon him with the ritual
I had a similar issue when I built my pc, where it would power off straightaway. The problem for me was power related unsurprisingly, with a small bit of the metal from the I/O shield touching the inside of a port and short-circuiting the mobo (not easy to spot). The fact your pc had been working means this is probably not your problem though.
An easy thing to check would be that there are no loose cables/connections inside your case aswell.
If its not posting it could also be mobo/cpu which are pretty hard to test unless you've got a spare mobo laying around.
Doesn't Setsul live in Germany? just summon him with the ritual
FirelockDoesn't Setsul live in Germany? just summon him with the ritualI tried but i guess due to my limited experience it takes a while.
You didn't even try it.
Also try not posting in the middle of the night. I've heard that helps.
FireHowever, since yesterday it got to a point where it will just stay inside that loop forever* (didnt test longer than 5 minutes but i guess thats enough). The only way to fix this is to reset bios by taking out the bios battery for a couple of seconds.
[...]
Also i could technically test whether its the gpu by using built in graphics, however i cant really stand using those for multiple weeks so id rather only do that as a very last backup plan.
Or you know, you could remove the GPU first instead of the CMOS battery next time it happens.
Have you thought about reading the mobo manual to figure out how to disable C6/C7 states on your mobo?
Also try booting with a single RAM stick (maybe try different ones in different slots).
[quote=Fire][quote=lock]Doesn't Setsul live in Germany? just summon him with the ritual[/quote]
I tried but i guess due to my limited experience it takes a while.[/quote]
You didn't even try it.
Also try not posting in the middle of the night. I've heard that helps.
[quote=Fire]
However, since yesterday it got to a point where it will just stay inside that loop forever[i]*[/i] (didnt test longer than 5 minutes but i guess thats enough). The only way to fix this is to reset bios by taking out the bios battery for a couple of seconds.
[...]
[i]Also i could technically test whether its the gpu by using built in graphics, however i cant really stand using those for multiple weeks so id rather only do that as a very last backup plan.[/i][/quote]
Or you know, you could remove the GPU first instead of the CMOS battery next time it happens.
Have you thought about reading the mobo manual to figure out how to disable C6/C7 states on your mobo?
Also try booting with a single RAM stick (maybe try different ones in different slots).
I tried but i guess due to my limited experience it takes a while.[/quote]
You didn't even try it.
Also try not posting in the middle of the night. I've heard that helps.
[quote=Fire]
However, since yesterday it got to a point where it will just stay inside that loop forever[i]*[/i] (didnt test longer than 5 minutes but i guess thats enough). The only way to fix this is to reset bios by taking out the bios battery for a couple of seconds.
[...]
[i]Also i could technically test whether its the gpu by using built in graphics, however i cant really stand using those for multiple weeks so id rather only do that as a very last backup plan.[/i][/quote]
Or you know, you could remove the GPU first instead of the CMOS battery next time it happens.
Have you thought about reading the mobo manual to figure out how to disable C6/C7 states on your mobo?
Also try booting with a single RAM stick (maybe try different ones in different slots).
That is not a proper summoning.
You turned it off, then removed the GPU and then tried to restart? That should rule out the GPU for now.
The "problem" started with Haswell, that's why you didn't find anything.
Does that mean you tried booting with all sticks removed? :D
That is not a proper summoning.
You turned it off, then removed the GPU and then tried to restart? That should rule out the GPU for now.
The "problem" started with Haswell, that's why you didn't find anything.
Does that mean you tried booting with all sticks removed? :D
You turned it off, then removed the GPU and then tried to restart? That should rule out the GPU for now.
The "problem" started with Haswell, that's why you didn't find anything.
Does that mean you tried booting with all sticks removed? :D
@setsul could you elaborate on the possible solutions? My Haswell PC does this as well and i could never find any solutions and nothing i tried fixed it.
@setsul could you elaborate on the possible solutions? My Haswell PC does this as well and i could never find any solutions and nothing i tried fixed it.
If it's because your PSU is shit then the solution is to either disable C6/C7 states or buy a non-shit PSU.
If it's because your PSU is shit then the solution is to either disable C6/C7 states or buy a non-shit PSU.
I'm guessing you don't have a spare PSU lying around.
Did you update the BIOS?
CPU running at stock now, RAM too?
I'm guessing you don't have a spare PSU lying around.
Did you update the BIOS?
CPU running at stock now, RAM too?
Did you update the BIOS?
CPU running at stock now, RAM too?
XMP profile I guess? Go back to JEDEC spec. You never know.
I'm guessing it's version 2117, nice coincidence.
XMP profile I guess? Go back to JEDEC spec. You never know.
I'm guessing it's version 2117, nice coincidence.
I'm guessing it's version 2117, nice coincidence.
in my professional opinion, it looks like your computer has been spooked by a ghost!
in my professional opinion, it looks like your computer has been spooked by a ghost!
Default XMP profile? I meant without XMP profile.
Anyway if it doesn't happen anymore you can obviously go back to full CPU and RAM speed.
Default XMP profile? I meant without XMP profile.
Anyway if it doesn't happen anymore you can obviously go back to full CPU and RAM speed.
Anyway if it doesn't happen anymore you can obviously go back to full CPU and RAM speed.
Yes, that means no XMP profile (just standard JEDEC profile). Because reasons.
Other mobos label it "XMP: [off/profile #1/profile #2/...], which makes more sense.
Yes, that means no XMP profile (just standard JEDEC profile). Because reasons.
Other mobos label it "XMP: [off/profile #1/profile #2/...], which makes more sense.
Other mobos label it "XMP: [off/profile #1/profile #2/...], which makes more sense.
Please
sign in through STEAM
to post a comment.