Laptop boot met bluescreen

[whitedreamvw]

Beste jongens,

telkens als mijn laptop boot, krijg ik een bluescreen.

De minidump heb ik hieronder geknald.

Help mij please.

-------------


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


Loading Dump File [H:\backup tante kim\Mini121410-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 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553e40
Debug session time: Tue Dec 14 20:21:53.000 2010 (GMT+1)
System Uptime: 0 days 0:00:26.572
*********************************************************************
* 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 1000000A, {714, 2, 0, 804fdc84}

***** 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 : ntoskrnl.exe ( nt+26c84 )

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

dit is het probleem van de mindump.

Iemand een oplossing? Het geheugen is al volledig getest geworden.

[TERW_DAN]

Heb je hier al eens gekeken: Windows XP en 2000 BSOD guide

Het is niet de bedoeling hier maar een log te dumpen en te hopen dat iemand een antwoord weet.
Wat heb je zelf geprobeerd en getest en wat waren daar de resultaten van? Als je die post kunnen we je wellicht een stuk beter helpen.

[whitedreamvw]

Hey,

Ik heb die dingen gekregen en de melding die ik krijg is namelijk 0x0000000A IRQL_NOT_LESS_OR_EQUAL

Het volgende heb ik zelf gedaan: Alle drivers geupdate; Windows Update; Memory test;

Wat opvalt is dat Veilige modus werkt.
Daar en tegen is dit niet elke keer het bluescreen. mss 6 van de 10 keer. Soms doet ie het ook 4 keer achter elkaar.

Heel raar dus.

[GENETX]

Dan gooi je die STOP code in Google en krijg je de volgende Microsoft-pagina:

In Windows XP wordt het foutbericht 'Stop 0x0000000A' weergegeven

Dit Stop-foutbericht treedt meestal op tijdens de installatie als in de kernel-modus is geprobeerd op een te hoog proces-IRQL (internal request level) wisselbaar geheugen aan te spreken. Deze fout treedt over het algemeen op wanneer er een onjuist geheugenadres wordt gebruikt door een stuurprogramma. Andere mogelijke oorzaken van deze fout zijn een incompatibel stuurprogramma, een algemeen hardwareprobleem en incompatibele software.

Het zal waarschijnlijk aan een driver liggen die niet helemaal goed is. Zeker omdat je het probleem in de veilige modus niet hebt. In dat geval worden minder drivers geladen en waarschijnlijk degene die deze problemen veroorzaakt niet. Ik zou eens proberen om drivers de te deinstalleren en een voor 1 opnieuw proberen, of in het uiterste geval een schone installatie proberen.

Overigens, hoe lang heb je die memory test laten draaien?

[whitedreamvw]

Ik heb de memory test in de extended fase laten lopen! dit houdt in dat hij in een fase heeft gelopen dat bijna 2 uur duurde. echt lang, maar goed voor een oplossing moet je wat over hebben.

Ik ga nog eens drivers verwijderen installeren.
Is er geen manier uit te halen, welke driver ik dit moet voorstellen?

[GENETX]

Uit de informatie die ik hier zie kan ik dat iig niet snel halen. Daarbij, het hoeft geen driver te zijn, het heeft alleen op dit moment mijn vermoeden.