crash dump

[Theezakje]

hallo,

ik krijg vaak crash dumps en dat vind ik zeer hinderlijk ik probeer het probleem op te lossen alleen weet ik nog niet echt wat het probleem is. Ik heb een windows Vista systeem.

Met het programma debugging tools voor windows kan ik de crash dumps openen en vervolgens in de file kijken wat de oorzaak is van de crash dump. Ik heb meerdere crash dump file's met verschillende oorzaken. Maar ik post hier de samenvatting van de laatste crash dump:


Ik weet niet precies wat het inhoud ik hoop dat jullie er meer mee kunnen:

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


Loading Dump File [C:\Users\Rhebas\Documents\Mini032908-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: scv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: scv*C:\symbols*http://msdl.microsoft.com/download/symbols
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sat Mar 29 20:16:45.907 2008 (GMT+1)
System Uptime: 0 days 2:14:52.042
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** 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 User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {f2d399e3, 1, 81c3fae3, 2}

*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware ( SYMEVENT+14219 )

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

 

[dnties]

Ik zie SYMEVENT staan als mogelijke oorzaak. Dat lijkt te wijzen op een Norton/Symantec softwarepakket als mogelijke oorzaak.
Heb je iets van Norton Antivirus, Norton 360 etc geïnstalleerd staan?

Haal dat pakket dan van je pc af tijdelijk, schakel even over op een ander anti-viruspakket (AVG Free bijvoorbeeld) en kijk of de meldingen dan wegblijven verder.

Succes,

Tijs.

 

[Theezakje]

bedankt voor je advies Tijs ik heb Norton antivirus van mijn computer verwijderd. Zoals ik verwacht had heb ik nog steeds last van crash dumps want voordat ik norton had geïnstalleerd had ik ook last van crashdump het is al een tijdje aan de gang.

Dus besloot ik een memtest te laten draaien een programma dat mijn Ram geheugen controleert op fouten ik kreeg na 1min al een melding dat er een fout zat in mijn Ram geheugen maar de geheugen module van OCZ is redelijk nieuw. Is het mogelijk dat nieuwe modules fouten bevatten??

Ik heb hier nog een samenvatting van een crash dump van een tijdje geleden:


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


Loading Dump File [C:\Users\Rhebas\Documents\Crashdump\Mini021708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: scv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: scv*C:\symbols*http://msdl.microsoft.com/download/symbols
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sun Feb 17 22:37:58.886 2008 (GMT+2)
System Uptime: 0 days 9:59:10.652
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
......
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffd450d8, 0, 8f8cac40, 0}

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

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe ( nt+a9ef2 )

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

 

[dnties]

Je geheugen kan wel degelijk kapot zijn.

Ik neem aan dat je garantie hebt, dus neem contact op met de leverancier voor een nieuwe module, en test die ook.

Verder de bekende riedel: Kast stofvrij maken, alle insteekkaarten + geheugenmodules even eruit, contactpunten schoonmaken met alcohol en weer terugplaatsen etc.

Kijk ook of alle ventilatoren goed draaien.

Succes,

Tijs.

 

[Theezakje]

Hey,

Was je helemaal vergeten te bedanken voor je hulp. Thanks nog. Heb inmiddels nieuwe geheugen.

greetz,

 

[dnties]

Bedankt voor je terugmelding, en fijn dat het nu goed werkt voor je.

Wil je nog even de vraag op opgelost zetten? Dat doe je door te klikken op "Vraag is opgelost" in het vakje "Status van de vraag" (rechts onderaan deze webpagina).

Tijs.