[fixed] PC Freezes + Locks up only when playing certain games

Plaayer · November 7, 2012

I recently got a new 2x4GB kit of RAM (Patriot G2 ) to accompany my 4GB (Corsair XMS3 2x2GB DDR3-1600) kit that I had. So, a total of 12GB. Similar spec and everything with the only difference being 1.65v and a 1.5v on the 4GB kit and 8GB kit, respectively and the varying densities of the RAM sticks. It only happens on the games Battlefield 3 and Bullet Run after ~15min of gameplay. All the other games that I have tested (CS:S, GMOD, TF2, League of Legends, Just Cause 2, and a couple others) run A-OK with 0 problems. Desktop/browsing the web is fine as well.

Sometimes it will freeze + lock up, resulting me just sitting there waiting to see something happens. But in the end, I usually just end up holding the power button as there is nothing else to do. Sometimes, it will give me the BSOD error code 0x00000101. I've researched on this and I'll post what I've done to my PC in efforts of relieving these problems.

Here are my specs as of right now:

Cooler Master CM690 II Basic

Intel Core i5-760

Corsair H70 (1 pulling fan)

Corsair XMS3 2x2GB DDR3-1600 @ 1.65v

Patriot Gamer Series G2 2x4GB DDR3-1600 @ 1.5v

EVGA GTX 460 Superclocked EE

Corsair TX750w

WD Blue 1TB

Seagate Barracuda 500gb

This list of things that I've done to my PC is very large! ):

General

Updated Windows 7 using Windows Update

Updated video drivers to latest version

Updated BIOS to latest revision

Installed .NET Framework 4.5

Updated DirectX

Prime95 ~ Small FFT for 2 hours // 0 errors

Prime95 ~ Blend for 2 hours // 0 errors

Prime95 ~ Custom w/ 11.5GB of RAM for 2 hours // 0 errors

Prime95 ~ Custom w/ 2x2GB kit of RAM ; 3.5GB tested for 2 hours // 0 errors

Prime95 ~ Custom w/ 2x4GB kit of RAM ; 7.5GB tested for 2 hours // 0 errors

Checked temps in-game: avg 56C on CPU (with a 3.4GHz OC); avg 68C on GPU

CPU

Lowered overclock of 3.6GHz (18mult, 200BCLK @ 1.3V) down to 3.4GHz (17mult, 200BCLK @ 1.3V) // Stable overclock tested w/ Prime95 for 6 hours

Stock clock @ "auto" voltage

Stock clock @ 1.3v

RAM

Memtest 86+ tested each stick individually // 0 errors

Memtest 86+ tested w/ all sticks together // 0 errors

Windows Memory Diagnostics w/ all sticks together // 0 errors

HDD

Ran "chkdsk /f" to search for broken, corrupt, or missing Windows files

I'm seriously out of ideas. If you have an idea, please post. I really just want to play. As of right now, I personally think it's Punkbuster that's screwing everything up since both BF3 and Bullet Run use it. Testing with Blacklight: Retribution, and I'll update the thread as more tests go by. (I also might have forgot some.)

Edited November 9, 2012 by Plaayer

enigma# · November 7, 2012

Another challenge! Post your minidump and event viewer log entry for this crash.

enigma# · November 7, 2012

As well some motherboards are very picky about the voltages. If its 1.5/1.65v, down clock your ram to 1.5 or overlock it all to 1.65. I wouldn't suggest going over 1.65 btw

Plaayer · November 8, 2012

I was running 1.5v ever since I got the new kit. I'll try 1.65v now.

Here's the minidumps that I have. However, none were the 0x00000101 error code. I used Blue Screen View to get these results.

==================================================
Dump File         : 110412-23602-01.dmp
Crash Time        : 11/4/2012 3:23:26 PM
Bug Check String  : CRITICAL_OBJECT_TERMINATION
Bug Check Code    : 0x000000f4
Parameter 1       : 00000000`00000003
Parameter 2       : fffffa80`0c2c8b30
Parameter 3       : fffffa80`0c2c8e10
Parameter 4       : fffff800`033e2460
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description  : NT Kernel & System
Product Name      : MicrosoftÂ® WindowsÂ® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\110412-23602-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 283,424
==================================================


==================================================
Dump File         : 110312-25677-01.dmp
Crash Time        : 11/3/2012 7:32:12 AM
Bug Check String  : 
Bug Check Code    : 0x00000109
Parameter 1       : a3a039d8`9b495659
Parameter 2       : b3b7465e`edc625af
Parameter 3       : fffff800`0309cfc0
Parameter 4       : 00000000`00000001
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description  : NT Kernel & System
Product Name      : MicrosoftÂ® WindowsÂ® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\110312-25677-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 283,312
==================================================


==================================================
Dump File         : 110312-27081-01.dmp
Crash Time        : 11/3/2012 7:28:45 AM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : fffff87f`831ca718
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000000
Parameter 4       : fffff880`016415a4
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+415a4
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\110312-27081-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 291,936
==================================================

The file that seems to be causing these three crashes are ntoskrnl.exe. I read up on it, and read somewhere that "chkdsk /f" should help fix this. (I already have done this.)

Cookie · November 8, 2012

if I had to guess your 0x000000f4 error is having to do with your overclocking man

Short · November 8, 2012

0x000000d1

bump your cpu-nb voltage, saw this when i was ocing my cpu today.

enigma# · November 8, 2012

it would be nice to see the minidumps, they are a bit more telltale =3

Plaayer · November 8, 2012

Enigma, do you want me to just upload the actual .dmp files? I only have 3.

enigma# · November 8, 2012

Sure that would be great ^_^

Plaayer · November 8, 2012

Here you go. http://www.mediafire.com/?13njptvqb7zzvk9

Thanks in advance for helping me.

enigma# · November 8, 2012

Latest Dump:

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [G:\downloads\Minidump\110412-23602-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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 Personal

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Machine Name:

Kernel base = 0xfffff800`03064000 PsLoadedModuleList = 0xfffff800`032a8670

Debug session time: Sun Nov 4 16:18:24.173 2012 (UTC - 7:00)

System Uptime: 0 days 0:00:57.484

Loading Kernel Symbols

...............................................................

................................................................

.......................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800c2c8b30, fffffa800c2c8e10, fffff800033e2460}

Probably caused by : csrss.exe

Followup: MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)

A process or thread crucial to system operation has unexpectedly exited or been

terminated.

Several processes and threads are necessary for the operation of the

system; when they are terminated (for any reason), the system can no

longer function.

Arguments:

Arg1: 0000000000000003, Process

Arg2: fffffa800c2c8b30, Terminating object

Arg3: fffffa800c2c8e10, Process image file name

Arg4: fffff800033e2460, Explanatory message (ascii)

Debugging Details:

------------------

PROCESS_OBJECT: fffffa800c2c8b30

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0xF4_C0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:

fffff880`061a1b08 fffff800`0346a822 : 00000000`000000f4 00000000`00000003 fffffa80`0c2c8b30 fffffa80`0c2c8e10 : nt!KeBugCheckEx

fffff880`061a1b10 fffff800`03416e0b : ffffffff`ffffffff fffffa80`0cd8f640 fffffa80`0c2c8b30 fffffa80`0c2c8b30 : nt!PspCatchCriticalBreak+0x92

fffff880`061a1b50 fffff800`03395f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0c2c8b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6

fffff880`061a1ba0 fffff800`030e2253 : fffffa80`0c2c8b30 fffff880`c0000005 fffffa80`0cd8f640 fffffa80`0d1e3200 : nt!NtTerminateProcess+0xf4

fffff880`061a1c20 00000000`77cb15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`0315e558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cb15da

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

Followup: MachineOwner

---------

0: kd> !process fffffa800c2c8b30 3

GetPointerFromAddress: unable to read from fffff80003312000

PROCESS fffffa800c2c8b30

SessionId: none Cid: 01fc Peb: 7fffffd3000 ParentCid: 01ec

DirBase: 2bf121000 ObjectTable: fffff8a000a2e920 HandleCount: <Data Not Accessible>

Image: csrss.exe

VadRoot fffffa800c328820 Vads 82 Clone 0 Private 2297. Modified 170. Locked 1749.

DeviceMap fffff8a000006090

Token fffff8a000a43780

ReadMemory error: Cannot get nt!KeMaximumIncrement value.

fffff78000000000: Unable to get shared data

ElapsedTime 00:00:00.000

UserTime 00:00:00.000

KernelTime 00:00:00.000

QuotaPoolUsage[PagedPool] 0

QuotaPoolUsage[NonPagedPool] 0

Working Set Sizes (now,min,max) (3425, 50, 345) (13700KB, 200KB, 1380KB)

PeakWorkingSetSize 4343

VirtualSize 67 Mb

PeakVirtualSize 67 Mb

PageFaultCount 7481

MemoryPriority BACKGROUND

BasePriority 13

CommitCharge 4334

*** Error in reading nt!_ETHREAD @ fffffa800c2be4e0

enigma# · November 8, 2012

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [G:\downloads\Minidump\110312-27081-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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 Personal

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Machine Name:

Kernel base = 0xfffff800`03005000 PsLoadedModuleList = 0xfffff800`03249670

Debug session time: Sat Nov 3 08:26:37.654 2012 (UTC - 7:00)

System Uptime: 0 days 18:19:32.919

Loading Kernel Symbols

...............................................................

................................................................

.................

Loading User Symbols

Loading unloaded module list

.............................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff87f831ca718, 2, 0, fffff880016415a4}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : memory_corruption

Followup: memory_corruption

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

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 kernel debugger is available get stack backtrace.

Arguments:

Arg1: fffff87f831ca718, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff880016415a4, address which referenced memory

Debugging Details:

------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b3100

fffff87f831ca718

CURRENT_IRQL: 2

FAULTING_IP:

tcpip!WfpAlepAuthorizeSend+ca4

fffff880`016415a4 4c8b842408010080 mov r8,qword ptr [rsp-7FFFFEF8h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff880031ca480 -- (.trap 0xfffff880031ca480)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=000000000000000a rbx=0000000000000000 rcx=000000000000003a

rdx=000000000000000c rsi=0000000000000000 rdi=0000000000000000

rip=fffff880016415a4 rsp=fffff880031ca610 rbp=0000000000000000

r8=0000000000000000 r9=0000000000000000 r10=fffff880031cab20

r11=fffff880031cad18 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

tcpip!WfpAlepAuthorizeSend+0xca4:

fffff880`016415a4 4c8b842408010080 mov r8,qword ptr [rsp-7FFFFEF8h] ss:0018:fffff87f`831ca718=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003083569 to fffff80003083fc0

STACK_TEXT:

fffff880`031ca338 fffff800`03083569 : 00000000`0000000a fffff87f`831ca718 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff880`031ca340 fffff800`030821e0 : 00000000`00000000 fffff880`031ca580 fffff880`072b22d0 fffff880`01747758 : nt!KiBugCheckDispatch+0x69

fffff880`031ca480 fffff880`016415a4 : 00000000`00000002 fffff880`01448755 00000000`00000000 fffffa80`0e388820 : nt!KiPageFault+0x260

fffff880`031ca610 fffff880`016406cc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0xca4

fffff880`031cad20 fffff880`01643b56 : 00000000`00000000 00000000`00000000 00000000`0000003a 00000000`00000000 : tcpip!WfpAleAuthorizeSend+0x31c

fffff880`031caff0 fffff880`0167a57e : 00000000`00000000 fffff880`031cb428 fffff880`031cb420 fffffa80`00000000 : tcpip!WfpAleConnectAcceptIndicate+0x106

fffff880`031cb0e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!ProcessALEForTransportPacket+0x5fe

STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !tcpip

fffff880016415ab - tcpip!WfpAlepAuthorizeSend+cab

[ 00:80 ]

1 error : !tcpip (fffff880016415ab)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption

---------

enigma# · November 8, 2012

Loading Dump File [G:\downloads\Minidump\110312-25677-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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 Personal

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Machine Name:

Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`0329e670

Debug session time: Sat Nov 3 08:30:16.744 2012 (UTC - 7:00)

System Uptime: 0 days 0:02:00.008

Loading Kernel Symbols

...............................................................

................................................................

................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89b495659, b3b7465eedc625af, fffff8000309cfc0, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)

This bugcheck is generated when the kernel detects that critical kernel code or

data have been corrupted. There are generally three causes for a corruption:

1) A driver has inadvertently or deliberately modified critical kernel code

or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx

2) A developer attempted to set a normal kernel breakpoint using a kernel

debugger that was not attached when the system was booted. Normal breakpoints,

"bp", can only be set if the debugger is attached at boot time. Hardware

breakpoints, "ba", can be set at any time.

3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.

Arguments:

Arg1: a3a039d89b495659, Reserved

Arg2: b3b7465eedc625af, Reserved

Arg3: fffff8000309cfc0, Failure type dependent information

Arg4: 0000000000000001, Type of corrupted region, can be

0 : A generic data region

1 : Modification of a function or .pdata

2 : A processor IDT

3 : A processor GDT

4 : Type 1 process list corruption

5 : Type 2 process list corruption

6 : Debug routine modification

7 : Critical MSR modification

Debugging Details:

------------------

BUGCHECK_STR: 0x109

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800030d8fc0

STACK_TEXT:

fffff880`031bd5d8 00000000`00000000 : 00000000`00000109 a3a039d8`9b495659 b3b7465e`edc625af fffff800`0309cfc0 : nt!KeBugCheckEx

STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

Followup: MachineOwner

---------

enigma# · November 8, 2012

Reading through all these, kinda gives me an idea that it's your RAM...

Plaayer · November 8, 2012

Maybe it's my old set of RAM. This was happening before I even got my new kit. Let me try running just the kits separately in BF3, and we'll see what happens.

I used to be able to play BF3 for hours upon hours when it was first released. Now, it's weird. Haha.

EDIT: I just tried playing BF3 using all 12GB's, then the 8GB kit, and then the 4GB kit with all of the tests running at 1.64v (my motherboard insists on only increasing/decreasing 0.02v at a time) and DDR3-1600. All crashed after ~15 minutes of gameplay. No minidumps were created.

Edit x2: I'm going to let Memtest86+ run overnight. Then, we shall see the problem tomorrow.

Edited November 8, 2012 by Plaayer

Plaayer · November 8, 2012

Update: after running Memtest86+ overnight, I ended up with these results. Now the hard part is to find out which RAM stick is the bad one..

http://imgur.com/inWK6.jpg

enigma# · November 8, 2012

It might be stick 3 (as in the last stick of RAM)... seeing as the error occurred at the end of it if my understanding of memtest is correct

Plaayer · November 8, 2012

Alright when I get home, I'll test just that one first.

Plaayer · November 9, 2012

Update! Here's the results of Memtest86+ on the DIMM that you wanted me to test.

http://i.imgur.com/ouKHA.jpg

I also did the 2nd DIMM of the kit. I let it go through 2 times and there were no errors. Unfortunately, I forgot to grab my camera to snap a pic of it.

-----------------------------------------------

Update x2! Here's the results of Memtest86+ on the Corsair 2x2GB kit.

http://i.imgur.com/B0B0g.jpg

The weird thing about this kit of memory is that it's detected as a DDR3-1333 kit by Memtest86 (and CPU-Z), when the XMP profile states that it is a DDR3-1600 kit. Another weird thing is that no errors popped up when testing the sticks individually. Maybe because my overnight run was @ 1.5v.... not sure though.

-----------------------------------------------

Update x3! I love updates... well, I'm just going to reformat entirely and start with a fresh install of Windows + essential drivers (video, audio, LAN, USB, etc.) to rule out anything software side... hopefully. And this is also partially because I possibly fucked up Windows to the point of no-return.

Edited November 9, 2012 by Plaayer

Plaayer · November 9, 2012

Well. I reformatted completely, and... it seems to be working. I guess it was software sided, and not hardware sided. Who woulda' thunk. If any problems arise, I'll probably update this thread.

Anyways, thanks Enigma for all your help.

Sign In

Welcome to The Forum

[fixed] PC Freezes + Locks up only when playing certain games

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Important Information