Po włączeniu gry restuje mi się komputer


(Szawelm) #1

Tak jak w temacie z tym że już sam porobiłem te Blue Screeny itp teraz tylko zostało odisntalować odpowiednie programy żeby było dobrze. i mam związane z tym pytanie czy z tego Minidump.dmp można odczytać jakie programy czy stery muszę odinstalować bądź przeinstalować ?

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [D]

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 2

*** 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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Sun Aug 8 13:00:06.250 2010 (GMT+2)

System Uptime: 0 days 1:30:30.889

*********************************************************************

* 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 2

*** 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 1000000A, {16, 1c, 0, 805023bc}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for atkosdmini.dll

*** ERROR: Module load completed but symbols could not be loaded for atkosdmini.dll

*** WARNING: Unable to verify timestamp for atkdisp.dll

*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

*** WARNING: Unable to verify timestamp for dxg.sys

*** ERROR: Module load completed but symbols could not be loaded for dxg.sys

Probably caused by : atkosdmini.dll ( atkosdmini+1370 )

Followup: MachineOwner


0: kd> !analyze

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {16, 1c, 0, 805023bc}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : atkosdmini.dll ( atkosdmini+1370 )

Followup: MachineOwner


0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 00000016, memory referenced

Arg2: 0000001c, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: 805023bc, address which referenced memory

Debugging Details:


***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45bd5dcc

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

00000016

CURRENT_IRQL: 1c

FAULTING_IP:

nt+2b3bc

805023bc 6683781601 cmp word ptr [eax+16h],1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804fa166 to 805023bc

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

acb41c0c 804fa166 acb41cfc e4275e98 e2198590 nt+0x2b3bc

acb41c20 bd051370 89a37310 00000000 00000000 nt+0x23166

acb41c44 bd0125d5 00000001 e32398c0 e16569f8 atkosdmini+0x1370

acb41c60 bf963037 acb41cfc 00000000 e11990c0 atkdisp+0x5d5

acb41ca4 bd000cb2 acb41cfc acb41d64 000ce81c win32k+0x163037

acb41d4c 8054089c 12200003 08400005 00000000 dxg+0xcb2

acb41d64 7c90e514 badb0d00 000ce80c 00000000 nt+0x6989c

acb41d68 badb0d00 000ce80c 00000000 00000000 0x7c90e514

acb41d6c 000ce80c 00000000 00000000 00000000 0xbadb0d00

acb41d70 00000000 00000000 00000000 00000000 0xce80c

STACK_COMMAND: kb

FOLLOWUP_IP:

atkosdmini+1370

bd051370 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: atkosdmini+1370

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atkosdmini

IMAGE_NAME: atkosdmini.dll

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner



(Arek F.) #2

Ten sam problem: http://www.searchengines.pl/Restart-kom … 02929.html

Rozwiązanie: http://www.searchengines.pl/index.php?s … t&p=461577


(Szawelm) #3

dzięki bardzo za szybką odpowiedź