Asensin puhtaan win7 asennuksen jonka jälkeen asentelin virusturvat ja näyttiksen ajurit kuntoon yms. Kaikki pelitti aivan normaalisti. No sen jälkeen heitin vanhan kovon sisään josta halusin tiedostoja ulos. Kovolta löytyi kuitenkin viruksia avastin tarkistuksessa. No kattelin sitten sieltä jotain kansioita musaa ja muuta mitkä eivät tarkistuksen mukaan sisältäneet viruksia ja siirsin uudelle kovolle. Formatoin vanhan kovon. No kuitenkin jo seuraavassa käynnistyksessä jymähti toi BSOD. Menee ohi niin nopee ettei ehdi lukemaan. Eli oon sen jälkeen yrittäny windowsin start up repairia mutta sen mukaan ei onnistu korjaus. Onko joku virus heittänyt jo windowsin sekaisin? Onko muuta mahista ku asentaa windows uudestaan? -duupadu-
F8 nappulaa naputtelemalla (pari kertaa sekunnissa tahtia) koneen käynnistyessä avautuu "vikasietotilavalikko". Siitä löytyy myös automaattisen käynnistyksen esto. Tämän jälkeen ehtii lukemaan virheilmoituksen siniseltä ruudulta. Ota kokeeksi vanha levy vielä irti, vaikka boottasihan kone jo senkin kanssa.
Ok en huomannut tuota automaattisen käynnistyksen estoa. Vikasietotilaa yms. sieltä jo kokeilinkin, ja juu on kokeiltu ilman vanhaa levyä. Luultavasti joutuu vetään winukan uudestaan kattellaan huomenna lisää..
Mites ku asensin just ennenku boottasin ja formatoin vanhan kovon ni finnish language packin windowsin mukaan onnistuneesti. Voiko olla että siinä meni jotain pieleen?
Moi, mulla kanssa on tommone BSOD onkelma ja nyt alkaa jo vähä tympii ku oon jo kaikkee kokeillu muttei oo mikää auttanu tossa kuva siitä ---> http://www.aijaa.com/v.php?i=5552207.jpg Olisin hyvin kiitollinen vastauksista.
Memory_management viittaisi muisteihin.. Tässä MS:n windowspäivitys joka tulisi ladata ja asentaa: http://support.microsoft.com/kb/929338/fi Tässä taas pähkäillään näytönohjaimen tiedostojen roolia vastaavalle ongelmalle (niiden uudelleenasennus), mutta ehdotetaan myös bios-patterin poistoa emolevyltä tuokioksi, mikä on auttanut jossain tapauksessa: http://www.tomshardware.com/forum/235436-45-memory_management-error-windows
Windows 7 kyseessä, mutta ajelin tuossa eilen vähän memtestiä ja molemmilla kammoilla illmeni 2 tunnin ajon jälkeen monta sataa erroria, sitten ajelin vain yhdellä kammalla eikä mitään erroreita ja ajelin toisella ja taas puski erroreita eli muisteissa vika?
Jos memetest antaa erroria, ilman muuta muistien vaihto takuuseen, jos se on mahdollista. Voip olla että koneesi toiminta on kiinni vain ehjistä muistikammoista.
Juu kyllähän se on muistikammasta kiinni, jos kone pätkii kun molemmat kammat on paikoillaan, mutta ei pätki jos vain toinen on kiinni. Useilla muistivalmistajilla on käsittääkseni elinikäinen takuu muistikammoille, joten takuun puolesta tuskin ongelmia tulee. Mutta toisaalta muisti on niin halpaa nykyisin, että jaksaako sitä lähetellä toiselle puolelle maailmaa ja odottaa pari-kolme viikkoa että saa uuden tilalle? Tietenkin jos muistien vaihto onnistuu liikkeessä, josta sen on ostanut (suomessa), niin nopeastihan se silloin hoituu.
Juu eli Takuuseen vaan, ja onko kellään noista jimmsin takuutoimista kokemuksia? millä mielellä ne yleensä lähtee noita takuuasioita hoitamaan, kauan kestöö?
Tähän voisi sitten tarkentaa yhden asian muistien takuusta. Elinikäinen takuu nimestä huolimatta ei tarkoita loputonta takuuta. Valmistajat haluavat tämän epämääräisen mainosnimen aiheuttamaan sekaannusta ja luuloja paremmasta. Takuu todellisuudessa kattaa valmistajan ennalta määräämän muistien oletetun eliniän. Se kuinka paljon se on vaihtelee valmistajien välillä ja ikää on vaikea saada selville. Kyse on kuitenkin 4+ vuodesta.
No jos viet sen ite sinne ja iillä sattuu olemaan heti aikaa testata se ni voipi olla että vaihtavat heti, mut jos joudut jättämään sen sinne ni varmaan viikon kaksi viepi... (ainakin helsingissä, turusta en osaa sanoa)
Ja taas tuli BSOD -.- tässä dumpfile Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\011810-25864-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50 Debug session time: Mon Jan 18 15:19:46.884 2010 (GMT+2) System Uptime: 0 days 0:00:27.351 ********************************************************************* * 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\ntoskrnl.exe, Win32 error 0n2 *** 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 3B, {c0000005, fffff80002dac56d, fffff880038a2740, 0} ***** 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 : ntoskrnl.exe ( nt+34b56d ) Followup: MachineOwner --------- Edit:Semmosta vielä tohon että luin jostain et näppäimistö vaikuttaa tohon ntoskrnl.exe erroriin ja ostin eilen uuden näppämistän mutta vasta tänään koulusta tullessa ilmeni tuo BSOD??
Ja taas tuli BSOD -.- tässä dumpfile Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\011810-25864-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50 Debug session time: Mon Jan 18 15:19:46.884 2010 (GMT+2) System Uptime: 0 days 0:00:27.351 ********************************************************************* * 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\ntoskrnl.exe, Win32 error 0n2 *** 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 3B, {c0000005, fffff80002dac56d, fffff880038a2740, 0} ***** 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 : ntoskrnl.exe ( nt+34b56d ) Followup: MachineOwner ---------
