0069 Skrevet 14. januar 2007 Rapporter Del Skrevet 14. januar 2007 Har fått WowError og får den hver gang jeg spiller wow. Noen som vet om det?? Og hva kan jeg gjøre? Lenke til kommentar
Walts Skrevet 14. januar 2007 Rapporter Del Skrevet 14. januar 2007 "bilen starter ikke, hva er feil" funker dårlig.. fortell kanskje hva erroren er og hva som skjer. Lenke til kommentar
Halvt horn ost skinka piffi varmt Skrevet 14. januar 2007 Rapporter Del Skrevet 14. januar 2007 Det finnes vell en fil i WoW mappa de som heter repair ett eller annet, prøv den Lenke til kommentar
gamer73 Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 samme opplevde jeg. Kjør repair og be den slette alt og sette til default igjen. Da funket det for min del. Du må uansett oppdattere alle addons nå når TBC kommer uansett regner jeg med. Jeg har konsekvent slettet alle addons nå før TBC. Lenke til kommentar
ahpadt Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 Jeg har konsekvent slettet alle addons nå før TBC. 7724409[/snapback] Alle addons som funker i 2.0.4 funker med TBC. Det er samme klienten. Om du installerer TBC fra cden du får, så går det fortsatt ann å spille "vanlig".. Lenke til kommentar
gamer73 Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 Poenget er at jeg ikke vil utsette meg selv for mulige problemer med alle patchene som kommer nå. Jeg klarer meg uten addons, da jeg uanset bare er i pvp gear for tiden. Ca en uke fra release av TBC skal jeg legge inn itemrack og titanpanel, da jeg regner med at begge dem to er testet og oppdattert:) Lenke til kommentar
ahpadt Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 Poenget er at jeg ikke vil utsette meg selv for mulige problemer med alle patchene som kommer nå. Jeg klarer meg uten addons, da jeg uanset bare er i pvp gear for tiden. Ca en uke fra release av TBC skal jeg legge inn itemrack og titanpanel, da jeg regner med at begge dem to er testet og oppdattert:) 7724561[/snapback] Poenget er at den patchen som du spiller med akkurat nå, er den samme som du vil spille med om 1 uke. (så sant det ikke kommer en småpatch). Lenke til kommentar
gamer73 Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 det kommer nok noen småpatcher regner jeg med:) så jeg venter:) dessuten fikser dem på en del addons i ukene etter at dem kommer ut med en ny versjon uansett. Det tra som oftest et par uker før dem får en versjon som fungerer tilfredstillende innen den aktuelle patchen. Lenke til kommentar
Walts Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 Poenget er at jeg ikke vil utsette meg selv for mulige problemer med alle patchene som kommer nå. Jeg klarer meg uten addons, da jeg uanset bare er i pvp gear for tiden. Ca en uke fra release av TBC skal jeg legge inn itemrack og titanpanel, da jeg regner med at begge dem to er testet og oppdattert:) 7724561[/snapback] Poenget er at den patchen som du spiller med akkurat nå, er den samme som du vil spille med om 1 uke. (så sant det ikke kommer en småpatch). 7724610[/snapback] 2.0.5 kommer nok, er vist ute i US Lenke til kommentar
elf_man Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 Poenget er at jeg ikke vil utsette meg selv for mulige problemer med alle patchene som kommer nå. Jeg klarer meg uten addons, da jeg uanset bare er i pvp gear for tiden. Ca en uke fra release av TBC skal jeg legge inn itemrack og titanpanel, da jeg regner med at begge dem to er testet og oppdattert:) 7724561[/snapback] Poenget er at den patchen som du spiller med akkurat nå, er den samme som du vil spille med om 1 uke. (så sant det ikke kommer en småpatch). 7724610[/snapback] 2.0.5 kommer nok, er vist ute i US 7724715[/snapback] Den var ute veldig kort før den ble trukket igjen. Var visst så mye problemer med den at de bare venter med den enn så lenge Lenke til kommentar
0069 Skrevet 15. januar 2007 Forfatter Rapporter Del Skrevet 15. januar 2007 "bilen starter ikke, hva er feil" funker dårlig.. fortell kanskje hva erroren er og hva som skjer. 7723088[/snapback] Sorry...Jeg fikk den World of WarCraft (build 6320) Exe: C:\Program Files\World of Warcraft\WoW.exe Time: Jan 15, 2007 8:58:03.953 PM User: xxx Computer:XXX This application has encountered a critical error: ERROR #132 (0x85100084) Fatal Exception Program: C:\Program Files\World of Warcraft\WoW.exe Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:008187F3 The instruction at "0x008187F3" referenced memory at "0x000001AC". The memory could not be "read". WoWBuild: 6320 ------------------------------------------------------------------------------ ---------------------------------------- x86 Registers ---------------------------------------- EAX=0D85A8F0 EBX=08C08008 ECX=00000000 EDX=00000001 ESI=0C16A408 EDI=00000000 EBP=0012F9F4 ESP=0012F9F4 EIP=008187F3 FLG=00210246 CS =001B DS =0023 ES =0023 SS =0023 FS =003B GS =0000 ---------------------------------------- Stack Trace (Manual) ---------------------------------------- Address Frame Logical addr Module 008187F3 0012F9F4 0001:004177F3 C:\Program Files\World of Warcraft\WoW.exe 0076740E 0012FAB8 0001:0036640E C:\Program Files\World of Warcraft\WoW.exe 00767815 0012FB74 0001:00366815 C:\Program Files\World of Warcraft\WoW.exe 007552E7 0012FC48 0001:003542E7 C:\Program Files\World of Warcraft\WoW.exe 0048AF33 0012FC88 0001:00089F33 C:\Program Files\World of Warcraft\WoW.exe 0048A6CA 0012FD14 0001:000896CA C:\Program Files\World of Warcraft\WoW.exe 007D1BF2 0012FD7C 0001:003D0BF2 C:\Program Files\World of Warcraft\WoW.exe 007C7857 0012FDA0 0001:003C6857 C:\Program Files\World of Warcraft\WoW.exe 007C610C 0012FDAC 0001:003C510C C:\Program Files\World of Warcraft\WoW.exe 004446BE 0012FE74 0001:000436BE C:\Program Files\World of Warcraft\WoW.exe 00426B60 0012FEA8 0001:00025B60 C:\Program Files\World of Warcraft\WoW.exe 0042351F 0012FF18 0001:0002251F C:\Program Files\World of Warcraft\WoW.exe 004230A1 0012FF30 0001:000220A1 C:\Program Files\World of Warcraft\WoW.exe 00404B0E 0012FFC0 0001:00003B0E C:\Program Files\World of Warcraft\WoW.exe 7C816FD7 0012FFF0 0001:00015FD7 C:\WINDOWS\system32\kernel32.dll ---------------------------------------- Stack Trace (Using DBGHELP.DLL) ---------------------------------------- 008187F3 WoW.exe <unknown symbol>+0 (0x00000001,0x00000001,0x000000F8,0x08C08008) ---------------------------------------- Loaded Modules ---------------------------------------- 0x00320000 - 0x003B0000 C:\Program Files\World of Warcraft\fmod.dll 0x00400000 - 0x00D9B000 C:\Program Files\World of Warcraft\WoW.exe 0x0FFD0000 - 0x0FFF8000 C:\WINDOWS\system32\rsaenh.dll 0x10000000 - 0x10069000 C:\Program Files\World of Warcraft\DivxDecoder.dll 0x16B60000 - 0x16C78000 C:\Program Files\World of Warcraft\dbghelp.dll 0x4FDD0000 - 0x4FF76000 C:\WINDOWS\system32\d3d9.dll 0x5AD70000 - 0x5ADA8000 C:\WINDOWS\system32\uxtheme.dll 0x5B860000 - 0x5B8B4000 C:\WINDOWS\system32\NETAPI32.dll 0x5D090000 - 0x5D12A000 C:\WINDOWS\system32\COMCTL32.dll 0x5ED00000 - 0x5EDCC000 C:\WINDOWS\system32\OPENGL32.dll 0x662B0000 - 0x66308000 C:\WINDOWS\system32\hnetcfg.dll 0x68B20000 - 0x68B40000 C:\WINDOWS\system32\GLU32.dll 0x6D990000 - 0x6D996000 C:\WINDOWS\system32\d3d8thk.dll 0x71A50000 - 0x71A8F000 C:\WINDOWS\system32\mswsock.dll 0x71A90000 - 0x71A98000 C:\WINDOWS\System32\wshtcpip.dll 0x71AA0000 - 0x71AA8000 C:\WINDOWS\system32\WS2HELP.dll 0x71AB0000 - 0x71AC7000 C:\WINDOWS\system32\WS2_32.dll 0x71AD0000 - 0x71AD9000 C:\WINDOWS\system32\WSOCK32.dll 0x71BF0000 - 0x71C03000 C:\WINDOWS\system32\SAMLIB.dll 0x722B0000 - 0x722B5000 C:\WINDOWS\system32\sensapi.dll 0x72D10000 - 0x72D18000 C:\WINDOWS\system32\msacm32.drv 0x72D20000 - 0x72D29000 C:\WINDOWS\system32\wdmaud.drv 0x73760000 - 0x737A9000 C:\WINDOWS\system32\DDRAW.dll 0x73BC0000 - 0x73BC6000 C:\WINDOWS\system32\DCIMAN32.dll 0x73EE0000 - 0x73EE4000 C:\WINDOWS\system32\KsUser.dll 0x73F10000 - 0x73F6C000 C:\WINDOWS\system32\dsound.dll 0x74720000 - 0x7476B000 C:\WINDOWS\system32\MSCTF.dll 0x76390000 - 0x763AD000 C:\WINDOWS\system32\IMM32.dll 0x769C0000 - 0x76A73000 C:\WINDOWS\system32\USERENV.dll 0x76B40000 - 0x76B6D000 C:\WINDOWS\system32\WINMM.dll 0x76C30000 - 0x76C5E000 C:\WINDOWS\system32\WINTRUST.dll 0x76C90000 - 0x76CB8000 C:\WINDOWS\system32\IMAGEHLP.dll 0x76E80000 - 0x76E8E000 C:\WINDOWS\system32\rtutils.dll 0x76E90000 - 0x76EA2000 C:\WINDOWS\system32\rasman.dll 0x76EB0000 - 0x76EDF000 C:\WINDOWS\system32\TAPI32.dll 0x76EE0000 - 0x76F1C000 C:\WINDOWS\system32\RASAPI32.DLL 0x76F20000 - 0x76F47000 C:\WINDOWS\system32\DNSAPI.dll 0x76F60000 - 0x76F8C000 C:\WINDOWS\system32\WLDAP32.dll 0x76FB0000 - 0x76FB8000 C:\WINDOWS\System32\winrnr.dll 0x76FC0000 - 0x76FC6000 C:\WINDOWS\system32\rasadhlp.dll 0x77120000 - 0x771AC000 C:\WINDOWS\system32\OLEAUT32.dll 0x771B0000 - 0x77256000 C:\WINDOWS\system32\WININET.dll 0x773D0000 - 0x774D3000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll 0x774E0000 - 0x7761D000 C:\WINDOWS\system32\ole32.dll 0x77690000 - 0x776B1000 C:\WINDOWS\system32\NTMARTA.DLL 0x77A80000 - 0x77B14000 C:\WINDOWS\system32\CRYPT32.dll 0x77B20000 - 0x77B32000 C:\WINDOWS\system32\MSASN1.dll 0x77BD0000 - 0x77BD7000 C:\WINDOWS\system32\midimap.dll 0x77BE0000 - 0x77BF5000 C:\WINDOWS\system32\MSACM32.dll 0x77C00000 - 0x77C08000 C:\WINDOWS\system32\VERSION.dll 0x77C10000 - 0x77C68000 C:\WINDOWS\system32\msvcrt.dll 0x77D40000 - 0x77DD0000 C:\WINDOWS\system32\USER32.dll 0x77DD0000 - 0x77E6B000 C:\WINDOWS\system32\ADVAPI32.dll 0x77E70000 - 0x77F01000 C:\WINDOWS\system32\RPCRT4.dll 0x77F10000 - 0x77F57000 C:\WINDOWS\system32\GDI32.dll 0x77F60000 - 0x77FD6000 C:\WINDOWS\system32\SHLWAPI.dll 0x77FE0000 - 0x77FF1000 C:\WINDOWS\system32\Secur32.dll 0x7C800000 - 0x7C8F4000 C:\WINDOWS\system32\kernel32.dll 0x7C900000 - 0x7C9B0000 C:\WINDOWS\system32\ntdll.dll 0x7C9C0000 - 0x7D1D5000 C:\WINDOWS\system32\SHELL32.dll 0x7E1E0000 - 0x7E280000 C:\WINDOWS\system32\urlmon.dll ---------------------------------------- Memory Dump ---------------------------------------- Code: 16 bytes starting at (EIP = 008187F3) 008187F3: 8B 81 AC 01 00 00 56 8B 75 08 8B D0 33 D6 83 E2 ......V.u...3... Stack: 1024 bytes starting at (ESP = 0012F9F4) * = addr ** * 0012F9F0: 00 00 00 00 B8 FA 12 00 0E 74 76 00 01 00 00 00 .........tv..... 0012FA00: 01 00 00 00 F8 00 00 00 08 80 C0 08 08 88 91 0E ................ 0012FA10: 00 00 80 BF 00 FA 12 00 B0 FF 12 00 B8 0F F5 4F ...............O 0012FA20: 01 00 00 00 80 C2 E5 11 BD 02 00 00 00 00 80 3F ...............? 0012FA30: 00 00 00 00 00 00 00 80 DF 00 CF 00 00 00 00 00 ................ 0012FA40: 60 FA 12 00 03 EC E1 4F 7B 05 00 00 60 B8 E5 11 `......O{...`... 0012FA50: C0 2D 15 00 00 00 80 3F 00 00 00 00 00 00 00 00 .-.....?........ 0012FA60: 00 00 00 00 00 00 00 00 00 00 80 3F 00 00 00 00 ...........?.... 0012FA70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0012FA80: 96 43 8B 3C 90 FA 12 00 32 F8 80 00 00 00 00 00 .C.<....2....... 0012FA90: A8 FA 12 00 96 08 81 00 11 00 00 00 00 00 00 00 ................ 0012FAA0: 48 C3 C4 08 00 00 00 00 10 A0 85 0D 00 00 00 00 H............... 0012FAB0: 00 00 00 00 F0 A8 85 0D 74 FB 12 00 15 78 76 00 ........t....xv. 0012FAC0: A4 D2 FF 04 08 88 91 0E 08 D2 FF 04 4B B3 B5 C5 ............K... 0012FAD0: 1E 75 66 C5 03 5F 67 C2 BB BE BB 3D 70 21 59 BF .uf.._g....=p!Y. 0012FAE0: 77 41 26 41 2C 95 B5 C5 DC 7F 66 C5 23 A1 67 C2 wA&A,.....f.#.g. 0012FAF0: 1E 27 B2 3D 20 1E 90 BD 5A 2D 62 41 00 00 00 00 .'.= ...Z-bA.... 0012FB00: 08 D2 FF 04 14 00 00 00 01 00 00 00 00 00 00 00 ................ 0012FB10: 00 00 00 00 10 00 00 00 00 00 00 00 67 CD 60 B0 ............g.`. 0012FB20: 00 80 FD 7F 00 F0 FD 7F 00 00 00 00 00 00 00 00 ................ 0012FB30: F8 FA 12 00 26 4E 92 44 B0 FF 12 00 96 43 8B 3C ....&N.D.....C.< 0012FB40: 24 72 5D 40 1E 27 B2 BD 4D 9E 57 3F 00 00 00 00 $r]@.'..M.W?.... 0012FB50: 82 8E BA BE 11 00 00 00 00 00 00 00 6C FB 12 00 ............l... 0012FB60: 00 00 00 00 10 00 42 09 00 00 00 00 00 00 00 00 ......B......... 0012FB70: F8 00 00 00 48 FC 12 00 E7 52 75 00 08 80 11 07 ....H....Ru..... 0012FB80: 08 D2 FF 04 28 6F 4E 0D 08 D6 B4 C5 79 B4 67 C5 ....(oN.....y.g. 0012FB90: C0 FF 6A C2 A4 FB 12 00 86 20 67 00 C8 45 BF 10 ..j...... g..E.. 0012FBA0: C8 45 BF 10 F0 FB 12 00 FF 9F 64 00 20 4C CD 08 .E........d. L.. 0012FBB0: C8 45 BF 10 20 4C CD 08 4C FC 12 00 E2 FB 6E 00 .E.. L..L.....n. 0012FBC0: 00 E4 6C 41 00 BA A0 40 80 45 22 42 0E E1 90 7C [email protected]"B...| 0012FBD0: 08 D2 FF 04 08 00 00 00 F0 FB 12 00 F6 9C 46 00 ..............F. 0012FBE0: 01 00 00 00 F6 9C 46 00 C8 45 BF 10 33 10 05 F0 ......F..E..3... 0012FBF0: 1C FC 12 00 92 27 65 00 F2 F0 07 00 01 00 00 00 .....'e......... 0012FC00: 92 27 65 00 00 00 00 00 00 00 00 00 00 00 00 00 .'e............. 0012FC10: 00 00 80 3F 00 00 80 3F 00 00 80 3F 48 FC 12 00 ...?...?...?H... 0012FC20: 13 50 75 00 24 46 53 44 00 00 00 00 20 4C CD 08 .Pu.$FSD.... L.. 0012FC30: 0B 00 00 00 08 88 C1 08 40 50 75 00 08 D2 FF 04 ........@Pu..... 0012FC40: 08 80 11 07 08 D2 FF 04 88 FC 12 00 33 AF 48 00 ............3.H. 0012FC50: 10 AC 18 07 08 80 11 07 00 00 00 00 00 00 00 00 ................ 0012FC60: 00 00 00 00 00 00 40 44 00 00 80 44 00 00 80 3F [email protected]...? 0012FC70: 00 00 80 3F 00 00 80 3F 00 00 00 00 00 00 00 00 ...?...?........ 0012FC80: 00 00 00 00 88 6F 4E 0D 14 FD 12 00 CA A6 48 00 .....oN.......H. 0012FC90: 00 00 00 00 00 00 80 3F 00 00 00 00 00 00 00 00 .......?........ 0012FCA0: 00 00 00 00 00 00 00 00 00 00 80 3F 00 00 00 00 ...........?.... 0012FCB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 3F ...............? 0012FCC0: 00 00 00 00 CD CC CC BE 99 99 99 BE 00 00 00 00 ................ 0012FCD0: 00 00 80 3F 00 00 20 40 00 00 00 00 00 00 00 00 ...?.. @........ 0012FCE0: 00 00 00 00 00 00 00 00 56 55 55 40 00 00 00 00 ........VUU@.... 0012FCF0: 00 00 00 00 00 00 00 80 00 00 00 80 6F 12 03 BB ............o... 0012FD00: 00 00 00 00 CD CC CC B9 CC CC CC 39 00 00 00 80 ...........9.... 0012FD10: 00 00 80 3F 7C FD 12 00 F2 1B 7D 00 00 00 00 00 ...?|.....}..... 0012FD20: 08 72 17 07 24 72 17 07 00 00 00 00 00 00 00 00 .r..$r.......... 0012FD30: 00 00 00 00 56 55 55 40 00 00 00 00 00 00 00 00 ....VUU@........ 0012FD40: 00 00 00 80 00 00 00 80 24 72 17 07 00 00 00 00 ........$r...... 0012FD50: CD CC CC B9 CC CC CC 39 00 00 00 80 00 00 80 3F .......9.......? 0012FD60: 99 99 99 3E CD CC CC 3E 00 00 00 00 CD CC CC BE ...>...>........ 0012FD70: 99 99 99 BE 00 00 00 00 A0 FD 12 00 A0 FD 12 00 ................ 0012FD80: 57 78 7C 00 08 15 E4 01 08 C0 15 07 08 08 DA 08 Wx|............. 0012FD90: 00 00 00 00 C8 37 DA 08 09 00 00 00 E8 CC 15 07 .....7.......... 0012FDA0: AC FD 12 00 0C 61 7C 00 20 08 DA 08 74 FE 12 00 .....a|. ...t... 0012FDB0: BE 46 44 00 20 08 DA 08 96 43 8B 3C 88 FE 12 00 .FD. ....C.<.... 0012FDC0: 68 97 B3 01 68 97 B3 01 00 00 00 00 20 F8 7B 3F h...h....... .{? 0012FDD0: 00 00 00 80 00 00 80 3F 00 00 00 00 3C FE 12 00 .......?....<... 0012FDE0: B2 DB 32 00 58 6D 67 01 A0 24 33 00 98 FE F8 04 ..2.Xmg..$3..... 0012FDF0: E0 DC 32 00 98 FE F8 04 40 00 00 00 0F 6F 66 45 [email protected] ------------------------------------------------------------------------------ ====================================================================== Hardware/Driver Information: Processor: 0x0 Page Size: 4096 Min App Address: 0x10000 Max App Address: 0x7ffeffff Processor Mask: 0x3 Number of Processors: 2 Processor Type: 586 Allocation Granularity: 65536 Processor Level: 6 Processor Revision: 3846 Percent memory used: 31 Total physical memory: 2146611200 Free Memory: 1472946176 Page file: -163659776 Total virtual memory: 2147352576 Her Lenke til kommentar
Overguard Skrevet 15. januar 2007 Rapporter Del Skrevet 15. januar 2007 Klikk for å se/fjerne innholdet nedenfor Error 132 This post exists to explain as well as detail known issues and solutions regarding “Error #132”. While this error is known in many forms, an explanation or solution for each individual error may be quite different due to this error being general in nature. The 132 error simply depicts that something was not processed correctly. As this is such a general implication of an issue, it can be difficult to find the cause and an ultimate solution. In many cases the information below the actual “Error #132” message can help better describe the cause, however in the majority of cases the error will simply depict an error within memory. It should be noted that while the system memory (RAM) may in fact be the cause of this error in some cases, many other causes must be taken into account. Below information exists on common 132 errors, as well as some helpful troubleshooting. However, as has been said already, while this troubleshooting may be a good jumping off point, in no way is it meant as a complete solution to each users 132 error. If you are experiencing one of these errors, a good start would be our FAQ article on 132 errors: http://faq.wow-europe.com/en/article.php?id=722 While we hope that you find a solution for your issue in this thread, we request that if you do not find a solution here, that you contact us through more direct means, via e-mail or on the phone, as the #132 error will often require or in-depth troubleshooting than is possible on these forums. Contact information is available here: http://www.wow-europe.com/en/support/ Memory Could Not Be Read/Written This 132 error is the most common, and unfortunately the most vague. Q u o t e: ERROR #132 (0x85100084) Fatal Exception Program: C:\Program Files\World of Warcraft\WoW.exe Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:0040C5B5 The instruction at "0x0040C5B5" referenced memory at "0x00000004". The memory could not be "written/read" Note: The above example may be different to the error you are getting. The explanation for this is that an error occurred while accessing data that caused the software (World of Warcraft) to be unable to continue functioning correctly. While the most common cause can indeed be system memory (RAM) related, it certainly does not imply that all occurrences of this issue are. Many RAM tests are available, some popular ones being MemTest86 or Prime95. Versions of both are linked below. While these tests will put the system memory through its paces, they are designed to find physical flaws within the RAM, which may not always be the cause of a RAM related error. More information on other causes for RAM failures is covered in the next section. Prime95 http://files.extremeoverclocking.com/file.php?f=103 When using Prime95, select ‘Torture Test’ in the Options menu and then choose ‘Blend’ and click ok. A continuous test will then start running. It is best to run this for a long period, such as overnight, if the test is still running after several hours, then that can be counted as a success, if the test has halted finding an error, then this would usually indicate an issue with the Motherboard, CPU or RAM in the computer Memtest http://hcidesign.com/memtest/ You may be able to find other ‘stress’ or ‘burn in’ software tests available for heavily testing RAM by searching for them through your favourite Internet search engine. Keep in mind that these programs will stress components and if they are prone to failure, or on their way there, it is possible that the failing component will not make it through the test alive. Any type of ‘stress’ or ‘burn in’ program should be used with the necessary precautions such as securing important data at a secondary location. A common question is: If there is an issue with a system’s ability to access memory, why does it only show up when playing World of Warcraft? While World of Warcraft may seem less visually demanding than some other games the amount of data being swapped in and out of RAM can be much greater than many games. With potentially hundreds of characters on-screen at a time, each with their own textures and models, then factoring in game data, terrain, spell effects, etc. the use of RAM and the necessity for stability can be quite important in World of Warcraft. Most games have the ability, and are designed to limit the amount of data seen and processed by the user at any one time. You can see this necessity for RAM mirrored in benchmarks showing that, while games such as Doom 3 or Half-Life 2 will perform better with more powerful video cards over other upgrades, World of Warcraft will perform better with greater amounts of RAM. Another common question or assumption: If the game ran fine before, and is now only crashing after a patch, isn’t the patch to blame? In most cases we have found that a specific hardware instability or flaw existed before the patch was introduced, and due to the changes in a patch, it can bring any instabilities or flaws to the surface. This has been proven to be the case many times through proper system troubleshooting steps. However that is not to say that a specific error could not be introduced by a patch and be due to a software error, only that it is still the rarest form of error. RAM Settings and Procedures Many RAM related issues stem not from physical errors within the RAM modules themselves, but rather how they interact with the computer they are installed to. Almost all cases of this will be in custom built systems, or those who have recently added additional or new RAM modules. In some cases users will experience a pleasant playing experience until they install additional RAM. This situation can also apply to newly built systems in which no previous point of ‘working’ reference is available, and so an assumption is made that the software is at fault. It would be best to begin by describing some more important and sometimes less known RAM terms and functions. Keep in mind that these descriptions are very basic and the actual meaning and relationship of each may be ‘softened’ for ease of reading. RAM – An acronym for Random Access Memory. It is a location for temporary storage of information. RAM queues up information from the hard drive and provides it to the CPU much faster than if it were to go directly from the hard drive to the CPU. FSB – An acronym for Frontside Bus, which is the data ‘highway’ between the CPU and RAM. You may see RAM labelled as PC3200 which is a different way of labelling the RAM as being compatible with an FSB of 400 MHz. The motherboard and processor must also be able to support the RAM’s FSB rating to take full advantage. Latency – The latency is a term to refer to the different response times inherently manufactured into specific RAM. This differs from the FSB speed as it is the RAM’s own personal speed rating, and not that of the path of data between the RAM and CPU. There are more specifics for latency times, such as the CAS, RAS, T, etc. which dictate where data is stored in memory as well as how frequent it is sent out. Normally seen as a string of 4 or 5 number sets when shopping for RAM (2-2-3-5 for example). These settings are very important but for the sake of the length of this document, further information will be left to you to research. Voltage – This refers to, quite simply, the amount of voltage (aka power) the motherboard supplies the RAM. Some RAM, especially that of higher quality and/or lower latency, will require a higher voltage than what is provided by the motherboard at default. Each of these settings can have equally important roles in how the RAM functions within the system. The motherboard is in control of these settings, and their values can only be changed through the motherboard BIOS. The BIOS can be a very sensitive set of controls over the primary functions of the system and it is not recommended that you enter the BIOS and change any settings without prior training or experience. If you have any doubt in your ability to change BIOS settings please involve a trained professional. For any changes of the above mentioned settings it recommended that you contact your motherboard and RAM manufacturer for the correct settings. Keep in mind that the RAM manufacturer may have a better grasp of their own product and settings over what the motherboard manufacturer may recommend. It should also be noted that some motherboards do not ‘play well’ with specific types of RAM, and some motherboards are pickier than others as far as what they will operate correctly with (more in this in the next section). It is best to look in your motherboard manufacturers suggestions for approved RAM modules before upgrading. However, even with their suggestions it may be necessary to change some of the settings detailed above. In addition, over clocking your system memory and/or CPU can result in a less stable environment for software to run under. It is not recommended to overclock any part of a computer system to achieve greater performance, and to certainly remove any over clocking if instability (crashing) should occur. Motherboard and RAM Interactivity There are several chipsets that are documented with stability issues when using certain RAM FSB speeds. The KT400 and nForce2 chipsets have been documented as unstable when DDR400 (PC3200) RAM is used. Other known instabilities may exist with many combinations, such as Athlon 64 processors and motherboards when using low latency RAM timings. http://www.via.com.tw/en/products/chipsets/k7-series/kt400/ http://www.nvidia.com/object/IO_20020930_9198.html It is recommended to search for technical issues with your own hardware. It can be surprising what you may find as a documented flaw with your motherboard that you may not have http://forums.wow-europe.com/thread.html?t...=35983656&sid=1 Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå