HELP! Freezing Custom Desktop

essenbe · 10 Feb 2015

No problem, Mr. Bear.

Anak · 10 Feb 2015

My pleasure Layback Bear.

Loxley · 11 Feb 2015

Anak said:

Hi Loxley, welcome to 7F! :)

I looked in your msinfo32 report and saw:
PCI Simple Communications Controller PCI\VEN_8086&DEV_8CBA&SUBSYS_85341043&REV_00\3&11583659&0&B0 The drivers for this device are not installed. Under Problem devices.
In the Windows Error Reporting area you're having problems with Steam, and I believe software called rogame?

One other major problem you're showing is there are errors with Windows Updates.
With those update problems use this to upload your .cbs logs to this thread don't start a new one like it says in step5, see step4 to see how to get the .cbs logs: Windows Update Posting Instructions

It would be nice to have some type of .dmp file even a minidump.
Check to see if you have your machine set to record them use this to set for a small .dmp see option1 step6: Dump Files - Configure Windows to Create on BSOD

If it's already set that way, use this to find them and upload them in your next post: Dump Files - Upload to SevenForums

I have had that PCI Simple Communications Controller driver issue for as long as I can remember.. not entirely sure what to do about it, but it predates even the current upgraded system I'm using, and back then, I never had these freezing problems, so I think that's unrelated.

Interestingly, I haven't much trouble with the game you mentioned. It rarely freezes when I play it.

I just downloaded that Windows Hotfix - thank you.

I do have some dmp files already (they were set for kernel, not small though), so I am uploading those here. Hope that helps, let me know if I should still proceed with small .dmp

essenbe said:

If you are overclocking anything, set everything back to default level.

Nothing has been overclocked, so that eliminates that.

Thank you!

Anak · 11 Feb 2015

You had 21 .dmp reports from Dec. 20, 2014 to Jan. 05 2015 and they all point to:

Code:

********************************************************************
*                                                                  *
*                        Bugcheck Analysis                         *
*                                                                  *
********************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa800b7e44e0, fffff8800f7f1530, 0, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+14f530 )

Followup: MachineOwner

Which means your video card.

http://Error Code 117 | www.carrona.org

Related Links:
STOP 0x116: VIDEO_TDR_ERROR troubleshooting See the link to Nvidia Statement on TDR errors and the quote in usasma first post.

This is essenbe's tutorial if he see's my post he will probably stop by after you rerun the furmark test.
NVIDIA Drivers - Avoid Problems

Rerun the furmark test, only this time run it longer than 20" more like a couple/few hours and monitor the temps until you see them level out. Use your machine as you normally would and see if it crashes. Report the max temps your seeing in your next post. If you can, upload some screenshots of furmark while the test is in progress especially your max temps screen/tab.

Loxley · 15 Feb 2015

Anak,

I ran the furman test for about 2 hours. Here's the results:

Anak · 15 Feb 2015

Your max temp of 105°C (221oF) matches the max temp for the card so it should be okay, but it's always nice to have a buffer of, lets say 10 to 15°'s less.

Did you get to read the first link under related?
From: nvidia

We also recommend that customers look carefully into the wide range of other causes of TDR issues such as overclocked components, incorrect component compatibility and settings (especially memory configuration and timings), defective parts (memory modules, motherboards, etc.), insufficient system cooling, and insufficient system power. Throughout the forums, there are numerous reports of hardware solutions to TDRs.

You've already replaced the MB and PS so you could try looking to see if there are problems there.

Since this is sleep related, can you look in the BIOS and see what sleep state its set at? If its S3 already try S4, Don't use S1 or S2 if, their available.

Loxley · 15 Feb 2015

Anak said:

Your max temp of 105°C (221oF) matches the max temp for the card so it should be okay, but it's always nice to have a buffer of, lets say 10 to 15°'s less.

Did you get to read the first link under related?
From: nvidia

We also recommend that customers look carefully into the wide range of other causes of TDR issues such as overclocked components, incorrect component compatibility and settings (especially memory configuration and timings), defective parts (memory modules, motherboards, etc.), insufficient system cooling, and insufficient system power. Throughout the forums, there are numerous reports of hardware solutions to TDRs.

You've already replaced the MB and PS so you could try looking to see if there are problems there.

Since this is sleep related, can you look in the BIOS and see what sleep state its set at? If its S3 already try S4, Don't use S1 or S2 if, their available.

I did read that. I'm still skeptical if this is an overheating issue.. sometimes it freezes before windows finishes loading. It almost always freezes within the first few minutes of use and seems to become more stable over time - quite the opposite I'd imagine if there was a heat problem. I am equally skeptical it's a sleep issue as it also happens when powering up from a shut down. I should also note that I'm not getting blue screens, it's just a freeze.

Still, I suppose I should try a different graphics card. I'd just hate to spend money throwing random solutions at a wall to see what sticks.

essenbe · 15 Feb 2015

You are also showing a lot of errors with Google Update and ProTools.

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Loxley · 17 Feb 2015

essenbe said:

You are also showing a lot of errors with Google Update and ProTools.

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Good news: I ran it the first time - it fixed errors. The second time it said there were none. We'll see if that fixes it.

essenbe · 17 Feb 2015

Hopefully it will. I think you also need to do something with Google update and ProToolls.. Thet are giving you a lot of errors too. Keep us informed about how things are going.