Disabling all sound system

Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

Hello

I have a self-rebooting computer and I am trying to disable all I can
to trace the problem source.

I have disabled the sound card but when I do a pstat I can see several
sound system files still loaded (drmkaud, drmk..)

Any way to disable them?

Thank you,
nafiton
4 answers Last reply
More about disabling sound system
  1. Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

    Bonjour *nafiton@geocities.com* :

    > Hello
    >
    > I have a self-rebooting computer and I am trying to disable all I can
    > to trace the problem source.
    >
    > I have disabled the sound card but when I do a pstat I can see several
    > sound system files still loaded (drmkaud, drmk..)
    >
    > Any way to disable them?
    >
    > Thank you,
    > nafiton

    You can used ServiWin of NirSoft to disable thoses drivers:
    http://www.nirsoft.net/utils/serviwin.html

    Take care with this program ...

    Did you really need to troubleshoot your system at this level ?

    Tell us what is the problem.
    Somebody here may have a bright idea !! ;-)

    :)
    --
    Claude LaFrenière [MVP] :-)

    «My Principal Design Was To Inform, Not To Amuse Thee.»
    Lemuel Gulliver, The Travels (IV:12)
    http://climenole.serendipia.net
  2. Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

    Bonjour Claude

    I understand there is no way to do this with any XP tools. Is it so?

    Well, the problem is this: we install our program in a clean XP and all
    went good and clean. We put this computer to production and forget it.
    After a few weeks, the user claims that the PC shutdowns and restarts
    itself.

    At minidump directory, we saw it was crashing twice or three times
    each day. We bring the PC and turn it on. Without touching it, it
    crashed three times in five days.

    We uninstall several programs the user had installed, disable hardware
    not necesary and disable several services (index server, automatic
    updates...). Now it has crashed one time in three weeks. I was trying
    to uninstall the sound system because the only modules listed by
    dumpchk are the sound drivers and the usb driver. You can see the dump
    below. I know the usb seems a better candidate (having opened several
    modules. i don´t know if it is normal behaviour) but I want to disable
    both modules.

    Thanks for help,
    nafiton

    ----- 32 bit Kernel Mini Dump Analysis

    DUMP_HEADER32:
    MajorVersion 0000000f
    MinorVersion 00000a28
    DirectoryTableBase 02a67000
    PfnDataBase 8104a000
    PsLoadedModuleList 8054c850
    PsActiveProcessHead 8054e8b8
    MachineImageType 0000014c
    NumberProcessors 00000001
    BugCheckCode 0000000a
    BugCheckParameter1 00000207
    BugCheckParameter2 000000ff
    BugCheckParameter3 00000001
    BugCheckParameter4 804d8b64
    PaeEnabled 00000000
    KdDebuggerDataBlock 8053e7e0
    MiniDumpFields 00000dff

    TRIAGE_DUMP32:
    ServicePackBuild 00000100
    SizeOfDump 00010000
    ValidOffset 0000fffc
    ContextOffset 00000320
    ExceptionOffset 000007d0
    MmOffset 00001068
    UnloadedDriversOffset 000010a0
    PrcbOffset 00001878
    ProcessOffset 000024c8
    ThreadOffset 00002720
    CallStackOffset 00002978
    SizeOfCallStack 00000540
    DriverListOffset 00003148
    DriverCount 0000006a
    StringPoolOffset 000050c0
    StringPoolSize 00000e88
    BrokenDriverOffset 00000000
    TriageOptions 00000041
    TopOfStack f5881ac0
    DebuggerDataOffset 00002eb8
    DebuggerDataSize 00000290
    DataBlocksOffset 00005f48
    DataBlocksCount 00000003


    Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
    Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c850
    Debug session time: Fri Jun 03 15:21:21 2005
    System Uptime: 14 days 8:09:14
    start end module name
    804d4000 806c7280 nt Checksum: 00200F03 Timestamp: Wed
    Mar 02 02:33:24 2005 (422517E4)

    Unloaded modules:
    f9e31000 f9e37000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9df9000 f9dff000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9d71000 f9d77000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9ce1000 f9ce7000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9e19000 f9e1f000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9cd9000 f9cdf000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9ce9000 f9cef000 RTL8139.SYS Timestamp: unavailable (00000000)
    f5ea8000 f5eb7000 drmk.sys Timestamp: unavailable (00000000)
    fa096000 fa097000 drmkaud.sys Timestamp: unavailable (00000000)
    f5cab000 f5cd2000 kmixer.sys Timestamp: unavailable (00000000)
    f5cd2000 f5cf3000 portcls.sys Timestamp: unavailable (00000000)
    f5eb8000 f5ec5000 DMusic.sys Timestamp: unavailable (00000000)
    f5ec8000 f5ed6000 swmidi.sys Timestamp: unavailable (00000000)
    f5d93000 f5db6000 aec.sys Timestamp: unavailable (00000000)
    f9fa3000 f9fa5000 splitter.sys Timestamp: unavailable (00000000)
    f9bd1000 f9bdb000 imapi.sys Timestamp: unavailable (00000000)
    f9d39000 f9d3e000 Cdaudio.SYS Timestamp: unavailable (00000000)
    f9844000 f9847000 Sfloppy.SYS Timestamp: unavailable (00000000)

    Finished dump check
  3. Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

    HI *nafiton@geocities.com* :

    > Bonjour Claude
    >
    > I understand there is no way to do this with any XP tools. Is it so?

    To disable drivers easily ?
    No.But the NirSoft's ServiWin can do that job...

    >
    > Well, the problem is this: we install our program in a clean XP and all
    > went good and clean. We put this computer to production and forget it.
    > After a few weeks, the user claims that the PC shutdowns and restarts
    > itself.

    I see...
    The client is always right... ;-) We have to say that, not believe that ;-)

    And this problem comes after few weeks... did they install or uninstall
    somethings else ?

    If the problem comes really from the sounds drivers you installed why those
    problems comes so late ???

    OK. So there's a fatal error detected by W xp and, by default , the PC
    reboot to protect the Operation System...

    If such crash happen you can set the error report (control panel | system )
    to send this report to MS Online Crash Analysis:
    http://oca.microsoft.com/en/

    (All the instructions are on this web site)

    Let the people of MS check this for you.
    This is their job :-D

    >
    > At minidump directory, we saw it was crashing twice or three times
    > each day. We bring the PC and turn it on. Without touching it, it
    > crashed three times in five days.
    >
    > We uninstall several programs the user had installed, disable hardware
    > not necesary and disable several services (index server, automatic
    > updates...). Now it has crashed one time in three weeks. I was trying
    > to uninstall the sound system because the only modules listed by
    > dumpchk are the sound drivers and the usb driver. You can see the dump
    > below. I know the usb seems a better candidate (having opened several
    > modules. i don´t know if it is normal behaviour) but I want to disable
    > both modules.

    Well this way you can easily add new problems instead of solving it...

    You assume that the problem comes from the sounds drivers...
    Don't be so sure... may be a "conflict" with an other driver explain this.

    >
    > Thanks for help,
    > nafiton

    Check on OCA site and let us Know.

    :)
    --
    Claude LaFrenière [MVP] :-)

    «My Principal Design Was To Inform, Not To Amuse Thee.»
    Lemuel Gulliver, The Travels (IV:12)
    http://climenole.serendipia.net
  4. Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

    Dumpchk is a waste of time. It does not tell you the problem (unless the blue screen could which is rare). This is what you do with dump files.

    Try all the following with existing dump files but you can also turn on the
    Driver Verifier (type verifier in Start Run and follow the wizard). This is
    strict checking of all drivers (so it makes computer slower). This may give
    different error messages and pinpoint one driver that is not crashing but
    causing another driver to crash. If you can't start after enabling verifier
    choose Last Known Good Configuration at the Failed Boot menu (which will
    start without verifier).

    Get your XP CD and install Windows Support Tools.


    Type in start run after installing and rebooting


    pstat > "%userprofile%\desktop\driverl­ist.txt"


    The last table in this file is a list of loaded drivers. Other things apart
    from hardware uses drivers. Post the list of drivers (the last table only -
    REPEAT THE LAST TABLE O N L Y ) or match the fault address to the driver.


    If you have the XP SP2 Security Update CD (else see
    http://www.microsoft.com/whdc/­devtools/debugging/symbolpkg.m­spx
    )


    Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS


    Download
    http://www.microsoft.com/whdc/­devtools/debugging/installx86.­mspx


    Load the crash dump file into windbg (File - Load Crash Dump and it's in
    c:\windows\minidump) and READ WHAT IT SAYS (you may need to tell it where
    the symbol files are), then
    Type
    !Analyze -v
    into Windbg's command line.
    (this will hopefully tell you the faulty component)

    If a minidump doesn't help use a kernel dump, if that doesn't help create a
    full dump.

    You can look up specific details here
    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/BCIntro_ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

    If it indicates faulty memory might be the cause you can get a memory tester
    here
    http://oca.microsoft.com/en/wi­ndiag.asp


    If it mentions a core windows system file, meaning it a MS fix is required,
    upload a minidump to

    http://oca.microsoft.com

    Also try typing the main error code in Help while online (ie,
    Stop 0x50
    and also try in the 8 digit form
    stop 0x00000050)
    and if there are too many hits use a filename if available. Generally memory
    addresses are different for each computer (as each computer has a different
    mix of drivers) so parameters aren't that useful for searching.


    --
    --------------------------------------------------------------------------------------------------
    http://webdiary.smh.com.au/archives/_comment/001075.html
    =================================================
    <nafiton@geocities.com> wrote in message news:1118135862.864910.90490@g47g2000cwa.googlegroups.com...
    Bonjour Claude

    I understand there is no way to do this with any XP tools. Is it so?

    Well, the problem is this: we install our program in a clean XP and all
    went good and clean. We put this computer to production and forget it.
    After a few weeks, the user claims that the PC shutdowns and restarts
    itself.

    At minidump directory, we saw it was crashing twice or three times
    each day. We bring the PC and turn it on. Without touching it, it
    crashed three times in five days.

    We uninstall several programs the user had installed, disable hardware
    not necesary and disable several services (index server, automatic
    updates...). Now it has crashed one time in three weeks. I was trying
    to uninstall the sound system because the only modules listed by
    dumpchk are the sound drivers and the usb driver. You can see the dump
    below. I know the usb seems a better candidate (having opened several
    modules. i don´t know if it is normal behaviour) but I want to disable
    both modules.

    Thanks for help,
    nafiton

    ----- 32 bit Kernel Mini Dump Analysis

    DUMP_HEADER32:
    MajorVersion 0000000f
    MinorVersion 00000a28
    DirectoryTableBase 02a67000
    PfnDataBase 8104a000
    PsLoadedModuleList 8054c850
    PsActiveProcessHead 8054e8b8
    MachineImageType 0000014c
    NumberProcessors 00000001
    BugCheckCode 0000000a
    BugCheckParameter1 00000207
    BugCheckParameter2 000000ff
    BugCheckParameter3 00000001
    BugCheckParameter4 804d8b64
    PaeEnabled 00000000
    KdDebuggerDataBlock 8053e7e0
    MiniDumpFields 00000dff

    TRIAGE_DUMP32:
    ServicePackBuild 00000100
    SizeOfDump 00010000
    ValidOffset 0000fffc
    ContextOffset 00000320
    ExceptionOffset 000007d0
    MmOffset 00001068
    UnloadedDriversOffset 000010a0
    PrcbOffset 00001878
    ProcessOffset 000024c8
    ThreadOffset 00002720
    CallStackOffset 00002978
    SizeOfCallStack 00000540
    DriverListOffset 00003148
    DriverCount 0000006a
    StringPoolOffset 000050c0
    StringPoolSize 00000e88
    BrokenDriverOffset 00000000
    TriageOptions 00000041
    TopOfStack f5881ac0
    DebuggerDataOffset 00002eb8
    DebuggerDataSize 00000290
    DataBlocksOffset 00005f48
    DataBlocksCount 00000003


    Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
    Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c850
    Debug session time: Fri Jun 03 15:21:21 2005
    System Uptime: 14 days 8:09:14
    start end module name
    804d4000 806c7280 nt Checksum: 00200F03 Timestamp: Wed
    Mar 02 02:33:24 2005 (422517E4)

    Unloaded modules:
    f9e31000 f9e37000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9df9000 f9dff000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9d71000 f9d77000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9ce1000 f9ce7000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9e19000 f9e1f000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9cd9000 f9cdf000 USBSTOR.SYS Timestamp: unavailable (00000000)
    f9ce9000 f9cef000 RTL8139.SYS Timestamp: unavailable (00000000)
    f5ea8000 f5eb7000 drmk.sys Timestamp: unavailable (00000000)
    fa096000 fa097000 drmkaud.sys Timestamp: unavailable (00000000)
    f5cab000 f5cd2000 kmixer.sys Timestamp: unavailable (00000000)
    f5cd2000 f5cf3000 portcls.sys Timestamp: unavailable (00000000)
    f5eb8000 f5ec5000 DMusic.sys Timestamp: unavailable (00000000)
    f5ec8000 f5ed6000 swmidi.sys Timestamp: unavailable (00000000)
    f5d93000 f5db6000 aec.sys Timestamp: unavailable (00000000)
    f9fa3000 f9fa5000 splitter.sys Timestamp: unavailable (00000000)
    f9bd1000 f9bdb000 imapi.sys Timestamp: unavailable (00000000)
    f9d39000 f9d3e000 Cdaudio.SYS Timestamp: unavailable (00000000)
    f9844000 f9847000 Sfloppy.SYS Timestamp: unavailable (00000000)

    Finished dump check
Ask a new question

Read More

Microsoft Windows XP