Newsgroup: it.comp.hardware
Titolo: Aiuto blocco pc con giochi

Ciao a tutti.
 
Tutto è cominciato una settimana fa mentre giocavo ad Assassin's Creed -
Revelation.
Durante il gioco piu' volte il gioco mi si bloccava ed il file eseguibile
smetteva di funzionare, tutto in modo
casuale. Ho pensato ad un problema del gioco ed ho provato ad effettuare una
nuova installazione.
Ieri però è comparsa anche la classica schermata blu con il riavvio del
sistema. Allora ho scaricato Windows debugger
sono andato sui file minidump ed ho visto che tutti i vari crash nel
registro sono riconducibili al file "DXGMMS1.SYS".
In rete onestamente delle spiegazioni, quasi tutte in inglese, non ci ho
capito tanto. Potreste darmi una mano per capire
quale potrebbe essere il problema. I crash comunque avvengono, almeno fin ad
ora,  solo quando gioco !!!!
 
 
Vi allego i Crash Vi prego datemi una mano.!!!!!
 
Grazie.
 
ECCO I 2 ULTIMI CRASH
 
 
 
 
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\122611-15007-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: c:\symbols*
http://msdl.microsoft.com/download/symbols
 
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Kernel base = 0x82c37000 PsLoadedModuleList = 0x82d7f810
Debug session time: Mon Dec 26 12:48:33.090 2011 (GMT+1)
System Uptime: 0 days 0:42:43.042
Loading Kernel Symbols
....................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* 
*
*                        Bugcheck Analysis 
*
* 
*
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1000007E, {c0000005, 91f1bbb1, 983129e8, 983125c0}
 
Probably caused by : dxgmms1.sys ( 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f )
 
Followup: MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
* 
*
*                        Bugcheck Analysis 
*
* 
*
*******************************************************************************
 
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 91f1bbb1, The address that the exception occurred at
Arg3: 983129e8, Exception Record Address
Arg4: 983125c0, Context Record Address
 
Debugging Details:
------------------
 
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto 
riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.
 
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
91f1bbb1 8b31            mov     esi,dword ptr [ecx]
 
EXCEPTION_RECORD:  983129e8 -- (.exr 0xffffffff983129e8)
ExceptionAddress: 91f1bbb1 
(dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000
 
CONTEXT:  983125c0 -- (.cxr 0xffffffff983125c0)
eax=858bf648 ebx=00000000 ecx=00000000 edx=00000001 esi=882fa000 
edi=882fa000
eip=91f1bbb1 esp=98312ab0 ebp=98312abc iopl=0         nv up ei pl nz na po 
nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000 
efl=00010202
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf:
91f1bbb1 8b31            mov     esi,dword ptr [ecx] 
ds:0023:00000000=????????
Resetting default scope
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto 
riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.
 
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d9f718
Unable to read MiSystemVaType memory at 82d7f160
00000000
 
BUGCHECK_STR:  0x7E
 
LAST_CONTROL_TRANSFER:  from 91f1f24c to 91f1bbb1
 
STACK_TEXT:
98312abc 91f1f24c 858bf648 00000001 00000000 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xf
98312bb8 91f3693e a97edea8 00000000 89606930 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x2f6
98312d18 91f3722f 85a82f08 89845008 98312d3c 
dxgmms1!VidSchiSubmitRenderCommand+0x1c0
98312d28 91f374cc 85a82f08 82c733f1 86e0a658 
dxgmms1!VidSchiSubmitQueueCommand+0x61
98312d3c 91f37573 86e0a658 00000000 86df8a48 
dxgmms1!VidSchiRun_PriorityTable+0x24
98312d50 82e456d3 86e0a658 bf4d7406 00000000 
dxgmms1!VidSchiWorkerThread+0x7f
98312d90 82cf70f9 91f374f4 86e0a658 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
91f1bbb1 8b31            mov     esi,dword ptr [ecx]
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: dxgmms1
 
IMAGE_NAME:  dxgmms1.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265
 
STACK_COMMAND:  .cxr 0xffffffff983125c0 ; kb
 
FAILURE_BUCKET_ID: 
0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
 
BUCKET_ID:  0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+f
 
Followup: MachineOwner
---------
 
 
 
 
 
 
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\123111-16208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: c:\symbols*
http://msdl.microsoft.com/download/symbols
 
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Kernel base = 0x82c0a000 PsLoadedModuleList = 0x82d52810
Debug session time: Sat Dec 31 12:31:07.067 2011 (GMT+1)
System Uptime: 0 days 1:17:22.019
Loading Kernel Symbols
...................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* 
*
*                        Bugcheck Analysis 
*
* 
*
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck A, {8d530f44, 2, 0, 82c7593c}
 
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchWaitForEvents+ca )
 
Followup: MachineOwner
---------
 
3: 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: 8d530f44, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only 
on chips which support this level of status)
Arg4: 82c7593c, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
8d530f44
 
CURRENT_IRQL:  2
 
FAULTING_IP:
nt!KiInsertTimerTable+138
82c7593c 8b48f8          mov     ecx,dword ptr [eax-8]
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
TRAP_FRAME:  8f0ee9c4 -- (.trap 0xffffffff8f0ee9c4)
ErrCode = 00000000
eax=8d530f4c ebx=00000044 ecx=00000000 edx=882610c0 esi=8d537a80 
edi=8d538f4c
eip=82c7593c esp=8f0eea38 ebp=8f0eea80 iopl=0         nv up ei ng nz na pe 
cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000 
efl=00010287
nt!KiInsertTimerTable+0x138:
82c7593c 8b48f8          mov     ecx,dword ptr [eax-8] 
ds:0023:8d530f44=????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from 82c7593c to 82c5082b
 
STACK_TEXT:
8f0ee9c4 82c7593c badb0d00 882610c0 00000000 nt!KiTrap0E+0x2cf
8f0eea80 82c773eb 882610c0 000000db 00000000 nt!KiInsertTimerTable+0x138
8f0eeab0 82c736ef 88261030 882610f0 000000db nt!KiCommitThreadWait+0x1a7
8f0eec2c 91f0a078 00000002 8f0eecdc 00000001 
nt!KeWaitForMultipleObjects+0x535
8f0eec68 91f31c89 00d90008 00000002 8f0eecdc 
dxgmms1!VidSchWaitForEvents+0xca
8f0eec90 91f11993 86d90008 8f0eecb0 ffffffff 
dxgmms1!VidSchWaitForCompletionEvent+0x11f
8f0eed28 91f364b7 00000000 82c463f1 86d90008 
dxgmms1!VidSchiScheduleCommandToRun+0x14d
8f0eed3c 91f36573 86d90008 00000000 88261030 
dxgmms1!VidSchiRun_PriorityTable+0xf
8f0eed50 82e186d3 86d90008 a8728641 00000000 
dxgmms1!VidSchiWorkerThread+0x7f
8f0eed90 82cca0f9 91f364f4 86d90008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:
dxgmms1!VidSchWaitForEvents+ca
91f0a078 894514          mov     dword ptr [ebp+14h],eax
 
SYMBOL_STACK_INDEX:  4
 
SYMBOL_NAME:  dxgmms1!VidSchWaitForEvents+ca
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: dxgmms1
 
IMAGE_NAME:  dxgmms1.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265
 
FAILURE_BUCKET_ID:  0xA_dxgmms1!VidSchWaitForEvents+ca
 
BUCKET_ID:  0xA_dxgmms1!VidSchWaitForEvents+ca
 
Followup: MachineOwner
---------
 

 registro sono riconducibili al file "DXGMMS1.SYS".
 
Prova in sequenza a reinstallare i driver della scheda video e 
successivamente le directx.
 
-- 
-------------------------------------------
 
Massimiliano Cairo - Webspring Group
http://www.zonadriver.it
 
 
http://www.webspring.it
 
-------------------------------------------