System Freeze: Only when I come back to computer

dinglesniff · 23 Jul 2013

Thanks for your help, I am not reluctant, I ordered a new PSU to see if this potentially is an issue as I rolled back mainboard defaults and I am not upgrading the GPU at all.

Arc said:

Two BSODs.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80056407f0, fffff80000b9c518, fffffa8005eedb40}

Unable to load image \SystemRoot\System32\Drivers\RtsUStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtsUStor.sys
*** ERROR: Module load completed but symbols could not be loaded for RtsUStor.sys
*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys
Probably caused by : nusb3hub.sys

Followup: MachineOwner
---------

It is a particular issue happens when the computer is idle, or goes to sleep. During the Sleep-Wake up power transition, a driver fails the power state. So I suggested you to update the Renesas USB 3.0 Host Controller Driver .... not sure what actually you have done.

My suggestions for this issue .....

Search for appropriate driver in Support/Design | Renesas Electronics
Disable Realtek USB Card Reader in device manager.
Disable USB Selective Suspend.
USB Selective Suspend - Turn On or Off

I went to Station Drivers as suggested and have installed the latest drivers
http://www.station-drivers.com/page/...a-x58a-ud5.htm

Arc said:

And the second BSOD .....

Code:

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000094, fffff88005239045, fffff8800c7fa478, fffff8800c7f9cd0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+1045 )

Followup: MachineOwner
---------

Display ... from the very beginning which is continuing. And with your level of overclocking, which as worked stable for that long and so you are not willing to revert ....

Code:

CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 3969

I am sorry to say, but nothing will help you. Even your attempt to roll back the display driver .....

Code:

fffff880`05238000 fffff880`05d19000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon May 13 00:39:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

...... will not be able to do anything for you.

You are not as lucky as the Titan here ... I am sorry to say.

I am sorry I am not understanding correclty, I rolled back to a previous generation drivers, should I try the last beta instead? Or is it possible the Platinum AX860 is the cause?

My system has been stable for years with the 1GHZ overclock and I have not had any issues. I have set the Titan to the default settings, but it should be able to Overclock. One titan had the same O/C and had little issues...[

And, I am concluding that, if you are ready to accept the suggestions, let us know. If you are reluctant even now, I am not seeing any real reason to continue with this issue.

Your computer ... your decision.

I really appreciate your help, you are correct the mainboard had loaded my old saved bios on the last reboot, and I had issues immediately after. I reverted again to the default settings and I am going to let the system idle to see if it makes a difference

Arc · 23 Jul 2013

If you are at stock settings now (GPU, CPU, RAM), use the 349.20 WHQL. See how it goes with there. Then, upon problem, we may take the other steps.

But, first of all, we have to observe how it is running at stock settings, with the latest WHQL driver.

dinglesniff · 08 Aug 2013

Arc said:

If you are at stock settings now (GPU, CPU, RAM), use the 349.20 WHQL. See how it goes with there. Then, upon problem, we may take the other steps.

But, first of all, we have to observe how it is running at stock settings, with the latest WHQL driver.

Hey I ran it at stock, non stock and the same issues occurred on my new windows install. It seems to have to deal with the monitors. When I turn them off only when running something graphics intensive (think game on idle like TF2 farming), video editing, the computer crashes.

Event viewer wise, I have turned off superfetch so we can ignore the readyboost errors.

Before closing out I get

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

The description for Event ID 1 from source NvStreamSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

NvStreamSvc
Unregistering VAD endpoint [0]

Arc · 08 Aug 2013

Now you should use another GPU to test the situation. If you have one that you can use for a couple of days, or in the family or with the friends, get it. Apply it and see if it is causing the same error there.

dinglesniff · 08 Aug 2013

I sadly don't but I just booted to an old image to see if that is an issue. I ran sfc /scannow and I got
Windows Resource Protection found corrupt files but was unable to fix some of them.

Any ideas?

Arc · 08 Aug 2013

Doing random things will not help you to resolve the issue. The problem is with the GPU hardware apparently, so you need to concentrate there.

dinglesniff · 08 Aug 2013

I am not so convinced it is a hardware issue, since the first issue was a power supply. Then the problem went away until I started benchmarking the system.

But I wonder if the issue may be part of the sfc /scannow logs were seeing. Any idea what or how to fix it?

NoelDP · 12 Aug 2013

Sorry about the delay....
Here are some of the errors from the CBS log - the SFC details don't give the full story.

Code:

 Line 1535: 2013-08-08 13:50:05, Error                 CSI    000000a3 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167028# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x138c970->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[122]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-comctl32-v5.resources_31bf3856ad364e35_6.1.7600.16385_hu-hu_a8b2089d86ece2f0"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x138c950, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
 Line 1537: 2013-08-08 13:50:05, Error                 CSI    000000a4@2013/8/8:17:50:05.194 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
 Line 1539: 2013-08-08 13:50:05, Error                 CSI    000000a5 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167027# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
 Line 1540: 2013-08-08 13:50:05, Error                 CSI    000000a6 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167026# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x138d268->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft-windows-comctl32-v5.resources_31bf3856ad364e35_6.1.7600.16385_hu-hu_a8b2089d86ece2f0"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
 Line 1542: 2013-08-08 13:50:05, Error                 CSI    000000a7 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167012# from PrimitiveInstaller::CCoordinator::RepairComponent(Component = Microsoft-Windows-Comctl32-v5.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"hu-HU", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral)[gle=0xd0000034]

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your SkyDrive Public folder so I can take a look - post a link in your reply.

dinglesniff · 12 Aug 2013

NoelDP said:

Sorry about the delay....
Here are some of the errors from the CBS log - the SFC details don't give the full story.

Code:

 Line 1535: 2013-08-08 13:50:05, Error                 CSI    000000a3 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167028# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x138c970->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[122]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-comctl32-v5.resources_31bf3856ad364e35_6.1.7600.16385_hu-hu_a8b2089d86ece2f0"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x138c950, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
 Line 1537: 2013-08-08 13:50:05, Error                 CSI    000000a4@2013/8/8:17:50:05.194 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
 Line 1539: 2013-08-08 13:50:05, Error                 CSI    000000a5 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167027# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
 Line 1540: 2013-08-08 13:50:05, Error                 CSI    000000a6 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167026# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x138d268->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft-windows-comctl32-v5.resources_31bf3856ad364e35_6.1.7600.16385_hu-hu_a8b2089d86ece2f0"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
 Line 1542: 2013-08-08 13:50:05, Error                 CSI    000000a7 (F) STATUS_OBJECT_NAME_NOT_FOUND #1167012# from PrimitiveInstaller::CCoordinator::RepairComponent(Component = Microsoft-Windows-Comctl32-v5.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"hu-HU", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral)[gle=0xd0000034]

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your SkyDrive Public folder so I can take a look - post a link in your reply.

Will do that now this was the last dump I got from the shut down

Ok I downloaded it and get this error when I go to run it. I downloaded:
Windows6.1-KB947821-v27-x64

Error:
Installer encountered an error 0x8007000d
The data is invalid.

Any ideas?