BSOD Assassin's Creed

[gotta91]

Sperando di aver fatto giusto ho provato a controllare con il debugger della microsoft i file .dmp che si creano dopo la famosa blue screen. il problema accade dopo pochi minuti che gioco ad Assassin's creed..(la mia configurazione la vedete in firma)


DUMP:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini080909-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 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Aug 9 21:30:22.460 2009 (GMT+2)
System Uptime: 0 days 11:20:17.567
*********************************************************************
* 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 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 19, {20, e91e97e0, e91e9bf8, c83061e}

***** 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!PVOID ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** 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 atkdisp.dll
*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
*************************************************************************
*** ***
*** ***
*** 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 : atkdisp.dll ( atkdisp+122c )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e91e97e0, The pool entry we were looking for within the page.
Arg3: e91e9bf8, The next pool entry.
Arg4: 0c83061e, (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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 <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+ *
*********************************************************************

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: atkdisp

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 488ee091

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
e91e97e0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8054b583 to 804f9f43

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b5b90b98 8054b583 00000019 00000020 e91e97e0 nt+0x22f43
b5b90be8 bf802a1d e91e97e8 00000000 b5b90c08 nt+0x74583
b5b90bf8 bf85b66d e91e97e8 e91e9818 b5b90c24 win32k+0x2a1d
b5b90c08 bf01322c e91e97f8 b5b90ce4 e4bb64f8 win32k+0x5b66d
b5b90c24 bf01354f 00000001 bf961b98 b5b90ce4 atkdisp+0x122c
b5b90c68 bf000663 b5b90ce4 b5b90d64 02f4eb7c atkdisp+0x154f
b5b90d40 8054162c 03400016 0340001a 001c98c0 dxg+0x663
b5b90d64 7c91e4f4 badb0d00 02f4eb60 b56c2d98 nt+0x6a62c
b5b90d68 badb0d00 02f4eb60 b56c2d98 b56c2dcc 0x7c91e4f4
b5b90d6c 02f4eb60 b56c2d98 b56c2dcc 00000000 0xbadb0d00
b5b90d70 b56c2d98 b56c2dcc 00000000 00000000 0x2f4eb60
b5b90d74 b56c2dcc 00000000 00000000 00000000 0xb56c2d98
b5b90d78 00000000 00000000 00000000 00000000 0xb56c2dcc


STACK_COMMAND: kb

FOLLOWUP_IP:
atkdisp+122c
bf01322c ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: atkdisp+122c

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: atkdisp.dll

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

[@less@ndro]

lo fa solo con questo gioco? :mc:

[gotta91]

si con altri anche più potenti come crysis,arma2,prototype fila tutto liscio. solo con assassin's :cry: cmq il gioco di per sè funziona su altri pc, su questo no..dopo pochi minuti crasha

[Wikkle]

si con altri anche più potenti come crysis,arma2,prototype fila tutto liscio. solo con assassin's :cry: cmq il gioco di per sè funziona su altri pc, su questo no..dopo pochi minuti crasha

é original o curato?

[gotta91]

originale

[Wikkle]

originale
ho la tua stessa vga e con me andava bene su vista64.

Su che OS giochi?
Hai messo gli ultimi driver ufficiali oppure usi i beta?

[gotta91]

uso xp sp3, i driver ho gli ultimi ufficiali nvidia, adesso però provo a mettere gli ultimi dell'asus per vedere se risolvono il problema

[Wikkle]

uso xp sp3, i driver ho gli ultimi ufficiali nvidia, adesso però provo a mettere gli ultimi dell'asus per vedere se risolvono il problema

vedo che hai anche win7..... perché non lo installi su quello?

[gotta91]

l'ho cancellato perchè avevo una versione vecchia, inoltre era in virtuale.
l'os cmq non penso sia il problema perchè mio cugino ha stesso pc e gli va perfettamente, l'unica cosa che ha di diverso è la scheda video( x di più meno potente):help:
piuttosto sai dirmi se si capisce qualcosa dal file dump? io ho capito solo che l'errore potrebbe essere causato da atkdisp.dll, però non sono sicuro

[Wikkle]

l'ho cancellato perchè avevo una versione vecchia, inoltre era in virtuale.
l'os cmq non penso sia il problema perchè mio cugino ha stesso pc e gli va perfettamente, l'unica cosa che ha di diverso è la scheda video( x di più meno potente):help:
piuttosto sai dirmi se si capisce qualcosa dal file dump? io ho capito solo che l'errore potrebbe essere causato da atkdisp.dll, però non sono sicuro

ti posso dire che sicuramente é un errore dovuto a vga, oppure dai suoi driver oppure dal OS con i relativi driver installati.

Lascerei tutto com'é e proverei solo a mettere i driver della vga:
prima gli ultimi beta, poi in caso, metterei la versione precedente a quelli che hai già installato :)

[gotta91]

la cosa strana è che il gioco funziona perfettamente, salta secondo me perchè si surriscalda troppo la VGA e quando arriva a 80° in automatico si spegne il PC, eppure le ventole sono accese, non capisco perchè non si raffredda abbastanza o meglio perchè si riscalda cosi tanto

[Wikkle]

la cosa strana è che il gioco funziona perfettamente, salta secondo me perchè si surriscalda troppo la VGA e quando arriva a 80° in automatico si spegne il PC, eppure le ventole sono accese, non capisco perchè non si raffredda abbastanza o meglio perchè si riscalda cosi tanto

ah be allora.... potevi dirlo prima.

Compra una ventolina da 92 mm da mettere che spara sulla vga, e così risolvi tutto, oltre che meglio preservare la gtx280 ;)


PS:oppure abbassa i dettagli del gioco, togli AA e dx10... in modo da non richiedere troppo dalla vga

[gotta91]

si AA e dx10 non li avevo messi neanche prima, cmq adesso ho provato e per quasi un ora è andato puntadogli il ventilatore contro poi ho chiuso io x vedere la temperatura XD, probabilmente scalda troppo la vga e devo comprare delle ventole, mentre dissipatori o ventole per la mia ci sono? anche se penso di no perchè è chiusa dal case ufficiale non è aperta.

[Wikkle]

si AA e dx10 non li avevo messi neanche prima, cmq adesso ho provato e per quasi un ora è andato puntadogli il ventilatore contro poi ho chiuso io x vedere la temperatura XD, probabilmente scalda troppo la vga e devo comprare delle ventole, mentre dissipatori o ventole per la mia ci sono? anche se penso di no perchè è chiusa dal case ufficiale non è aperta.

io con una silent da 9 euro ho risolto il problema :D

[ezio]

Potrebbe essere un problema specifico della release dei driver da te installata (se è la più recente provane un'altra più vecchia).

A volte gli errori dovuti al file atkdisp.dll sono collegate alle feature dei software Asus a corredo dei driver video e della scheda madre, prova a disattivarle tutte se presenti (soprattutto Asus OSD).


PS: nel file di debug noto che non stai usando i simboli corretti, invece di scaricarli manualmente utilizza il percorso di rete
SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
QUI (http://www.hwupgrade.it/forum/showthread.php?t=1955647) altri dettagli.

[gotta91]

0k grazie qnd torno provo a mettere i symbol, asus OSD l'ho cancellato mentre tengo smartdoctor

[gotta91]

ora spero di aver fatto giusto

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, e91e97e0, e91e9bf8, c83061e}

Unable to load image atkdisp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atkdisp.dll
*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll
Probably caused by : atkdisp.dll ( atkdisp+122c )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e91e97e0, The pool entry we were looking for within the page.
Arg3: e91e9bf8, The next pool entry.
Arg4: 0c83061e, (reserved)

Debugging Details:
------------------


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: e91e97e0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: AssassinsCreed_

LAST_CONTROL_TRANSFER: from 8054b583 to 804f9f43

STACK_TEXT:
b5b90b98 8054b583 00000019 00000020 e91e97e0 nt!KeBugCheckEx+0x1b
b5b90be8 bf802a1d e91e97e8 00000000 b5b90c08 nt!ExFreePoolWithTag+0x2a3
b5b90bf8 bf85b66d e91e97e8 e91e9818 b5b90c24 win32k!HeavyFreePool+0xbb
b5b90c08 bf01322c e91e97f8 b5b90ce4 e4bb64f8 win32k!EngFreeMem+0x1c
WARNING: Stack unwind information not available. Following frames may be wrong.
b5b90c24 bf01354f 00000001 bf961b98 b5b90ce4 atkdisp+0x122c
b5b90c68 bf000663 b5b90ce4 b5b90d64 02f4eb7c atkdisp+0x154f
b5b90d40 8054162c 03400016 0340001a 001c98c0 dxg!DxD3dDrawPrimitives2+0x1b9
b5b90d40 7c91e4f4 03400016 0340001a 001c98c0 nt!KiFastCallEntry+0xfc
02f4eb8c 00000000 00000000 00000000 00000000 0x7c91e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
atkdisp+122c
bf01322c ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: atkdisp+122c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atkdisp

IMAGE_NAME: atkdisp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 488ee091

FAILURE_BUCKET_ID: 0x19_20_atkdisp+122c

BUCKET_ID: 0x19_20_atkdisp+122c

Followup: MachineOwner
---------