Constant Crashing. Need Help!

Toggle sidebar Toggle sidebar
Z

zachary21

Commendable
Jan 30, 2017
6
0
1,510
So as of recently I've been having problems with my PC crashing. It would start occasionally when playing games but is now happening multiple times a day. Generally the game will crash first and after I re-launch it, the pc will crash completely and goes blue screen. I have a corsair water cooler, This was also happening while using sony vegas, after a couple minutes of editing the computer would shut down and restart. I have corsair fans running on max. Sorry if this is in the wrong place but I don't know what to do or how to fix this.

Graphics card is gtx -970
Cpu is i7-3770
 
Sort by date Sort by votes
Z

zachary21

Commendable
Jan 30, 2017
6
0
1,510
MERGED QUESTION
Question from zachary21 : "Constant Crashing (Blue Screen)"

So as of a week ago my pc is crashing every time I do something intensive as in running a game or using Sony Vegas. This is a newer problem and I have no idea how to fix it but I have copied some of the crash files hoping somebody knows what they mean.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA801B9E7028
BCP3: 00000000BE000000
BCP4: 0000000000800400
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020217-52556-01.dmp
C:\Users\AppData\Local\Temp\WER-52650-0.sysdata.xml

(First Dump File is this one)

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880033d7180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff880`15fd47b8 fffff800`0332ab49 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`033d7180 : nt!KeBugCheckEx
fffff880`15fd47c0 fffff800`032daf17 : 00000000`00000000 fffff800`00000003 00000000`00002710 fffff880`0f4d08cd : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`15fd4850 fffff800`03222895 : fffff800`03248460 fffff880`15fd4a00 fffff800`03248460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`15fd4950 fffff800`032cd953 : 00000000`13d312ec fffffa80`1bedee58 fffffa80`18eaf540 fffffa80`1bedee58 : hal!HalpHpetClockInterrupt+0x8d
fffff880`15fd4980 fffff800`032b8c80 : fffff880`00000000 00000000`00000000 00000000`00000000 fffff880`057bce23 : nt!KiInterruptDispatchNoLock+0x163
fffff880`15fd4b10 fffff800`032da889 : 00000000`00000000 fffff880`033dc040 00000000`00000000 fffff880`05455000 : nt!KxWaitForSpinLockAndAcquire+0x20
fffff880`15fd4b40 fffff880`054589e9 : fffffa80`20f49d80 fffffa80`00000000 fffffa80`20759010 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x89
fffff880`15fd4b90 fffffa80`20f49d80 : fffffa80`00000000 fffffa80`20759010 00000000`00000000 fffff880`03502180 : MZ0380_X64+0x39e9
fffff880`15fd4b98 fffffa80`00000000 : fffffa80`20759010 00000000`00000000 fffff880`03502180 74754d74`00002000 : 0xfffffa80`20f49d80
fffff880`15fd4ba0 fffffa80`20759010 : 00000000`00000000 fffff880`03502180 74754d74`00002000 00000000`00000b81 : 0xfffffa80`00000000
fffff880`15fd4ba8 00000000`00000000 : fffff880`03502180 74754d74`00002000 00000000`00000b81 3d582c72`65767200 : 0xfffffa80`20759010


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner


(Second one is this)

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa801b93f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff800`00ba6a98 fffff800`0380ea3b : 00000000`00000124 00000000`00000000 fffffa80`1b93f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba6aa0 fffff800`0339fbaf : 00000000`00000001 fffffa80`1b942a60 00000000`00000000 fffffa80`1b942ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba6ae0 fffff800`0380e700 : 00000000`00000728 fffffa80`1b942a60 fffff800`00ba6e70 fffff800`00ba6e00 : nt!WheaReportHwError+0x26f
fffff800`00ba6b40 fffff800`0380e052 : fffffa80`1b942a60 fffff800`00ba6e70 fffffa80`1b942a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba6c90 fffff800`0380df0d : 00000000`00000008 00000000`00000001 fffff800`00ba6ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba6cd0 fffff800`03801e88 : fffff800`03404e80 fffff800`03412cc0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba6d00 fffff800`03284cec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba6d30 fffff800`03284b53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba6e70 fffff800`0327e114 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x64


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner


(Third)

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, 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: fffff80003211005, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bd100
GetUlongFromAddress: unable to read from fffff800034bd1c8
0000000000000000 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiSelectNextThread (nt+0x5)+0
fffff800`03211005 0000 add byte ptr [rax],al

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880045f93f0 -- (.trap 0xfffff880045f93f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880045f9cc0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003211005 rsp=fffff880045f9588 rbp=0000000000000005
r8=fffff880045f9500 r9=00000000003431b3 r10=00000000003431b3
r11=fffffa801f19ea68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiSelectNextThread (nt+0x5):
fffff800`03211005 0000 add byte ptr [rax],al ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032809a9 to fffff80003281400

STACK_TEXT:
fffff880`045f92a8 fffff800`032809a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`045f92b0 fffff800`0327f620 : 00000000`00000000 fffffa80`1ed9c250 fffffa80`1ed37802 fffff880`03490180 : nt!KiBugCheckDispatch+0x69
fffff880`045f93f0 fffff800`03211005 : 00000000`00000028 fffffa80`1f19ea18 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`045f9588 00000000`00000028 : fffffa80`1f19ea18 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSelectNextThread (nt+0x5)
fffff880`045f9590 fffffa80`1f19ea18 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x28
fffff880`045f9598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`1f19ea18


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSelectNextThread (nt+0x5)+0
fffff800`03211005 0000 add byte ptr [rax],al

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiSelectNextThread (nt+0x5)+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 57fcfdf3

FAILURE_BUCKET_ID: X64_0xA_nt!KiSelectNextThread__PERF__(nt+0x5)+0

BUCKET_ID: X64_0xA_nt!KiSelectNextThread__PERF__(nt+0x5)+0

Followup: MachineOwner

Any Help would be greatly appreciated as I don't have the slightest clue about computers and how to go about fixing this.
 
Upvote 0 Downvote
Z

zachary21

Commendable
Jan 30, 2017
6
0
1,510
MERGED QUESTION
Question from zachary21 : "Blue Screen Crash"

So as of recently my computer constantly crashes. This happens mostly when playing games. I'm not sure what the problem is but I have copied some of the crash notes hoping somebody knows what they mean. These crashes are happening multiple times a day after only a couple minutes of playing any game.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA801B9E7028
BCP3: 00000000BE000000
BCP4: 0000000000800400
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020217-52556-01.dmp
C:\Users\AppData\Local\Temp\WER-52650-0.sysdata.xml

(First Dump File is this one)

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880033d7180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff880`15fd47b8 fffff800`0332ab49 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`033d7180 : nt!KeBugCheckEx
fffff880`15fd47c0 fffff800`032daf17 : 00000000`00000000 fffff800`00000003 00000000`00002710 fffff880`0f4d08cd : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`15fd4850 fffff800`03222895 : fffff800`03248460 fffff880`15fd4a00 fffff800`03248460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`15fd4950 fffff800`032cd953 : 00000000`13d312ec fffffa80`1bedee58 fffffa80`18eaf540 fffffa80`1bedee58 : hal!HalpHpetClockInterrupt+0x8d
fffff880`15fd4980 fffff800`032b8c80 : fffff880`00000000 00000000`00000000 00000000`00000000 fffff880`057bce23 : nt!KiInterruptDispatchNoLock+0x163
fffff880`15fd4b10 fffff800`032da889 : 00000000`00000000 fffff880`033dc040 00000000`00000000 fffff880`05455000 : nt!KxWaitForSpinLockAndAcquire+0x20
fffff880`15fd4b40 fffff880`054589e9 : fffffa80`20f49d80 fffffa80`00000000 fffffa80`20759010 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x89
fffff880`15fd4b90 fffffa80`20f49d80 : fffffa80`00000000 fffffa80`20759010 00000000`00000000 fffff880`03502180 : MZ0380_X64+0x39e9
fffff880`15fd4b98 fffffa80`00000000 : fffffa80`20759010 00000000`00000000 fffff880`03502180 74754d74`00002000 : 0xfffffa80`20f49d80
fffff880`15fd4ba0 fffffa80`20759010 : 00000000`00000000 fffff880`03502180 74754d74`00002000 00000000`00000b81 : 0xfffffa80`00000000
fffff880`15fd4ba8 00000000`00000000 : fffff880`03502180 74754d74`00002000 00000000`00000b81 3d582c72`65767200 : 0xfffffa80`20759010


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner


(Second one is this)

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa801b93f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff800`00ba6a98 fffff800`0380ea3b : 00000000`00000124 00000000`00000000 fffffa80`1b93f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba6aa0 fffff800`0339fbaf : 00000000`00000001 fffffa80`1b942a60 00000000`00000000 fffffa80`1b942ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba6ae0 fffff800`0380e700 : 00000000`00000728 fffffa80`1b942a60 fffff800`00ba6e70 fffff800`00ba6e00 : nt!WheaReportHwError+0x26f
fffff800`00ba6b40 fffff800`0380e052 : fffffa80`1b942a60 fffff800`00ba6e70 fffffa80`1b942a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba6c90 fffff800`0380df0d : 00000000`00000008 00000000`00000001 fffff800`00ba6ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba6cd0 fffff800`03801e88 : fffff800`03404e80 fffff800`03412cc0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba6d00 fffff800`03284cec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba6d30 fffff800`03284b53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba6e70 fffff800`0327e114 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x64


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner


(Third)

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, 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: fffff80003211005, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bd100
GetUlongFromAddress: unable to read from fffff800034bd1c8
0000000000000000 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiSelectNextThread (nt+0x5)+0
fffff800`03211005 0000 add byte ptr [rax],al

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880045f93f0 -- (.trap 0xfffff880045f93f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880045f9cc0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003211005 rsp=fffff880045f9588 rbp=0000000000000005
r8=fffff880045f9500 r9=00000000003431b3 r10=00000000003431b3
r11=fffffa801f19ea68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiSelectNextThread (nt+0x5):
fffff800`03211005 0000 add byte ptr [rax],al ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032809a9 to fffff80003281400

STACK_TEXT:
fffff880`045f92a8 fffff800`032809a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`045f92b0 fffff800`0327f620 : 00000000`00000000 fffffa80`1ed9c250 fffffa80`1ed37802 fffff880`03490180 : nt!KiBugCheckDispatch+0x69
fffff880`045f93f0 fffff800`03211005 : 00000000`00000028 fffffa80`1f19ea18 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`045f9588 00000000`00000028 : fffffa80`1f19ea18 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSelectNextThread (nt+0x5)
fffff880`045f9590 fffffa80`1f19ea18 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x28
fffff880`045f9598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`1f19ea18


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSelectNextThread (nt+0x5)+0
fffff800`03211005 0000 add byte ptr [rax],al

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiSelectNextThread (nt+0x5)+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 57fcfdf3

FAILURE_BUCKET_ID: X64_0xA_nt!KiSelectNextThread__PERF__(nt+0x5)+0

BUCKET_ID: X64_0xA_nt!KiSelectNextThread__PERF__(nt+0x5)+0

Followup: MachineOwner




Any Help would be greatly appreciated as I don't have the slightest clue about computers and how to go about fixing this.
 
Upvote 0 Downvote
Z

zachary21

Commendable
Jan 30, 2017
6
0
1,510


What? Maybe you misunderstood but I have no clue about computers or how the hell this website works. I posted something, didn't get the correct solution, made another post with more detail as my first one lacked that.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom