locked
When is the next version? RRS feed

  • Question

  • I have been having a lot of troubles with the beta.  From the profile lockout during tuneup to the constant nonresponsive program error from WinSSUI.exe.  As well as frequent errors with nvraid since the install (although if I boot into anything but the XP that has WLOC installed, there are no errors). 

    Is the next version soon?  I am happy to help with beta testing and play with WLOC, but at this point, I have spent way too many hours towards the effort, and I actually use my pc for things other than troubleshooting WLOC.


    The following are the most frequent errors I get.  I have been faithfully reporting them.
    Event Type:    Error
    Event Source:    Application Hang
    Event Category:    None
    Event ID:    1001
    Date:        8/1/2007
    Time:        7:59:33 PM
    User:        N/A
    Computer:    OPTY170
    Description:
    Fault bucket 475714805.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 42 75 63 6b 65 74 3a 20   Bucket:
    0008: 34 37 35 37 31 34 38 30   47571480
    0010: 35 0d 0a                  5..    


    Event Type:    Error
    Event Source:    Application Hang
    Event Category:    (101)
    Event ID:    1002
    Date:        8/1/2007
    Time:        7:01:16 AM
    User:        N/A
    Computer:    OPTY170
    Description:
    Hanging application WinSSUI.exe, version 2.0.2284.28, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74   Applicat
    0008: 69 6f 6e 20 48 61 6e 67   ion Hang
    0010: 20 20 57 69 6e 53 53 55     WinSSU
    0018: 49 2e 65 78 65 20 32 2e   I.exe 2.
    0020: 30 2e 32 32 38 34 2e 32   0.2284.2
    0028: 38 20 69 6e 20 68 75 6e   8 in hun
    0030: 67 61 70 70 20 30 2e 30   gapp 0.0
    0038: 2e 30 2e 30 20 61 74 20   .0.0 at
    0040: 6f 66 66 73 65 74 20 30   offset 0
    0048: 30 30 30 30 30 30 30      0000000



    Event Type:    Warning
    Event Source:    Ci
    Event Category:    CI Service
    Event ID:    4149
    Date:        8/1/2007
    Time:        3:35:06 PM
    User:        N/A
    Computer:    OPTY170
    Description:
    Read of USN log for NTFS volume c: failed with error code 0xC00000A1.  Volume will remain offline until the Indexing Service (cisvc) is restarted.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Event Type:    Error
    Event Source:    MSFWSVC
    Event Category:    (2)
    Event ID:    1080
    Date:        8/1/2007
    Time:        4:40:29 PM
    User:        N/A
    Computer:    OPTY170
    Description:
    OneCare Firewall failed while executing the following method: DeleteSingleInstance. Error Code: 0x80070490, Error Message: Element not found.
    .

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type:    Error
    Event Source:    MSFWSVC
    Event Category:    (2)
    Event ID:    1080
    Date:        8/1/2007
    Time:        3:53:08 PM
    User:        N/A
    Computer:    OPTY170
    Description:
    OneCare Firewall failed while executing the following method: DeleteSingleInstance. Error Code: 0x8007007A, Error Message: The data area passed to a system call is too small.
    .

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Here are the controller errors I get while onecare is running. 

    Event Type:    Error
    Event Source:    nvraid
    Event Category:    None
    Event ID:    11
    Date:        8/1/2007
    Time:        3:52:06 PM
    User:        N/A
    Computer:    OPTY170
    Description:
    The driver detected a controller error on .

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 0e 00 68 00 01 00 ba 00   ..h...º.
    0008: 00 00 00 00 0b 00 04 c0   .......À
    0010: 03 01 00 00 00 00 00 00   ........
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    0028: 72 6c 00 00 00 00 00 00   rl......
    0030: ff ff ff ff 06 00 00 00   ÿÿÿÿ....
    0038: 40 00 00 00 00 00 00 00   @.......
    0040: 00 00 06 12 08 00 00 00   ........
    0048: 00 00 00 00 00 00 00 00   ........
    0050: 00 00 00 00 00 00 00 00   ........
    0058: 00 00 00 00 48 1e eb 87   ....H.ë‡
    0060: 00 00 00 00 00 00 00 00   ........
    0068: 00 00 00 00 00 00 00 00   ........
    0070: 00 00 00 00 00 00 00 00   ........
    0078: 00 00 00 00 00 00 00 00   ........
    0080: 00 00 00 00 00 00 00 00   ........
    0088: 00 00 00 00 00 00 00 00   ........

    Thursday, August 2, 2007 3:05 AM

Answers

  • First of all, thank your for reporting the problems and filing bugs.

    In my experience, we won't be told anything about when a new build will be released until after it is made available, except in rare cases where a release is pushed to resolve a very widespread and serious defect.

    I'm sorry that the program hangs are occurring for you. I can tell you that the ID 1080 errors you pasted are a known issue and will be fixed in a refresh. I don't know about the others. As I see it, you can choose to continue to use the beta unless it is impacting your regular PC use, in which case I'd recommend uninstalling it and checking back here every once in a while to see if a new build was released. You could also contact support for help - http://help.live.com/help.aspx?project=onecarev2 - use the get more help link in the lower right.

    -steve

    Friday, August 3, 2007 5:06 PM
    Moderator

All replies

  • First of all, thank your for reporting the problems and filing bugs.

    In my experience, we won't be told anything about when a new build will be released until after it is made available, except in rare cases where a release is pushed to resolve a very widespread and serious defect.

    I'm sorry that the program hangs are occurring for you. I can tell you that the ID 1080 errors you pasted are a known issue and will be fixed in a refresh. I don't know about the others. As I see it, you can choose to continue to use the beta unless it is impacting your regular PC use, in which case I'd recommend uninstalling it and checking back here every once in a while to see if a new build was released. You could also contact support for help - http://help.live.com/help.aspx?project=onecarev2 - use the get more help link in the lower right.

    -steve

    Friday, August 3, 2007 5:06 PM
    Moderator
  • Slavearm,

     

    You wouldn't happen to have the following motherboard would you?

     

    Asus M2N32-SLI (nForce 590)

    If so, there is a thread about file system corruption issues at the link below. This might explain your issues with the operation of WLOC on your PC quite well. I sounds like there have been driver problems with this board that are difficult to find a solution to.

     

    http://forums.nvidia.com/lofiversion/index.php?t18692.html

     

    Even if this isn't your exact hardware, I'd suspect that you're having hardware/driver issues with your nVidia controller based on the errors you've been having.

     

    OneCareBear

    Sunday, August 5, 2007 6:19 AM
    Moderator
  • Nope.  Running A8N32 Deluxe.  Thanks for the effort though.
    Sunday, August 5, 2007 4:37 PM
  • I have just experienced WLOC

    crashing when it opens.  It appears to still be running but the user interface

    will not open.  It reports the following information:

     

    Problem signature:

    Problem Event Name: APPCRASH

    Application Name: WinSSUI.exe

    Application Version: 1.6.2111.30

    Application Timestamp: 469d8d69

    Fault Module Name: WinSSCommon.dll

    Fault Module Version: 1.6.2111.30

    Fault Module Timestamp: 469d8d4e

    Exception Code: c0000005

    Exception Offset: 00007773

    OS Version: 6.0.6000.2.0.0.768.3

    Locale ID: 1033

    Additional Information 1: ef96

    Additional Information 2: 799ed31877374dfce677fb551f197de0

    Additional Information 3: e28b

    Additional Information 4: 2be366d4f09c3eb461aa11400c631d1d

    Sunday, August 19, 2007 11:43 PM
  • Monday, August 20, 2007 1:45 AM
    Moderator