Witam,
w grudniu zakupiłem komputer o takie konfiguracji(dane z aida64 bo nie chcialo sie przepisywac):
Typ procesora QuadCore AMD Phenom II X4 945, 3000 MHz (15 x 200)
Nazwa płyty głównej Gigabyte GA-770TA-UD3 (4 PCI, 2 PCI-E x1, 1 PCI-E x16, 4 DDR3 DIMM, Audio, Gigabit LAN, IEEE-1394)
Ram: 3xKingston 99U5474-001.A00LF 1 GB DDR3-1333 DDR3 SDRAM (8-8-8-22 @ 609 MHz) (7-7-7-20 @ 533 MHz) (6-6-6-17 @ 457 MHz)
karta gaficzna his radeon 6850 1gb
Dysk nr 1 - WDC WD5001AALS-00E3A0 (465 GB)
zasilacza 600w ale nie jestem teraz w stanie powiedziec jaki (kosztowal prawie 300zl)
System: windows 7 x64 ultimate, kompilacja 7600
Przejdzmy do problemu, otoz po zakupie komputera nie maiolm zbyt wymagajacyh gier wiec gralem np w fife10 czy gears of war i nic sie nie dzialo. Po dwoch tygodniach kupilem Crysisa i brak problemów. Ale gdy juz wgralem GTA 4 to zaczely sie nie widomego pochodzeni bsod lub bledy exe gry. zrobilem foramta kompa bo nie moglem znalezc rozwiazania (wczsniej mialm tego windowsa w wersji x86). Teraz po zakupie TDU2(test drive unlimited 2),nieraz po 10min nieraz po godzinie dwoch grania wyskakuje mi blue screen. Ten blue sceen zawsze ma inny kod bledu ale przy pomocy Microsoft debuger sprawdzilem ze najczesciej chodzi o plik “ntoskrnl.exe”.Raz wyskoczyl blie screen z bledem pliku " dxgkrnl.sys" i “dxgmms1.sys”.
Prosze o pomoc bo uz naprawde probowalem wiel rzeczy:
-zaktualizowalem sterownik grafiki
-sprawdzilem w biosie czy zintegrowana nie jest wlaczona
-przegooglowalem caly internet i nic
zamiesczam jeszcze kilka zrzutow pamiec :
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) 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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`0305ce50
Debug session time: Wed Feb 16 09:49:05.046 2011 (GMT+1)
System Uptime: 0 days 0:05:43.233
*********************************************************************
* 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
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff880040b6088, 80000000b986b121, fffff88007d8b660, b}
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
***** 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***
******
*************************************************************************
*********************************************************************
* 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 : dxgkrnl.sys ( dxgkrnl+17088 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880040b6088, Virtual address for the attempted write.
Arg2: 80000000b986b121, PTE contents.
Arg3: fffff88007d8b660, (reserved)
Arg4: 000000000000000b, (reserved)
Debugging Details:
------------------
***** 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***
******
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: dxgkrnl
FAULTING_MODULE: fffff80002e1f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc590
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xBE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002f0fdb2 to fffff80002e90f00
STACK_TEXT:
fffff880`07d8b4f8 fffff800`02f0fdb2 : 00000000`000000be fffff880`040b6088 80000000`b986b121 fffff880`07d8b660 : nt+0x71f00
fffff880`07d8b500 00000000`000000be : fffff880`040b6088 80000000`b986b121 fffff880`07d8b660 00000000`0000000b : nt+0xf0db2
fffff880`07d8b508 fffff880`040b6088 : 80000000`b986b121 fffff880`07d8b660 00000000`0000000b 00000000`00000011 : 0xbe
fffff880`07d8b510 80000000`b986b121 : fffff880`07d8b660 00000000`0000000b 00000000`00000011 00000000`00000001 : dxgkrnl+0x17088
fffff880`07d8b518 fffff880`07d8b660 : 00000000`0000000b 00000000`00000011 00000000`00000001 00000000`00000000 : 0x80000000`b986b121
fffff880`07d8b520 00000000`0000000b : 00000000`00000011 00000000`00000001 00000000`00000000 00000000`03250100 : 0xfffff880`07d8b660
fffff880`07d8b528 00000000`00000011 : 00000000`00000001 00000000`00000000 00000000`03250100 fffff800`00000001 : 0xb
fffff880`07d8b530 00000000`00000001 : 00000000`00000000 00000000`03250100 fffff800`00000001 fffff880`000a0008 : 0x11
fffff880`07d8b538 00000000`00000000 : 00000000`03250100 fffff800`00000001 fffff880`000a0008 fffff800`03195f60 : 0x1
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl+17088
fffff880`040b6088 30cb xor bl,cl
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgkrnl+17088
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: dxgkrnl.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) 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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Wed Feb 16 16:20:08.519 2011 (GMT+1)
System Uptime: 0 days 0:06:44.096
*********************************************************************
* 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
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff7fffb0ebad0, 8, fffff7fffb0ebad0, 2}
***** 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***
******
*************************************************************************
*********************************************************************
* 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+71f00 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff7fffb0ebad0, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff7fffb0ebad0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
***** 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***
******
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e07000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff7fffb0ebad0
FAULTING_IP:
+0
fffff7ff`fb0ebad0 ?? ???
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ef6bc2 to fffff80002e78f00
STACK_TEXT:
fffff880`07e84438 fffff800`02ef6bc2 : 00000000`00000050 fffff7ff`fb0ebad0 00000000`00000008 fffff880`07e845a0 : nt+0x71f00
fffff880`07e84440 00000000`00000050 : fffff7ff`fb0ebad0 00000000`00000008 fffff880`07e845a0 00000000`00000002 : nt+0xefbc2
fffff880`07e84448 fffff7ff`fb0ebad0 : 00000000`00000008 fffff880`07e845a0 00000000`00000002 fffff8a0`0727ca50 : 0x50
fffff880`07e84450 00000000`00000008 : fffff880`07e845a0 00000000`00000002 fffff8a0`0727ca50 fffff880`07e84548 : 0xfffff7ff`fb0ebad0
fffff880`07e84458 fffff880`07e845a0 : 00000000`00000002 fffff8a0`0727ca50 fffff880`07e84548 00000000`00000000 : 0x8
fffff880`07e84460 00000000`00000002 : fffff8a0`0727ca50 fffff880`07e84548 00000000`00000000 fffff880`07e846e0 : 0xfffff880`07e845a0
fffff880`07e84468 fffff8a0`0727ca50 : fffff880`07e84548 00000000`00000000 fffff880`07e846e0 00000000`00100003 : 0x2
fffff880`07e84470 fffff880`07e84548 : 00000000`00000000 fffff880`07e846e0 00000000`00100003 00000000`00000001 : 0xfffff8a0`0727ca50
fffff880`07e84478 00000000`00000000 : fffff880`07e846e0 00000000`00100003 00000000`00000001 fffff800`02e7ea84 : 0xfffff880`07e84548
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+71f00
fffff800`02e78f00 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+71f00
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Prosze o pomoc. JEzeli jescze cos potrzebne podam niezwlocznie
