First, here's my specs:
OS: Windows 7 64-bit.
CPU: AMD FX-8320 3.5GHz 8-Core Processor
Motherboard: Asus M5A97 R2.0 ATX AM3+ Motherboard
Memory: Crucial Ballistix Sport 16GB (2 x 8GB) DDR3-1600 Memory
Storage: Seagate Barracuda 3TB 3.5" 7200RPM Internal Hard Drive
Video Card: Gigabyte GeForce GTX 750 Ti 2GB WINDFORCE Video Card
Case: Corsair SPEC-03 Red ATX Mid Tower Case
Power Supply: Corsair Builder 600W 80+ Bronze Certified ATX Power Supply
Optical Drive: Lite-On iHAS124-04 DVD/CD Writer
Sound Card (PURCHASED TO-DAY): Asus Xonar DG 24-bit 96 KHz Sound Card
Cooling: friend sent fan that looks like the one on the back of my case, totalling 3 120mm Corsair fans.
I'm having some odd problems of late. This may be a software problem as well, tough to say, but I don't believe it's malware. I'd love some general diagnostic tool should anyone know one. What the PC's done for the second time this week is it's become generally unresponsive, one task at a time, and if I request it shut down, it remains on the blue shutdown screen until I use the physical front panel power button. I left it for an hour this time before hitting the power button. The PC worked fine when I built it a couple weeks ago, internet access apart, which is now sorted thanks to some fine help from the lads here on Bleeping Computer.
I've run fairly extensive malware tests and come up clean with all but Roguekiller, which listed a few 'suspicious' files which I believe are probably no bother, though perhaps I ought to post the log somewhere (suggestions?).
Another odd thing is it takes for ever to get to the log-in screen, though once that happens it runs extremely fast. BIOS is set to delay 3 seconds on powering on, but it's a fair fifteen it waits, and then there's a black screen, then the monitor has no signal for a bit, then there's a black screen with the mouse pointer visilbe, and finally WIndows begins. When the 'Windows is starting' screen is on, it's on for ages as well. I remember when I used Autoruns to disable all the stuff I thought I didn't need it was real fast, but some stuff didn't work so I reticked all the boxes and now it starts slow again. The most worrying bit to me is the monitor (not that I've any knowledge of this stuff, just never seen that before).
When the problem occurred I was doing very resource-heavy music production, the first time, whereafter I restarted and it did not work well at-all, soon enough becoming unresponsive again till I had to shut it down and eventually use the power button again. This was about a week ago. To-day, it was *after* a large amount of time mucking about in my production stuff. When I tried to open a different programme it wouldn't, and then the whole thing happened again.
I do shut down every night and put it to sleep during the day if not in use (the fans do stop when sleeping).
My music software: the DAW is Ableton Live 8, which only does 32-bit. My VSTs require some power, often recommending 8GB of RAM and in one case 16GB (though I've not used that one yet). This could theoretically be the problem. Most of them don't work flawlessly unless used in standalone mode (where you can't save your work, so it doesn't help a composer but rather a performer; I'm not the latter) . The VSTs are East West Quantum Leap.
Whilst playing games, they do a scan of my system on the first time playing, and put themselves on Ultra High settings (the highest available as I understand it), and there's no lagging or any problems whatever. One time, Outlast crashed but I restarted it immediately and played it all night. That is the only problem I've ever had with the games.
Finally, occasionally a piece of the screen will go black but eventually will be grand. The mouse pointer is visible atop the black bits. I believe it may have something to do with Ableton as well. It affects my Windows theme, and on my old laptop Ableton would sometimes be black in some parts of the screen on switching back to it from a different programme, but on that computer the screen was never black outside of Ableton.
Thanks for all help. Sorry that I'm being slightly vague here. I really don't know exactly what's the problem.
EDIT: Using the following programmes my computer's components is generally of a good temperature, approximately 30°C, though they won't open when I'm experiencing the unresponsiveness:
Open Hardware Monitor, Core Temp 64, GPU Temp.
Edited by EPDGaffney, 02 July 2014 - 07:59 PM.