Problem z pamięcią 4GB - VISTA 32-bit - blue screen i reset


(Bochenekmarcin) #1

Wrzuciłem do lapka 4GB RAM i jest problem z Vistą 32-bit.

Nie chodzi mi o to, że faktycznie system korzysta jedynie z 3GB - bo przecież tak jest w systemach 32bit.

Problem tkwi w tym, że co jakiś czas wyskakuje blue screen i jest reset.

Wszystkie poprawki są zainstalowane w VISCIE we właściwościach widać 4GB RAM.

Kości są na pewno sprawne i kompatybilne.

VISTA ma zainstalowane wszystkie poprawki.

Opis problemu - z raportu windows:

Sygnatura problemu

Nazwa zdarzenia problemu: BlueScreen

Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.2

Identyfikator ustawień regionalnych: 1045

Pliki pomagające opisać problem (niektóre pliki mogą być już niedostępne)

Mini022812-01.dmp

sysdata.xml

Version.txt

Wyświetl tymczasową kopię tych plików

Ostrzeżenie: Jeśli problem został spowodowany przez wirusa lub inne zagrożenie zabezpieczeń, otwarcie kopii tych plików może zakłócić działanie komputera.

Dodatkowe informacje o problemie

BCCode: 1a

BCP1: 00008884

BCP2: 8396A440

BCP3: 8398F658

BCP4: 00000105

OS Version: 6_0_6002

Service Pack: 2_0

Product: 768_1

Informacje o serwerze: d36befad-24bc-4de4-8808-71fef11044cb

Proszę o Waszą pomoc :frowning:


(Frog) #2

mbs600 , popraw tytuł tematu, używając przycisku image.php?album_id=20&image_id=4038


(nnick) #3

przejedź pamięć memtestem, możliwe że jest walnięta


(Pawko86) #4

zainstaluj Windbg znajduje się w pakiecie Debugging Tools

przechwytywaniewhg.jpg

Uploaded with ImageShack.us

po zainstalowaniu odpalasz program Windbg wciskasz CTRL+D i wybierasz plik mididump znajdujący się w folderze c:\Windows\minidump

narzędzie bardzo dokładnie opisze ci co jest przyczyna blue screen możesz wrzuci cały log z programu tutaj to pomożemy jakbyś coś nie wiedział

Pozdrawiam


(Mutant5) #5

Pamięć może być walnięta, lub po prostu nie jest kombatybilna z Twoją płytą główną. Zaktualizuj BIOS i przetestuj pamięć, wtedy będziesz mógł mnie więcej się dowiedzieć co ma wpływ na BSy.


(Bochenekmarcin) #6

pamięc jest sprawna i kompatybilna na 100%.

nie mogę nigdzie znaleźć programu do odczytu minidump dla vista, wszędzie są wersje na windows 7 albo już 8.

nawet w podanym powyżej linku.

z tego co się gdzieś doczytałem problem powinien zniknąć jeśli zainstaluje viste najpierw na 2 gb ram, zainstaluje wszystkie aktualizacje, a potem dopiero dołoże drugie 2 gb, problem w tym, ze nie chce reinstalować systemu.

macie jeszcze jakieś pomysły, czy jest może jakaś poprawka systemowa naprawiająca ten problem? sp1 nie pomógł chociaż po zainstalowaniu go widzę w systemie 4 gb - nadal są BS.


(Mutant5) #7

Przeinstalowanie systemu raczej nic nie, to nie procesor system automatycznie się przystosowywuję do włożonej ilości. Skąd wiesz, że pamięci są sprawne i kombatybilne? Sprawdzałeś na innym systemie?


(Bochenekmarcin) #8

sprawdzane na wiele sposobów na innych komputerach i przez programy. poza tym pojedynczo w kazdym gniezdzie u mnie w lapku dzialaja bez problemu.


(Mutant5) #9

W takim razie po prostu ta para nie jest ze soba kombatybilna skoro każda z osobna działa.


(Bochenekmarcin) #10

zrzut z pliku minidump:

Microsoft ® Windows Debugger Version 6.2.8229.0 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\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 6002 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0x81c0f000 PsLoadedModuleList = 0x81d1c930

Debug session time: Mon Mar 5 17:47:15.947 2012 (UTC + 1:00)

System Uptime: 0 days 0:01:26.634

*********************************************************************

* 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\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

.....

TRIAGER: Could not open triage file : C:\Programy\Windows Kits\8.0\Debuggers\x86\triage\oca.ini, error 2

TRIAGER: Could not open triage file : C:\Programy\Windows Kits\8.0\Debuggers\x86\winxp\triage.ini, error 2

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8884, 83969828, 8396a440, 501}

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

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***

*** ***

*************************************************************************

TRIAGER: Could not open triage file : C:\Programy\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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 : ntoskrnl.exe ( nt+bb89f )

Followup: MachineOwner


Pomocy! :slight_smile: