freezing up after sleep mode

Page 2 of 2 FirstFirst 12

  1. Posts : 2,528
    Windows 10 Pro x64
       #11

    Can you upload the .etl file the trace created (compressed in a .zip or .rar first, of course) to a file sharing site?
      My Computer


  2. Posts : 2,566
    Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
       #12

    Do you have Intel(R) 82567LM-3 Gigabit Network Connection on your computer? If so, that's the reason why it is freezing up your system.

    e1kexpress (27) = Event ID 27 Source e1kexpress
      My Computer


  3. Posts : 17
    Windows 7 64 bit
    Thread Starter
       #13

    Dean P - The communication specs on my computer are as follows:

    LAN: Intel® 1Gbit TX Ethernet

    Wireless Communication: 802.11(a/g/n)

    Cluberti - here's the link you're after:

    trace results.zip - 4shared.com - online file sharing and storage - download

    Thanks you both
    Joshua
      My Computer


  4. Posts : 2,528
    Windows 10 Pro x64
       #14

    Well, I did see the total stoppage of just about everything in your trace all at the same time, and the odd thing is, a driver loads just as everything is stopping - avast (aswsnx.sys). The fact that, right as everything is freezing, the avast driver loads.... frankly, that's very, very suspicious. What is happening is that once the system is up, it looks like explorer.exe is parsing your E: drive, specifically the Music folder - this consumes almost 100% of the disk's time, which is fine - CPU usage is normal, etc. However, *as soon as the avast driver loads*, the entire system comes to a halt, CPU time drops to 0% used, 99% idle, and the disks go virtually silent.

    Honestly, if this were my machine, I'd be uninstalling Avast (and making sure the drivers are actually gone after the reboot), and I'd try again to see if the problem continued. This could be a red herring, but it doesn't look like one. Here's the relevant data - the top portion of the graph shows disk activity, and the bottom shows driver load and delay - note that you can see ntfs and filter manager (ntfs.sys and fltmgr.sys, respectively) get called multiple times in sequence, which means a driver is loading (and the disk is being hit to load it) - what comes after is the avast driver, which is the *very* last activity in the trace you took. Again, it *could* be a red herring, but it's not likely.

      My Computer


  5. Posts : 17
    Windows 7 64 bit
    Thread Starter
       #15

    Cluberti

    Thanks for your help. Since Avast is otherwise a good program I'll try disabling the automated scans that the program has been performing at boot time and system start-up first. If the problem persists, I'll do as suggest, and uninstall the program, drivers and all.

    Thanks again.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 04:50.
Find Us