Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Crash Dump Debug File!, luafv.sys?


  • Please log in to reply
2 replies to this topic

#1 Domobaby

Domobaby

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:05:07 AM

Posted 16 December 2008 - 03:55 PM

Hi all first time here,

My computer has started crash dumping literally within every 5 minutes. Admittidly I have been downloading addons this afternoon. Can someone advise me with what is causing this please.


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mark\Desktop\Mini121608-10.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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82206000 PsLoadedModuleList = 0x8231dc70
Debug session time: Tue Dec 16 20:01:22.474 2008 (GMT+0)
System Uptime: 0 days 0:05:46.346
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8224b6e3, 88d6fbdc, 88d6f8d8}

Probably caused by : luafv.sys ( luafv!LuafvDeleteElementTable+24 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8224b6e3, The address that the exception occurred at
Arg3: 88d6fbdc, Exception Record Address
Arg4: 88d6f8d8, Context Record Address

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


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

FAULTING_IP:
nt!RtlDeleteNoSplay+46
8224b6e3 3931 cmp dword ptr [ecx],esi

EXCEPTION_RECORD: 88d6fbdc -- (.exr 0xffffffff88d6fbdc)
ExceptionAddress: 8224b6e3 (nt!RtlDeleteNoSplay+0x00000046)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000004
Attempt to read from address 00000004

CONTEXT: 88d6f8d8 -- (.cxr 0xffffffff88d6f8d8)
eax=00000000 ebx=00000000 ecx=00000004 edx=9c7e53c0 esi=9c7e5f60 edi=96ea9a08
eip=8224b6e3 esp=88d6fca4 ebp=88d6fcb0 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
nt!RtlDeleteNoSplay+0x46:
8224b6e3 3931 cmp dword ptr [ecx],esi ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 10

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000004

READ_ADDRESS: GetPointerFromAddress: unable to read from 8233d868
Unable to read MiSystemVaType memory at 8231d420
00000004

FOLLOWUP_IP:
luafv!LuafvDeleteElementTable+24
80c14b6a ff4e08 dec dword ptr [esi+8]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 80c14b6a to 8224b6e3

STACK_TEXT:
88d6fcb0 80c14b6a 9c7e5f60 96ea9a08 9c7e5fd8 nt!RtlDeleteNoSplay+0x46
88d6fcc8 80c14b14 96ea9a08 9c7e5f60 96feb590 luafv!LuafvDeleteElementTable+0x24
88d6fce4 80c13f6a 96ea9a08 00000000 82236e90 luafv!RemoveTableNode+0x7a
88d6fd24 80c0c347 00000000 8230813c 84480020 luafv!LuafvScavengeFileTable+0x1a9
88d6fd44 8223e445 00000000 00000000 84480020 luafv!ScavengerThread+0x3c
88d6fd7c 823dbb18 00000000 ef1dff8c 00000000 nt!ExpWorkerThread+0xfd
88d6fdc0 82234a2e 8223e348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: luafv!LuafvDeleteElementTable+24

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: luafv

IMAGE_NAME: luafv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918afb

STACK_COMMAND: .cxr 0xffffffff88d6f8d8 ; kb

FAILURE_BUCKET_ID: 0x7E_luafv!LuafvDeleteElementTable+24

BUCKET_ID: 0x7E_luafv!LuafvDeleteElementTable+24

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8224b6e3, The address that the exception occurred at
Arg3: 88d6fbdc, Exception Record Address
Arg4: 88d6f8d8, Context Record Address

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


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

FAULTING_IP:
nt!RtlDeleteNoSplay+46
8224b6e3 3931 cmp dword ptr [ecx],esi

EXCEPTION_RECORD: 88d6fbdc -- (.exr 0xffffffff88d6fbdc)
ExceptionAddress: 8224b6e3 (nt!RtlDeleteNoSplay+0x00000046)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000004
Attempt to read from address 00000004

CONTEXT: 88d6f8d8 -- (.cxr 0xffffffff88d6f8d8)
eax=00000000 ebx=00000000 ecx=00000004 edx=9c7e53c0 esi=9c7e5f60 edi=96ea9a08
eip=8224b6e3 esp=88d6fca4 ebp=88d6fcb0 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
nt!RtlDeleteNoSplay+0x46:
8224b6e3 3931 cmp dword ptr [ecx],esi ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 10

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000004

READ_ADDRESS: GetPointerFromAddress: unable to read from 8233d868
Unable to read MiSystemVaType memory at 8231d420
00000004

FOLLOWUP_IP:
luafv!LuafvDeleteElementTable+24
80c14b6a ff4e08 dec dword ptr [esi+8]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 80c14b6a to 8224b6e3

STACK_TEXT:
88d6fcb0 80c14b6a 9c7e5f60 96ea9a08 9c7e5fd8 nt!RtlDeleteNoSplay+0x46
88d6fcc8 80c14b14 96ea9a08 9c7e5f60 96feb590 luafv!LuafvDeleteElementTable+0x24
88d6fce4 80c13f6a 96ea9a08 00000000 82236e90 luafv!RemoveTableNode+0x7a
88d6fd24 80c0c347 00000000 8230813c 84480020 luafv!LuafvScavengeFileTable+0x1a9
88d6fd44 8223e445 00000000 00000000 84480020 luafv!ScavengerThread+0x3c
88d6fd7c 823dbb18 00000000 ef1dff8c 00000000 nt!ExpWorkerThread+0xfd
88d6fdc0 82234a2e 8223e348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: luafv!LuafvDeleteElementTable+24

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: luafv

IMAGE_NAME: luafv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918afb

STACK_COMMAND: .cxr 0xffffffff88d6f8d8 ; kb

FAILURE_BUCKET_ID: 0x7E_luafv!LuafvDeleteElementTable+24

BUCKET_ID: 0x7E_luafv!LuafvDeleteElementTable+24

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8224b6e3, The address that the exception occurred at
Arg3: 88d6fbdc, Exception Record Address
Arg4: 88d6f8d8, Context Record Address

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


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

FAULTING_IP:
nt!RtlDeleteNoSplay+46
8224b6e3 3931 cmp dword ptr [ecx],esi

EXCEPTION_RECORD: 88d6fbdc -- (.exr 0xffffffff88d6fbdc)
ExceptionAddress: 8224b6e3 (nt!RtlDeleteNoSplay+0x00000046)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000004
Attempt to read from address 00000004

CONTEXT: 88d6f8d8 -- (.cxr 0xffffffff88d6f8d8)
eax=00000000 ebx=00000000 ecx=00000004 edx=9c7e53c0 esi=9c7e5f60 edi=96ea9a08
eip=8224b6e3 esp=88d6fca4 ebp=88d6fcb0 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
nt!RtlDeleteNoSplay+0x46:
8224b6e3 3931 cmp dword ptr [ecx],esi ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 10

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000004

READ_ADDRESS: GetPointerFromAddress: unable to read from 8233d868
Unable to read MiSystemVaType memory at 8231d420
00000004

FOLLOWUP_IP:
luafv!LuafvDeleteElementTable+24
80c14b6a ff4e08 dec dword ptr [esi+8]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 80c14b6a to 8224b6e3

STACK_TEXT:
88d6fcb0 80c14b6a 9c7e5f60 96ea9a08 9c7e5fd8 nt!RtlDeleteNoSplay+0x46
88d6fcc8 80c14b14 96ea9a08 9c7e5f60 96feb590 luafv!LuafvDeleteElementTable+0x24
88d6fce4 80c13f6a 96ea9a08 00000000 82236e90 luafv!RemoveTableNode+0x7a
88d6fd24 80c0c347 00000000 8230813c 84480020 luafv!LuafvScavengeFileTable+0x1a9
88d6fd44 8223e445 00000000 00000000 84480020 luafv!ScavengerThread+0x3c
88d6fd7c 823dbb18 00000000 ef1dff8c 00000000 nt!ExpWorkerThread+0xfd
88d6fdc0 82234a2e 8223e348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: luafv!LuafvDeleteElementTable+24

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: luafv

IMAGE_NAME: luafv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918afb

STACK_COMMAND: .cxr 0xffffffff88d6f8d8 ; kb

FAILURE_BUCKET_ID: 0x7E_luafv!LuafvDeleteElementTable+24

BUCKET_ID: 0x7E_luafv!LuafvDeleteElementTable+24

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

BC AdBot (Login to Remove)

 


#2 Domobaby

Domobaby
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:05:07 AM

Posted 16 December 2008 - 04:01 PM

Just looked at another dump and the info seems different. Heres one from before


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mark\Desktop\Mini121608-09.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8223e000 PsLoadedModuleList = 0x82355c70
Debug session time: Tue Dec 16 19:47:18.602 2008 (GMT+0)
System Uptime: 0 days 0:00:35.445
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 82446890, 88d57a30, 88d5772c}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamQueryWorker+76 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82446890, The address that the exception occurred at
Arg3: 88d57a30, Exception Record Address
Arg4: 88d5772c, Context Record Address

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


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

FAULTING_IP:
nt!RtlUpcaseUnicodeString+71
82446890 0fb70c51 movzx ecx,word ptr [ecx+edx*2]

EXCEPTION_RECORD: 88d57a30 -- (.exr 0xffffffff88d57a30)
ExceptionAddress: 82446890 (nt!RtlUpcaseUnicodeString+0x00000071)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0000000a
Attempt to read from address 0000000a

CONTEXT: 88d5772c -- (.cxr 0xffffffff88d5772c)
eax=88e2064c ebx=97de44f0 ecx=00000000 edx=00000005 esi=8808b210 edi=88d57b50
eip=82446890 esp=88d57af8 ebp=88d57b2c iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!RtlUpcaseUnicodeString+0x71:
82446890 0fb70c51 movzx ecx,word ptr [ecx+edx*2] ds:0023:0000000a=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 9

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 0000000a

READ_ADDRESS: GetPointerFromAddress: unable to read from 82375868
Unable to read MiSystemVaType memory at 82355420
0000000a

FOLLOWUP_IP:
fileinfo!FIStreamQueryWorker+76
82c4138a 85c0 test eax,eax

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 8244f1e0 to 82446890

STACK_TEXT:
88d57b2c 8244f1e0 88d57b50 8808b210 00000001 nt!RtlUpcaseUnicodeString+0x71
88d57bac 82c22669 87529384 8750aa80 82c18e00 nt!FsRtlIsNameInExpression+0x29
88d57be0 82c26601 864be3e0 8808b1e0 87529384 fltmgr!FltpQueryInformationFile+0xc3
88d57c14 82c276ec 864be3e0 8750aa80 88d57c40 fltmgr!FltpGetFileName+0x63
88d57c24 82c24a04 8750aa80 00000000 8750aa80 fltmgr!FltpGetOpenedFileName+0x18
88d57c40 82c2776c 8750aa80 00000000 8750aa80 fltmgr!FltpCallOpenedFileNameHandler+0x8a
88d57c5c 82c27f07 8750aa80 00000000 87529384 fltmgr!FltpGetNormalizedFileNameWorker+0x16
88d57c74 82c251a1 8750aa80 00000000 8750aa80 fltmgr!FltpGetNormalizedFileName+0x19
88d57c8c 82c101df 8750aa80 8808b1e0 00000000 fltmgr!FltpCreateFileNameInformation+0x81
88d57cbc 82c25713 88093c94 00000001 00000000 fltmgr!FltpGetFileNameInformation+0x31d
88d57cd0 82c4138a 8808b1e0 86853538 8750aa80 fltmgr!FltGetFileNameInformationUnsafe+0x59
88d57d10 82c2bba2 86c260b8 86853538 0000059d fileinfo!FIStreamQueryWorker+0x76
88d57d44 82276445 00000000 00000000 84487828 fltmgr!FltpProcessGenericWorkItem+0x38
88d57d7c 82413b18 86c260b8 04370deb 00000000 nt!ExpWorkerThread+0xfd
88d57dc0 8226ca2e 82276348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: b

SYMBOL_NAME: fileinfo!FIStreamQueryWorker+76

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME: fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918be3

STACK_COMMAND: .cxr 0xffffffff88d5772c ; kb

FAILURE_BUCKET_ID: 0x7E_fileinfo!FIStreamQueryWorker+76

BUCKET_ID: 0x7E_fileinfo!FIStreamQueryWorker+76

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

#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:07 AM

Posted 16 December 2008 - 04:18 PM

These are Windows system files that are trying to access memory that doesn't exist (the address is incorrect).

Most times this is because another process is passing information to the Windows files in an incorrect manner (although it can be because Windows is corrupted).

I'd suggest 2 things:
- uninstalling anything that you've installed this afternoon
- an independent (online) virus scan to see if you're infected: http://www.bleepingcomputer.com/blogs/usas...?showentry=1252
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users