Stopfout (af en toe)

[math678]

heren, dames

Wie kan me helpen met het volgende.
Ik heb sinds c.a. december 2008 ongeveer om de 14 dagen eens een stopfout melding bij het opstarten van de PC. Na de restart is er niks meer aan de hand.
Vervolgens gaat het ongeveer 14 dagen goed en dan krijg ik weer eens een stopfout.

Wel heb ik eind december mijn pc weer bijgewerkt met alle essentiele Windows updates.
Dit waren er een stuk of 20. Kan het hier aan liggen ?

Kan ik evt een logfile van de stopfout van mijn pc halen en hier posten zodat jullie aan de hand van een eventuele foutcode kunnen zien waar het probleem zit ??
Hoor het wel.

 

[ErpCity]

Het zou inderdaad ontzettend helpen als je de "code" van deze stopfout wist... want van daar uit kunnen we makkelijker mee zoeken naar de oorzaak...

Hier een paar voorbeeldjes van stopcodes:

Software en stuurprogrammafouten

0x0000001E KMODE_EXCEPTION_NOT_HANDLED
0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
0x00000050 PAGE_FAULT_IN_NONPAGED_AREA
0x0000000A IRQL_NOT_LESS_OR_EQUAL
0x0000007B INACCESSIBLE_BOOT_DEVICE
0x0000009F DRIVER_POWER_STATE_FAILURE
0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH

Stop fouten 0x0000001E, 0x0000000A, en 0x0000007B kunnen ook duiden op hardwarefouten.

Bestandssysteemfouten

0x00000023 FAT_FILE_SYSTEM
0x00000024 NTFS_FILE_SYSTEM


Fouten mbt falende hardware

0x0000001E KMODE_EXCEPTION_NOT_HANDLED
0x0000000A IRQL_NOT_LESS_OR_EQUAL
0x0000007B INACCESSIBLE_BOOT_DEVICE
0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
0xC0000218 UNKNOWN_HARD_ERROR

 

[math678]

dank je, daar zal ik de volgende keer al op letten.
Kan ik de foutcode ergens uit een logfile van mijn computer halen ??

 

[adnieuwenhuizen]

Als je eind december de laatste updates hebt opgehaald zou ik snel de nieuwste downloaden. en dit vervolgens regelmatig doen zodat je systeem up to date blijft

 

[math678]

Beste Ad,

Dat doe ik ook regelmatig.
In december kreeg ik ineens een popup met nieuwe updates.
Bij installatie bleken het er c.a. 20 te zijn
Hou PC altijd up-to-date met updates.
Heb ook geen idee of het daa aan ligt.
Het waren normale windows (ESSENTIELE) updates

 

[math678]

Momenteel geen nieuwe updates meer te installeren. ben up to date

 

[ErpCity]

Zover ik weet, maar ik check zelden de logfiles omdat ik automatisch herstarten uitgezet heb, dus dat (BSOD) schattige blauwe scherm blijft staan zodat ik de code kan aflezen, staat die foutcode ook in de logfile.....

 

[math678]

Iemand een idee waar ik de logfile met code kan ophalen op mijn computer /

 

[math678]

niemand ?

 

[math678]

Vandaag weer eens stopfout gehad. Heeft weer c.a 2 weken geduurd voordat ik er weer een kreeg.
PC startte normaal op en bleef uiteindelijk op het bureaublad hangen. Na c.a 1 minuut de melding voor restart
Na restart melding ernstige waarschuwing van stopfout met de volgende inhoud:

BCCode : 10000050 BCP1 : FFFFFFFC BCP2 : 00000000 BCP3 : 80551168
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 768_1

Wie kan me verder helpen.

 

[anton44]

Mijn aanpak zou zijn.
Met CCleaner overtollige bestanden opruimen en registerfouten verwijderen. Vervolgens met een defragmentatiesoftware die ook de MFT bewerkt defragmenten (bv Paragon Total Defrag)

 

[math678]

beste Anton,

CC cleaner heb ik op mijn systeem.
Zal eens een volledige verfrissing van het systeem uitvoeren.
Wat bedoel je exact met die ook de MFT (?) bewerkt.
Hoor het wel.

P.s. kan het kwaad voor mijn systeem als dit om de 2 weken ongeveer gebeurd ??

 

[anton44]

beste Anton,

CC cleaner heb ik op mijn systeem.
Zal eens een volledige verfrissing van het systeem uitvoeren.
Wat bedoel je exact met die ook de MFT (?) bewerkt.
Hoor het wel.

P.s. kan het kwaad voor mijn systeem als dit om de 2 weken ongeveer gebeurd ??

MFT = Master File Table. Google kan je dat verder uitleggen.
CClener gebruik ik al jaren en frequent en heeft me nog nooit problemen bezorgd. Ook regelmatige de updates ophalen en installeren !
Als je Paragon Total Defrag gebruikt zal het proces een aantal uurtjes in beslag nemen.
Succes, Ton

 

[math678]

Beste Anton,

CCleaner volledig uitgevoerd. (incl. alle registeropschoningen).
Paragon Total Defrag ken ik niet.
Dan zal ik me deze moeten aanschaffen.
Zijn er nog andere programma's die het identieke proces op MFT uitvoeren ?

Zag op internet ook nog van Paragon:
Harddisk Manager 2009 Professional
Paragon partition manager 9.0
Kunnen deze programma's ook het door jou bedoelde proces ??

 

[anton44]

Beste Anton,

CCleaner volledig uitgevoerd. (incl. alle registeropschoningen).
Paragon Total Defrag ken ik niet.
Dan zal ik me deze moeten aanschaffen.
Zijn er nog andere programma's die het identieke proces op MFT uitvoeren ?

Zag op internet ook nog van Paragon:
Harddisk Manager 2009 Professional
Paragon partition manager 9.0
Kunnen deze programma's ook het door jou bedoelde proces ??

Van de harddiskmanager is de defrag een onderdeel = dus goed.
Andere ken ik op dit moment niet.

 

[math678]

Momenteel geinstalleerd: Paragon harddisk Manager 2009 Professional edition.

In keuzemenu:
1) Backup and restore
2) Maintenance
3) Rescue and recovery
4) wiping
5) advanced options

In keuze 2: Harddisk Optimalisation: defragment file system
Moet ik deze keuze uitvoeren ?
Ik kom dan in een ongeveer identiek scherm als defragmenteren in XP.
Deze volledig uitvoeren ? dan nog iets speciaal s doen ??
Hoor het wel.

 

[anton44]

Momenteel geinstalleerd: Paragon harddisk Manager 2009 Professional edition.

In keuzemenu:
1) Backup and restore
2) Maintenance
3) Rescue and recovery
4) wiping
5) advanced options

In keuze 2: Harddisk Optimalisation: defragment file system
Moet ik deze keuze uitvoeren ?
Ik kom dan in een ongeveer identiek scherm als defragmenteren in XP.
Deze volledig uitvoeren ? dan nog iets speciaal s doen ??
Hoor het wel.

Alles goed ! Gewoon doen om te beginnen voor schijf C:
Bij dit alles is een waarschuwing op zijn plaats om al je data veilig gesteld te hebben op een andere gegevensdrager voordat je begint.

 

[math678]

Paragon harddisk manager heeft neit geholpen.
Vandaag kreeg ik wederom een stopfout.
Na volledige opstart van het systeem ging hij ineens weer in reboot.

Opmerking: Systeem is hersteld van een ernstige fout.
Er is een logboekvermelding van deze fout gemaakt.
Vertel Micosoft dit Probleem (gedaan middels verzenden).
Als u de inhoud van dit foutenrapport wilt weergeven klik hier:

De inhoud was:
handtekening van fout:
BCCode : 19 BCP1 : 00000020 BCP2 : E2EC52D2 BCP3 : E2EC5D52
BCP4 : 0D500417 OSVer : 5_1_2600 SP : 3_0 Product : 768_1


Vervolgens kreef ik nog een Windows Error reporting scherm te zien met de volgende inhoud:
hebt dit bericht ontvangen omdat een apparaatstuurprogramma op uw computer heeft veroorzaakt dat het besturingssysteem van Windows ineens niet meer werkt. Dit fouttype wordt een "stopfout" genoemd. Als een stopfout zich voordoet, moet de computer opnieuw worden opgestart.

Wie kan me verder helpen aub

 

[Mik Zjegger]

Kijk ff naar de tip van dnties #3 hier http://www.helpmij.nl/forum/showthread.php?t=397656 voor het terughalen van 't foutenreport.

 

[math678]

debugger for windows gedownloaded.
Ik heb inderdaad 2 bestanden (2 dumpbestanden) in een map C:\windows\minidump
Middels keuze Open Crash Dump uit debugger for windows geprobeerd deze te lezen zodat jullie er misschien de juiste info uit kunnen halen.

Output bestand 1: (van dump 25 febr)
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini022509-01.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 0n2
*** 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Feb 25 23:07:49.062 2009 (GMT+1)
System Uptime: 0 days 3:23:26.627
*********************************************************************
* 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 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
..............
Unable to load image ftdisk.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ftdisk.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {60, 2, 0, f7868f9b}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ftdisk.sys ( ftdisk+f9b )

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

output bestand 2 van vandaag:
icrosoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini030809-01.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 0n2
*** 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Mar 8 22:32:06.406 2009 (GMT+1)
System Uptime: 0 days 0:00:52.109
*********************************************************************
* 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 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 19, {20, e2ec52d2, e2ec5d52, d500417}

***** 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!PVOID ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for d347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for d347bus.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : sptd.sys ( sptd+60e3 )

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


Is dit de fout:
Unable to load image ntoskrnl.exe, Win32 error 0n2
??

Hoor het wel.