Associate
- Joined
- 9 Dec 2015
- Posts
- 865
try turning off Global C-states as mentioned above
Losing peripheral outputs
- Thread starter Dirk Diggler
- Start date
- Joined
- 6 Jan 2013
- Posts
- 22,607
- Location
- Rollergirl
I've left global C states for now as it's not something I'd want to run with 24/7.
I've now swapped the GPU out and will see if that makes any difference, and failing that then I think it will be pretty conclusive; faulty Motherboard.
I've now swapped the GPU out and will see if that makes any difference, and failing that then I think it will be pretty conclusive; faulty Motherboard.
Last edited:
Associate
- Joined
- 7 Oct 2008
- Posts
- 954
- Location
- Birmingham
Are you plugged directly into the I/O or through case USBs?
- Joined
- 6 Jan 2013
- Posts
- 22,607
- Location
- Rollergirl
I've tried both and it's froze on both configurations.
Associate
- Joined
- 7 Oct 2008
- Posts
- 954
- Location
- Birmingham
If you have video or a visible programme running, I assume the system doesn't hang? You're just losing inputs? Have you got any Bluetooth peripherals you could try?
- Joined
- 6 Jan 2013
- Posts
- 22,607
- Location
- Rollergirl
I lose the screen so I'd need to SSH in or similar if I wanted to check system was responsive or not.
Last edited:
Configure the power button to shutdown. Press the power button. If it doesn't shutdown, you know it's crashed.
- Joined
- 6 Jan 2013
- Posts
- 22,607
- Location
- Rollergirl
Yes, that is what happens. Under normal circumstances, holding the power button will shutdown the PC, but when this fault happens then the power button does nothing; I need to flick the PSU switch to reset the system.
Not holding. A press. If a press doesn't shut it down (software shutdown) then it is definitely crashing.
If you a long press (hardware shutdown) isn't turning it off then that is a hardware fault.
- Joined
- 6 Jan 2013
- Posts
- 22,607
- Location
- Rollergirl
It's been fine since I swapped the GPU out. I'll leave it idle overnight and see how it performs.
- Joined
- 6 Jan 2013
- Posts
- 22,607
- Location
- Rollergirl
And it's did it again. 
We're now down to CPU-MOBO-RAM as I've swapped out and tested everything else.
Now running memtest on the memory, using my test rig.
We're now down to CPU-MOBO-RAM as I've swapped out and tested everything else.
Now running memtest on the memory, using my test rig.
Sounding like the motherboard at this stage tbh but you do right to rule everything else out first (as far as you possibly can).
I always think if our systems just worked perfectly all the time, we would get bored eventually.
Part of the fun is having to do the odd bit of troubleshooting every so often and maybe learning something new along the way.
That’s how I look at it anyway
I always think if our systems just worked perfectly all the time, we would get bored eventually.
Part of the fun is having to do the odd bit of troubleshooting every so often and maybe learning something new along the way.
That’s how I look at it anyway
Last edited:
- Joined
- 6 Jan 2013
- Posts
- 22,607
- Location
- Rollergirl
Yes, I agree it's looking very much like the motherboard at this point. I've been testing the RAM for a couple of hours now with no issues, so that's pretty much ruled out, too.
I've already tested the CPU with video encodes and Cinebench.
I've already tested the CPU with video encodes and Cinebench.
Could be either the mobo or could still be the CPU...though i agree the mobo is the more likely culprit
the reason is that video encodes/cinebench just stress the core, whereas the problems you're describing is in the PCIE portion of the IO die, which you haven't tested yet
i only like troubleshooting if i don't own said parts and it's not my money
