freezing up after sleep mode

I have a Toshiba R700 PT31OA-05NO1 laptop and I am experiecing a freezing problem after I wake the computer form sleep mode: I put it into sleep mode (in the shut down options), later I wake it my pressing the power button, I type in my password, and when I press ENTER it freezes, cursor stops flashing, and I have to hard shut down to get it going again.

I running windows 7 in 64 bit. The freeze occurs about one time out of five.

Any suggestions as to what might be the problem?

The first suspect with Sleep issues is the display driver. Check optional Windows Updates or the Support Downloads webpage for your computer or display adapter model for a newer or different driver to try. Uninstall the driver in Device manager to reinstall it.

Study the logs and other resources to see if you can detect the cause: Win7 troubleshooting fundamentals

If those steps don't help, run a trace to find what is causing the problem: Trace Windows 7 boot/shutdown/hibernate/standby/resume issues - MSFN Forum

I have run the trace as per your instructions, and am now faced with a series of graphs that I don't know how to interpret...

Read the tutorial on how to interpret the charts. You can also PM the trace's expert Cluberti to look at your file if you zip it up and post it via a file sharing link.

I tried the tutorial, but nothing there correlates (in my mind and its very limited experience in such matters), so I think I'll go with the latter suggestion. I've zipped the file now, but can you please tell me how I go about sharing it with Cluberti please? Forgive my ignorance!

I've added Cluberti to my contact list but don't know how to contact him. I don't seem to have permission to PM (whatever that is). Can anyone help me with this please?

I just seem to have been abandoned. This is very disappointing.

Hi Crowblue,

Everyone here volunteers their free time, and it may just be that people are/were too busy to answer your query. I'll ask Cluberti if he can help you with this.

In the menatime, can you please confirm that you have downloaded and installed the latest display driver.

Regards,
Golden

Go to Event Viewer (just type Event Viewer in Start Search Box), head to Windows Log >> Application Tab
Check for critical errors (they have red in the left column) that say app crash, app hang, or anything relating to the problem.
When you find them please note the event ID and source code and tell us what they are.

Thanks Golden. Yes I believe I have downloaded the latest display driver.

DeanP - the log immediately preceding the one that registers my hard shut down today to get out of the freeze doesn't seem to relate to the problem. Here are the specs anyway:

source: e1kexpress

event id: 27

The logs - I had to create a custom folder for them because there was nothing to see before, don't seem to register the error at all as far as I can see, only the forced shutdown in response to the problem.

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

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

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

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.

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.