Sign in with
Sign up | Sign in
Your question

CS:GO weird freeze

Tags:
  • Go
  • Video Games
Last response: in Video Games
Share
October 9, 2014 1:04:49 PM

Hello there. I've changed my PC a few days ago and I am experiencing some weird CS:GO "bug". Sometimes I can play a whole MM game without any problems and sometimes I won't be able to play a single round. What happens is me getting some random freeze (I can look around, hear people using voice chat in-game, hear all the stuff like bomb ticking etc.) and I can't move, change weapon and all that stuff. Waiting about 10-15 seconds leads to drop to CS:GO menu with Timed Out message. After this I am not able to reconnect (getting Time Out after every try) until I completely restart Steam.

My specs:
i5-4690k
gigabyte gtx 970 (344.16 drivers)
msi gaming 7
windows 8.1
8gb ram
asus vg248qe monitor

Anyone having the same problem? How to fix that? Thanks for any help!

More about : weird freeze

October 9, 2014 2:24:59 PM

macieqq said:
Hello there. I've changed my PC a few days ago and I am experiencing some weird CS:GO "bug". Sometimes I can play a whole MM game without any problems and sometimes I won't be able to play a single round. What happens is me getting some random freeze (I can look around, hear people using voice chat in-game, hear all the stuff like bomb ticking etc.) and I can't move, change weapon and all that stuff. Waiting about 10-15 seconds leads to drop to CS:GO menu with Timed Out message. After this I am not able to reconnect (getting Time Out after every try) until I completely restart Steam.

My specs:
i5-4690k
gigabyte gtx 970 (344.16 drivers)
msi gaming 7
windows 8.1
8gb ram
asus vg248qe monitor

Anyone having the same problem? How to fix that? Thanks for any help!


I haven't had this particular problem, but I've had problems with the game stuttering due to missing assets (vgui material) that often popped up at the most inconvenient time. Validating game files did not fix it. I reinstalled the game yesterday, haven't tried since.
m
0
l
October 9, 2014 3:03:14 PM

I doubt that's the issue for me. I have already reinstalled Windows and same thing happens, so reinstalling a game won't help either.
m
0
l
Related resources
October 10, 2014 1:15:22 PM

Bump.
m
0
l
October 11, 2014 5:14:08 AM

Soooo I found the problem... sort of... Switched to Windows 7 - didn't help. So I've bought an external PCI-E network card. Played some games and everything is great so far. However, I don't really want to use some crappy external card when I have such an expensive (for me at least) mobo. Now I know for sure which part fails but how to fix it? Theoretically my connecting works while using mobo ethernet so it might be the software?
m
0
l
October 11, 2014 2:10:51 PM

macieqq said:
Soooo I found the problem... sort of... Switched to Windows 7 - didn't help. So I've bought an external PCI-E network card. Played some games and everything is great so far. However, I don't really want to use some crappy external card when I have such an expensive (for me at least) mobo. Now I know for sure which part fails but how to fix it? Theoretically my connecting works while using mobo ethernet so it might be the software?


Sounds like a driver issue. See if there's a newer revision available, include beta releases.
m
0
l
October 11, 2014 2:29:20 PM

i've faced some issue like yours , due having a 144hz monitor , i recommend to limiting game fps , type in console fps_max 150 , instead of fps_max 300 , hope it helps or even fps_max 120 .
m
0
l
October 11, 2014 2:29:55 PM

Pinhedd said:
macieqq said:
Soooo I found the problem... sort of... Switched to Windows 7 - didn't help. So I've bought an external PCI-E network card. Played some games and everything is great so far. However, I don't really want to use some crappy external card when I have such an expensive (for me at least) mobo. Now I know for sure which part fails but how to fix it? Theoretically my connecting works while using mobo ethernet so it might be the software?


Sounds like a driver issue. See if there's a newer revision available, include beta releases.


I've tried with drivers from mobo CD, MSI website as well as from Qualcomm website. Nothing helps and all of them do not fix this thing :( 
m
0
l
October 11, 2014 3:25:12 PM

macieqq said:
Pinhedd said:
macieqq said:
Soooo I found the problem... sort of... Switched to Windows 7 - didn't help. So I've bought an external PCI-E network card. Played some games and everything is great so far. However, I don't really want to use some crappy external card when I have such an expensive (for me at least) mobo. Now I know for sure which part fails but how to fix it? Theoretically my connecting works while using mobo ethernet so it might be the software?


Sounds like a driver issue. See if there's a newer revision available, include beta releases.


I've tried with drivers from mobo CD, MSI website as well as from Qualcomm website. Nothing helps and all of them do not fix this thing :( 


Did you try this one?

http://www.qca.qualcomm.com/drivers/KillerSuite_1.1.47....

I remember a post from a few months ago where a user was plagued by a memory leak that occurred when a Killer e2200 driver conflicted with the Windows network monitoring driver. I think that a patch fixed it.
m
0
l
October 12, 2014 2:35:47 AM

Azizinum said:
i've faced some issue like yours , due having a 144hz monitor , i recommend to limiting game fps , type in console fps_max 150 , instead of fps_max 300 , hope it helps or even fps_max 120 .


As I discovered lately, it's not a 144hz problem.


Pinhedd said:
Did you try this one?

http://www.qca.qualcomm.com/drivers/KillerSuite_1.1.47....

I remember a post from a few months ago where a user was plagued by a memory leak that occurred when a Killer e2200 driver conflicted with the Windows network monitoring driver. I think that a patch fixed it.


Yes, as I said before I've tried these drivers from Qualcomm website. Didn't fix the problem :/ 

EDIT:

Switched drivers using this guide:

http://www.techpowerup.com/forums/threads/guide-turn-yo...

hoping it's software problem. The issue is still there, so it looks like it's something deeper. What now? :( 
m
0
l
!