Classic Shell
http://www.classicshell.net/forum/

Crash on starup
http://www.classicshell.net/forum/viewtopic.php?f=7&t=5873		 Page 1 of 1
Author:  AUserInEssex [ Tue Apr 05, 2016 2:44 pm ]
Post subject:  Crash on starup
Dear all

I've got Classic Shell 4.2.5, which is the latest version. (I am confident I have the latest version. However, when trying to verify this, I find that I can't locate the version number - I've forgotten how. Surely this needs fixing i.e. should be easier.)

Sometimes when Windows boots it tells me that Classic shell has crashed. Now, Classic Shell seems, nevertheless, to work as normal - yet, I would like to be rid of this error message.

Advice, please? Thanks.

Windows 8.1 x64.
Author:  Ivo [ Tue Apr 05, 2016 3:03 pm ]
Post subject:  Re: Crash on starup
What is the exact error message? A screenshot would be helpful.
Author:  AUserInEssex [ Tue Apr 05, 2016 3:38 pm ]
Post subject:  Re: Crash on starup
Thanks. I haven't a screenshot, though I'll take one the next time the opportunity arises, should the information that I give now - from the Windows Event Log - prove insufficient.

Code:
Log Name: Application
Source: Application Error
Date: 05/04/2016 22:40:33
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: desktop
Description:
Faulting application name: ClassicStartMenu.exe, version: 4.2.5.0, time stamp: 0x5645894a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process ID: 0xde4
Faulting application start time: 0x01d18f83c8735a84
Faulting application path: C:\Program Files\Classic Shell\ClassicStartMenu.exe
Faulting module path: unknown
Report ID: 0637bde9-fb77-11e5-bea8-001c25393088
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-04-05T21:40:33.000000000Z" />
<EventRecordID>9809</EventRecordID>
<Channel>Application</Channel>
<Computer>desktop</Computer>
<Security />
</System>
<EventData>
<Data>ClassicStartMenu.exe</Data>
<Data>4.2.5.0</Data>
<Data>5645894a</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>0000000000000000</Data>
<Data>de4</Data>
<Data>01d18f83c8735a84</Data>
<Data>C:\Program Files\Classic Shell\ClassicStartMenu.exe</Data>
<Data>unknown</Data>
<Data>0637bde9-fb77-11e5-bea8-001c25393088</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


This further message in the log, occuring some 15 minutes later, may be related [EDIT: probably it isn't; rather, it's Sky-OneDrive complaining that I've disabled as much of it as I can):

Code:
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 05/04/2016 23:05:56
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: desktop\Nicholas
Computer: desktop
Description:
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-04-05T22:05:56.334851600Z" />
<EventRecordID>15935</EventRecordID>
<Correlation />
<Execution ProcessID="792" ThreadID="5760" />
<Channel>System</Channel>
<Computer>desktop</Computer>
<Security UserID="S-1-5-21-3297121681-1545341759-4092395967-1001" />
</System>
<EventData>
<Data Name="param1">{1B1F472E-3221-4826-97DB-2C2324D389AE}</Data>
</EventData>
</Event>


(Sorry for the formatting of these logs - it's the fault of Windows Event Viewer.)
Author:  Gaurav [ Tue Apr 05, 2016 10:21 pm ]
Post subject:  Re: Crash on starup
Can you capture a crash dump using these instructions? viewtopic.php?f=12&t=6 If it's crashing at startup when Windows boots and closes, simply run procdump -e explorer.exe as those instructions say from an elevated command prompt and then run C:\Program Files\Classic Shell\ClassicStartMenu.exe. If it crashes at startup it should crash when loaded manually too.
Author:  AUserInEssex [ Thu Apr 21, 2016 4:36 pm ]
Post subject:  Re: Crash on starup
Sorry for the belated reply.

Now:

Gaurav wrote:
Can you capture a crash dump using these instructions? viewtopic.php?f=12&t=6 If it's crashing at startup when Windows boots and closes, simply run procdump -e explorer.exe as those instructions say from an elevated command prompt and then run C:\Program Files\Classic Shell\ClassicStartMenu.exe. If it crashes at startup it should crash when loaded manually too.


Well, (1) it does not crash when loaded manually. Indeed it crashes at startup only occasionally; the problem is intermittent. (2) I tried to generate a crash dump after one of the intermittent crashes, but I received an error message from procdump to the effect that there was more than one explorer.exe process.
Page 1 of 1 All times are UTC - 8 hours [ DST ]
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/