Sign in with
Sign up | Sign in
Your question
Solved

Intermittent hard freeze/crashes, generally while idle. No event viewer details.

Last response: in Components
Share
November 16, 2013 2:07:32 PM

Subject says most of it. My HTPC will occasionally be found in this hard-locked/crashed state when nothing of note was being done. The past couple times, it has been while the screensaver was running over top of the Steam client (not Big Picture, just the normal client) and nothing else of note was running. I've not experienced this crash when watching TV via Windows Media Center, nor when playing Steam games like Dark Souls.

Checking Event Viewer has been fruitless, as no BugChecks or other errors are found, aside from the Kernel Power errors saying the previous shutdown was unexpected. Presumably, whatever happens is happening suddenly enough that the OS doesn't have time to react before it's locked.

I was also getting random reboots with the same level of mystery and non-existent reproduction steps. I turned off the auto-reboot-on-crash feature, so the next time of of those occurs, I should get a legit BugCheck, but I've not had one since to use for troubleshooting.

Image of what I see when this occurs (apologies for the poor quality, taking photos of a TV with a camera phone)


------------
Machine details:

OS: Windows 7
CPU: Intel Pentium G645 2.9GHz
Mobo: H77MU3 LGA 1155 mATX
PSU: OCZ StealthXStream OCZ600SXS 600W
RAM: Ballistix Sport 4GB DDR3-1600
GPU: SAPPHIRE 100355OCL Radeon HD 7850 2GB 256-bit GDDR5 (OC version)
OS SSD: SSDNow V200 SV200S37A/64G 64GB SATA
Media HDD: Barracuda 2TB 7,200 RPM SATA
some SATA DVD burner
some cheap media card reader
some cheap USB3.0 hub that slots into PCI

All hardware is factory-default, no overclocking or other mods done.


------------
Steps already taken:

Thorough dust cleaning with compressed air.
Memtest86+ on each stick of RAM individually. Both passed.


My suspicion is either PSU or GPU, both should be pretty damn healthy, as neither are a year old (both bought in April of this year). How would I test them for faults, especially given the anomalous nature of the error? This is eating away at the Spouse Acceptance Factor of my hand-rolled HTPC, so any tips on getting the stability back on track would be great.
a b ) Power supply
November 17, 2013 5:12:02 AM

avulhop said:

Memtest86+ on each stick of RAM individually. Both passed.


Memtest isn't foolproof too so have you tried it with just one stick of ram at the time doing the normal stuff?
m
0
l
November 17, 2013 12:02:49 PM

I have not because the issue is relatively sporadic. I would be running with 2gigs of RAM for quite a long time before I could definitively say it had any impact. I haven't narrowed down a readily repeatable reproduction process, so that's not a very appealing solution until other paths are exhausted (I hope you understand).

While I know Memtest86+, like any other software, isn't infallible, I think other components are more likely to have issues, since they haven't been health tested like the RAM has.

Frankly, I'm not sure how to health test my SSD, PSU, or MOBO. I can use FurMark to do a burn-in on my GPU and Prime95 to burn-in my CPU when the HTPC isn't in use later (hockey game on right now).


Vic 40 said:
avulhop said:

Memtest86+ on each stick of RAM individually. Both passed.


Memtest isn't foolproof too so have you tried it with just one stick of ram at the time doing the normal stuff?

m
0
l

Best solution

a b ) Power supply
November 17, 2013 12:22:07 PM

You could check the ssd with the next program afaik,
http://www.hdtune.com/download.html
you can do the error scan or check the health/smart values.

With the next program you can make a log which you can read with either excel or libre office calc,
hwinfo32
open it,check=V sensors and click run,next on the bottom click "logging start",choose a name and location for the log->for instance hwlog on the desktop.You can let it log for a while after that,half an hour minimum, and even do some stresstests.When done like i said you can look through the log with the before mentioned programs.You can then see if there are weird values,for the psu for example,wonky rails or under the atx specs,for the cpu and gpu temps etc.
Share
!