Witam.
Czytając poradnik na jednej ze stron znalazłem częściowe rozwiązanie. Mianowicie zainstalowałem Microsoft Debugging Tools i sprawdziłem co jest nie tak.
21.10.2007
Microsoft ® Windows Debugger Version 6.8.0004.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. *
****************************************************************************
*** ***
*** ***
*** 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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+7351a )
Followup: MachineOwner
Czyli Probably caused by : ntoskrnl.exe ( nt+7351a ) Z tego co wyczytałem jest to problem ze sprzętem. sleep.gif
15.10.2007
Probably caused by : ks.sys ( ks+8f85 )
Jest to jakiś plik windowsowy, więc raczej też związany ze sprzętem sleep.gif
29.09.2007
Probably caused by : nv4_disp.dll ( nv4_disp+1767bb )
Też jakiś systemowy.
27.09.2007
Probably caused by : nv4_disp.dll ( nv4_disp+176727 )
Znów 27.09.2007
Probably caused by : nv4_disp.dll ( nv4_disp+176727 )
23.09.2007
Probably caused by : nv4_disp.dll ( nv4_disp+176727 )
To niby wszystkie, z tego co pamiętam było ich więcej ;p Jak widać 4 pierwsze były spowodowane tym samym plikiem. nv… może ma na myśli kartę graficzną. Od pewnego czasu mam domyślne taktowanie na karcie (wcześniej było kręcone) i możliwe, że dzięki temu nie wyskakuje. Jednak są jakieś 2 nowe błędy.
Konfiguracja:
Procek: E4300 @ 3 GHz
RAM: PDP Patriot 2 x 1 GB 800 MHz LKK @ 1000 MHz CL5
Płyta: Asus P5K
Karta graf.: MSI 8800 GTS 320 mb OC
Dysk: Samsung SP2514N 250 GB
Zasiłka: Chiftec 500 W
Windows XP Home SP 2
No to ja może podam to, co ja uważam za złe i dobre tongue.gif Robiłem testy SP 2004 (jak kto woli Orthos), HD Tune, Mem Test, wiadomo 3d mark 06. Wszystko w normie. Temp. znakomite. Mimo dobrego wyniku w HD Tune przyczyną moim zdaniem może być dysk twardy. Jest on na ATA 133, czyli już nie taki super ;p co prawda nie jest jakiś stary, ale może?
A może zasilacz? Powinien ciągnąć bez problemów i tak też jest, ale EVEREST pokazuje mi złe napięcie dla +5V, a mianowicie 5.59V. Wiadomo, że w tej kwestii programy jak i BIOS często się mylą, ale jednak.
Sterowniki do karty i chipsetu płyty głównej są nowe, BIOS tak samo.
Możliwe, że zapomniałem podać jakąś informację :-/ Za dużo tego wszystkiego sleep.gif Błąd wyskakuje podczas gry w UT 3 demo (w inne gry aktualnie nie gram, a jak grałem to nie wyskakiwał), wcześniej (gdy był to błąd nv4_disp.dll ) podczas CoD 2, ale tak jak mówiłem, dałem standardowe taktowanie i niby było wszystko ok.
PS. numeru błędu zapomniałem spisać, następnym razem się postaram, ale i tak jest to chyba zbędne przy tych informacjach.
Proszę o pomoc smile.gif
