locked
Error in qsm.exe several times each day RRS feed

  • Question

  • For the last couple of weeks I have been finding my WHS disconnected from every workstation when we go to use them in the morning. When I reboot the server and log into the console I get several promts to report an Application Error in module qsm.exe. There are corresponding entries in the Event Log that look like this:

    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1000
    Date:  1/20/2010
    Time:  9:16:42 AM
    User:  N/A
    Computer: SERVER
    Description:
    Faulting application qsm.exe, version 6.0.2423.0, faulting module qsm.exe, version 6.0.2423.0, fault address 0x0002c234.

    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 46 61 69 6c   ion Fail
    0010: 75 72 65 20 20 71 73 6d   ure  qsm
    0018: 2e 65 78 65 20 36 2e 30   .exe 6.0
    0020: 2e 32 34 32 33 2e 30 20   .2423.0
    0028: 69 6e 20 71 73 6d 2e 65   in qsm.e
    0030: 78 65 20 36 2e 30 2e 32   xe 6.0.2
    0038: 34 32 33 2e 30 20 61 74   423.0 at
    0040: 20 6f 66 66 73 65 74 20    offset
    0048: 30 30 30 32 63 32 33 34   0002c234


    For the last week or so there have been more than 10 of these each day, usually clustered within a few minutes of each other. They seem to be around backup times and I sometimes get warnings about various machines on the network not having been backed up for X number of days.

    After I reboot the server it will run fine until the following day when the cycle repeats. There are no other error events in the Event Log, and except for the warnings about a machine not having been backed up, the WHS console reports the system as healthy.

    Does anyone have any idea what the problem is and how I can solve it?

    Thanks!

    Wednesday, January 20, 2010 3:30 PM

Answers

All replies

  • Try running chkdsk on all the drives in your server.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, January 20, 2010 4:26 PM
    Moderator
  • Thanks, Ken. I did that and saw some messages about Windows replacing some bad blocks in a handful of files. There are no entries in the event log for "winlogon" (that doesn't even appear in the sources list) and the only thing I see from chkdsk in the event log are startup messages, so there may have been other on-screen error messages while I wasn't watching. When I rebooted the server and RDC'd to the console I was immediately greeted with 8 more Application Errors, same message as before. They happened as the Drive Migrator Services was started up. There are 5 events in the log about DMS starting, separated by Application Errors. I also see an additonal event between each error saying "Fault bucket 1624832787."

    Any other suggestions?

    Thursday, January 21, 2010 2:43 PM
  • Thanks, Ken. I did that and saw some messages about Windows replacing some bad blocks in a handful of files. There are no entries in the event log for "winlogon" (that doesn't even appear in the sources list) and the only thing I see from chkdsk in the event log are startup messages, so there may have been other on-screen error messages while I wasn't watching. When I rebooted the server and RDC'd to the console I was immediately greeted with 8 more Application Errors, same message as before. They happened as the Drive Migrator Services was started up. There are 5 events in the log about DMS starting, separated by Application Errors. I also see an additonal event between each error saying "Fault bucket 1624832787."

    Any other suggestions?


    You could try replacing that drive (which is what I would suggest anyway when a drive starts having issues like that).
    Friday, January 22, 2010 1:19 AM
    Moderator