Bluescreen & Coil Whine R9 290x Reference

**frakka** · 31-12-2013, 01:23

Il settaggio è generico ma è difficile che sbagli così tanto...
A ventilazione come sei messo nel case? Hai provato a vedere se con il settaggio standard ed il case aperto il problema si presenta uguale?

**Federico G. Mirabelli** · 31-12-2013, 10:20

Originariamente inviato da frakka

Il settaggio è generico ma è difficile che sbagli così tanto...
A ventilazione come sei messo nel case? Hai provato a vedere se con il settaggio standard ed il case aperto il problema si presenta uguale?

Il mio case è un HAF 922 con tre ventole larghe un palmo una sopra, una davanti ed una dietro.

Poco sopra la GPU vi è il dissipatore del processore, un cooler master v8, che è giusto un poco sovradimensionato ed anche quando il pc lavora pompa aria fredda.

Non credo che il case aperto serva a mollto in quanto è già aperto di per sè.

**frakka** · 31-12-2013, 11:12

Originariamente inviato da Federico G. Mirabelli

Non credo che il case aperto serva a mollto in quanto è già aperto di per sè.

No, infatti...

**Federico G. Mirabelli** · 01-01-2014, 17:34

per ora con la nuova impostazione delle ventole non ho ancora riscontrato i problemi delll'OT....

**Federico G. Mirabelli** · 01-01-2014, 21:05

Originariamente inviato da Federico G. Mirabelli

per ora con la nuova impostazione delle ventole non ho ancora riscontrato i problemi delll'OT....

Niente da fare, ho fatto circa 20 ore di altri giochi pesanti senza crash, 20 minuti di league of legends ed ho ottenuto l'ennesima blue screen.

**giampa** · 01-01-2014, 21:16

se il problema è solo League of Legends, che oltretutto non è certamente uno dei giochi più pesanti in circolazione, il problema, secondo me, non va ricercato nella scheda video in sé ma nella versione dei driver abbinati ...

che versione di Catalyst stai utilizzando ?

**Federico G. Mirabelli** · 01-01-2014, 21:29

Ho provato sia i 13.12 che i 13.11 Beta 9.5 ed il risultato è lo stesso (al momento ho quest'ulltimo).

Sì, al momento gli unici crash frequenti sono con video di youtube e league of legends.

Non so più cosa fare... alla fine della fiera ho fatto una spesa abbastanza sostanziale per non avere altro che problemi

**Federico G. Mirabelli** · 02-01-2014, 00:20

Ho spostato lo switch da uber a quiet mode ma non è cambiato nullla. Dopo 20 minuti su youtube, blue screen.

MEMORY.DMP:

	Spoiler:
	Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [S:\Desktop\MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is 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+ * ******************************************************************* * ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 8 Kernel Version 9600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505 Machine Name: Kernel base = 0xfffff801`0fe86000 PsLoadedModuleList = 0xfffff801`1014a990 Debug session time: Thu Jan 2 15:34:09.315 2014 (UTC + 1:00) System Uptime: 0 days 17:47:16.997 ********************************************************************* * 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+ * ******************************************************************* * ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list .................. *********** Symbol Loading Error Summary ********** Module name Error ntkrnlmp The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. * ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ******************************************************************************* * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck A0000001, {5, 0, 0, 0} * ERROR: Module load completed but symbols could not be loaded for atikmpag.sys * ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys - * ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.sys - *** Kernel symbols are WRONG. Please fix symbols to do analysis. ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * ********************************************************************* ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * ********************************************************************* ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * ********************************************************************* ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * ********************************************************************* ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * ********************************************************************* ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * ********************************************************************* ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * ********************************************************************* ********************************************************************* * * * * * Either you specified an unqualified symbol, or your debugger * * doesn't have full symbol information. Unqualified symbol * * resolution is turned off by default. Please either specify a * * fully qualified symbol module!symbolname, or enable resolution * * of unqualified symbols by typing ".symopt- 100". Note that * * enabling unqualified symbol resolution with network symbol * * server shares in the symbol path may cause the debugger to * * appear to hang for long periods of time when an incorrect * * symbol name is typed or the network symbol server is down. * * * * For some commands 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 * * * *********************************************************************** Probably caused by : atikmdag.sys ( atikmdag+277ce ) Followup: MachineOwner ---------

!analyze :

	Spoiler:
	ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. FAULTING_MODULE: fffff8010fe86000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 52a23f6f DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0xA0000001 CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from fffff80001ce17ce to fffff8010ffd3ca0 STACK_TEXT: ffffd000`20aaab58 fffff800`01ce17ce : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffd000`20aaab60 fffff800`01cf0880 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe000`00301000 : atikmdag+0x277ce ffffd000`20aaaba0 fffff800`01d3a4f5 : ffffe000`00301e50 00000000`00000000 00000000`00200286 fffff800`01cf1e8a : atikmdag+0x36880 ffffd000`20aaabd0 fffff800`01d3bfa8 : ffffe000`00320f00 fffff800`01cefe43 ffffe000`00320ba0 fffff801`000000a0 : atikmdag+0x804f5 ffffd000`20aaac50 fffff800`01d3c0e5 : ffffe000`00332580 ffffd000`20aaadb1 00000000`00000000 ffffd000`20aaadb1 : atikmdag+0x81fa8 ffffd000`20aaacd0 fffff800`01d3c1a2 : 00000000`00000000 00000000`00000000 00000000`00000030 00000000`00000433 : atikmdag+0x820e5 ffffd000`20aaad10 fffff800`01d3c2c1 : ffffe000`00301000 00000000`00000000 ffffe000`00000000 00000000`ffffffff : atikmdag+0x821a2 ffffd000`20aaae10 fffff800`01d44ab1 : ffffe000`00302cf0 ffffe000`00311660 ffffe000`00301000 fffff800`01d448d6 : atikmdag+0x822c1 ffffd000`20aaae60 fffff800`01d38e14 : ffffe000`00000000 ffffe000`00301000 00000000`00000001 00000000`00000001 : atikmdag+0x8aab1 ffffd000`20aaaeb0 fffff800`01cde60f : ffffe000`00264440 ffffd000`20a95180 fffff801`1012be00 00000000`00000001 : atikmdag+0x7ee14 ffffd000`20aaaee0 fffff800`01a3428e : ffffd000`20aaafa0 fffff801`0fee0813 fffff801`0fe86000 ffffd000`20a9b2c0 : atikmdag+0x2460f ffffd000`20aaaf10 fffff800`014f9fc1 : ffffe000`00400a02 fffff801`0fee0900 fffff800`014f9f90 00000000`00009201 : atikmpag+0x928e ffffd000`20aaaf40 fffff801`0ff1c3c2 : ffffd000`221f2c80 00000000`00000000 ffffe262`e2bd9128 00000000`00000010 : dxgkrnl!DpSynchronizeExecution+0x461 ffffd000`20aaaf70 fffff801`0ffd4ee8 : ffffd000`221f2c80 00000000`0000001c 00000000`ffffffff ffffe000`02d24000 : nt!ExAcquireRundownProtection+0x14a ffffd000`20aaafb0 fffff801`0ffd523b : 00000000`00000000 fffff801`10125100 ffffd000`201a0180 00000000`00000000 : nt!KeSynchronizeExecution+0x5f8 ffffd000`20108380 fffff800`0168243e : 00000000`00000001 00000000`002bd89e ffffe000`032a6d00 ffffe000`032c0080 : nt!KeSynchronizeExecution+0x94b ffffd000`20108510 fffff800`01681933 : ffffe000`032a6c01 fffff800`00000000 ffffe000`00000000 fffff801`0febfbb0 : dxgmms1+0x543e ffffd000`20108620 fffff800`01681804 : 00000000`00000000 ffffe000`03207220 ffffe000`02a6f000 ffffe000`02fe1240 : dxgmms1+0x4933 ffffd000`20108670 fffff800`014f9e6b : ffffe000`00298000 ffffd000`20108709 ffffe000`00301000 00000000`00000064 : dxgmms1+0x4804 ffffd000`201086c0 fffff800`01ce29cf : ffffe000`00298000 ffffe000`00311550 ffffe000`00298000 00000000`00000000 : dxgkrnl!DpSynchronizeExecution+0x30b ffffd000`20108770 fffff800`01cf0880 : 00000000`00000000 ffffd000`20a9ac34 ffffe000`003097f0 00000000`00000000 : atikmdag+0x289cf ffffd000`201087a0 fffff800`01d3a4f5 : 00003656`69df0e56 fffff800`01cf4559 00000000`01000010 00000000`00000002 : atikmdag+0x36880 ffffd000`201087d0 fffff800`01d3bfa8 : ffffe000`00000030 fffff800`01d3a1b1 ffffd000`20108c60 00000000`00000007 : atikmdag+0x804f5 ffffd000`20108850 fffff800`01d3d8da : ffffe000`00301000 ffffd000`20aa1340 ffffe000`00301ef0 ffffe000`00301ef0 : atikmdag+0x81fa8 ffffd000`201088d0 fffff800`01d3d98a : ffffe000`00301000 ffffd000`20aa1340 ffffe000`00301ef0 00000000`00000000 : atikmdag+0x838da ffffd000`20108910 fffff800`01d386ee : ffffe000`00301000 ffffd000`20108be0 ffffd000`20108c60 fffff801`100805b1 : atikmdag+0x8398a ffffd000`20108a00 fffff800`01cde5a4 : ffffe000`00264440 ffffe000`027450e0 00000000`00000001 ffffe000`02745000 : atikmdag+0x7e6ee ffffd000`20108a30 fffff800`01a342c9 : ffffe000`0268b980 ffffd000`20a95180 ffffe000`02745000 ffffe000`024a7a50 : atikmdag+0x245a4 ffffd000`20108a60 fffff800`014fa09b : ffffe000`0062e000 ffffe000`001fb060 00000002`00000100 ffffd000`ffffffff : atikmpag+0x92c9 ffffd000`20108a90 fffff801`0fee0d10 : ffffd000`20a97f00 ffffe000`027453f0 ffffd000`20a95180 ffffe000`02745000 : dxgkrnl!DpiGetSchedulerCallbackState+0x5b ffffd000`20108ae0 fffff801`0fee09f0 : ffffe000`00000000 00001f80`00000001 ffffe262`e207b7a8 00000000`00000002 : nt!NtTraceEvent+0x1430 ffffd000`20108c30 fffff801`0ffd77ea : ffffd000`20a95180 ffffd000`20a95180 00000000`00000000 ffffd000`20aa1340 : nt!NtTraceEvent+0x1110 ffffd000`20108da0 00000000`00000000 : ffffd000`20109000 ffffd000`20103000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2efa STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+277ce fffff800`01ce17ce cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: atikmdag+277ce FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys BUCKET_ID: WRONG_SYMBOLS FAILURE_BUCKET_ID: WRONG_SYMBOLS ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:wrong_symbols FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8} Followup: MachineOwner ---------

dettagli su atikmdag:

Nell'attesa ho fatto la prova di ridurre il clock della memoria della GPU (come ha fatto http://www.nexthardware.com/forum/as...x-vapor-x.html dicendo che così non aveva problemi) da 1250 (default) a 1000 ma non cambia nulla, crasha lo stesso con league / youtube.

**Federico G. Mirabelli** · 03-01-2014, 17:21

Può essere una prova usare i driver 13.9 ? Non ho ben capiito se possono andare bene con la mia scheda...

**frakka** · 03-01-2014, 18:36

I 13.9 non supportano la tua scheda o almeno non è nella lista di compatibilità.

Per cortesia prova a disabilitare il plugin flash e a guardare youtube usando HTML5. Vediamo se anche così ti crasha oppure no...

Processore:	AMD Threadripper 2990X 32c/64t
Scheda Madre:	Gigabyte X399 Designare EX
Memorie RAM:	64 Gb Crucial Ballistix Sport LT DDR4 3200 MHz (4x16Gb CL16)
Scheda Video:	EVGA GeForce GTX 1060 SuperClocked 6Gb
Harddisk:	1x Sandisk UltraII 480Gb + 1x SSD Kingston A400 240Gb + 1x Sabrent NVME 1Tb + Un po' di hdd
Alimentatore:	Corsair RM1000
Raffreddamento ad Aria:	Noctua U14S TR4-SP3 + Ventola aggiuntiva in push/pull
Raffreddamento a Liquido:	Tanti bei ricordi...
Case:	CoolerMaster HAF Stacker 935
Lettori CD/DVD:	L'ho dovuto togliere...
Sistema Operativo:	CentOS / Windows 10 Pro + varie ed eventuali

Processore:	Intel Core i7-870
Scheda Madre:	Asus P7P55D-E
Memorie RAM:	2x4GB Corsair Vengance DDR3 @1600mhz
Scheda Video:	Sapphire AMD R9 290x
Harddisk:	2x Western Digital Caviar Black, 1x Crucial SSD
Alimentatore:	Corsair 750W 80+ Efficiency (bronze)
Case:	Cooler Master HAF 922
Schermo LCD/CRT:	Benq RL2455hm
Sistema Operativo:	Windows 8.1 pro

Processore:	AMD Threadripper 2990X 32c/64t
Scheda Madre:	Gigabyte X399 Designare EX
Memorie RAM:	64 Gb Crucial Ballistix Sport LT DDR4 3200 MHz (4x16Gb CL16)
Scheda Video:	EVGA GeForce GTX 1060 SuperClocked 6Gb
Harddisk:	1x Sandisk UltraII 480Gb + 1x SSD Kingston A400 240Gb + 1x Sabrent NVME 1Tb + Un po' di hdd
Alimentatore:	Corsair RM1000
Raffreddamento ad Aria:	Noctua U14S TR4-SP3 + Ventola aggiuntiva in push/pull
Raffreddamento a Liquido:	Tanti bei ricordi...
Case:	CoolerMaster HAF Stacker 935
Lettori CD/DVD:	L'ho dovuto togliere...
Sistema Operativo:	CentOS / Windows 10 Pro + varie ed eventuali

Processore:	Intel Core i7-870
Scheda Madre:	Asus P7P55D-E
Memorie RAM:	2x4GB Corsair Vengance DDR3 @1600mhz
Scheda Video:	Sapphire AMD R9 290x
Harddisk:	2x Western Digital Caviar Black, 1x Crucial SSD
Alimentatore:	Corsair 750W 80+ Efficiency (bronze)
Case:	Cooler Master HAF 922
Schermo LCD/CRT:	Benq RL2455hm
Sistema Operativo:	Windows 8.1 pro

Processore:	Intel Core i7-870
Scheda Madre:	Asus P7P55D-E
Memorie RAM:	2x4GB Corsair Vengance DDR3 @1600mhz
Scheda Video:	Sapphire AMD R9 290x
Harddisk:	2x Western Digital Caviar Black, 1x Crucial SSD
Alimentatore:	Corsair 750W 80+ Efficiency (bronze)
Case:	Cooler Master HAF 922
Schermo LCD/CRT:	Benq RL2455hm
Sistema Operativo:	Windows 8.1 pro

Bluescreen & Coil Whine R9 290x Reference

Strumenti della discussione

Valuta questa discussione

Display

Informazioni Thread

Users Browsing this Thread

Regole d'invio

	Spoiler:
	http://rwlabs.com/images/articles/co...af_922_036.jpg

	Spoiler:
	http://prohardver.hu/dl/cnt/2009-09/...r_v8_mb2_b.jpg

	Spoiler:
	STACK_COMMAND: kb FOLLOWUP_IP: atikmdag+277ce fffff800`01ce17ce cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: atikmdag+277ce FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys BUCKET_ID: WRONG_SYMBOLS FAILURE_BUCKET_ID: WRONG_SYMBOLS ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:wrong_symbols FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8} Followup: MachineOwner --------- 1: kd> lmvm atikmdag start end module name fffff800`01cba000 fffff800`029aa000 atikmdag (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Fri Dec 06 22:19:43 2013 (52A23F6F) CheckSum: 00CA856E ImageSize: 00CF0000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4