Announcement

Collapse
No announcement yet.

Ultrawire3 Crashes on HS3 exit

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Ultrawire3 Crashes on HS3 exit

    Every time I shut down HS3, about 3 seconds later I get a crash from Ultrawire3.

    Running HS3 Pro on Win7, TEMP08 using serial connection.

    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: HSPI_ULTRA1WIRE3.exe
    Application Version: 3.0.5054.16334
    Application Timestamp: 52750ab0
    Fault Module Name: clr.dll
    Fault Module Version: 4.0.30319.1
    Fault Module Timestamp: 4ba1d9ef
    Exception Code: c0000005
    Exception Offset: 000d17da
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033
    Additional Information 1: 2caf
    Additional Information 2: 2caf49507491cfc2ddc51923c117ec68
    Additional Information 3: df90
    Additional Information 4: df908305440428337136b58c127a15a6

    Any ideas what is happening?

    Thanks

  • #2
    I was able to duplicate this issue on Windows 7. It does not occur on Windows 8. I found a few references to similar issues on Google that suggest Microsoft has a hotfix for the issue. I am still looking into this to see what is causing the clr.dll crash.
    Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

    Comment


    • #3
      thanks for the update.

      Comment


      • #4
        I noticed an update to Ultra1Wire3 so I updated the plug in, Still got a crash, this time it went down with HS3 running as well as blue screened the box. :-(

        Fault bucket , type 0
        Event Name: APPCRASH
        Response: Not available
        Cab Id: 0

        Problem signature:
        P1: HSPI_ULTRA1WIRE3.exe
        P2: 3.0.5054.16334
        P3: 52750ab0
        P4: clr.dll
        P5: 4.0.30319.1
        P6: 4ba1d9ef
        P7: c0000005
        P8: 0005f60b
        P9:
        P10:

        Attached files:

        These files may be available here:
        C:\Users\burger\AppData\Local\Microsoft\Windows\WER\ReportAr chive\AppCrash_HSPI_ULTRA1WIRE3_693d48824ea55c9b311a77f9a16e 8f1381bc9f1_20546298

        Analysis symbol:
        Rechecking for solution: 0
        Report Id: ce18c8c9-7e55-11e3-8824-000c2939a925
        Report Status: 0

        Also

        Faulting application name: HSPI_ULTRA1WIRE3.exe, version: 3.0.5125.18780, time stamp: 0x52d2b408
        Faulting module name: clr.dll, version: 4.0.30319.1, time stamp: 0x4ba1d9ef
        Exception code: 0xc0000005
        Fault offset: 0x0005f60b
        Faulting process id: 0xe28
        Faulting application start time: 0x01cf1262a5c58b2a
        Faulting application path: C:\Program Files (x86)\HomeSeer HS3\HSPI_ULTRA1WIRE3.exe
        Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
        Report Id: 763f6eda-7e5b-11e3-8824-000c2939a925

        Comment


        • #5
          Hello. I think I have this issue fixed. Can you try the version I just uploaded to the HS3 updater and confirm? Please also make sure you're running HS3 3.0.0.55 or greater.

          Regards,
          Ultrajones
          Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

          Comment


          • #6
            Fixed.

            You Rock, Thanks!

            Comment


            • #7
              Originally posted by Ultrajones View Post
              Hello. I think I have this issue fixed. Can you try the version I just uploaded to the HS3 updater and confirm? Please also make sure you're running HS3 3.0.0.55 or greater.

              Regards,
              Ultrajones
              Hey Jones,
              I have this issue in a completely unrelated piece of software that I'm responsible for, but I'm getting the identical crash. I'm curious if you can share any insights as to how you fixed this? I'd really appreciate it if you could shoot me a PM or email just to point me in the right direction.
              thanks,
              Curt Hayes
              curth_usethenormalatsign_electroimpact.com

              Comment


              • #8
                This is actually still happening. It stopped for a while then started again, I just never got around to posting about it. But it still crashes every time I exit the program.

                Comment

                Working...
                X