Hello there, yesterday I've swapped the stock 4 rgb fans, into a 4 pin 4 rgb pwm fans from deepcool and I when I booted the pc and started watching 4k youtube video , it seemed that for a second or two, the cpu and the audio became extremely laggy more like everything became superslow and then it disappeared, could that be because of some software or that I have too many fans connected into the cpu header? Cause, As I've read on mobo manual, it says that the Cpu header can support up to a 2A, and since I've connected 4 fans into the hub and into to the cpu header I was started to wonder if it could be the fans that would make the system slower than usual, the same is for the rgb leds as one rgb header supports up to 3A and I've daisy chained the rgb connectors.
-
Have a passion for hardware and the written word? Tom's Hardware is seeking contributors!
Question Can too many rgb fans slow down the system?
- Thread starter zgzdgz
- Start date
Is every fan connected to the CPU header for power because I don't think that's a good idea...? I'm not familiar with the Windows 11 and it could be because of that but don't know for sure, but it's still relatively new operating system with certain bugs around. Run the video, keep an eye on your temperatures (CPU, GPU) and have a Task Manager running open and see if any component spikes up to 100 % usage, which when happening, could cause the glitch.
If OP have fan hub with external power via SATA/Molex power cable then power limits are not relevant anymore. However he still must be sure that fans are connected to correct sockets in hub. @zgzdgz , which hub model you use by the way?
Also 4K video viewing in YouTube is heavy load on Internet connection and system itself. Would not hurt to enable some background monitoring for CPU, GPU and RAM loads, CPU and GPU temperature and Internet traffic. To be sure that problem is not related to CPU overload, lack of RAM or Internet congestion. Also Windows 11 is still black box.
Well, on the manual it says that cpu fan header can support up 2 amps, so if all 4 cpu fans in total consume around 0.92a~ I think that it shouldnt be issue, as for that fan hub, its like you can connect 4 fans into hub and then you connect the fan hub into the cpu fan header.
Nothing wrong here. Except network utilization around 30 Mbit. Let say... what is happening with network usage and GPU load in same time? Also how 4K videos behave on your system if played locally from local drive? I suspect network hiccups here which cause video stuttering. I'm not saying that it is happening in your side, it is quite possible that YouTube is lagging. 4K is huge network resource hog.
Well, I rearranged connections so only 2 fans would cool the cpu via it's header, and the rest of it would be used as a case fans, I did tried to use the "Latency Mon" and "WhySoSlow" , latency mon at first it was fine, and then maybe I triggered somehow but it said "your system seems to be having difficulty performing real time tasks " and the rest of it I didn't understood, and "WhySoSlow" said nothing is wrong, so are those even reliable apps ? Oh and also, I'm using some sort of an xmp, and sometimes the voltage it up to v1.404, should I decrease the voltage?
https://prnt.sc/26x2qsc
https://prnt.sc/26x2rre
https://prnt.sc/26x2qsc
Last edited:
Still believe that playback lagging have nothing to do with fans. Either network or video driver issues. Or some roque Windows update appeared and spoiled your day. Are video playback return to normal when new case fan/hub assemby is disconnected?
At first check are 4K videos are played without lag when stored locally. Some examples under link below. First two 4K examples (120 and 160 Mbps) should play without noticeable lag.
If these are passed, try to realize why streaming lag is happening. There are some next steps in your PC connectivity mutilation 😉
thegeekpage.com
At first check are 4K videos are played without lag when stored locally. Some examples under link below. First two 4K examples (120 and 160 Mbps) should play without noticeable lag.
If these are passed, try to realize why streaming lag is happening. There are some next steps in your PC connectivity mutilation 😉
Fix High DPC Latency on Windows 11/10
DPC (Deferred Procedure Call) is a mechanism in Windows makes the system execute low-priority tasks later when the system is idle and high-priority tasks first.
Okay, so none of them lagged at all, even the 4k ones, I mean the worst case scenario that I thought would be, like, I might have knocked something while installing the fans, but, I was pretty careful (wearing an esd) , and I also somehow accidentally I dropped the screwdriver on the metal chassis at the bottom, and it didn't landed anywhere but on the bottom of the case, so, I've checked motherboard 3 times, no even a scratch, nothing been knocked out, neither I think too many fans would have cause that, but I'm just wanted to be sure that it had nothing to do with that.
- Nov 19, 2010
- 21,156
- 5,291
- 106,640
I would not trust to any 3rd party app here. Also Windows Update sometimes manage to smuggle in Microsoft branded driver with "newer" version, which under the hood really is older and limited. It is still happening even in Windows 11. Download and install network drivers from motherboard/chipset/network chip manufacturer.
Exactly. So called driver downloaders are de facto adware and malware aggregators. It is not worth to risk with them.
Yeah, you are exactly right, windows does that as well, it shows that there are new drivers available even though the device websites dont offer that kind of newer drivers themselves, so how in the world windows or 3rd party apps offer newer drivers that dont event exist yet?
Branded desktop/laptop manufacturers (HP, Dell, Lenovo etc.) often offer their system management software. It also include periodic updated driver and BIOS check online and downloading/updating if necessary. Particular software is available also for newer motherboards (Dragon Center for MSI hardware for example) and GPUs (NVIDIA - Geforce Experience, AMD - Catalyst Control Center). Works not in all OSes and not for all models though. For the rest and for custom hardware only way is to check online servers for newer drivers in motherboard from time to time. Still better than rely on some 3rd party driver downloader and catch accidental virus or ransomware. There is no free cheese as they said.
We with @DSzymborski are telling you about potential dangers of 3rd party driver downloaders. Who came from same box as malevolent registry optimizers and fake antiviruses. Nothing more than 20+ year experience with cleaning out consequences of these things. You mileage may vary though. Just for idea in what you can run into.
Yeah I understand and totally agree with that, the only reason I was using those apps was to make driver installations easier, that's all, ain't gonna use them anymore, but I had no idea they could have create such a mess in the system, I guess the same goes for some AV's?
Yes. There are plenty of good free utilities around, but there are malevolent ones too. Malware writers especially "love" driver downloaders and various system optimizers, because those are real honeypots for lazy people and people in rush. Because of that such software is default taboo and instant red flag for techies and IT support.
Unfortunately for Windows OS updated driver obtaining is messy business. There is no central driver repository except one provided by Windows update infrastructure, which contain only basic drivers to make things going, but nothing more. For the rest the only option is to periodically check appropriate hardware manufacturer servers. Which can be suddenly moved elsewhere without a warning when particular hardware reach end of life for manufacturer.
Unfortunately for Windows OS updated driver obtaining is messy business. There is no central driver repository except one provided by Windows update infrastructure, which contain only basic drivers to make things going, but nothing more. For the rest the only option is to periodically check appropriate hardware manufacturer servers. Which can be suddenly moved elsewhere without a warning when particular hardware reach end of life for manufacturer.
So okay, I did managed to get the BSOD by using driver verifier and in a half hour or so, it gave me the code "BUGCODE_NDIS_DRIVER", and I will upload the dump file later, and also here is the dumpstack.log
"
DLOGFILE00010000DUMP 0
Dump stack initialized at UTC: 2022/02/18 10:30:10, local time: 2022/02/18 12:30:10.
Progress 0x00000042
Elapsed BugCheck duration 00001796ms
Starting get secondary dump callbacks size.
Finish get secondary dump callbacks size.
Dump Type: 6, Total Dump Size: 4415119041, Secondary Dump Size: 429761.
Starting write of dump header.
Finish write of dump header.
Starting write of kernel bitmap dump header.
Finish write of bitmap dump header.
Starting write of memory dump data.
Elapsed BugCheck duration 00001867ms
Dumping physical memory to disk: 0%
Dumping physical memory to disk: 5%
Dumping physical memory to disk: 10%
Dumping physical memory to disk: 15%
Dumping physical memory to disk: 20%
Dumping physical memory to disk: 25%
Dumping physical memory to disk: 30%
Dumping physical memory to disk: 35%
Dumping physical memory to disk: 40%
Dumping physical memory to disk: 45%
Dumping physical memory to disk: 50%
Dumping physical memory to disk: 55%
Dumping physical memory to disk: 60%
Dumping physical memory to disk: 65%
Dumping physical memory to disk: 70%
Dumping physical memory to disk: 75%
Dumping physical memory to disk: 80%
Dumping physical memory to disk: 85%
Dumping physical memory to disk: 90%
Dumping physical memory to disk: 95%
Dumping physical memory to disk: 100%
Finish write of bitmap dump data. Total pages:1077541 Pages written:1077541
Progress 0x00000043
Elapsed BugCheck duration 00021482ms
Starting invoking secondary dump callbacks.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling CRASHDUMP secondary callback.
Return from CRASHDUMP secondary callback.
Writing CRASHDUMP secondary callback data.
Writing CRASHDUMP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling nvlddmkm.sys secondary callback. "
"
DLOGFILE00010000DUMP 0
Dump stack initialized at UTC: 2022/02/18 10:30:10, local time: 2022/02/18 12:30:10.
Progress 0x00000042
Elapsed BugCheck duration 00001796ms
Starting get secondary dump callbacks size.
Finish get secondary dump callbacks size.
Dump Type: 6, Total Dump Size: 4415119041, Secondary Dump Size: 429761.
Starting write of dump header.
Finish write of dump header.
Starting write of kernel bitmap dump header.
Finish write of bitmap dump header.
Starting write of memory dump data.
Elapsed BugCheck duration 00001867ms
Dumping physical memory to disk: 0%
Dumping physical memory to disk: 5%
Dumping physical memory to disk: 10%
Dumping physical memory to disk: 15%
Dumping physical memory to disk: 20%
Dumping physical memory to disk: 25%
Dumping physical memory to disk: 30%
Dumping physical memory to disk: 35%
Dumping physical memory to disk: 40%
Dumping physical memory to disk: 45%
Dumping physical memory to disk: 50%
Dumping physical memory to disk: 55%
Dumping physical memory to disk: 60%
Dumping physical memory to disk: 65%
Dumping physical memory to disk: 70%
Dumping physical memory to disk: 75%
Dumping physical memory to disk: 80%
Dumping physical memory to disk: 85%
Dumping physical memory to disk: 90%
Dumping physical memory to disk: 95%
Dumping physical memory to disk: 100%
Finish write of bitmap dump data. Total pages:1077541 Pages written:1077541
Progress 0x00000043
Elapsed BugCheck duration 00021482ms
Starting invoking secondary dump callbacks.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling CRASHDUMP secondary callback.
Return from CRASHDUMP secondary callback.
Writing CRASHDUMP secondary callback data.
Writing CRASHDUMP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling nvlddmkm.sys secondary callback. "
Last edited:
TRENDING THREADS
-
-
-
News Defendnot tool pitched as 'an even funnier way’ to disable Windows Defender- Started by Admin
- Replies: 7
-
My week with Linux: I'm dumping Windows for Ubuntu to see how it goes
- Started by Admin
- Replies: 231
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 4K
-
Discussion PSU recommendations and power supply discussion thread - Tom's hardware- Started by Darkbreeze
- Replies: 2K
-
News Nvidia RTX 5060 is up to 25% faster than RTX 4060 with frame generation in new GPU preview
- Started by Admin
- Replies: 30
Latest posts
-
-
-
Question Brand new Asus laptop is freezing & rebooting without any BSODs ?- Latest: foxcraft_deacon
-
-
Facebook
Twitter
Instagram