Stránka 1 z 1
BSOD /zase/
Napsal: ned 2. kvě 2010, 13:24
od 4_X_4
problemy s bsod som uz maval predtym ale dal som to do servisu kde mi povedali ze som mal zle zapojeny hardware a bsod sa prestali objavovat... pred 3-4 dnami sa mi do ruk dostal datadisk na dow2 a hned ako si hram prvych 5-10 min. ma zase potesila stara znama.... vyzera asi takto
Podpis problému:
Název události problému: BlueScreen
Verze operačního systému: 6.1.7600.2.0.0.256.1
ID národního prostředí: 1051
Další informace o problému:
BCCode: 124
BCP1: 00000000
BCP2: 865DB024
BCP3: F6204000
BCP4: 00000135
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
software mam updatnuty pouzivam driver genius ... a memtest som skusal vcera nevyhodilo mi ziadny error prikladam spravu o pocitaci z everestu a dump files vopred dakujem za odp.
http://www.ulozto.sk/4707904/dump.rar
...pouzivam win 7
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 14:05
od spike18
Nemáš náhodou case od Lian-Li?
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 14:14
od 4_X_4
netusim to zistim ako ?
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 14:44
od spike18
Kúnki na zadnů stranu, toto mi právě jednou dělalo.
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 14:56
od LiveBomb
driver genius ....
V tomhle bude problem, natahl sis tam buhvi co a buhvi odkud ....
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 15:03
od 4_X_4
preco to hadze bsod iba pri tom dow 2? a to mi uz hadzalo davno pred tym ako som stiahol geniusa... ale keby to nahodou bolo tym tak co mam robit?
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 15:06
od 4_X_4
kral píše:Kúnki na zadnů stranu, toto mi právě jednou dělalo.
no pozrel som to jedine co tam je vyryte je nejake AJOHO co nwm co je ale urcite tam neni lian li ja mam akysi shit no....
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 15:46
od spike18
Zkus ju vyměniť.
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 16:15
od LiveBomb
A co ma jako skrin spolecneho s tim, ze ma bud chybu v software (ovladaci) nebo hardware (ramky, deska, grafika) ?
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 17:03
od 4_X_4
V tych dump suboroch nieje napisane ci to je soft abo hardware?
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 17:30
od LiveBomb
Melo by to tam bejt, ale me se nepodarilo ani jeden analyzovat
Kazdopadne jak tu nekdo psal skrin je 100% blbost (leda by ti nekde omylem probijela, ale to bys poznal spatnej vylisek uz pri montazi).
Ted nevim, MemTest86+ si zkousel???
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 17:45
od 4_X_4
jj memtest86+ verzia211 bo novsiu ktora by sa dala hodit na bootovacie usb som nenasiel
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 18:10
od LiveBomb
A vysledek?
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 18:16
od 4_X_4
a memtest som skusal vcera nevyhodilo mi ziadny error
ako som uz napisal ziadny error
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 20:02
od spike18
LiveBomb píše:A co ma jako skrin spolecneho s tim, ze ma bud chybu v software (ovladaci) nebo hardware (ramky, deska, grafika) ?
Mě to tak robilo a to jsem měl kvalitní casu.
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 20:31
od LiveBomb
A co s tim ma spolecnyho skrin? Ta s tim nemuze mit nic spolecnyho. Leda by byl problem se spinaci na panelu, ale to bych cekal u sragorek za 500,- a ne u skrine za 5000,- .
To si spis mel nekde spatnej kontakt a pri tom prehazovani si to nevedomky opravil ..
Tohle to z 90% zpusobji pameti, graficke karty, zvukovky, vyjimecne sitovky (nebo jejich ovladace) .....
Re: BSOD /zase/
Napsal: ned 2. kvě 2010, 21:12
od tielka
Další informace o problému:
BCCode: 124
Toto by měl dělat procesor.
Re: BSOD /zase/
Napsal: pon 3. kvě 2010, 08:06
od zombux
a sestava je jaká?
Re: BSOD /zase/
Napsal: pon 3. kvě 2010, 09:18
od 4_X_4
hmm zostava je to,teda bola geforce 9500 gt, 2gb ram, zakladna asrock n61p-s s dual amd procakom kt. vcera asi dobojovala pretoze mi uz nejde ani spustit comp iba 3x dlhsie pipne a opakuje az kym nevypnem pc malo by to byt ramkou podla tych pipnuti ale uz som aj resetol bios aj vymenil ram a nic ,cize asi pass co?
Re: BSOD /zase/
Napsal: pon 3. kvě 2010, 13:24
od LiveBomb
Kód: Vybrat vše
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\042910-17593-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\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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c47000 PsLoadedModuleList = 0x82d8f810
Debug session time: Thu Apr 29 21:59:14.195 2010 (GMT+2)
System Uptime: 0 days 0:42:27.523
*********************************************************************
* 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
.......
1: kd> !analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 86640024, b6204000, 135}
***** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware
Followup: MachineOwner
---------