[XP] pc reboot spontaan (bsod)*

[Cisk]

Help me.

Ik heb windows XP draaien en ineens uit het niets reboot mijn systeem zonder blauw scherm.
Ik heb geen virussen en geen spyware of iets. Dit alles is al getest. Nieuwste driver geinstalleer voor mijn MSI motherboard en de nieuwste BIOS etc etc.

Hieronder een minidump:

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [A:\Mini101805-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Tue Oct 18 00:13:06.187 2005 (GMT+2)
System Uptime: 0 days 0:02:30.750
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..........................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for sr.sys
*** ERROR: Module load completed but symbols could not be loaded for sr.sys
*** WARNING: Unable to verify timestamp for Tmpreflt.sys
*** ERROR: Module load completed but symbols could not be loaded for Tmpreflt.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Tmpreflt.sys ( Tmpreflt+2afe )

Followup: MachineOwner
---------

Iemand hier die dit herkent of mij opweg kan helpen?
Dit is namelijk vreselijk irritant!

Alvast bedankt.

[ShellGhost]

Wat staat er over in de eventviewer?
Wat zijn de specs van je pc?
Hoe zijn de temps?

[elevator]

Ik begin even met het OS in je topic titel te zetten conform de Windows Operating Systems Policy - let hier aub ook zelf op

Verder:

Cisk schreef op dinsdag 18 oktober 2005 @ 12:33:
Probably caused by : Tmpreflt.sys ( Tmpreflt+2afe )

Lijkt me duidelijk - als je die filename in Google inklopt is de eerste hit ook al wat het precies is (een of ander component van TrendMicro) dus het lijkt erop dat je even TrendMicro moet deinstalleren?

[Cisk]

Dat zoeken met google had ik al gedaan, maar trend micro is het probleem niet (100%zeker).

Verder heb ik een msi motherboard, pentium4 2.5GHz, 512MB memory, ATI Radeon 9600.
Hoe warm het systeem is/wordt weet ik nu even niet, ik ben nu op mijn werk namelijk.

[elevator]

Kan je ons vertellen hoe je 100% zeker bent dat hte TrendMicro niet is? Waarom deinstalleer je het niet gewoon om te zien of het probleem daarmee verdwijnt?

[Cisk]

Waarom ik dat zo zeker weet........

Het systeem reboten voor de installatie ook al en nu heb ik pc cillen eraf gehaald en systeem reboot nog steeds spontaan.

temp cpu 25 graden, systeem temp 30 graden. videokaart is een sapphire ati radeon

[Verwijderd]

Om de hoeveel tijd gebeurt het?

Probeer anders eens minimaal op te starten, alle startup items uitzetten en zoveel mogelijk niet windows services. Als het probleem zich dan niet meer voordoet zal je daarin moeten gaan zoeken

[Cisk]

Hier weer een nieuwe dump file:


Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\dump files\Mini101905-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Oct 19 08:26:15.515 2005 (GMT+2)
System Uptime: 0 days 0:11:16.081
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {dff984, 1e, 0, 804e3e91}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image ALCXWDM.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ALCXWDM.SYS ( ALCXWDM+66d97 )

Followup: MachineOwner
---------

ALCXWDM.SYS heeft met de onboard sound kaart te maken. Of dit nu de echte oorzaak is weet ik niet. Voordat ik bij MSI alle updates en de nieuwste drivers heb gedraait, kreeg ik ook spontane reboots.