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
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.
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)
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\driverlist.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.
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.
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/archive [...] 01075.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.
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)
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
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.