- Jul 14, 2012
- 25
- 0
- 10,540
In the past couple of days, I've been having trouble with my two-year-old build. Originally, I built it with the same 400W Rosewill my previous rig had, but swapped it for a 600W Corsair when I later added a new GPU. I recognized at the time that 600W was still very low, but the system seemed stable.
When I got up today, I found that the computer was turned off. I booted it and checked the event log, which showed no signs of struggle and no bugcheck, just the "the previous system shutdown was unexpected" message.
However, just a few minutes ago, while I was using it (not for anything unordinarily strenuous), the screen started looking a bit distorted for a second and then quite literally slowly faded away, as did the lights on my USB-powered devices. It wasn't like pulling the plug, but like literally dropping the voltage to the extremities.
This time, upon booting the PC, it told be that it had suffered a 0x7a STOP. Of course, Microsoft's documentation on this one is unhelpful:
"Stop 0x7A is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware."
In other words, it can be caused by anything at all.
Based on the comically non-abrupt shutdown, do you suppose it's likely a PSU issue from the 110%-rated-wattage load I've been putting on it for a year?
When I got up today, I found that the computer was turned off. I booted it and checked the event log, which showed no signs of struggle and no bugcheck, just the "the previous system shutdown was unexpected" message.
However, just a few minutes ago, while I was using it (not for anything unordinarily strenuous), the screen started looking a bit distorted for a second and then quite literally slowly faded away, as did the lights on my USB-powered devices. It wasn't like pulling the plug, but like literally dropping the voltage to the extremities.
This time, upon booting the PC, it told be that it had suffered a 0x7a STOP. Of course, Microsoft's documentation on this one is unhelpful:
"Stop 0x7A is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware."
In other words, it can be caused by anything at all.
Based on the comically non-abrupt shutdown, do you suppose it's likely a PSU issue from the 110%-rated-wattage load I've been putting on it for a year?
Facebook
Twitter
Instagram