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

BSOD when idle.


  • Please log in to reply
19 replies to this topic

#1 ouat

ouat

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 20 May 2015 - 05:18 PM

Hi. For a couple of months now, when I leave my computer idle for around 20 minutes, it bsods and restarts. I managed to be at it one time and see the message "driver irql less or not equal" but wasn't able to catch the error code.

 

After that, I tried to update the drivers via windows updates, which completely disabled my wifi, my only way to get online. I had to system restore it back before the updates.

 

I have tested my ram and it has come up with no issues.

 

Acer Aspire 5733Z-4469 laptop

Windows 7 OEM
64 bit

 

The restarts and getting more frequent and I'd love it if someone could take a look for me. Thanks!

 

 

Attached File  perfmon.zip   148.23KB   0 downloads
Attached File  SysnativeFileCollectionApp.zip   1.5MB   1 downloads

 



BC AdBot (Login to Remove)

 


#2 ring 0

ring 0

  • BSOD Kernel Dump Expert
  • 89 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:07:46 AM

Posted 20 May 2015 - 05:23 PM

No dumps in your output.

 

If you check C:\Windows\Minidump, are there any files there?



#3 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 20 May 2015 - 05:25 PM

No dumps in your output.

 

If you check C:\Windows\Minidump, are there any files there?

 

It's an empty folder.



#4 ring 0

ring 0

  • BSOD Kernel Dump Expert
  • 89 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:07:46 AM

Posted 20 May 2015 - 05:28 PM

See if this stuff is set properly:

 

1. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

3. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.


Edited by ring 0, 20 May 2015 - 05:28 PM.


#5 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 20 May 2015 - 05:38 PM

See if this stuff is set properly:

 

1. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

3. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Thanks. Everything was good except the last one -- I started the Error Reporting service and set it to automatic as instructed.

 

Do I have to wait for another bsod in order to get any reports now?



#6 ring 0

ring 0

  • BSOD Kernel Dump Expert
  • 89 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:07:46 AM

Posted 20 May 2015 - 06:16 PM

 

Do I have to wait for another bsod in order to get any reports now?

 

Correct.



#7 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 20 May 2015 - 06:32 PM

 

 

Do I have to wait for another bsod in order to get any reports now?

 

Correct.

 

 

Okay, thanks for the help!



#8 ring 0

ring 0

  • BSOD Kernel Dump Expert
  • 89 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:07:46 AM

Posted 20 May 2015 - 06:59 PM

You're welcome.



#9 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 23 May 2015 - 02:28 PM

My computer has had a bsod twice and still won't produce a memory dump. I double checked the settings and they all still match the post. Is there any way around the memory dump?



#10 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:12:46 PM

Posted 23 May 2015 - 03:27 PM

No there isn't.

 

Start > Right click Computer > Properties > Advanced system settings (Left hand side) > Advance tab > Startup and Recovery section click Settings > Untick automatic restart.

When the BSOD appears take a picture then restart the PC.

 

Is there anything under C:\Windows\MEMORY.dmp ?



#11 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 23 May 2015 - 11:36 PM

No there isn't.

 

Start > Right click Computer > Properties > Advanced system settings (Left hand side) > Advance tab > Startup and Recovery section click Settings > Untick automatic restart.

When the BSOD appears take a picture then restart the PC.

 

Is there anything under C:\Windows\MEMORY.dmp ?

 

Thanks, have unchecked auto restart.

 

There's nothing in the minidump folder and memory.dmp doesn't exist.



#12 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 09 June 2015 - 06:26 PM

Attached File  perfmon.zip   130.91KB   0 downloadsAttached File  SysnativeFileCollectionApp.zip   1.6MB   2 downloads

 

My computer finally gave me information regarding the bsod and produced a memory dump. I have no clue how or why it chose now to do it as I haven't change my settings and they have been as instructed through several bsods. Here are the new files. This is the information that it gave me on startup:

 

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

Additional information about the problem:
  BCCode:    1000007e
  BCP1:    FFFFFFFFC0000005
  BCP2:    FFFFF880010815BE
  BCP3:    FFFFF8800334E948
  BCP4:    FFFFF8800334E1A0
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1



#13 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 12 June 2015 - 03:41 PM

Should I start a new thread instead?



#14 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:06:46 AM

Posted 14 June 2015 - 02:45 AM

Hi,

 

Try updating this driver: iaStor.sys

 

Here's a link from Acer's website: http://global-download.acer.com/GDFiles/Driver/AHCI/AHCI_Intel_9.6.2.1001_W7x86W7x64_A.zip?acerid=634406169365346948&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE%205733Z&OS=711&LC=en&BC=ACER&SC=PA_6#_ga=1.118568777.1931356611.1434268143

 

source: http://us.acer.com/ac/en/US/content/drivers -> Search "5733z"

 

__

Loading User Symbols
Loading unloaded module list
..........
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880010815be, fffff8800334e948, fffff8800334e1a0}

Probably caused by : iaStor.sys ( iaStor+725be )

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

0: kd> kd: Reading initial command '!analyze -v; !sysinfo cpuspeed;  !sysinfo SMBIOS; lmtsmn; q'
*******************************************************************************
*                                                                             *
*                        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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010815be, The address that the exception occurred at
Arg3: fffff8800334e948, Exception Record Address
Arg4: fffff8800334e1a0, 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: 
iaStor+725be
fffff880`010815be 8901            mov     dword ptr [rcx],eax

EXCEPTION_RECORD:  fffff8800334e948 -- (.exr 0xfffff8800334e948)
ExceptionAddress: fffff880010815be (iaStor+0x00000000000725be)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800334e1a0 -- (.cxr 0xfffff8800334e1a0;r)
rax=0000000000000001 rbx=fffffa8007b16210 rcx=1ffff8800356e101
rdx=0000000000000000 rsi=fffffa8009b0a130 rdi=fffffa8007b0fb00
rip=fffff880010815be rsp=fffff8800334eb80 rbp=0000000000000000
 r8=fffffa8007b16210  r9=0000000000000000 r10=0000000000000001
r11=fffffa8007b16210 r12=0000000000000001 r13=0000000000000000
r14=fffffa8007b12000 r15=fffff8800356e000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
iaStor+0x725be:
fffff880`010815be 8901            mov     dword ptr [rcx],eax ds:002b:1ffff880`0356e101=????????
Last set context:
rax=0000000000000001 rbx=fffffa8007b16210 rcx=1ffff8800356e101
rdx=0000000000000000 rsi=fffffa8009b0a130 rdi=fffffa8007b0fb00
rip=fffff880010815be rsp=fffff8800334eb80 rbp=0000000000000000
 r8=fffffa8007b16210  r9=0000000000000000 r10=0000000000000001
r11=fffffa8007b16210 r12=0000000000000001 r13=0000000000000000
r14=fffffa8007b12000 r15=fffff8800356e000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
iaStor+0x725be:
fffff880`010815be 8901            mov     dword ptr [rcx],eax ds:002b:1ffff880`0356e101=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100
GetUlongFromAddress: unable to read from fffff800030fe1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
iaStor+725be
fffff880`010815be 8901            mov     dword ptr [rcx],eax

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffffa8007b13000 to fffff880010815be

STACK_TEXT:  
fffff880`0334eb80 fffffa80`07b13000 : fffffa80`07b16210 fffffa80`09b0a130 fffffa80`07b0fb00 fffffa80`07b0fb01 : iaStor+0x725be
fffff880`0334eb88 fffffa80`07b16210 : fffffa80`09b0a130 fffffa80`07b0fb00 fffffa80`07b0fb01 fffff880`0108174f : 0xfffffa80`07b13000
fffff880`0334eb90 fffffa80`09b0a130 : fffffa80`07b0fb00 fffffa80`07b0fb01 fffff880`0108174f 1ffff880`0356e101 : 0xfffffa80`07b16210
fffff880`0334eb98 fffffa80`07b0fb00 : fffffa80`07b0fb01 fffff880`0108174f 1ffff880`0356e101 00000000`00000000 : 0xfffffa80`09b0a130
fffff880`0334eba0 fffffa80`07b0fb01 : fffff880`0108174f 1ffff880`0356e101 00000000`00000000 fffffa80`07b16538 : 0xfffffa80`07b0fb00
fffff880`0334eba8 fffff880`0108174f : 1ffff880`0356e101 00000000`00000000 fffffa80`07b16538 fffff880`01013302 : 0xfffffa80`07b0fb01
fffff880`0334ebb0 1ffff880`0356e101 : 00000000`00000000 fffffa80`07b16538 fffff880`01013302 00000000`00000000 : iaStor+0x7274f
fffff880`0334ebb8 00000000`00000000 : fffffa80`07b16538 fffff880`01013302 00000000`00000000 00000000`00000000 : 0x1ffff880`0356e101


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  iaStor+725be

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bc49f60

STACK_COMMAND:  .cxr 0xfffff8800334e1a0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_iaStor+725be

BUCKET_ID:  X64_0x7E_iaStor+725be

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_iastor+725be

FAILURE_ID_HASH:  {87674482-1e5c-a681-6bf5-697e63231772}

Followup: MachineOwner

Edited by thisisu, 14 June 2015 - 02:53 AM.


#15 ouat

ouat
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 18 June 2015 - 12:22 PM

 

Hi,

 

Try updating this driver: iaStor.sys

 

Here's a link from Acer's website: http://global-download.acer.com/GDFiles/Driver/AHCI/AHCI_Intel_9.6.2.1001_W7x86W7x64_A.zip?acerid=634406169365346948&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE%205733Z&OS=711&LC=en&BC=ACER&SC=PA_6#_ga=1.118568777.1931356611.1434268143

 

source: http://us.acer.com/ac/en/US/content/drivers -> Search "5733z"

 

__

Loading User Symbols
Loading unloaded module list
..........
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880010815be, fffff8800334e948, fffff8800334e1a0}

Probably caused by : iaStor.sys ( iaStor+725be )

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

0: kd> kd: Reading initial command '!analyze -v; !sysinfo cpuspeed;  !sysinfo SMBIOS; lmtsmn; q'
*******************************************************************************
*                                                                             *
*                        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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010815be, The address that the exception occurred at
Arg3: fffff8800334e948, Exception Record Address
Arg4: fffff8800334e1a0, 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: 
iaStor+725be
fffff880`010815be 8901            mov     dword ptr [rcx],eax

EXCEPTION_RECORD:  fffff8800334e948 -- (.exr 0xfffff8800334e948)
ExceptionAddress: fffff880010815be (iaStor+0x00000000000725be)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800334e1a0 -- (.cxr 0xfffff8800334e1a0;r)
rax=0000000000000001 rbx=fffffa8007b16210 rcx=1ffff8800356e101
rdx=0000000000000000 rsi=fffffa8009b0a130 rdi=fffffa8007b0fb00
rip=fffff880010815be rsp=fffff8800334eb80 rbp=0000000000000000
 r8=fffffa8007b16210  r9=0000000000000000 r10=0000000000000001
r11=fffffa8007b16210 r12=0000000000000001 r13=0000000000000000
r14=fffffa8007b12000 r15=fffff8800356e000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
iaStor+0x725be:
fffff880`010815be 8901            mov     dword ptr [rcx],eax ds:002b:1ffff880`0356e101=????????
Last set context:
rax=0000000000000001 rbx=fffffa8007b16210 rcx=1ffff8800356e101
rdx=0000000000000000 rsi=fffffa8009b0a130 rdi=fffffa8007b0fb00
rip=fffff880010815be rsp=fffff8800334eb80 rbp=0000000000000000
 r8=fffffa8007b16210  r9=0000000000000000 r10=0000000000000001
r11=fffffa8007b16210 r12=0000000000000001 r13=0000000000000000
r14=fffffa8007b12000 r15=fffff8800356e000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
iaStor+0x725be:
fffff880`010815be 8901            mov     dword ptr [rcx],eax ds:002b:1ffff880`0356e101=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100
GetUlongFromAddress: unable to read from fffff800030fe1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
iaStor+725be
fffff880`010815be 8901            mov     dword ptr [rcx],eax

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffffa8007b13000 to fffff880010815be

STACK_TEXT:  
fffff880`0334eb80 fffffa80`07b13000 : fffffa80`07b16210 fffffa80`09b0a130 fffffa80`07b0fb00 fffffa80`07b0fb01 : iaStor+0x725be
fffff880`0334eb88 fffffa80`07b16210 : fffffa80`09b0a130 fffffa80`07b0fb00 fffffa80`07b0fb01 fffff880`0108174f : 0xfffffa80`07b13000
fffff880`0334eb90 fffffa80`09b0a130 : fffffa80`07b0fb00 fffffa80`07b0fb01 fffff880`0108174f 1ffff880`0356e101 : 0xfffffa80`07b16210
fffff880`0334eb98 fffffa80`07b0fb00 : fffffa80`07b0fb01 fffff880`0108174f 1ffff880`0356e101 00000000`00000000 : 0xfffffa80`09b0a130
fffff880`0334eba0 fffffa80`07b0fb01 : fffff880`0108174f 1ffff880`0356e101 00000000`00000000 fffffa80`07b16538 : 0xfffffa80`07b0fb00
fffff880`0334eba8 fffff880`0108174f : 1ffff880`0356e101 00000000`00000000 fffffa80`07b16538 fffff880`01013302 : 0xfffffa80`07b0fb01
fffff880`0334ebb0 1ffff880`0356e101 : 00000000`00000000 fffffa80`07b16538 fffff880`01013302 00000000`00000000 : iaStor+0x7274f
fffff880`0334ebb8 00000000`00000000 : fffffa80`07b16538 fffff880`01013302 00000000`00000000 00000000`00000000 : 0x1ffff880`0356e101


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  iaStor+725be

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bc49f60

STACK_COMMAND:  .cxr 0xfffff8800334e1a0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_iaStor+725be

BUCKET_ID:  X64_0x7E_iaStor+725be

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_iastor+725be

FAILURE_ID_HASH:  {87674482-1e5c-a681-6bf5-697e63231772}

Followup: MachineOwner

Hi, thank you for the reply!

I downloaded this and tried running the setup.exe that was included in the zip, however it won't install.

05612-d36a2dd3-4968-4542-9411-6cfe45aa98

I don't know much about installing drivers so I'm not sure if that's the proper way to do it or not, or the only way.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users