Mam problem(pisałem na innych forach jednak nie pomogli mam nadzieje że wy jesteście tak mili że pomożecie) kiedy gram w Wiedźmina nagle komp mi się zawiesza i tylko reset pomaga dziwne jest w tym że obraz się zawiesza a muza gra dalej,w kronikach riddicka po zmianie zasiłki tylko raz się zawiesił oraz przy no mercy na n64 zresetował się więc niżej podam log Debugging Tools for Windows może pomoże.Tak się dzieje tylko przy grach,jak miałem stary zasilacz to zwisy i resety występowały cały czas a jak już następowały to tak że wszystko zamarło nie było żadnej muzy ani nic,a jak mam nowy to tylko w niektórych momentach zwisy ale muza gra może napięcia są złe??nie wiem mam nadzieje że wy pomożecie:).
Moim zdaniem to grafika bo to wina sprzętu a podczas włączenia Wiedźmina jakoś dziwnie karta syczy ale do końca nie wiem czy to karta.
Mój komp to:
Athlon 3000+ 1.8 GHZ
geforce 7600GT
twardziel 40GB
Asus a8v-vm
Windows XP sp2
Ramy 1.7GB
Zasilacz Modecom MC-350ATX 2.0 PFC 400W (we Wtorek kupiony)
Bardzo bym prosił o odpowiedź.
Pozdrawiam… smile.gif
Log z Debugging Tools for Windows
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. *
****************************************************************************
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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805535a0
Debug session time: Mon Mar 3 22:02:08.770 2008 (GMT+1)
System Uptime: 0 days 2:27:42.658
*********************************************************************
* 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 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
…
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {4, 805463f0, b2000010, 10c0f}
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+21c3f )
Followup: MachineOwner
pokazuję ntoskrnl.exe więc coś ze sprzętem(jak się nie mylę bo się na tym nie znam).