[THREAD UFFICIALE] ATI RADEON 4870X2

[pierpanga]

Salve a tutti, chiedo dove si possa scaricare il manule di installazione del dissipatore Accelero XTREME 4870X2.
Sul sito ufficiale non c'è.
Gli ho scritto, ancora nessuna risposta.
Spero mi aiutate.
Grazie

[BigEyes89]

Originariamente inviato da pierpanga

Salve a tutti, chiedo dove si possa scaricare il manule di installazione del dissipatore Accelero XTREME 4870X2.
Sul sito ufficiale non c'è.
Gli ho scritto, ancora nessuna risposta.
Spero mi aiutate.
Grazie

Da quel che mi ricordo era una cosa piuttosto intuitiva da fare..

Vedi se questo ti può dare una mano:
http://www.youtube.com/watch?v=qUrnolMS5eA

[Jeremy01]

se si usa lo stesso sistema operativo la stessa vga e i drivers + cap, sapete cosa puo influire sul fatto che in un sistema con un gioco le due gpu girano bene mentre su un altro sistema (quindi con quelle cose uguali) e con lo stesso gioco va solo una GPU? (mi riferisco a BF3...a me non va in nessun modo)

[china87]

sono usciti i cap2 per i catalyst 11.11 LINK

attenzione! serve window 7 service pack 1 per i cata 11.11 LINK

[china87]

sono usciti i nuovi hotfix 11.11a e 11.11b
AMD Catalyst 11.11a performance driver features:



· Batman Arkham City

o Improves DirectX 11 performance for single GPU configurations

· Rage

o Delivers AMD CrossfireX performance scaling

o Resolves a number of image / stability issues seen with the title:

§ Fix geometry corruption, sometimes seen in Bash TV entrance

§ Fix issues with Low-memory conditions on 32bit systems.

§ Fix issue with extreme corruption with missing textures on 32bit systems.

§ Fix memory leaks when deleting/reusing sync objects.

§ Fix hitching and pausing, especially noticeable on some Quad Core systems when doing races and Stanley Express runs.

§ Fix some missing shadows

· Elder Scrolls Skyrim

o Improves performance 2-7% on single GPU configurations

o Resolve corruption seen when enabling Multi-Sample Anti-Aliasing on the AMD Radeon HD 6970 Series

o Disables CrossFireX (to resolve negative scaling and image quality issues seen when CrossFireX is enabled)

§ AMD is continuing to work on a CrossFireX solution for Skyrim – as soon as it’s ready we’ll make it publicly available

· Battlefield 3

o Resolves intermittent corruption seen when playing the game at specific camera angles






AMD Catalyst release 11.11b Performance, compatibile con le schede video dalla serie Radeon HD 5000 e Radeon HD 6000. Di seguito le note fornite a corredo:

Delivers AMD CrossfireX performance scaling for (Elder Scrolls Skyrim and Assassin’s Creed: Revelations)

* Elder Scrolls Skyrim
o Delivers AMD CrossfireX performance scaling
o Improves performance 2-7% on single GPU configurations
o Resolve corruption seen when enabling Multi-Sample Anti-Aliasing on the AMD Radeon HD 6970 Series
* Assassin’s Creed: Revelations
o Delivers AMD CrossfireX performance scaling
* Batman Arkham City
o Improves DirectX 11 performance for single GPU configurations
* Rage
o Delivers AMD CrossfireX performance scaling
o Resolves a number of image / stability issues seen with the title:
+ Fix geometry corruption, sometimes seen in Bash TV entrance
+ Fix issues with Low-memory conditions on 32bit systems.
+ Fix issue with extreme corruption with missing textures on 32bit systems.
+ Fix memory leaks when deleting/reusing sync objects.
+ Fix hitching and pausing, especially noticeable on some Quad Core systems when doing races and Stanley Express runs.
+ Fix some missing shadows
* Battlefield 3
o Resolves intermittent corruption seen when playing the game at specific camera angles



installati in successione, ho notato miglioramenti nel framerate in skyrim e bf3.
finalmente amd sta dando un succoso supporto alla nostra fin'ora mal sfruttata scheda.

[netcrusher]

Originariamente inviato da china87

sono usciti i nuovi hotfix 11.11a e 11.11b
AMD Catalyst 11.11a performance driver features:



· Batman Arkham City

o Improves DirectX 11 performance for single GPU configurations

· Rage

o Delivers AMD CrossfireX performance scaling

o Resolves a number of image / stability issues seen with the title:

§ Fix geometry corruption, sometimes seen in Bash TV entrance

§ Fix issues with Low-memory conditions on 32bit systems.

§ Fix issue with extreme corruption with missing textures on 32bit systems.

§ Fix memory leaks when deleting/reusing sync objects.

§ Fix hitching and pausing, especially noticeable on some Quad Core systems when doing races and Stanley Express runs.

§ Fix some missing shadows

· Elder Scrolls Skyrim

o Improves performance 2-7% on single GPU configurations

o Resolve corruption seen when enabling Multi-Sample Anti-Aliasing on the AMD Radeon HD 6970 Series

o Disables CrossFireX (to resolve negative scaling and image quality issues seen when CrossFireX is enabled)

§ AMD is continuing to work on a CrossFireX solution for Skyrim – as soon as it’s ready we’ll make it publicly available

· Battlefield 3

o Resolves intermittent corruption seen when playing the game at specific camera angles






AMD Catalyst release 11.11b Performance, compatibile con le schede video dalla serie Radeon HD 5000 e Radeon HD 6000. Di seguito le note fornite a corredo:

Delivers AMD CrossfireX performance scaling for (Elder Scrolls Skyrim and Assassin’s Creed: Revelations)

* Elder Scrolls Skyrim
o Delivers AMD CrossfireX performance scaling
o Improves performance 2-7% on single GPU configurations
o Resolve corruption seen when enabling Multi-Sample Anti-Aliasing on the AMD Radeon HD 6970 Series
* Assassin’s Creed: Revelations
o Delivers AMD CrossfireX performance scaling
* Batman Arkham City
o Improves DirectX 11 performance for single GPU configurations
* Rage
o Delivers AMD CrossfireX performance scaling
o Resolves a number of image / stability issues seen with the title:
+ Fix geometry corruption, sometimes seen in Bash TV entrance
+ Fix issues with Low-memory conditions on 32bit systems.
+ Fix issue with extreme corruption with missing textures on 32bit systems.
+ Fix memory leaks when deleting/reusing sync objects.
+ Fix hitching and pausing, especially noticeable on some Quad Core systems when doing races and Stanley Express runs.
+ Fix some missing shadows
* Battlefield 3
o Resolves intermittent corruption seen when playing the game at specific camera angles



installati in successione, ho notato miglioramenti nel framerate in skyrim e bf3.
finalmente amd sta dando un succoso supporto alla nostra fin'ora mal sfruttata scheda.

Ma non erano solo per la serie 5000 e 6000???? A me oggi la vga è morta di nuovo urrà!!!!!!!!!!!!!!! Mi toccherà infornarla di nuovo!!!!

[china87]

il passaggio da 11.11a a 11.11b si sente eccome, viene abilitato il crossfire e viene attenuato lo shuttering di molto in skyrim.
anche se quel gioco per pc è prematuro, ho cercato diverse texture mod e ora è uno spettacolo giocarci.

[netcrusher]

sono usciti i driver 11.11c con ottimizzazioni varie per la serie 5000 e 6000, penso siano installabili però non credo che le ottimizzazioni tocchino pure la hd4870x2, invece mi incuriosivano più i catalyst 12.1 beta 2 di cui alcuni utenti stanno parlando nel forum, vorrei provare quelli però non trovo i link per scaricarli.

[china87]

Originariamente inviato da netcrusher

sono usciti i driver 11.11c con ottimizzazioni varie per la serie 5000 e 6000, penso siano installabili però non credo che le ottimizzazioni tocchino pure la hd4870x2, invece mi incuriosivano più i catalyst 12.1 beta 2 di cui alcuni utenti stanno parlando nel forum, vorrei provare quelli però non trovo i link per scaricarli.

li ho provati e le prestazioni sono identiche, anche se credo qusta revisione C sia più stabile con skyrim ho avuto meno crash fin'ora.

sono curioso di questi 12.1 ma dove l'hai letto che ci sono?

[netcrusher]

Originariamente inviato da china87

li ho provati e le prestazioni sono identiche, anche se credo qusta revisione C sia più stabile con skyrim ho avuto meno crash fin'ora.

sono curioso di questi 12.1 ma dove l'hai letto che ci sono?

Nella news di hardwareupgrade relativa all'uscita dei nuovi catalyst 11.11c , l'utente markk117 nei commenti dice di aver installato i 12.1 beta2 e di non avere nessun problema con battlefield 3:
http://www.hwfiles.it/news/amd-catal....html#commenti

leggi nei commenti, io personalmente gli ho mandato un messaggio in pvt per sapere dove trovarli!!!! sono curioso anche io!!!!

[netcrusher]

In rete stanno circolando i catalyst beta che alcuni chiamano 11.12 ed altri 12.1 forse perchè nn si sà se escono a dicembre o gennaio, comunque io li sto scaricando, ho scaricato anche l'application profile 12.1 (o 11.12 come lo volete chiamare) usciti il 29 novembre 2011

Battlefield 3 dovrebbe essere stato fixato per benino, ciao.

[Jeremy01]

Originariamente inviato da netcrusher

In rete stanno circolando i catalyst beta che alcuni chiamano 11.12 ed altri 12.1 forse perchè nn si sà se escono a dicembre o gennaio, comunque io li sto scaricando, ho scaricato anche l'application profile 12.1 (o 11.12 come lo volete chiamare) usciti il 29 novembre 2011

Battlefield 3 dovrebbe essere stato fixato per benino, ciao.

potresti linkarli i drivers?

[stefan0a]

Mi potreste suggerire un buon dissipatore per questa scheda video (4870x2 appunto) e che sia il più possibile silezioso..?
Ho quello standard della sapphire credo ma quando le ventolo sono al 100% il rumore è paragonabile a quello di un 747...
Grazie

[netcrusher]

Originariamente inviato da stefan0a

Mi potreste suggerire un buon dissipatore per questa scheda video (4870x2 appunto) e che sia il più possibile silezioso..?
Ho quello standard della sapphire credo ma quando le ventolo sono al 100% il rumore è paragonabile a quello di un 747...
Grazie

l'unico dissipatore ad aria che conosco è l'accelero extreme però è pressochè introvabile visto che è fuori commercio, magari c'è qualcuno sul forum che lo possiede ma difficilmente se ne priva se non con tutta la scheda video.

[Jeremy01]

in tre sessioni lunghe di gioco (40-50 min.) ho avuto tre BSOD. Ram testate e OC testato con un ora e mezza di prime blend.

I BSOD

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120911-17238-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a62000 PsLoadedModuleList = 0xfffff800`03ca7670
Debug session time: Fri Dec  9 01:02:41.288 2011 (UTC + 1:00)
System Uptime: 0 days 1:34:53.132
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {a1e06, d, 1, fffff80003ae9468}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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: 00000000000a1e06, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, 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: fffff80003ae9468, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d11100
 00000000000a1e06 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KeUpdateSystemTime+348
fffff800`03ae9468 483b8c3a18240000 cmp     rcx,qword ptr [rdx+rdi+2418h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80005690840 -- (.trap 0xfffff80005690840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000918e
rdx=00000000000011a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ae9468 rsp=fffff800056909d0 rbp=fffff78000000320
 r8=000000000005918d  r9=000000000005918e r10=0000000000000000
r11=fffff80005690a20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeUpdateSystemTime+0x348:
fffff800`03ae9468 483b8c3a18240000 cmp     rcx,qword ptr [rdx+rdi+2418h] ds:00000000`000035b8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ade1e9 to fffff80003adec40

STACK_TEXT:  
fffff800`056906f8 fffff800`03ade1e9 : 00000000`0000000a 00000000`000a1e06 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`05690700 fffff800`03adce60 : 00000000`00000000 00000000`0000000f 00000000`00000000 00000000`0005918f : nt!KiBugCheckDispatch+0x69
fffff800`05690840 fffff800`03ae9468 : 00000000`00000000 fffff800`03c54e80 00000000`00000001 fffff800`03c54e80 : nt!KiPageFault+0x260
fffff800`056909d0 fffff800`03a23895 : fffff800`03a49460 fffff800`05690b80 fffff800`03a49460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x348
fffff800`05690ad0 fffff800`03adb173 : 00000000`00000000 fffff800`05690b80 00000000`00000001 fffffa80`0792df10 : hal!HalpHpetClockInterrupt+0x8d
fffff800`05690b00 fffff880`04d309c2 : fffff800`03ae84a9 00000000`0038c5ce fffffa80`0792f938 fffff800`03c62cc0 : nt!KiInterruptDispatchNoLock+0x163
fffff800`05690c98 fffff800`03ae84a9 : 00000000`0038c5ce fffffa80`0792f938 fffff800`03c62cc0 00000000`00000001 : intelppm+0x39c2
fffff800`05690ca0 fffff800`03ad693c : fffff800`03c54e80 fffff800`00000000 00000000`00000000 fffff880`060b352c : nt!PoIdle+0x52a
fffff800`05690d80 00000000`00000000 : fffff800`05691000 fffff800`0568b000 fffff800`05690d40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`03adce60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

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

II BSOD

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\121011-19016-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a5b000 PsLoadedModuleList = 0xfffff800`03ca0670
Debug session time: Sat Dec 10 00:59:42.703 2011 (UTC + 1:00)
System Uptime: 0 days 0:41:47.546
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 0, fffff80003ae35dc}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessTimerDpcTable+4c )

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

1: 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: 0000000000000004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80003ae35dc, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d0a100
 0000000000000004 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800371b360 -- (.trap 0xfffff8800371b360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880009f2180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ae35dc rsp=fffff8800371b4f0 rbp=0000000000000000
 r8=fffff8800371b580  r9=00000000009f2180 r10=fffff80003a5b000
r11=fffff8800371b530 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessTimerDpcTable+0x4c:
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4] ds:b520:00000000`00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ad71e9 to fffff80003ad7c40

STACK_TEXT:  
fffff880`0371b218 fffff800`03ad71e9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0371b220 fffff800`03ad5e60 : 00000000`00000000 fffffa80`0c2c8120 fffffa80`0a5c2b40 fffff880`0371b580 : nt!KiBugCheckDispatch+0x69
fffff880`0371b360 fffff800`03ae35dc : fffffa80`0a5c2b40 fffffa80`0419b2f8 00000003`0419b200 00000000`0000000d : nt!KiPageFault+0x260
fffff880`0371b4f0 fffff800`03ae3496 : fffffa80`0c2c8168 fffffa80`0c2c8168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x4c
fffff880`0371b560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiProcessExpiredTimerList+0xc6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiProcessTimerDpcTable+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

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

III BSOD

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\121011-17487-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a04000 PsLoadedModuleList = 0xfffff800`03c49670
Debug session time: Sat Dec 10 16:02:25.752 2011 (UTC + 1:00)
System Uptime: 0 days 4:10:45.596
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {24, 2, 0, fffff80003a896cb}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )

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

1: 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: 0000000000000024, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80003a896cb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cb3100
 0000000000000024 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+22b
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800371b350 -- (.trap 0xfffff8800371b350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007777aa0 rbx=0000000000000000 rcx=fffffa800ad94100
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a896cb rsp=fffff8800371b4e8 rbp=fffffa800985d9a8
 r8=fffff880009f4301  r9=0000000000000002 r10=0000000000000067
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h] ds:5000:00000000`00000024=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a801e9 to fffff80003a80c40

STACK_TEXT:  
fffff880`0371b208 fffff800`03a801e9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0371b210 fffff800`03a7ee60 : 00000000`0038c5c4 fffffa80`09faf000 00000000`00000000 fffffa80`0985d9a8 : nt!KiBugCheckDispatch+0x69
fffff880`0371b350 fffff800`03a896cb : 00000000`0000000f fffffa80`08eb4010 fffffa80`0ae95948 fffffa80`0ae95948 : nt!KiPageFault+0x260
fffff880`0371b4e8 fffffa80`0ae95948 : fffffa80`0985d9a0 00000000`00000000 fffffa80`08eb4218 00000000`00000102 : nt!KiTimerWaitTest+0x22b
fffff880`0371b568 fffffa80`0985d9a0 : 00000000`00000000 fffffa80`08eb4218 00000000`00000102 fffffa80`09f917a8 : 0xfffffa80`0ae95948
fffff880`0371b570 00000000`00000000 : fffffa80`08eb4218 00000000`00000102 fffffa80`09f917a8 00000000`00000002 : 0xfffffa80`0985d9a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerWaitTest+22b
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerWaitTest+22b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

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

Sapreste dirmi se queste BSOD possono essere legate ad un malfunzionamento (o avvisagklia di rottura) della VGA?

[swattolo]

Ragazzi ho montato dopo mesi che l'ho tenuta nella scatola questa scheda video qui e appena montata con i drivers di Windows e ventola al 40% in idle sto sopra le 90°C, é possibile ciò secondo voi ? Vorrei venderla in quanto non la utilizzo più e volevo sapere se era normale tutto ciò

[illidan2000]

Originariamente inviato da swattolo

Ragazzi ho montato dopo mesi che l'ho tenuta nella scatola questa scheda video qui e appena montata con i drivers di Windows e ventola al 40% in idle sto sopra le 90°C, é possibile ciò secondo voi ? Vorrei venderla in quanto non la utilizzo più e volevo sapere se era normale tutto ciò

no. 90% in idle sono troppi. dovresti ripulirla un po', smontando il dissipatore

[swattolo]

E' pulta. Ho fatto poi un test con FurMark , la ventola da sola é andata al 100% e le temperature ottenute sono state queste qui:



Se é tutto ok la metto in vendita, altrimenti vediamo un pò cosa c'é che non va

[Revelator]

http://sites.amd.com/us/game/downloa...n_win7-64.aspx


11.12 ufficiali.

[netcrusher]

Originariamente inviato da swattolo

E' pulta. Ho fatto poi un test con FurMark , la ventola da sola é andata al 100% e le temperature ottenute sono state queste qui:



Se é tutto ok la metto in vendita, altrimenti vediamo un pò cosa c'é che non va

bè a pieno carico con frequenze default 750/900 e con 1.250 V di alimentazione raggiunge quelle temperature, per un uso in 2D 90° sono anomali, che la funzione di risparmio energetico non entri in funzione correttamente???
Ti conviene cancellare tutti i driver e fare una pulita con driversweeper e reinstallarla da zero.