BSOD...rozlusteni debugger

[TRINI]

Dobrý den,
prosím o pomoc s rozlustenim neustalych padu systemu,tady je log z debuggeru,co je u mě špatně ????
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [I:\Minidump\Mini032309-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 \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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x81a0a000 PsLoadedModuleList = 0x81b21c70
Debug session time: Mon Mar 23 21:19:50.577 2009 (GMT+1)
System Uptime: 0 days 0:00:23.389
*********************************************************************
* 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 \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 4E, {99, a4e6a, 2, a42fa}

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

Followup: MachineOwner
ještě trochu přidám :
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: nt

FAULTING_MODULE: 81a52000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12

BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81af594b to 81b1f163

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9a75ffc0 81af594b 0000004e 00000099 0008b20a nt+0xcd163
9a760024 81af37c5 88e45a40 88ea8b70 88e45a40 nt+0xa394b
9a76048c 81af1f4e 88e45a40 00000000 00000000 nt+0xa17c5
9a7604b8 81c60f8e e1e458d8 88ea8dd0 88ea8b70 nt+0x9ff4e
9a76051c 81c612ff 00000000 00000000 88ea8b70 nt+0x20ef8e
9a76053c 81c35064 88ea8b70 c0000005 00000001 nt+0x20f2ff
9a76056c 81aa9a7a ffffffff c0000005 9a7609b0 nt+0x1e3064
9a76057c 81aa8aa1 badb0d00 9a7605f4 00000000 nt+0x57a7a
9a7609b0 81a7e832 9a7609dc 00000000 9a760d64 nt+0x56aa1
9a760d34 81aad573 0011db88 0011dba4 00000000 nt+0x2c832
9a760d50 81aa9a7a 0011db88 0011dba4 00000000 nt+0x5b573
9a760d64 770a9a94 badb0d00 0011db7c 00000000 nt+0x57a7a
9a760d68 badb0d00 0011db7c 00000000 00000000 0x770a9a94
9a760d6c 0011db7c 00000000 00000000 00000000 0xbadb0d00
9a760d70 00000000 00000000 00000000 00000000 0x11db7c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+cd163
81b1f163 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+cd163

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

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

[zombux]

log uvádí jen obecnou chybu, spíš bych hledal problém v něčem typu vadné paměti, prvně bych zkusil memtest

[TRINI]

log uvádí jen obecnou chybu, spíš bych hledal problém v něčem typu vadné paměti, prvně bych zkusil memtest

tak memtest nic neukazal....ale zkusil jsem moje paměti GEIL v daném PC a jede bez problémů...bios desky je nejnovější...tak asi špatná kompatibilita pamětí A-data Vitesta DDR2 s deskou Gigabyte EP45-DS3....????

[zombux]

to je možné, vitesty jsou notoricky problémové paměti, už jsem taky zažil že zlobily a přitom memtest neukázal nic ani po mnoha hodinách testování

[Wlkus]

ja sem mel treba vitesty, co normalne bezely v memtestu, ale pri spustebni 3d hry to obcas padalo a resetovalo sbernici. Spolehlive to odhalil az FurMark, ve kterem pocitac nevydrzel vic nez deset sekund a tak jsem nakonec objevil onen spatny modul. problem jsem reklamoval v alze a prekvapila me pohotova vymena kus za kus rovnou bez testovani...

[TRINI]

ja sem mel treba vitesty, co normalne bezely v memtestu, ale pri spustebni 3d hry to obcas padalo a resetovalo sbernici. Spolehlive to odhalil az FurMark, ve kterem pocitac nevydrzel vic nez deset sekund a tak jsem nakonec objevil onen spatny modul. problem jsem reklamoval v alze a prekvapila me pohotova vymena kus za kus rovnou bez testovani...

tak u mě taky proběhla reklamace...nejřív v czc.cz vyměnili HDD , ale asi jim stale padalo tak zkusili ještě novou desku no a nakonec vyměnili RAMky a bylo po problému...takže reklamace v pořádku a za 4 dny jsem mel PC zpět.....