Classic Shell http://www.classicshell.net/forum/ |
|
Issue with Classic Shell - Explorer.exe Crash http://www.classicshell.net/forum/viewtopic.php?f=12&t=7257 |
Page 1 of 1 |
Author: | DylanDuffy [ Thu Jan 12, 2017 6:50 am ] | ||
Post subject: | Issue with Classic Shell - Explorer.exe Crash | ||
Hello everyone, I am wondering if I can get some assistance with my classic shell installation here at my work. We installed CS on our Windows 10 & Windows 7 Machines so everywhere would match but all of a sudden it keeps hanging and crashing, I have run a procdump -e and a -n just in case, they are below. Please could someone offer some assistance, thanks ![]() Dylan
|
Author: | DylanDuffy [ Thu Jan 12, 2017 6:58 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
C:\Windows\System32>procdump -e explorer.exe ProcDump v8.2 - Sysinternals process dump utility Copyright (C) 2009-2016 Mark Russinovich and Andrew Richards Sysinternals - www.sysinternals.com Process: explorer.exe (6524) Process image: C:\windows\explorer.exe CPU threshold: n/a Performance counter: n/a Commit threshold: n/a Threshold seconds: n/a Hung window check: Disabled Log debug strings: Disabled Exception monitor: Unhandled Exception filter: [Includes] * [Excludes] Terminate monitor: Disabled Cloning type: Disabled Concurrent limit: n/a Avoid outage: n/a Number of dumps: 1 Dump folder: C:\Windows\System32\ Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS Queue to WER: Disabled Kill after dump: Disabled Press Ctrl-C to end monitoring without terminating the process. [13:35:16] Exception: 000006BA [13:35:16] Exception: 000006BA [13:35:16] Exception: 000006BA [13:35:31] Exception: 000006BA [13:36:01] Exception: 000006BA [13:36:01] Exception: 000006BA [13:36:01] Exception: 000006BA [13:36:16] Exception: 000006BA ^C [13:36:44] Dump count not reached. and also this C:\windows\system32>procdump -n 20 -s 1 explorer.exe ProcDump v8.2 - Sysinternals process dump utility Copyright (C) 2009-2016 Mark Russinovich and Andrew Richards Sysinternals - www.sysinternals.com Process: explorer.exe (1372) Process image: C:\windows\explorer.exe CPU threshold: n/a Performance counter: n/a Commit threshold: n/a Threshold seconds: 1 Hung window check: Disabled Log debug strings: Disabled Exception monitor: Disabled Exception filter: [Includes] * [Excludes] Terminate monitor: Disabled Cloning type: Disabled Concurrent limit: n/a Avoid outage: n/a Number of dumps: 20 Dump folder: C:\windows\system32\ Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS Queue to WER: Disabled Kill after dump: Disabled Press Ctrl-C to end monitoring without terminating the process. [13:37:29] Timed: [13:37:29] Dump 1 initiated: C:\windows\system32\explorer.exe_170112_133729.dmp [13:37:29] Dump 1 complete: 4 MB written in 0.2 seconds [13:37:31] Timed: [13:37:31] Dump 2 initiated: C:\windows\system32\explorer.exe_170112_133731.dmp [13:37:31] Dump 2 complete: 4 MB written in 0.2 seconds [13:37:33] Timed: [13:37:33] Dump 3 initiated: C:\windows\system32\explorer.exe_170112_133733.dmp [13:37:33] Dump 3 complete: 4 MB written in 0.2 seconds [13:37:35] Timed: [13:37:35] Dump 4 initiated: C:\windows\system32\explorer.exe_170112_133735.dmp [13:37:35] Dump 4 complete: 4 MB written in 0.2 seconds [13:37:37] Timed: [13:37:37] Dump 5 initiated: C:\windows\system32\explorer.exe_170112_133737.dmp [13:37:38] Dump 5 complete: 5 MB written in 0.2 seconds [13:37:40] Timed: [13:37:40] Dump 6 initiated: C:\windows\system32\explorer.exe_170112_133740.dmp [13:37:40] Dump 6 complete: 5 MB written in 0.2 seconds [13:37:42] Timed: [13:37:42] Dump 7 initiated: C:\windows\system32\explorer.exe_170112_133742.dmp [13:37:42] Dump 7 complete: 5 MB written in 0.2 seconds [13:37:44] The process has exited. [13:37:44] Dump count not reached. C:\windows\system32> |
Author: | Ivo [ Thu Jan 12, 2017 8:15 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
According to the output from procdump, there is no crash. The explorer.exe process keeps running. Are you certain explorer is the one that crashes? |
Author: | DylanDuffy [ Thu Jan 12, 2017 8:26 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
Ivo wrote: According to the output from procdump, there is no crash. The explorer.exe process keeps running. Are you certain explorer is the one that crashes? Hi, Yes I click the start button - nothing happens and then explorer freezes and windows asks me to close or restart it. Dylan |
Author: | Ivo [ Thu Jan 12, 2017 8:36 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
You need to create a crash dump after explorer is frozen. Is that the case with these dumps? |
Author: | DylanDuffy [ Thu Jan 12, 2017 8:57 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
Ivo wrote: You need to create a crash dump after explorer is frozen. Is that the case with these dumps? Hi, I run proc dump then click start menu button, it then freezes + crashes and then i finish the dump Is that not right? |
Author: | Ivo [ Thu Jan 12, 2017 9:18 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
You are trying to open "My Network Places", and there is some server there that doesn't respond quickly enough. The server may be named "helios". |
Author: | DylanDuffy [ Thu Jan 12, 2017 9:21 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
Ivo wrote: You are trying to open "My Network Places", and there is some server there that doesn't respond quickly enough. The server may be named "helios". Ok interesting, how can I remove my network places from it? Thanks!! |
Author: | DylanDuffy [ Thu Jan 12, 2017 9:31 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
Ivo wrote: You are trying to open "My Network Places", and there is some server there that doesn't respond quickly enough. The server may be named "helios". I set a CNAME to move helios to a different server - will update. |
Author: | moopere [ Wed Feb 01, 2017 12:37 am ] |
Post subject: | Re: Issue with Classic Shell - Explorer.exe Crash |
Hello OP, I suspect your freezing issue is very similar to this one: viewtopic.php?f=12&t=5954 I have not been able to find a solution and have been forced to stop Classic Menu from automatically starting at login. This leaves users with the standard Win10 menu (ugh!) but for most end users its just something that they have to suffer for now. Since doing this I've not had any more explorer crashes and the systems are working fine - end users are benefiting from using Classic Explorer and, for a few willing to deal with the crashing, they have the option to switch on Classic Menu for their profile only. If you find a solution there are several people (at least) who would be most interested to know - so please report back if you have some success. |
Page 1 of 1 | All times are UTC - 8 hours [ DST ] |
Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |