So my PC decides to stop working suddenly. I loaded my pc and it wouldn’t load, I reset it. Came up this time with 3 options from bios ‘Load optimized defaults reboot’ ‘ “ “ and restart’ And enter bios... I chose defaults reboot. It restarted and I got in to PC. Then the next day I started up again. And I get nothing. No display, not detected. No option to default bios etc. So I fiddled today and reset cmos. First time it did nothing. Took out gpu and ram, left a stick in. Nothing. Reset cmos again. It loaded with optimized bios or enter bios options again. So I enter bios. Have a look At the settings and seems same as it was before. I save and exit. Reboots to nothing, again. The mobo was cycling different codes. I just reboot. It goes through and comes up sitting on A0. No screen though. Guess maybe not using the onboard. So I left it 5 min or so. Still nothing, sitting st A0. I restart, it doesn’t boot again. Reset CMOS. Get into bios and set onboard GPU as default. Check other bits. Restart. It sits and cycles the codes I have linked video of... seems to shut off by itself then loads again and carries on into windows. Goes into windows, it runs some check of hdd and diagnosis and then loads into the desktop. I think great, I’ll try other ram stick in. I reboot (no change of ram yet) - it doesn’t load. No screen nothing. Get this cycling error codes continually. I’ve reset cmos and it still does it. MOBO G1 Sniper z97 Not sure on cpu, an i5 of some sort. Palit 970 GPU Anyone know what else I could try or an order? Bit annoying this. It does a diff error if I have gpu in cycling the mobo codes like it is at the moment. Thanks (Wrote this on mobile hope it is readable :/)
Ahh just moved ram to other slot. Came up with the load opt/boot/reboot/enter bios screen again. Check bios and save exit. Get to windows. Reboot got into it again. Turn off and turn on and it comes up with the same mobo cycling numbers.
So I simply moved the ram to the other slot. And it loads windows. If I turn off and back it does the error cycling codes. Move ram. Loads again. Then error. Was just finding memtest86 to do that hopefully I can get into the bios to start it ;D haha
Failing at 32 and rebooting constantly is a memory error, so it might be that your memory is toast. It could also be something to do with the CPU as the memory controller is on there. I'd suggest removing the CPU and reseating it. It's worth a shot.
Done mem test, memory passes no errors. When it hits 32, it doesn't reboot. Just keeps repeating the error codes in a cycle. So far, it loads to windows if I have memory in a slot. If I turn off or reboot, it won't load into windows until I move the mem stick to the other slot. So... Load windows turn off - move mem to slot closest to cpu turn on to windows turn off - move to furthest from cpu turn on to windows. and so on... If I leave it seated, 32 error. -_- ehhh
This may be risky, but your bios may be corrupt. You could try flashing it.. There may also be a way to force it onto the other bios, too. Just to see if that is the issue.
