The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Corsair Utility Engine (CUE) 1.x and 2.x

Reply
 
Thread Tools Search this Thread Rate Thread Display Modes
  #31  
Old 10-15-2016, 03:07 AM
xobs xobs is offline
Registered User
 
Join Date: Oct 2016
Posts: 1
POST ID # = 875433
xobs Reputation: 10
Default

Hi guys,

It's definitely a bug in 2.5.66. As with others, I experienced a system crash during the install of the software, upgrading from 2.4.66. My install has never worked well, and in fact the media keys and scripting engine are currently broken. Auto-update in CUE has never worked. But still, manually installing 2.5.66 causes my system to go into what others have called a "boot loop", where the only recourse is to do a System Restore.

It is clearly a bug somewhere in the VHid Driver. The driver doesn't have symbols, so windbg shows the error was in "AV_CorsairVHidDriver!unknown_function", specifically "CorsairVHidDriver+173f".

Some interesting debug information for your enjoyment:

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

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: 0000000000060001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800eba4726a, address which referenced memory

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10.0.14393.321 (rs1_release_inmarket.161004-2338)

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0502

BIOS_DATE:  08/31/2015

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X99-M WS

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

BUGCHECK_P1: 60001

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff800eba4726a

READ_ADDRESS:  0000000000060001 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+34a
fffff800`eba4726a 483901          cmp     qword ptr [rcx],rax

CPU_COUNT: 8

CPU_MHZ: daa

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

CPU_MICROCODE: 6,3f,2,0 (F,M,S,R)  SIG: 36'00000000 (cache) 36'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  CUBOID

ANALYSIS_SESSION_TIME:  10-15-2016 15:00:12.0494

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

TRAP_FRAME:  ffffce01642887f0 -- (.trap 0xffffce01642887f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa30d35a45678 rbx=0000000000000000 rcx=0000000000060001
rdx=ffffa30d35bf8940 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800eba4726a rsp=ffffce0164288980 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff78000000008
r11=fffff800044816b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x34a:
fffff800`eba4726a 483901          cmp     qword ptr [rcx],rax ds:00000000`00060001=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800ebb65429 to fffff800ebb5a2c0

STACK_TEXT:  
ffffce01`642886a8 fffff800`ebb65429 : 00000000`0000000a 00000000`00060001 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffce01`642886b0 fffff800`ebb63a07 : 00000000`00000000 ffffa30d`334c4040 fffff800`ebcff880 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffce01`642887f0 fffff800`eba4726a : 00000000`00000000 ffffa30d`334c4040 00000000`00000098 ffff8839`b1255db4 : nt!KiPageFault+0x247
ffffce01`64288980 fffff800`eba1a081 : ffffa30d`35a45670 ffffa30d`00000022 00000000`00000000 ffffa30d`00000000 : nt!KeWaitForSingleObject+0x34a
ffffce01`64288a30 fffff800`eba3cd78 : 00000000`00000000 ffffa30d`35a455d0 ffffa30d`35bf8b20 00000000`00000000 : nt!ExpAcquireFastMutexContended+0x79
ffffce01`64288a70 fffff800`0448173f : ffffa30d`35a455d0 00000000`00000000 00000000`00000000 ffffa30d`35c33d00 : nt!ExAcquireFastMutex+0x138
ffffce01`64288ab0 fffff800`044826f7 : ffffa30d`35ac4370 ffffa30d`35c33e40 00000000`00000000 ffffa30d`35c33d90 : CorsairVHidDriver+0x173f
ffffce01`64288b60 fffff800`ebae2405 : ffffce01`633c0180 fffff800`ebb5f6af 00000000`02017210 ffffa30d`35bf8800 : CorsairVHidDriver+0x26f7
ffffce01`64288c10 fffff800`ebb5f786 : ffffce01`633c0180 ffffa30d`35bf8800 fffff800`ebae23c4 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffce01`64288c60 00000000`00000000 : ffffce01`64289000 ffffce01`64283000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  548fc1aa05548fa28fc24a06229b359e4fa83d6d

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5d2e934dfe7cba9a58b0207375c9dcca65c1246d

THREAD_SHA1_HASH_MOD:  ddeaa141a6874ca0a5438cdb2569030372e54419

FOLLOWUP_IP: 
CorsairVHidDriver+173f
fffff800`0448173f 488b8424b0000000 mov     rax,qword ptr [rsp+0B0h]

FAULT_INSTR_CODE:  24848b48

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  CorsairVHidDriver+173f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CorsairVHidDriver

IMAGE_NAME:  CorsairVHidDriver.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57d152f2

BUCKET_ID_FUNC_OFFSET:  173f

FAILURE_BUCKET_ID:  AV_CorsairVHidDriver!unknown_function

BUCKET_ID:  AV_CorsairVHidDriver!unknown_function

PRIMARY_PROBLEM_CLASS:  AV_CorsairVHidDriver!unknown_function

TARGET_TIME:  2016-10-15T06:15:27.000Z

OSBUILD:  14393

OSSERVICEPACK:  321

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-10-05 17:17:53

BUILDDATESTAMP_STR:  161004-2338

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.321

ANALYSIS_SESSION_ELAPSED_TIME: 1bbb3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_corsairvhiddriver!unknown_function

FAILURE_ID_HASH:  {bf4e5acc-2399-6d8c-8866-e576655a9b96}

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

0: kd> k
 # Child-SP          RetAddr           Call Site
00 ffffce01`642886a8 fffff800`ebb65429 nt!KeBugCheckEx
01 ffffce01`642886b0 fffff800`ebb63a07 nt!KiBugCheckDispatch+0x69
02 ffffce01`642887f0 fffff800`eba4726a nt!KiPageFault+0x247
03 ffffce01`64288980 fffff800`eba1a081 nt!KeWaitForSingleObject+0x34a
04 ffffce01`64288a30 fffff800`eba3cd78 nt!ExpAcquireFastMutexContended+0x79
05 ffffce01`64288a70 fffff800`0448173f nt!ExAcquireFastMutex+0x138
06 ffffce01`64288ab0 fffff800`044826f7 CorsairVHidDriver+0x173f
07 ffffce01`64288b60 fffff800`ebae2405 CorsairVHidDriver+0x26f7
08 ffffce01`64288c10 fffff800`ebb5f786 nt!PspSystemThreadStartup+0x41
09 ffffce01`64288c60 00000000`00000000 nt!KiStartSystemThread+0x16
Reply With Quote


  #32  
Old 10-15-2016, 08:45 AM
HajuZenar HajuZenar is offline
Registered User
HajuZenar's PC Specs
 
Join Date: Oct 2016
Location: Austria
Posts: 3
POST ID # = 875455
HajuZenar Reputation: 10
Default

full dxdiag list in the attachment
Attached Files
File Type: txt DxDiag.txt (73.8 KB, 69 views)
Reply With Quote


  #33  
Old 10-15-2016, 03:06 PM
BaconTits BaconTits is offline
Registered User
 
Join Date: May 2016
Posts: 1
POST ID # = 875506
BaconTits Reputation: 10
Default

I'd just like to chime in on my experience too.

I have Windows 10, and I also have been using Cue2 since the beta was put on r/pcmasterrace. Today when I logged into my computer, I noticed that there was an update to the CUE software, but I also noticed that CUE was unresponsive and kept giving me an error when I tried to download the update through the client (I can't remember what exactly the error was, sorry). Instead, I downloaded the updated CUE through the website. After about 90% of the way installing, my computer blue screened and gave me the error "IRQL_NOT_LESS_OR_EQUAL". It happened about 4 times in a row before I did a windows restore. I have the RGB Strafe and the VOID USB headset.
Reply With Quote


  #34  
Old 10-15-2016, 09:55 PM
Co6alt Co6alt is offline
Registered User
 
Join Date: Oct 2016
Posts: 1
POST ID # = 875559
Co6alt Reputation: 10
Default Same bootlooping.

Just checking in to say that I'm having the same issues, was on Cue 2.3.xx, automatic updating from in the software didn't work, went to the website and downloaded it. Got to installing drivers --whole computer froze up and Spotify started skipping through about 30 songs before BSOD boot looping. unable to boot in safe mode at all.

I have a HP H9-1355
http://h20564.www2.hp.com/hpsc/doc/p...r_na-c03534739

Running Windows 10 Anniversary update running off an Samsung evo 750 SSD.

The Corsair product I'm using is the Strafe Silent. I was using a mouse through the bypass at the time.

Computer won't even successfully refresh Win 10-- any advise on getting it up and running again?

VVVVVVVV THANKS SO MUCH MAC_COSMO VVVVVVVV was able to get it up and running with this. uninstalled and cleaned the registry of the current CUE installation and installed 2.5 without a problem.

EDIT: I have now tried restoring, booting from windows 10 iso and restoring and nothing is working. I don't have any backups of this windows install because it is fairly new, but I still have over 10 hours into setting a bunch of stuff up. It's pretty upsetting that a little keyboard software has done this.

Last edited by Co6alt; 10-18-2016 at 06:45 PM. Reason: more info
Reply With Quote


  #35  
Old 10-16-2016, 10:19 PM
mac_cosmo mac_cosmo is offline
Fanatic
mac_cosmo's PC Specs
 
Join Date: Jun 2016
Location: Munich, Germany
Posts: 11
POST ID # = 875730
mac_cosmo Reputation: 10
Default

When you are stuck in a boot loop, there's help.

This is what i did -- not sure if all steps are necessary and i'm writing this down from memory.
First, boot your computer into the boot options menu.
From there select "command line" - a command prompt with "X:\>" will appear.

Type the following [and btw. don't write the dash in front of each command. press enter after each line]:
- D:
- cd windows
- cd system32
- cd driverstore
- cd filerepository
- dir *cor*

now look for directories that look like corsair drivers
- rmdir cor[PRESS TAB TO AUTOCOMPLETE NAME] /s
do this repeatedly until there are no corsair directories left. in my case there were two directories. then type:

- cd ..
- cd ..
- cd drivers

you are now in \Windows\System32\drivers

- dir *corsair*

there should be two corsair drivers. go and delete them.

- del cors[PRESS TAB TO AUTOCOMPLETE]
and again:
- del cors[PRESS TAB TO AUTOCOMPLETE]

close the command prompt window. shut down your computer from the menu. boot your computer and cross your fingers!

good luck!

(and don't try two install the drivers again. i learned it the hard way..)

Last edited by mac_cosmo; 10-16-2016 at 10:27 PM.
Reply With Quote


  #36  
Old 10-17-2016, 12:03 PM
Corsair Calico Jack's Avatar
Corsair Calico Jack Corsair Calico Jack is offline
Registered User
 
Join Date: Oct 2016
Posts: 138
POST ID # = 875829
Corsair Calico Jack Reputation: 10
Default

Thank you all who have sent information. It has been forwarded.
Reply With Quote


  #37  
Old 10-17-2016, 03:26 PM
Rimischonie Rimischonie is offline
Registered User
 
Join Date: Feb 2016
Posts: 2
POST ID # = 875851
Rimischonie Reputation: 10
Default

If you stuck in the boot loop. Unplug the hardware (for me it was the K70) and boot it up again. No Bluescreen.

Removed the new version and installed the old version.
Reply With Quote


  #38  
Old 10-17-2016, 03:45 PM
gyroknight gyroknight is offline
Registered User
gyroknight's PC Specs
 
Join Date: Oct 2014
Posts: 55
POST ID # = 875855
gyroknight Reputation: 10
Default

Experiencing the same issue. Thanks to mac_cosmo for the driver location, was the only way to solve the boot loop since I didn't have system protection enabled or a backup. Tried unplugging my hardware (K95 RGB) as Rimischonie suggested, was still stuck in loop. Once back up, I uninstalled the previous version and installed 2.5.66 after a restart. That seemed to work, however, CUE was complaining about the macro execution driver being broken and I had to perform a repair installation.

Last edited by gyroknight; 10-17-2016 at 03:48 PM.
Reply With Quote


  #39  
Old 10-20-2016, 12:45 AM
eagle132 eagle132 is offline
Registered User
eagle132's PC Specs
 
Join Date: Aug 2012
Posts: 9
POST ID # = 876176
eagle132 Reputation: 10
Angry Bootloop

How the hell is this software still on the site? I had a version of CUE 2.4 installed and the macros weren't working. It said to do a repair install. So I downloaded the newest version of CUE2 to get my macros working again and right when the drivers were being installed... Windows 10 bootloop. I also had to do a system restore to get my PC functional again but it caused all other sorts of issues.

I actually didn't at first believe that this software could possibly have caused the BSOD and bootloop so I went to install it again and the SAME thing happened. Then I come to the forum and see this... again how can this bugged software possibly still be available for download!?
Reply With Quote


  #40  
Old 10-20-2016, 02:00 AM
Inheritance's Avatar
Inheritance Inheritance is offline
βetα Nayn Cat
 
Join Date: Jul 2013
Location: Somewhere in Texas
Posts: 5,249
POST ID # = 876180
Inheritance Reputation: 41
Default

Quote:
Originally Posted by eagle132 View Post
How the hell is this software still on the site? I had a version of CUE 2.4 installed and the macros weren't working. It said to do a repair install. So I downloaded the newest version of CUE2 to get my macros working again and right when the drivers were being installed... Windows 10 bootloop. I also had to do a system restore to get my PC functional again but it caused all other sorts of issues.

I actually didn't at first believe that this software could possibly have caused the BSOD and bootloop so I went to install it again and the SAME thing happened. Then I come to the forum and see this... again how can this bugged software possibly still be available for download!?
Just because a few users have issues with a software release doesnt mean they are going to remove it on your call. Its possibly still be available for download because most users arent reporting a problem.
__________________
Colors of the RAINBOW shine so bright!
USER IS NOT A CORSAIR EMPLOYEE
Come Join My Discord =(^.^)= [iCUE Guide]
Corsair USER Forums is NOT Corsair Tech Support
Reply With Quote


  #41  
Old 10-20-2016, 05:10 PM
eagle132 eagle132 is offline
Registered User
eagle132's PC Specs
 
Join Date: Aug 2012
Posts: 9
POST ID # = 876268
eagle132 Reputation: 10
Default

Quote:
Originally Posted by Inheritance View Post
Just because a few users have issues with a software release doesnt mean they are going to remove it on your call. Its possibly still be available for download because most users arent reporting a problem.
I understand that but causing a full system BSOD bootloop for more than one user certainly shows that there is something seriously wrong with the software. Keyboard software should never have the potential to completely kill your computer upon install and I would think the potential risk of this happening to more users (like it happened to me when this software was not taken down after initial reports) should be taken extremely seriously.

Even if this happens to less than 1% of the users who download the software, that is more than enough reason to take down that particular release of the software. This isn't a few users having "issues", an issue would be if the install failed or features were buggy, this is a number of users almost losing their entire OS.
Reply With Quote


1 members found this post helpful.
  #42  
Old 10-20-2016, 07:03 PM
Inheritance's Avatar
Inheritance Inheritance is offline
βetα Nayn Cat
 
Join Date: Jul 2013
Location: Somewhere in Texas
Posts: 5,249
POST ID # = 876288
Inheritance Reputation: 41
Default

Quote:
Originally Posted by eagle132 View Post
I understand that but causing a full system BSOD bootloop for more than one user certainly shows that there is something seriously wrong with the software. Keyboard software should never have the potential to completely kill your computer upon install and I would think the potential risk of this happening to more users (like it happened to me when this software was not taken down after initial reports) should be taken extremely seriously.

Even if this happens to less than 1% of the users who download the software, that is more than enough reason to take down that particular release of the software. This isn't a few users having "issues", an issue would be if the install failed or features were buggy, this is a number of users almost losing their entire OS.
I understand it's frustrating to encounter a boot loop after a software install, but ATM it is not conclusive that CUE is the problem. It could be a Windows update, or the lack of a certain windows patch, or various other reasons. There's about 15-20 people that I've seen mention this problem on the forums. The install base is vastly greater than the people with the issue.

They are working on figuring out a the cause of this boot loop, and a fix.

PS: I've seen someone post a BSOD complaint after every other CUE update.
__________________
Colors of the RAINBOW shine so bright!
USER IS NOT A CORSAIR EMPLOYEE
Come Join My Discord =(^.^)= [iCUE Guide]
Corsair USER Forums is NOT Corsair Tech Support
Reply With Quote


  #43  
Old 10-21-2016, 07:04 PM
Corsair Calico Jack's Avatar
Corsair Calico Jack Corsair Calico Jack is offline
Registered User
 
Join Date: Oct 2016
Posts: 138
POST ID # = 876374
Corsair Calico Jack Reputation: 10
Default

Quote:
Originally Posted by eagle132 View Post
I understand that but causing a full system BSOD bootloop for more than one user certainly shows that there is something seriously wrong with the software. Keyboard software should never have the potential to completely kill your computer upon install and I would think the potential risk of this happening to more users (like it happened to me when this software was not taken down after initial reports) should be taken extremely seriously.

Even if this happens to less than 1% of the users who download the software, that is more than enough reason to take down that particular release of the software. This isn't a few users having "issues", an issue would be if the install failed or features were buggy, this is a number of users almost losing their entire OS.
Do you happen to have your system information available?

To obtain the DXDIAG file:
1. Press the Windows Key (the key with the Windows logo on your keyboard) + R (at the same time).
2. Type "dxdiag", and select "OK".
3. At the bottom right, there will be a "Save All Information" button, select it.

This will create and save a text file named "DxDiag" onto your desktop with all your system configurations.
Reply With Quote


  #44  
Old 10-24-2016, 01:08 PM
Corsair James's Avatar
Corsair James Corsair James is offline
iCUE Product Manager
 
Join Date: Oct 2013
Location: Fremont, CA
Posts: 4,374
POST ID # = 876643
Corsair James Reputation: 71
Default

Quote:
Originally Posted by EdHart View Post
I'm not sure if this can help, do you guys need the log xml file? I'm not really familiar with event log, i found minidump file but couldn't find the other files.

Fault bucket AV_corsairvhiddriver!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 45f2507f-087c-407b-882a-01f3eecb73b9

Problem signature:
P1: a
P2: 60001
P3: 2
P4: 0
P5: fffff801e26b825a
P6: 10_0_14393
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\Minidump\100316-6531-01.dmp
\\?\C:\Windows\Temp\WER-6875-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER67C2.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_491edcbe77bb8bc477c641ee33aee88b1b4ca3_0 0000000_cab_1254a930

Analysis symbol:
Rechecking for solution: 0
Report Id: 418ae6ab-0052-43b3-a7df-e4b0567a69a4
Report Status: 0
Hashed bucket:
Hi Ed,

I need these files here:

Attached files:
\\?\C:\WINDOWS\Minidump\100316-6531-01.dmp
\\?\C:\Windows\Temp\WER-6875-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER67C2.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_491edcbe77bb8bc477c641ee33aee88b1b4ca3_0 0000000_cab_1254a930

These are the most important information that we can use to analyze why it BSOD.

For reference to everyone, these are the files I need the most. Please let me know if you have this issue and can submit it as without these files, our devs can't look into why it would blue screen the system.
__________________

iCUE - A CORSAIR Interface
https://www.corsair.com/us/en/icue
Reply With Quote


  #45  
Old 10-24-2016, 07:06 PM
Corsair James's Avatar
Corsair James Corsair James is offline
iCUE Product Manager
 
Join Date: Oct 2013
Location: Fremont, CA
Posts: 4,374
POST ID # = 876678
Corsair James Reputation: 71
Default

Update to everyone:

In lieu of reports that some people have lost their OS due to Windows files corruption, I am removing 2.5 from the website for now until we can properly diagnose the issue. This issue doesn't affect 99% of users but anyone unable to restore their Windows after a BSOD is one too many. We will continue to evaluate the issue and see what may be the root cause so if anyone has dump files to share, it would be great.

For now, we will restore 2.4 back on the website as that version didn't have any BSOD issues from what I can tell.

Thanks,
James
__________________

iCUE - A CORSAIR Interface
https://www.corsair.com/us/en/icue
Reply With Quote


Reply

Tags
boot loop, bsod, corsair cue, irql

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 01:14 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2018, vBulletin Solutions, Inc.