System Crashes When Sleeping

Page 1 of 2 12 LastLast

  1. Posts : 7
    Win 7 64 bit Home Premium
       #1

    System Crashes When Sleeping


    Hello,

    First off, please find the attached package of reports and images. My signature will have the specs of my system. If you have any questions feel free to ask.

    Quite simply put: At times (60 percent) when my system sleeps (screen is black) it crashes and is unresponsive. I have to reboot, then have Windows start normally.

    I have had windows catch a BSOD and issue a notice but that is very rare (report is in the attached docs).

    I've been following this community for a while and have gained a lot of info. Also I downloaded and have used an awesome program called SF Diagnostic Tool which is where most of the attached info is from.

    Any help is appreciated.

    My Name is Kevin.
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    The most noticeable error is a STOP 0x116. This involves your video card. Please see this topic for troubleshooting suggestions: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

    FWIW - I had system crashes while sleeping with the Win7 beta - Microsoft helped to troubleshoot it and we assumed it was either due to storage drivers (to include RAID drivers) - or video issues. None of this fixed my system and nothing helped until I upgraded my mobo on a hunch!

    Also try this:
    OLDER DRIVERS PRESENT IN THE DUMP FILES
    - Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
    - Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
    - DO NOT use Windows Update or the Update Drivers function of Device Manager.
    - Please feel free to post back about any drivers that you are having difficulty locating.
    - Windows Update exceptions may be noted below for Windows drivers:
    Code:
    
    jraid.sys            Wed Nov 24 22:27:17 2010 (4CEDD795)
    3wareDrv.sys         Tue Mar 24 21:31:37 2009 (49C98979)
    amdxata.sys          Fri Mar 19 12:18:18 2010 (4BA3A3CA) - Windows Update will take care of this if it's available
    PxHlpa64.sys         Mon Dec 10 18:49:01 2007 (475DD06D)
    timntr.sys           Wed Jun 02 08:56:47 2010 (4C06550F)
    snapman.sys          Thu Nov 11 06:05:10 2010 (4CDBCDE6)
    tdrpm273.sys         Tue Aug 10 05:54:18 2010 (4C6121CA)
    Rt64win7.sys         Thu Feb 26 04:04:13 2009 (49A65B0D)
    wacomvhid.sys        Mon Sep 21 19:29:14 2009 (4AB80C4A)
    wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
    wacmoumonitor.sys    Fri Oct 29 12:30:06 2010 (4CCAF68E) - Wacom HID Mouse Monitor Filter Driver
    LHidFilt.Sys         Tue Aug 24 13:21:36 2010 (4C73FFA0)
    LMouFilt.Sys         Tue Aug 24 13:21:43 2010 (4C73FFA7)
    adfs.SYS             Thu Jun 26 16:52:37 2008 (48640195)
    afcdp.sys            Thu Nov 18 11:20:02 2010 (4CE55232)
    avgldx64.sys         Tue Dec 07 21:01:55 2010 (4CFEE713)
    avgtdia.sys          Fri Nov 12 06:08:42 2010 (4CDD203A)
    avgmfx64.sys         Mon Sep 06 20:49:14 2010 (4C858C0A)
    AVGIDSEH.Sys         Mon Sep 13 18:46:38 2010 (4C8EA9CE)
    avgrkx64.sys         Mon Sep 06 20:49:37 2010 (4C858C21)
    AVGIDSFilter.Sys     Tue Aug 03 18:23:21 2010 (4C5896D9)
    AVGIDSDriver.Sys     Tue Aug 03 18:24:45 2010 (4C58972D)
    
    http://www.carrona.org/dvrref.html#jraid.sys
    http://www.carrona.org/dvrref.html#3wareDrv.sys
    http://www.carrona.org/dvrref.html#amdxata.sys
    http://www.carrona.org/dvrref.html#PxHlpa64.sys
    http://www.carrona.org/dvrref.html#timntr.sys
    http://www.carrona.org/dvrref.html#snapman.sys
    http://www.carrona.org/dvrref.html#tdrpm273.sys
    http://www.carrona.org/dvrref.html#Rt64win7.sys
    http://www.carrona.org/dvrref.html#wacomvhid.sys
    http://www.carrona.org/dvrref.html#wacommousefilter.sys
    http://www.carrona.org/dvrref.html#LHidFilt.Sys
    http://www.carrona.org/dvrref.html#LMouFilt.Sys
    http://www.carrona.org/dvrref.html#adfs.SYS
    http://www.carrona.org/dvrref.html#afcdp.sys
    http://www.carrona.org/dvrref.html#avgldx64.sys
    http://www.carrona.org/dvrref.html#avgtdia.sys
    http://www.carrona.org/dvrref.html#avgmfx64.sys
    http://www.carrona.org/dvrref.html#AVGIDSEH.Sys
    http://www.carrona.org/dvrref.html#avgrkx64.sys
    http://www.carrona.org/dvrref.html#AVGIDSFilter.Sys
    http://www.carrona.org/dvrref.html#AVGIDSDriver.Sys
    If all of this doesn't help, please post back and we'll try Driver Verifier according to these instructions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052011-28033-01.dmp]
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Fri May 20 23:02:38.942 2011 (UTC - 4:00)
    System Uptime: 0 days 2:11:25.269
    *** 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+164520 )
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    Bugcheck code 00000116
    Arguments fffffa80`084f8010 fffff880`0f375520 00000000`00000000 00000000`00000002
    BiosVersion = F6
    BiosReleaseDate = 11/14/2008
    CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz"
    MaxSpeed:     2660
    CurrentSpeed: 2666
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050711-13322-01.dmp]
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Sat May  7 20:39:34.410 2011 (UTC - 4:00)
    System Uptime: 0 days 10:58:52.737
    Probably caused by : ntkrnlmp.exe ( nt!IopSynchronousServiceTail+7b )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_0x50_nt!IopSynchronousServiceTail+7b
    Bugcheck code 00000050
    Arguments fffff87f`f1f49a80 00000000`00000000 fffff800`031db69b 00000000`00000005
    BiosVersion = F6
    BiosReleaseDate = 11/14/2008
    CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz"
    MaxSpeed:     2660
    CurrentSpeed: 2666
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042511-15350-01.dmp]
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Debug session time: Mon Apr 25 15:18:19.320 2011 (UTC - 4:00)
    System Uptime: 0 days 7:16:15.647
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  sidebar.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 00000000`00000000 fffff880`07c70e20 00000000`00000000
    BiosVersion = F6
    BiosReleaseDate = 11/14/2008
    CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz"
    MaxSpeed:     2660
    CurrentSpeed: 2666
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      
      
      My Computer


  3. Posts : 7
    Win 7 64 bit Home Premium
    Thread Starter
       #3

    USASMA,
    Thank you so much for the quick reply.
    I will need to work through the list and employ the fixes.

    Regarding the drivers: I will need to work through the hyperlinks and locate the appropriate drivers, then just run the executables?
    Should I do restore points between each or are they pretty straightforward and could just do them all at once?
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    You'll just have to run the executables for the driver installation package
    Just set a system restore point before you start, and one after each reboot (while installing drivers). This is overkill, but it'll be the safest way until the system is up and running properly.

    For example, these 3 drivers are from Acronis. So when you remove/update the program they'll all be updated:
    timntr.sys Wed Jun 02 08:56:47 2010 (4C06550F)
    snapman.sys Thu Nov 11 06:05:10 2010 (4CDBCDE6)
    tdrpm273.sys Tue Aug 10 05:54:18 2010 (4C6121CA)
    And these 7 are from AVG, so they'll be removed/updated when you remove/update that program:
    avgldx64.sys Tue Dec 07 21:01:55 2010 (4CFEE713)
    avgtdia.sys Fri Nov 12 06:08:42 2010 (4CDD203A)
    avgmfx64.sys Mon Sep 06 20:49:14 2010 (4C858C0A)
    AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE)
    avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21)
    AVGIDSFilter.Sys Tue Aug 03 18:23:21 2010 (4C5896D9)
    AVGIDSDriver.Sys Tue Aug 03 18:24:45 2010 (4C58972D)
      My Computer


  5. Posts : 7
    Win 7 64 bit Home Premium
    Thread Starter
       #5

    Hi USASMA,
    I hope you don't mind, but I have to tackle this issue in chunks of available time.
    The problem was getting worse.
    Last night I uninstalled video drivers and reinstalled the latest from evga. I didn't install the utilities just the necessary drivers.
    Then I ran Memtest86 over night and got the following results (captured by my phone).
    Pass:4 Errors 20 (That's bad. right?)

    Based on this result. Can I assume that the RAM is bad? What about the MOB?

    Thanks,
    Kevin
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #6

    This is most likely bad RAM - but it can be bad other things (such as the mobo).
    To tell, run the stuff after step 6 at this link: http://www.carrona.org/memdiag.html (read the details at the link)
      My Computer


  7. Posts : 7
    Win 7 64 bit Home Premium
    Thread Starter
       #7

    ok so I have been testing RAM for the last 24 hours.
    Of 4 sticks (4X2Gb DDR2 PC2-8500 | 1066MHz | 2.1v | Patriot) only 1 worked without errors.
    The one good stick i placed in each individual slot and let go for at least 4 passes each without any errors (red line items in the lower half of the screen)
    ****However*** on two such occasions when I came back to check on it the screens had wierd artifacts (see screen shots) once I restarted the test in the same slot and didn't see the artifacts again. In neither case the test didn't stop and there were not red line items in the lower portion of the screen and I could exit without any problems.

    Obviously the RAM is bad. the question is What's up with the wierd stuff on the screen?
    Could it be the mobo and/or Video card?
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    First check for overheating. I use Speedfan (free from here: Download SpeedFan - Access temperature sensor in your computer )

    Then try these free stress tests:
    FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    NOTE: Set the alarm to go off at 90บC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
    - Click "Quit" to exit
    Prime95 download site: Free Software - GIMPS
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    This won't necessarily crash the system - but check the output in the test window for errors.
    The Test selection box and the stress.txt file describes what components that the program stresses.
    More details on the use of this test: Torture test your CPU with Prime95
    Two other video stress tests (may be more stressful than FurMark):
    Video Memory stress Test - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / VMT
    Artifact Locator - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / Artifact Locator
    Sorry, but I don't read the language that this website is made in.
    Another interesting test that just came to my attention: Download - OCCT Website english
    USE AT YOUR OWN RISK - program doesn't have a whole bunch of safety features to protect you from yourself!
      My Computer


  9. Posts : 5,705
    Win7 x64 + x86
       #9

    - duplicate post -
      My Computer


  10. Posts : 7
    Win 7 64 bit Home Premium
    Thread Starter
       #10

    ok, here is where we are at.
    I did the above tests with the questionable RAM and the CPU and Video card held up exceptionally.
    So I went to Frys and bought 2 sticks of new RAM Kingston 4GB (2x2GB) DDR2 unopened. Did a Memtest on them for 5 hours and no errors appeared.
    So at this point I am going to run the machine as I would normally run it and see if the crashing problem returns. Either way I will repost by Wednesday 6/3/2011 with the results.
    Hopefully the new RAM is the ticket.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

ฉ Designer Media Ltd
All times are GMT -5. The time now is 01:33.
Find Us