Problems with Linux 367.27 driver and CS:GO

Hi,
I upgraded to the 367.27 driver yesterday and when playing CS:GO my FPS suddenly dropped to ~15 and the game became very laggy and unplayable. I played 4 matches and this happened in 3 of them. The thing that triggered it was when I died or when I was buying stuff at the start of a round, and the only way to fix it was to quit CS:GO and restart it. Reverting to the 361.45.11 seems to fix the problem.

I have also reported this problem to valve here: https://github.com/ValveSoftware/csgo-osx-linux/issues/1116

I have an nVidia GTX-560Ti and I am using Linux kernel 4.4.14 on Slackware64 current with xorg 1.18.3.

Steam system info:

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected
    
Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Family:  0x15
    CPU Model:  0x1
    CPU Stepping:  0x2
    CPU Type:  0x0
    Speed:  3100 Mhz
    8 logical processors
    8 physical processors
    HyperThreading:  Unsupported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported
    
Network Information:
    Network Speed:  
    
Operating System Version:
    Linux (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.4.14af
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11803000
    X Window Manager:  i3
    Steam Runtime Version:  steam-runtime-beta-release_2016-06-15
    
Video Card:
    Driver:  NVIDIA Corporation GeForce GTX 560 Ti/PCIe/SSE2

    Driver Version:  4.5.0 NVIDIA 367.27
    OpenGL Version: 4.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x10de
    DeviceID:  0x1200
    Revision Not Detected
    Number of Monitors:  2
    Number of Video Cards Not Detected
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 3360 x 1080
    Primary Display Size: 21.77" x 12.17"  (24.92" diag)
                                            55.3cm x 30.9cm  (63.3cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 1024 MB
    Supported MSAA Modes:  2x 4x 8x 16x 
    
Sound card:
    Audio device: SigmaTel STAC9750,51
    
Memory:
    RAM:  15971 Mb
    
Miscellaneous:
    UI Language:  English
    LANG:  en_GB.UTF-8
    Microphone:  Not set
    Total Hard Disk Space Available:  831415 Mb
    Largest Free Hard Disk Block:  128763 Mb
    VR Headset: None detected

Bug also triggered by new round start, before even buying anything. I have had it happen to me on Cache, Dust II and Mirage maps so it doesn’t seem to be related to any map.

No problems with nvidia 361.45.18 driver (which seems to be newer than 367.27)

Just played a few games with todays CS:GO update and the nvidia 367.35 driver. For a while I thought this bug was fixed but then it got bugged again. It did seem like the bug occurred a few times but then fixed itself, just going laggy for 1 second - but eventually it dropped to 15fps and stayed there.

I may have experienced the same on 367.27 last week in L4D2. The framerate was stuck at about 10fps. I had to restart the game and that was the first time I ever had that happen.

I will report back if I see it again.