Game settings?

Discussion in 'Razer Cortex' started by Gidea, Mar 15, 2017.

Thread Status:
Not open for further replies.
  1. Gidea

    Gidea New Member

    Oh right there are NONE.

    Why ami in " gaming desktop mode" when theres absolutely NO SETTING FOR IT.
    I cannot put it into this mode and its a *********** to get it out.
    I have to to ctrl-alt-del to open task manager, shut down this $^%^&&&^ software,
    JUST to get back to my desktop.

    ( cleaned and sanitized for your protection )
     
    Last edited: Apr 14, 2017
  2. zoraw

    zoraw Cortex Product Developer Staff Member

    Hi @Gidea

    I am sorry that the beta is not working out for you.
    Would you be able to help us investigate the issue?

    Here are the steps that would assist in getting out of the gaming desktop mode:
    • Gaming Desktop mode would automatically be cancelled when the game ends
      • I suppose that this did not kick in automatically in your case and I suspect that this is because Cortex did not detect the game exit correctly
      • Can you tell me which game you encountered the issue in?
    • There should be an indicator that the gaming desktop mode is active:
      • In case the game desktop is not automatically cancelled when the quits, you should be able to see this indicator
      • This indicator would also show the shortcut to cancel the game desktop mode
      • Do you see such an indicator?
      • Did the shortcut work for you?
    • There is an option to control the game desktop mode.
      • You can disable it here:
        • Cortex >> click BOOST tab >> click Configure button in BOOST tab >> click OTHERS and untick option "Launch game on Game Desktop"
      • This option is supposed to be disabled by default and we need to investigate how it ended up getting enabled in your system
     
  3. Gidea

    Gidea New Member

     
  4. zoraw

    zoraw Cortex Product Developer Staff Member

    Hi @Gidea

    Thank you for support Razer Cortex beta.
    We have actually released the public version out.
    Could you please try it to see whether you still encounter the issues that you have reported?

    You either trigger the update from within or perform a manual update from:
    https://www.razerzone.com/cortex


    If you continue to encounter these issues, please submit a feedback from within Cortex and include your logs. We can better track your issues that way.
     
    freakydoctor likes this.
  5. Gidea

    Gidea New Member

    so ive figured out WHY I CANT COLLECT ANY SILVER
    the razer servers, have been in maintanace since april 5th.
    i have an alert notification, took a screen shot. it says servers are in maintanace fir 2 hours.

    now assuming this is APRIL 14TH. i had hoped they are done. guess not.

    below is my log analyze from today.

    good luck.--------------------------------
    tried to add my log report and its over 10,000 characters.
    i cannot UPLOAD a text file, because its " illegal " or something.
    i dont know.
    so for now, you do not get the priviledge of my log report, which was requested BY razer to send TO razer.

    ok so you get my log report in chunks!!!

    Razer Cortex Diagnostics Report v2.0 Version: 8.0.104.420
    Date: 2017/04/13 23:41:34

    ----------------------------------
    01 - Operating System
    ----------------------------------

    0101 - Operating System : Windows 8.1 with Bing 64-bit (6.3, Build 9600) (9600.winblue_ltsb.160930-0600)
    0102 - Language : English (Regional Setting: English)
    0103 - BIOS : 80.14
    0104 - Processor : AMD E1-2500 APU with Radeon(TM) HD Graphics (2 CPUs), ~1.4GHz
    0105 - Memory : 6144MB RAM
    0106 - Available OS Memory : 5566MB RAM
    0107 - Page File : 2741MB used, 6907MB available
    0108 - Windows Dir : C:\WINDOWS
    0109 - DirectX Version : DirectX 11
    0110 - DX Setup Parameters : Not found
    0111 - User DPI Setting : Using System DPI
    0112 - System DPI Setting : 96 DPI (100 percent)
    0113 - DWM DPI Scaling : Disabled
    0114 - DxDiag Version : 6.03.9600.17415

    ----------------------------------
    02 - Processor
    ----------------------------------

    0201 - Caption : AMD E1-2500 APU with Radeon(TM) HD Graphics x2 ~1400MHz
    0202 - Current Clock Speed : 1400MHz

    ----------------------------------
    03 - Video Adapter
    ----------------------------------

    0301 - Card Name : AMD Radeon HD 8200 / R3 Series
    0302 - Manufacturer : Advanced Micro Devices, Inc.
    0303 - Chiptype : AMD Radeon Graphics Processor (0x9838)
    0304 - DAC Type : Internal DAC(400MHz)
    0305 - Device Key : Enum\PCI\VEN_1002&DEV_9838&SUBSYS_2AFE103C&REV_00
    0306 - Display Memory : 3054 MB
    0307 - AdapterRAM : 512.00 MB
    0308 - Current Mode : 1366 x 768 (32 bit) (60Hz)
    0309 - Monitor Name : Generic PnP Monitor
    0310 - Driver Name : aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    0311 - Driver Version : 21.19.0384.0000
    0312 - Driver Language : English
    0313 - DDI Version : 11.1
    0314 - Driver Model : WDDM 1.3
    0315 - Driver Beta : False
    0316 - Driver Debug : False
    0317 - Driver Date : 1/15/2017 20:11:54
    0318 - Driver Size : 1564728
    0319 - VDD : n/a
    0320 - Mini VDD : n/a
    0321 - Mini VDD Date : n/a
    0322 - Mini VDD Size : 0
    0323 - Device Identifier : {D7B71EE2-DB78-11CF-8C73-7E0BBCC2D835}
    0324 - Vendor ID : 0x1002
    0325 - Device ID : 0x9838
    : 0x2AFE103C
    0327 - Revision ID : 0x0000
    0328 - Driver Strong Name : oem14.inf:cb0ae414003f2f8b:WB64A_ati2mtag_Kabini_Mobile:21.19.384.0:stuck_out_tongue_winking_eye:ci\ven_1002&dev_9838
    0329 - Rank Of Driver : 00DA2001
    0330 - Video Accel : ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
    0331 - Deinterlace Caps : {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
    {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
    {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
    {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
    0332 - D3D9 Overlay : Not Supported
    0333 - DXVA-HD : Not Supported
    0334 - DDraw Status : Enabled
    0335 - D3D Status : Enabled
    0336 - AGP Status : Enabled
    0337 - Notes : No problems found.


    0338 - OpenGL : 6.3.9600.17415 (winblue_r4.141028-1500)

    ----------------------------------
    04 - Memory
    ----------------------------------
    0401 - Total Memory : 5.445 GB
    0402 - Free Memory : 3.31 GB
    0403 - Total Pagefile : 9.433 GB
    0404 - Free Pagefile : 6.769 GB

    0405 - Bank Label : CHANNEL A
    0406 - Speed : 1333 MHz
    0407 - Total Width : 64 Bits
    0408 - Capacity : 2.00 GB

    0405 - Bank Label : CHANNEL A
    0406 - Speed : 1333 MHz
    0407 - Total Width : 64 Bits
    0408 - Capacity : 4.00 GB

    ----------------------------------
    05 - Network
    ----------------------------------

    0501 - Description : Realtek PCIe FE Family Controller
    0502 - Driver Date : 10-7-2016
    0503 - Driver Version : 8.49.1007.2016

    ----------------------------------
    06 - Motherboard
    ----------------------------------

    0601 - Model : 2AFE
    0602 - Manufacturer : Hewlett-Packard

    ----------------------------------
    07 - Sound Device
    ----------------------------------

    0701 - Description : Speakers (Realtek High Definition Audio)
    0702 - Default Sound Playback : True
    0703 - Default Voice Playback : True
    0704 - Hardware ID : HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_103C2AFE&REV_1003
    0705 - Manufacturer ID : 1
    0706 - Product ID : 100
    0707 - Type : WDM
    0708 - Driver Name : RTKVHD64.sys
    0709 - Driver Version : 6.00.0001.8004
    0710 - Driver attributes : Final Retail
    0711 - Date and Size : 12/23/2016 03:31:11
    0713 - Driver Provider : Realtek Semiconductor Corp.
    0714 - Min/Max Sample Rate : N/A, N/A
    0715 - Static/Strm HW Mix Bufs : N/A, N/A
    0716 - Static/Strm HW 3D Bufs : N/A, N/A
    0717 - HW Memory : N/A
    0718 - Voice Management : False
    0719 - EAX(tm) 2.0 Listen/Src : False, False
    0720 - I3DL2(tm) Listen/Src : False, False
    0721 - Notes : No problems found.


    ----------------------------------
    08 - Harddisk
    ----------------------------------

    0801 - Model : SDHC Card
    0802 - Media Type : Removable Media
    0803 - Size : 7.409 GB

    0801 - Model : WDC WD5000AAKX-60U6AA0(Western Digital)
    0802 - Media Type : Fixed hard disk media
    0803 - Size : 465.777 GB
    0804 - Interface Type : Serial ATA

    0807 - Caption : C:\
    0808 - Capacity : 450.223 GB
    0809 - Free Space : 77.246 GB
    0810 - Drive Type : 3-Fixed
    0811 - File System : NTFS

    0807 - Caption : D:\
    0808 - Capacity : 14.62 GB
    0809 - Free Space : 407.512 MB
    0810 - Drive Type : 3-Fixed
    0811 - File System : NTFS

    ----------------------------------
    12 - Event Log
    ----------------------------------

    1201 - Time : 4/13/2017 23:34:22
    1202 - Source : SideBySide
    1203 - Description : Activation context generation failed for "C:\Program Files (x86)\Razer\Razer Cortex\StreamingServicesAPI.dll.Manifest".Error in manifest or policy file "C:\Program Files (x86)\Razer\Razer Cortex\StreamingServicesAPI.dll.Manifest" on line 2. The value "F:\joju\projects\XSplitCSDemo\RazerLauncher\Components\StreamingServicesAPI.dll" of attribute "name" in element "urn:schemas-microsoft-com:asm.v1^file" is invalid.

    1201 - Time : 4/13/2017 23:31:18
    1202 - Source : SideBySide
    1203 - Description : Activation context generation failed for "c:\program files (x86)\razer\razer cortex\StreamingServicesAPI.dll.Manifest".Error in manifest or policy file "c:\program files (x86)\razer\razer cortex\StreamingServicesAPI.dll.Manifest" on line 2. The value "F:\joju\projects\XSplitCSDemo\RazerLauncher\Components\StreamingServicesAPI.dll" of attribute "name" in element "urn:schemas-microsoft-com:asm.v1^file" is invalid.

    1201 - Time : 4/13/2017 23:31:13
    1202 - Source : SideBySide
    1203 - Description : Activation context generation failed for "C:\Program Files (x86)\Razer\Razer Cortex\StreamingServicesAPI.dll.Manifest".Error in manifest or policy file "C:\Program Files (x86)\Razer\Razer Cortex\StreamingServicesAPI.dll.Manifest" on line 2. The value "F:\joju\projects\XSplitCSDemo\RazerLauncher\Components\StreamingServicesAPI.dll" of attribute "name" in element "urn:schemas-microsoft-com:asm.v1^file" is invalid.

    1201 - Time : 4/13/2017 23:25:31
    1202 - Source : Service Control Manager
    1203 - Description : The RzKLService service terminated unexpectedly. It has done this 1 time(s).

    1201 - Time : 4/13/2017 19:39:33
    1202 - Source : Service Control Manager
    1203 - Description : A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

    1201 - Time : 4/13/2017 19:39:03
    1202 - Source : Service Control Manager
    1203 - Description : A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

    1201 - Time : 4/13/2017 19:38:33
    1202 - Source : Service Control Manager
    1203 - Description : A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

    1201 - Time : 4/13/2017 19:05:37
    1202 - Source : Service Control Manager
    1203 - Description : A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

    1201 - Time : 4/13/2017 19:05:07
    1202 - Source : Service Control Manager
    1203 - Description : A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

    1201 - Time : 4/13/2017 19:04:37
    1202 - Source : Service Control Manager
    1203 - Description : A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

    1201 - Time : 4/13/2017 10:46:40
    1202 - Source : Service Control Manager
    1203 - Description : The Windows Media Player Network Sharing Service service depends on the Windows Search service which failed to start because of the following error:
    After starting, the service hung in a start-pending state.

    1201 - Time : 4/13/2017 10:46:40
    1202 - Source : Service Control Manager
    1203 - Description : The Windows Search service hung on starting.

    1201 - Time : 4/13/2017 10:43:18
    1202 - Source : Service Control Manager
    1203 - Description : The Razer Game Manager service hung on starting.

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

    End of file - 26455 Bytes.
     

    Attached Files:

    Last edited by a moderator: Apr 14, 2017
  6. MissSwaggy

    MissSwaggy Active Member

    Sorry for the problem you faced but it is better if you contact support directly. Razer Insider is not a support forum.
     
Thread Status:
Not open for further replies.
Sign In with Razer ID >


Don't have a Razer ID yet?
Get Razer ID >