Event ID 33 source SideBySide, and BSOD at WinCDEmu Settings

Sysprogs forums › Forums › WinCDEmu › Event ID 33 source SideBySide, and BSOD at WinCDEmu Settings

Log In Register Lost Password
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • December 17, 2011 at 15:38 #396
    pps
    Participant

    Regularly I am getting the same error in the Windows Application log as described at http://forum.sysprogs.org/viewtopic.php?f=3&t=554&hilit=sidebyside. Example log entry of mine in the box below. My OS is Windows 7 Professional 32bit, unfortunately localized to German. Also I get the errors whether using WinCDEmu or not.

    I need to admit that I am getting similar ID 33 SideBySide errors for Drivermax. Of course I uninstalled WinCDEmu and Drivermax, rebooted and installed new versions.

    Interestingly, for both softwares log entries say processorArchitecture=”amd64″, for WinCDEmu 100% of the entries, for Drivermax 50% of them. For Drivermax the other half of the entries say processorArchitecture=”ia64″. But my environment is Intel and 32 bit.

    Next issue: I can’t open the small WinCDEmu Settings window from the Start menu. I see the spinning wait cursor for a few seconds but no window appears. I also cannot launch it from an ordinary command prompt, but from an elevated command prompt.

    One time when I opened from the elevated command prompt I got a BSOD upon hitting the OK button after changing to “Prefer drive letters starting with” and unchecking “Require administrator rights (UAC) to mount an image”. The blue screen crash occurred in BazisVirtualCDBus.sys at address 0x161cb .

    
Protokollname: Application
Quelle:        SideBySide
Datum:         17.12.2011 13:33:20
Ereignis-ID:   33
Aufgabenkategorie:Keine
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      PS10
Beschreibung:
Fehler beim Generieren des Aktivierungskontextes für "C:Program FilesWinCDEmuvmnt64.exe". Die abhängige Assemblierung "Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"" konnte nicht gefunden werden. Verwenden Sie für eine detaillierte Diagnose das Programm "sxstrace.exe".
Ereignis-XML:

    

    

    
33
    
2
    
0
    
0x80000000000000
    

    
24893
    
Application
    
PS10
    

    

    

    
Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    

    
C:Program FilesWinCDEmuvmnt64.exe
    December 25, 2011 at 12:54 #2025
    pps
    Participant

    Besides C:Program FilesWinCDEmuvmnt.exe , the installation indeed has left vmnt64.exe , and also batchmnt64.exe and uninstall64.exe , in the installation folder C:Program FilesWinCDEmu . Now, having renamed all three file extensions from .exe in .exe_ the SideBySide event 33 has gone.

    I am curious what the root cause was. Question to other 32bit Vista and 32bit Windows 7 users: Do you also find the three …64.exe in the installation folder?

    January 11, 2012 at 08:32 #2026
    pps
    Participant

    Hi bazis / SysProgs,
    Why these 64 bit issues in Windows 7 x86 environment? At least the last question should be very easy for you to answer: is it expected that the WinCDEmu installation leaves vmnt64.exe, batchmnt64.exe, and uninstall64.exe in the installation folder C:Program FilesWinCDEmu ?

  • Author
    Posts
Log In Register Lost Password
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.