Computer hanging because of csgo

[Polygon]

It's @Blake Nig ga is the tag

yes, I've reinstalled steam ,csgo, changed registry values for valve , uninstalled my av, changed sound settings, disabled my sound drivers and a lot of other shit but nothing seems to fix the issue. The only thing that remotely temp fixes is turning all my settings on low and I have to make sure multicore rendering is off.

I assume you've updated all your drivers?
Also, when running CS:GO, what is your CPU usage?

[Blake]

I assume you've updated all your drivers?
Also, when running CS:GO, what is your CPU usage?

My cpu usage is low but my system idle process is at 60%-90% . Even while im typing this to you without any program running other than teamspeak and skype.

[[MPGH]Austin]

virus rip blake

[AnusForce]

Do a Defrag maybe?

[Polygon]

My cpu usage is low but my system idle process is at 60%-90% . Even while im typing this to you without any program running other than teamspeak and skype.

Tried a program like Advanced System Care yet? I'm out of options, this is the last one I can think off.

[Blake]

Do a Defrag maybe?

I can't be rude to you since you're trying to help. Yes , I've done a defrag, I've reformtated my pc.

Tried a program like Advanced System Care yet? I'm out of options, this is the last one I can think off.

Before I did this windows update, almost every program was non-responsive. After I updated like 170 files, everything seems fine.
here are some bugs windows found

[Prometheois117]

My cpu usage is low but my system idle process is at 60%-90% . Even while im typing this to you without any program running other than teamspeak and skype.

System idle process does not actually use CPU, it merely makes your computer think you're using the CPU so intel doesn't automatically underclock your CPU. (go to power options > plan and turn the minimum cpu to 5%. You should see system idle process go away, though it is recommended to have it on 100%)

EDIT: Go to your headsets' website, and see if they have any drivers built for them. Run windows update again.

[Blake]

System idle process does not actually use CPU, it merely makes your computer think you're using the CPU so intel doesn't automatically underclock your CPU. (go to power options > plan and turn the minimum cpu to 5%. You should see system idle process go away, though it is recommended to have it on 100%)

EDIT: Go to your headsets' website, and see if they have any drivers built for them. Run windows update again.

I have and I have also done research on this error.
https://www.reddi*****m/r/GlobalOffens...ce_the_update/
and so many other threads about this topic , so I'm willing to it's not my hardware. It's the game it self.

[Polygon]

I have and I have also done research on this error.
https://www.reddi*****m/r/GlobalOffens...ce_the_update/
and so many other threads about this topic , so I'm willing to it's not my hardware. It's the game it self.

Last option is that you can report it to Valve.

[Trollaux]

Since I cannot provide any help related to this crash, I can make one suggestion about your autoexec.cfg...
Assuming you play competitive 64-tic servers and not another league that has 128-tic servers you might want to do something like this
cl_updaterate 64 // Maximum Command Packets per second sent to server
cl_cmdrate 64 // Maximum number of Update packets per second received
cl_interp 0 // Interpolation Fix
cl_interp_ratio 1 // Interpolation Fix
fps_max 65 // Since rates are 64, make fps 64, prevents fps spikes

There is some verified facts about doing this somewhere that I read a while ago, and it does help. I used to run my rates at 128 and fpsmax 120 and then changing over to this config definitely made a difference in shooting the awp and getting a kill or dying by the enemy awper.

Also a quick tip on people who do fps_max...
E.G. you want your fps to be capped at 128
128 + 1 = 129
fps_max 129
this is because the source engine is retarded and yeah
if you use net_graph in game with fps_max 129 it will show that your fps is 128.

GL on solving your problem, its never happened to me before and I don't really understand the problem at all myself.

[Blake]

Since I cannot provide any help related to this crash, I can make one suggestion about your autoexec.cfg...
Assuming you play competitive 64-tic servers and not another league that has 128-tic servers you might want to do something like this
cl_updaterate 64 // Maximum Command Packets per second sent to server
cl_cmdrate 64 // Maximum number of Update packets per second received
cl_interp 0 // Interpolation Fix
cl_interp_ratio 1 // Interpolation Fix
fps_max 65 // Since rates are 64, make fps 64, prevents fps spikes

There is some verified facts about doing this somewhere that I read a while ago, and it does help. I used to run my rates at 128 and fpsmax 120 and then changing over to this config definitely made a difference in shooting the awp and getting a kill or dying by the enemy awper.

Also a quick tip on people who do fps_max...
E.G. you want your fps to be capped at 128
128 + 1 = 129
fps_max 129
this is because the source engine is retarded and yeah
if you use net_graph in game with fps_max 129 it will show that your fps is 128.

GL on solving your problem, its never happened to me before and I don't really understand the problem at all myself.

My autoexec has been like that for the longest. So I highly doubt it has anything to do with the tickrate.

I will try some other programs to help solve this problem, if it doesn't work then I'll just reinstall windows.