It is currently Fri Apr 19, 2024 7:27 am

All times are UTC - 8 hours [ DST ]


Forum rules


Before posting a bug report or a feature request, search the forum for an older post on the same topic. If you are reporting a crash, try capturing a crash dump. You can find instructions here: How to capture crash dumps



Post new topic Reply to topic  [ 35 posts ] 
Author Message
PostPosted: Wed Apr 02, 2014 6:07 am 
Offline
User avatar

Joined: Wed Apr 02, 2014 5:49 am
Posts: 31
After installing Classic Shell v4.0.5, Explorer would crash upon launch just about every time.

Here's some event logs:

Quote:
Faulting application name: Explorer.EXE, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process ID: 0x568
Faulting application start time: 0x01cf4dde4fe0d704
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: unknown
Report ID: ba634f59-b9d1-11e3-83d8-6805ca1eeee0
Faulting package full name:
Faulting package-relative application ID:


Quote:
Faulting application name: explorer.exe, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: ClassicExplorer64.dll_unloaded, version: 4.0.5.0, time stamp: 0x5338c5c9
Exception code: 0xc0000005
Fault offset: 0x000000000000a360
Faulting process ID: 0xeac
Faulting application start time: 0x01cf4dde7ced9a9c
Faulting application path: C:\Windows\explorer.exe
Faulting module path: ClassicExplorer64.dll
Report ID: 4fdad950-b9d4-11e3-83d8-6805ca1eeee0
Faulting package full name:
Faulting package-relative application ID:


Quote:
Faulting application name: explorer.exe, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: ClassicExplorer64.dll_unloaded, version: 4.0.5.0, time stamp: 0x5338c5c9
Exception code: 0xc0000005
Fault offset: 0x000000000000a360
Faulting process ID: 0x83c
Faulting application start time: 0x01cf4de1124cb7f3
Faulting application path: C:\Windows\explorer.exe
Faulting module path: ClassicExplorer64.dll
Report ID: 1759fac1-b9da-11e3-83d8-6805ca1eeee0
Faulting package full name:
Faulting package-relative application ID:


Quote:
Faulting application name: Explorer.EXE, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process ID: 0x550
Faulting application start time: 0x01cf4de704fd7065
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: unknown
Report ID: 7011ee2f-b9da-11e3-83d9-6805ca1eeee0
Faulting package full name:
Faulting package-relative application ID:


Quote:
Faulting application name: explorer.exe, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process ID: 0x490
Faulting application start time: 0x01cf4de73295123d
Faulting application path: C:\Windows\explorer.exe
Faulting module path: unknown
Report ID: b8659c9d-b9da-11e3-83d9-6805ca1eeee0
Faulting package full name:
Faulting package-relative application ID:


Quote:
Faulting application name: explorer.exe, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: wercplsupport.dll, version: 6.3.9600.16384, time stamp: 0x5215edff
Exception code: 0xc0000005
Fault offset: 0x000000000000a360
Faulting process ID: 0xcc8
Faulting application start time: 0x01cf4de77ad5ad73
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\System32\wercplsupport.dll
Report ID: 13aa792c-b9db-11e3-83d9-6805ca1eeee0
Faulting package full name:
Faulting package-relative application ID:


Quote:
Faulting application name: explorer.exe, version: 6.3.9600.16441, time stamp: 0x5265dec8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process ID: 0x404
Faulting application start time: 0x01cf4de7d6232bde
Faulting application path: C:\Windows\explorer.exe
Faulting module path: unknown
Report ID: 7d9f1ec7-b9db-11e3-83d9-6805ca1eeee0
Faulting package full name:
Faulting package-relative application ID:


--

I went back to Classic Shell v4.0.4, which works just fine.

(Win8.1Pro/x64)


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 6:15 am 
Offline
User avatar

Joined: Thu Jan 03, 2013 12:38 am
Posts: 5374
Try capturing a crash dump with Classic Shell 4.0.5: viewtopic.php?f=12&t=6

_________________
Links to some general topics:

Compare Start Menus

Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 7:34 am 
Offline
User avatar

Joined: Wed Apr 02, 2014 5:49 am
Posts: 31
I caught a crash with ProcDump.
The .dmp file is huge (8.95 MB)!
What on Earth does these files contain?


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 7:39 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
It contains the state of the explorer process. It allows me to see the point of the crash and hopefully deduce the cause.

Zip it and attach it here or drop it in the FileDrop folder at the bottom if this page: http://www.classicshell.net/downloads
If you can make a few more that would be even better.


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 7:46 am 
Offline
User avatar

Joined: Wed Apr 02, 2014 5:49 am
Posts: 31
Yeah, I figured that much.
I just don't understand why it's this big.
It only contains text, right?


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 7:50 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
No, it doesn't contain text. It contains portions of the process memory, information about loaded DLLs, the running threads, the stack for each thread, etc.

BTW, this is a "minidump". A full dump can be multiple gigabytes.


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 7:58 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
BTW, are you the same person as "Szentei Balázs" who posted on Facebook? The symptoms look the same but he's using Windows 8 instead of 8.1


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 8:02 am 
Offline
User avatar

Joined: Wed Apr 02, 2014 5:49 am
Posts: 31
Nope. Different person.


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 8:31 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
So are you going to send me the dump files or not? Without them it is very difficult to even begin to guess what is going on.


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 8:48 am 
Offline
User avatar

Joined: Wed Apr 02, 2014 5:49 am
Posts: 31
Sorry, but I currently don't have anything installed on my computer to open .dmp files.
Nothing against you guys, but I just don't feel comfortable uploading these kind of files without having looked at them first, and edited out any potential personal information.

From the Classic Shell v4.0.5 changelog, I see that you have added the option to pin drives and folders from Explorer.
I have removed the ability to pin programs to both the Taskbar and Start Menu by using the Local Group Policy Editor..
Could this be related?


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 9:03 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
I can assure you that if you drop the file in the mediafire folder or if you send it directly to classicshell@ibeltchev.com nobody but me will have access to it. And I don't care about your data, I care about improving my software.

Minidumps contain the state of the code, not the state of the data. Unless you use the options -ma or -mp, very little data is captured. Also the Explorer process doesn't usually access personal data, especially since it crashes on startup. If you try editing the dmp file you will most likely corrupt it and make it useless.

And besides, NSA probably already has all your data anyway.


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 02, 2014 12:37 pm 
Offline
User avatar

Joined: Thu Jan 03, 2013 12:38 am
Posts: 5374
@Tomaso, The dump file will mostly include data about the state of the Explorer.exe process as it was in memory when it crashed, not your personal data. Beyond finding out what's crashing Explorer.exe, your data is of no interest. :) It may also be a shell extension that's crashing it and not Classic Shell.

_________________
Links to some general topics:

Compare Start Menus

Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.


Top
 Profile  
Reply with quote  
PostPosted: Thu Apr 03, 2014 10:52 am 
Offline

Joined: Thu Apr 03, 2014 10:20 am
Posts: 3
I too have receive a few explorer.exe crashes I uploaded the .dmp file in to your file drop link.


Top
 Profile  
Reply with quote  
PostPosted: Thu Apr 03, 2014 9:57 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
Thanks, boyds. The information from the crash dump is inconclusive, but at least helps eliminate some of the potential causes.

The next step is to determine which Classic Shell component is the cause of the problem. Please temporarily disable the start menu by unchecking "Start automatically for this user" in the General Behavior tab. Log off and see if the crash happens again. If it does then it is not the start menu but most likely by the Classic Explorer component. Save the Classic Explorer settings to XML file and attach it here.


Top
 Profile  
Reply with quote  
PostPosted: Thu Apr 03, 2014 10:06 pm 
Offline

Joined: Thu Apr 03, 2014 9:51 pm
Posts: 3
I am also having this issue. However i'm quite sure it is caused by classic shell considering i just bought this PC today.

I'll try disabling it and see if the crash occurs again.

I've attached a crash dump, just to be sure i'm not having a different issue.


Attachments:
explorer_140404_005006.zip [2.04 MiB]
Downloaded 882 times
Top
 Profile  
Reply with quote  
PostPosted: Thu Apr 03, 2014 10:13 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
Everybody, please elaborate on the circumstances of the crash. What are you doing at the time? Like opening the start menu, clicking on a shortcut on the Desktop (is it a program, a document or a folder?), clicking on the taskbar, or what.


Top
 Profile  
Reply with quote  
PostPosted: Thu Apr 03, 2014 10:22 pm 
Offline

Joined: Thu Apr 03, 2014 9:51 pm
Posts: 3
It crashes when i click on a shortcut. For example, clicking on "This PC" might cause a crash.

This can happen with any of the shortcuts in the start menu.


Top
 Profile  
Reply with quote  
PostPosted: Thu Apr 03, 2014 11:35 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
I was able to isolate the problem and I have a temporary fix. Try the following.

For 32-bit Windows:
1) Download the attached file ClassicExplorer32.zip
2) Go to the Classic Shell installation folder, for example C:\Program Files\Classic Shell
3) Locate the file ClassicExplorer32.dll and rename it to _ClassicExplorer32.dll
4) Extract the ClassicExplorer32.dll from the zip file and place it in the Classic Shell folder
5) Log off and log in

For 64-bit Windows:
1) Download the attached file ClassicExplorer64.zip
2) Go to the Classic Shell installation folder, for example C:\Program Files\Classic Shell
3) Locate the file ClassicExplorer64.dll and rename it to _ClassicExplorer64.dll
4) Extract the ClassicExplorer64.dll from the zip file and place it in the Classic Shell folder
5) Log off and log in

Please report if this fixes the issue. If everything checks out I will release a new official version in the next 24-48 hours

(Note that the DLL fixes are only for Classic Shell 4.0.5. Later versions include the fix)


Attachments:
ClassicExplorer32.zip [298.71 KiB]
Downloaded 905 times
ClassicExplorer64.zip [329.35 KiB]
Downloaded 1151 times
Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 7:14 am 
Offline

Joined: Sat Dec 21, 2013 3:23 pm
Posts: 17
OK, thanks.

I left it running overnight, with the procdump running, but this morning the problem didn't occur.


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 7:17 am 
Offline

Joined: Thu Apr 03, 2014 10:20 am
Posts: 3
Thanks for the new .DLL files.

So far so good, no crashes.

However (maybe by intention) the items launched off of the start bar, seem to lag about 1-2 seconds more than before.


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 7:36 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
The change is very minor and has nothing to do with launching stuff.
When you say "start bar" do you mean "start menu", "task bar" or maybe "start screen"?


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 7:43 am 
Offline
User avatar

Joined: Wed Apr 02, 2014 5:49 am
Posts: 31
Yes, you seem to have fixed it! :)
No crashes anymore.
Thanks a lot.
Sorry for being difficult about the dump file.

I'm not sure what boyds is talking about, but I'm not noticing any lag.


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 9:00 am 
Offline

Joined: Fri Apr 04, 2014 8:55 am
Posts: 4
Just wanted to let the author know that I too had experienced explorer crashes with 4.0.5. I was only able to fix it by reinstalling W8.1 and using the previous Version. I have been using Classic shell through many versions and this was the 1st time I had a problem.


It also seems to be really noticeable when right clicking and going to the properties, such as 'this pc'.


I am now running on the last version, and everything is working fine.


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 9:04 am 
Offline

Joined: Thu Apr 03, 2014 10:20 am
Posts: 3
It just seems when I click the start menu, select "This PC" it seems it takes just that moment longer to populate the icons in the 'This PC' window (eg: C:\, network shares, etc)


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 9:22 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
gameovr wrote:
It also seems to be really noticeable when right clicking and going to the properties, such as 'this pc'.

I am now running on the last version, and everything is working fine.

The problem is not related to "properties" but to launching Explorer after it was not used for a while. Since the properties for "This PC" actually open an Explorer window instead of the small Properties dialog, it crashes.

When you say that you are running the last version, do you mean the original 4.0.5 or the patch that was uploaded in the previous message?


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 10:24 am 
Offline
User avatar

Joined: Wed Apr 02, 2014 5:49 am
Posts: 31
boyds wrote:
It just seems when I click the start menu, select "This PC" it seems it takes just that moment longer to populate the icons in the 'This PC' window (eg: C:\, network shares, etc)

Try turning off the Windows Search Indexing.


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 10:50 am 
Offline

Joined: Thu Apr 03, 2014 9:51 pm
Posts: 3
I can also confirm that the DLL file fixed the crashes for me too.

As for the lag boyds mentioned, i can't really say since I've only started using classic shell yesterday.

Thanks for the help!


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 7:22 pm 
Offline

Joined: Fri Apr 04, 2014 8:55 am
Posts: 4
Ivo wrote:
gameovr wrote:
It also seems to be really noticeable when right clicking and going to the properties, such as 'this pc'.

I am now running on the last version, and everything is working fine.

The problem is not related to "properties" but to launching Explorer after it was not used for a while. Since the properties for "This PC" actually open an Explorer window instead of the small Properties dialog, it crashes.

When you say that you are running the last version, do you mean the original 4.0.5 or the patch that was uploaded in the previous message?



No, I mean I went back to 4.0.4 and all problems went away. And I do understand that going to properties launches explorer - but it also has nothing to do with being idle or idle time - as explorer crashed repeatedly several times in a row just by launching it by clicking on my pc. It also crashed when selecting mapped drives, where it gave a weird message and even though I had an entered set of credentials via Cred manager - it also wiped out that.


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 7:39 pm 
Offline

Joined: Fri Apr 04, 2014 7:34 pm
Posts: 2
Hi there,


I have been installing classic shell for about a year now on clients windows 8 pcs and just lately every single computer I put it on explorer keeps crashing when you try to open say documents or pictures folder from within the classic shell start button.
Had 3 yesterday and 2 today and all different brands of computer. They were all windows 8.1.
Any idea when a fix for this will be out?


Top
 Profile  
Reply with quote  
PostPosted: Fri Apr 04, 2014 7:41 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
@nathand - try the fix listed here: viewtopic.php?f=12&t=2405&view=unread#p11866


Top
 Profile  
Reply with quote  
PostPosted: Sat Apr 05, 2014 4:37 pm 
Offline

Joined: Fri Apr 04, 2014 7:34 pm
Posts: 2
Thanks for that. I just decided to install 4.0.5 on my own 8.1 computer and sure enough explorer also crashed every time I tried to open folders from within classicshell start.
I just applied the 64 patch as you described above and it worked! All working fine now.
Surely this is not just happening to me though? I'm not doing anything unusual when installing. I download from your site install it and every single persons computer crashes since the release of 4.0.5.


Top
 Profile  
Reply with quote  
PostPosted: Sat Apr 05, 2014 10:54 pm 
Offline
User avatar

Joined: Thu Jan 03, 2013 12:38 am
Posts: 5374
Classic Shell 4.0.6 is released which incorporates the fix for this crash.

_________________
Links to some general topics:

Compare Start Menus

Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.


Top
 Profile  
Reply with quote  
PostPosted: Wed Apr 09, 2014 6:00 pm 
Offline

Joined: Wed Apr 09, 2014 5:31 pm
Posts: 1
I've kind of gotten over the seemingly universal hatred for the Windows 8 navigation changes. However, so many friends, family and clients are having a hard time dealing with it that I have been recommending ClassicShell. And let's face it - the new Windows navigation isn't just bad because it's new - it's bad because it's, well, bad...
After a time, I realized I couldn't answer questions about ClassicShell's use and features because I didn't have it on my own system. So I installed 4.0.5. Had a lot of explorer.exe crashes. No, I can't tell you specifically what triggered it - never noticed, and became impatient and uninstalled and quickly remedied the situation.
Guess I'm not one to give up, figuring I can't continue recommending it if I can't make it work myself. Came across this thread and was pretty impressed at how available the developer is to the masses. Don't see much of that...
Going to install the newly released 4.0.6 and see what happens.

Thanks for being there...


Top
 Profile  
Reply with quote  
PostPosted: Sat May 31, 2014 9:38 am 
Offline

Joined: Sat May 31, 2014 9:33 am
Posts: 1
I am having a similar problem, although it may be a bit different, and I think I've found the cause:
Currently running 4.05 on four different 8.1 computers (mine, wife's, and family) but this issue is only occurring on my main system (real bummer).
What happens is intermittently (not every time), when I open Windows Explorer, there is a significant pause, then explorer crashes, then re-opens. Oddly, when it does this, it turns off Carbonite, McAfee, and a few other programs (strange).
I have found that this happens reliably when I turn on the 'Classic Explorer Bar' feature, and it goes away with same feature turned off - reproducibly.
Has the patch noted above been applied to 4.1?


Top
 Profile  
Reply with quote  
PostPosted: Sat May 31, 2014 9:42 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5333
Yes, version 4.0.5 has a bug that can crash Explorer if you have buttons in the toolbar to toggle the navigation, detail or preview panes.
The bug is specific to version 4.0.5. All other versions don't have the bug.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 35 posts ] 

All times are UTC - 8 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 51 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group, Almsamim WYSIWYG Classic Shell © 2010-2016, Ivo Beltchev.
All right reserved.