BSOD: NEEeeeeeeee !!

[P.de Gast]

Al enige tijd wordt ik geteisterd door BSOD (blauwe schermen).

Daar ik aankomende zaterdag heb gereserveerd om hier aandacht aan te geven doe ik een beroep op alle Help-mij-ers.

Tot dusver heb ik wat gegoogeld en ben ik iets wijzer waar de oorzaak vaak mee te maken heeft.
Mijn probleem is alleen dat ik steeds verschillende meldingen krijg en dus niet mijn vinger op het juiste onderdeel kan leggen.....
Na de herstart is er een scherm met de melding "onverwachte afsluiting" bladibla...
"Wilt u zoeken naar een oplossing?"
Wanneer ik daar akkoord voor geef lijkt dat programma te gaan zoeken maar sluit vervolgens af....
Bestanden die helpen bij het beschrijven van het probleem zoals vermeld in de eerste BcCode hieronder kan ik niet op die plaats vinden

Hier de meldingen die ik heb ontvangen (er is nog een gebruiker).

*******************************************************************
BCCode: 10000050
BCP1: E2D43591
BCP2: 00000008
BCP3: E2D43591
BCP4: 00000002
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1
Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\Mini030309-02.dmp
C:\Users\Peter\AppData\Local\Temp\WER-71760-0.sysdata.xml
C:\Users\Peter\AppData\Local\Temp\WER740.tmp.version.txt
**********************************************************

BCCode: 1000000a
BCP1: 00F1EBB0
BCP2: 00000002
BCP3: 00000000
BCP4: 826E561C

BCCode: 1000008e
BCP1: C0000005
BCP2: 05773B81
BCP3: 8AEA4CE0
BCP4: 00000000

BCCode: 1000008e
BCP1: C0000005
BCP2: 826C0009
BCP3: 8D1FDB25
BCP4: 00000000

BCCode: 1000007e
BCP1: C0000005
BCP2: 931285BC
BCP3: 80599600
BCP4: 805992FC

BCCode: da
BCP1: 00000504
BCP2: C0400000
BCP3: 00000012
BCP4: 00000000

BCCode: 1a
BCP1: 00000030
BCP2: 891B9548
BCP3: F4B97000
BCP4: A8D5F904

BCCode: 100000d1
BCP1: 4F444648
BCP2: 00000002
BCP3: 00000001
BCP4: 8C17FA46

BCCode: 1000000a
BCP1: 43FD0520
BCP2: 00000002
BCP3: 00000001
BCP4: 829DBFF9

BCCode: 1000007e
BCP1: C0000005
BCP2: 827353C2
BCP3: 8E6C4528
BCP4: 8E6C4224

Tot 25 maart 2009

========================================

Wanneer meer info nodig is hoor ik dit graag.
Alle hulp is van harte welkom.

Alvast bedankt
Peter

 

[jackall]

De meeste info die ik tegenkom mbt deze foutcode is een probleem met het geheugen of een corrupte bestandsindeling(ntfs).
Misschien is dit een duwtje in de goede richting.

Suc6

 

[P.de Gast]

Hallo Jackall,
Bd voor jouw reactie !!

Op welke van de 10 genoemde BSOD's heb jij gezocht?

 

[dnties]

C:\Windows\Minidump\Mini030309-02.dmp

Lees die eens uit als Crash-dump uit met Debugging Tools for Windows.
Kijk even deze discussiedraad goed door voor links en 'bijzonderheden' van Vista m.b.t. het starten van WinDbg en toegang tot de C:\Windows\Minidump map.

Succes,

Tijs.

 

[P.de Gast]

27-3-2009
Deze met opstarten, na correct afsluiten
BCCode: 1000007e
BCP1: C0000005
BCP2: 931245BC
BCP3: 80599600
BCP4: 805992FC

Ik zie dat de BCCode 1000007e nu twee keer achter elkaar terug komen...
Waar kan dit op duiden?

 

[P.de Gast]

Wat kan ik hiermee?


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


Loading Dump File [C:\Windows\Minidump\Mini032609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82647000 PsLoadedModuleList = 0x8275ec70
Debug session time: Thu Mar 26 09:30:30.648 2009 (GMT+1)
System Uptime: 0 days 0:00:25.413
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 ecache.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ecache.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 827353c2, 8e6c4528, 8e6c4224}

*** WARNING: Unable to verify timestamp for mssmbios.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 ***
*** ***
*************************************************************************
Probably caused by : ecache.sys ( ecache!EcMdlFree+52 )

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

0: kd> g
^ No runnable debuggees error in 'g'
0: kd> .reload
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
..
0: kd> !analyze -show
Unable to load image ecache.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ecache.sys
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 827353c2, The address that the exception occurred at
Arg3: 8e6c4528, Exception Record Address
Arg4: 8e6c4224, Context Record Address

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for mssmbios.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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: ecache

FAULTING_MODULE: 82647000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918fb7

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.

FAULTING_IP:
nt+ee3c2
827353c2 f644241004 test byte ptr [esp+10h],4

EXCEPTION_RECORD: 8e6c4528 -- (.exr 0xffffffff8e6c4528)
ExceptionAddress: 827353c2 (nt+0x000ee3c2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000010
Attempt to read from address 00000010

CONTEXT: 8e6c4224 -- (.cxr 0xffffffff8e6c4224)
eax=00000010 ebx=000001ff ecx=00000300 edx=00000400 esi=00000002 edi=87d83d08
eip=827353c2 esp=8e6c45f0 ebp=8e6c4648 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
nt+0xee3c2:
827353c2 f644241004 test byte ptr [esp+10h],4 ss:0010:8e6c4600=02
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8c368f3c to 827353c2

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8e6c4648 8c368f3c 87d83d10 00000000 8c37d500 nt+0xee3c2
8e6c4660 8c370838 87d83d10 000171ea 8c37de28 ecache!EcMdlFree+0x52
8e6c46f0 8c372888 88d59b80 8c37dc70 8c37d500 ecache!EcCacheIoCleanup+0xa8
8e6c4c8c 8c373e54 8eb2fd80 00000000 86a13820 ecache!EcCacheIoDereference+0x558
8e6c4d7c 8281cb18 8c37d500 56991f18 00000000 ecache!EcCacheIoWorker+0x886
8e6c4dc0 82675a2e 8c3735ce 8c37d500 00000000 nt+0x1d5b18
00000000 00000000 00000000 00000000 00000000 nt+0x2ea2e


FOLLOWUP_IP:
ecache!EcMdlFree+52
8c368f3c ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ecache!EcMdlFree+52

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ecache.sys

STACK_COMMAND: .cxr 0xffffffff8e6c4224 ; kb

BUCKET_ID: WRONG_SYMBOLS

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 827353c2, The address that the exception occurred at
Arg3: 8e6c4528, Exception Record Address
Arg4: 8e6c4224, Context Record Address

Debugging Details:
------------------

***** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: ecache

FAULTING_MODULE: 82647000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918fb7

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.

FAULTING_IP:
nt+ee3c2
827353c2 f644241004 test byte ptr [esp+10h],4

EXCEPTION_RECORD: 8e6c4528 -- (.exr 0xffffffff8e6c4528)
ExceptionAddress: 827353c2 (nt+0x000ee3c2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000010
Attempt to read from address 00000010

CONTEXT: 8e6c4224 -- (.cxr 0xffffffff8e6c4224)
eax=00000010 ebx=000001ff ecx=00000300 edx=00000400 esi=00000002 edi=87d83d08
eip=827353c2 esp=8e6c45f0 ebp=8e6c4648 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
nt+0xee3c2:
827353c2 f644241004 test byte ptr [esp+10h],4 ss:0010:8e6c4600=02
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8c368f3c to 827353c2

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8e6c4648 8c368f3c 87d83d10 00000000 8c37d500 nt+0xee3c2
8e6c4660 8c370838 87d83d10 000171ea 8c37de28 ecache!EcMdlFree+0x52
8e6c46f0 8c372888 88d59b80 8c37dc70 8c37d500 ecache!EcCacheIoCleanup+0xa8
8e6c4c8c 8c373e54 8eb2fd80 00000000 86a13820 ecache!EcCacheIoDereference+0x558
8e6c4d7c 8281cb18 8c37d500 56991f18 00000000 ecache!EcCacheIoWorker+0x886
8e6c4dc0 82675a2e 8c3735ce 8c37d500 00000000 nt+0x1d5b18
00000000 00000000 00000000 00000000 00000000 nt+0x2ea2e


FOLLOWUP_IP:
ecache!EcMdlFree+52
8c368f3c ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ecache!EcMdlFree+52

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ecache.sys

STACK_COMMAND: .cxr 0xffffffff8e6c4224 ; kb

BUCKET_ID: WRONG_SYMBOLS

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

0: kd> lmvm ecache
start end module name
8c366000 8c38d000 ecache M (pdb symbols) c:\windows\symbols\sys\ecache.pdb
Loaded symbol image file: ecache.sys
Image path: ecache.sys
Image name: ecache.sys
Timestamp: Sat Jan 19 06:50:47 2008 (47918FB7)
CheckSum: 0002BF07
ImageSize: 00027000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Harry Snor]

Hoi !

Groot aantal verschillende foutmeldingen kan duiden op een corrupte geheugen-module.

De meldingen betr.ecache.sys zou daar ook op kunnen wijzen.

Ook een beschadigde boot-sector is mogelijk.

Blijkt je geheugen correct, dan opstarten van de Vista-DVD en kiezen voor: repair

Greetz,

Harry.

 

[P.de Gast]

Hallo Harry,

Met dat geheugen bedoel je RAM ?
Deze heb ik enige tijd geleden wel vervangen (van 2 x 512 mb naar 2x2G)
Hoe controleer ik de boot sector?

Ik ben er klaar voor

Peter

 

[telwat]

Zijn de problemen mischien begonnen na het vervangen van het geheugen?

 

[P.de Gast]

Zijn de problemen mischien begonnen na het vervangen van het geheugen?

Dat kan ik mij niet herinneren, dat is te lang geleden.

Ik weet 99% zeker dat het RAM geheugens zijn, die geschikt zijn voor deze PC:
Oude: Swissbit 512mb-pc2-5300-555
Nieuw: Kingston 4GB-pc2-5300 CL5 240-pin DIMM Kit (2pcs)
(ligt nog voor me !)

Dusszzz....

 

[Harry Snor]

Hoi !

Kijk es op de site van de maker van je mobo of er een bios-update voorhanden is i.v.m. geheugenuitbreiding o.i.d. ?

En is je nieuwe geheugen wel geschikt voor je mobo; d.w.z. staan de modules in de Q.L.V. ? (d.w.z. de lijst met aanbevolen/goedgekeurde modules ?

Heb je ook rekening gehouden met de enkel/of dubbel-zijdige modules ?

Ik garandeer je dat hier ergens de oorzaak ligt.

Greetz,

Harry.

 

[telwat]

Oude geheugen terug zetten en kijk of het probleem blijft.

 

[P.de Gast]

@Harry:

Fijn dat je mee wilt denken: dikke pluim!!

Hier mijn PC gegevens

http://www.targa.nl/index.jsp?SID=0&NAV=236&DOC=&PAGE=1968&PCAT=2&PROD=364&PTUBE=10&PARAMS=undefined&PARAMS2=undefined&SPCAREA=undefined

Kan ik aan de hand van de specs concluderen dat de BIOS "klaar" was voor de 4G RAM set?

 

[Harry Snor]

Hoi !

Hier: http://www.service.targa.co.uk/garantien.php?lang_id=2 even je serienr. intrommelen en zoeken naar een Qualified Vendoes List, of een evt. bios-update.

Greetz,

Harry.

 

[P.de Gast]

28-03-2009:
Dit sond open: Explorer, Aangifte 2008, verzenden met digid, Vuze, MSOutlook

En toen.....BSOD....

BCCode: 1000000a
BCP1: 00004E70
BCP2: 00000004
BCP3: 00000000
BCP4: 8270C373

Windbg verteld:

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


Loading Dump File [C:\Windows\Minidump\Mini032809-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82651000 PsLoadedModuleList = 0x82768c70
Debug session time: Sat Mar 28 10:10:45.980 2009 (GMT+1)
System Uptime: 0 days 0:43:09.899
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, {4e70, 4, 0, 8270c373}

***** 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 : hardware ( nt+bb373 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00004e70, memory referenced
Arg2: 00000004, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8270c373, address which referenced memory

Debugging Details:
------------------

***** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 82651000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00004e70

CURRENT_IRQL: 0

FAULTING_IP:
nt+bb373
8270c373 0200 add al,byte ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

MISALIGNED_IP:
nt+bb373
8270c373 0200 add al,byte ptr [eax]

LAST_CONTROL_TRANSFER: from 826a2b4c to 8270c373

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805ecb60 826a2b4c 00000020 805ecb88 805ecba8 nt+0xbb373
805ecbb4 8270c0be 805ecbe0 00000000 00000002 nt+0x51b4c
805ecc00 8270c1c7 00000f43 20004000 00000008 nt+0xbb0be
805ecc2c 826a47c8 85724bf8 00005200 13700c5f nt+0xbb1c7
00000000 00000000 00000000 00000000 00000000 nt+0x537c8


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+bb373
8270c373 0200 add al,byte ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+bb373

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

Wat is nt+bb373 voor onderdeel ??

 

[P.de Gast]

Hoi !

Hier: http://www.service.targa.co.uk/garantien.php?lang_id=2 even je serienr. intrommelen en zoeken naar een Qualified Vendoes List, of een evt. bios-update.

Greetz,

Harry.

Bedoel je het serie nummer van het MOBO?
Kan ik dat optrommelen met Everest?
(of moet ik de pc openmaken)

Fijn dat je er bij bent :thumb:

 

[Harry Snor]

Hoi !

Geen idee, maar: heb je nu eindelijk het eens met 1 geheugen-module in het eerste slot geprobeerd ?

Of: je oude geheugen terug te plaatsen ?

Geheugen al getest met memtest ?

Zo schiet het dus niet op; je moet wel wat doen met onze suggestie's.

 

[P.de Gast]

@Harry

Mijn excuses als ik de verkeerde indruk wek.....

Ik wil graag door bliven werken met de 4G Ram geheugens.
Ik heb ze tenslotte niet voor niets gekocht...

Ondertussen draait MemTest (3x) en deze heeft al diverse errors gevonden.....
Deze verwijzen allen naar online faq, question 2:
http://hcidesign.com/memtest

Op de site van Targe is inderdaad een Bios update geplaatst welke ik ook al eens heb binnen gehaald maar waarschijnlijk niet heb geinstalleerd (of verkeerd).

Zal het niet updaten van de Bios de gemelde MemTest RAM fouten tot gevolg kunnen hebben?

Groet,
Peter

 

[Harry Snor]

Hoi !

Als memtest al zo vlug fouten aan geeft is1 of meerdere van je geheugenbanken corrupt.

Dus: opstarten met 1 geheugen-module, kijken of je probleem is opgelost, en testen.

Zoniet: volgende proberen, etc.

Mogelijk heb je nog garantie op je geheugen, dan dus onder RMA alles omruilen voor het JUISTE geheugen.
Kun je vinden op de site van Targa.

Greetz,

Harry.

 

[P.de Gast]

Onder MemTest weer een Bsod:

BCCode: 1000007e
BCP1: C0000005
BCP2: 8268C588
BCP3: 8E73DB20
BCP4: 8E73D81C
En de uitslag:

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


Loading Dump File [C:\Windows\Minidump\Mini032809-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82600000 PsLoadedModuleList = 0x82717c70
Debug session time: Sat Mar 28 13:21:48.383 2009 (GMT+1)
System Uptime: 0 days 0:00:24.258
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 ecache.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ecache.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8268c588, 8e73db20, 8e73d81c}

*** WARNING: Unable to verify timestamp for mssmbios.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 ***
*** ***
*************************************************************************
Probably caused by : ecache.sys ( ecache!EcMemoryCacheIoRoutine+16e )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8268c588, The address that the exception occurred at
Arg3: 8e73db20, Exception Record Address
Arg4: 8e73d81c, Context Record Address

Debugging Details:
------------------

***** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: ecache

FAULTING_MODULE: 82600000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918fb7

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.

FAULTING_IP:
nt+8c588
8268c588 8b4b10 mov ecx,dword ptr [ebx+10h]

EXCEPTION_RECORD: 8e73db20 -- (.exr 0xffffffff8e73db20)
ExceptionAddress: 8268c588 (nt+0x0008c588)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000021
Attempt to read from address 00000021

CONTEXT: 8e73d81c -- (.cxr 0xffffffff8e73d81c)
eax=00000000 ebx=00000011 ecx=00000000 edx=00000000 esi=8c37a640 edi=88d99980
eip=8268c588 esp=8e73dbe8 ebp=8e73dbec iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210282
nt+0x8c588:
8268c588 8b4b10 mov ecx,dword ptr [ebx+10h] ds:0023:00000021=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8c370490 to 8268c588

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8e73dbec 8c370490 88d99980 00000000 00000001 nt+0x8c588
8e73dc91 00000000 b8000000 0086a33a 00000000 ecache!EcMemoryCacheIoRoutine+0x16e


FOLLOWUP_IP:
ecache!EcMemoryCacheIoRoutine+16e
8c370490 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ecache!EcMemoryCacheIoRoutine+16e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ecache.sys

STACK_COMMAND: .cxr 0xffffffff8e73d81c ; kb

BUCKET_ID: WRONG_SYMBOLS

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

Ik ga even een geheugen verwijderen.....