Computer Issues
- Thread starter brekk
- Start date
-
Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!
Go here and give us your nominations!Who's been the biggest Asshat in the last year? Give us your worst ones!
uncognito
Trakanon Raider
- 1,181
- 754
The fan on my HP, Windows 10 laptop is loud as fuck. I am trying to figure out how to turn it completely off.
I tried opening it up so I could just unplug it, but it does not seem to be designed to be opened.
I do not care at all if the laptop melts and explodes from lack of a fan.
Any suggestions?
I tried opening it up so I could just unplug it, but it does not seem to be designed to be opened.
I do not care at all if the laptop melts and explodes from lack of a fan.
Any suggestions?
Lanx
<Prior Amod>
- 66,100
- 150,632
just stick a zip tie through the vent and try to wrap around one blade and secure.
Noodleface
A Mod Real Quick
- 38,375
- 16,286
It won't melt or explode, it'll just turn off. May report as a fan fault too and shutdown fast.
Put something non conductive in there to stop it from moving. That's how we insert fan faults at work
- 17,781
- 25,897
I believe I am Admin and always have been.
So I rolled back my Nvidia drivers to 375.x. I got an error that said that DirectX has detected 375.x, but required 384.x or later.
My previous driver update was to get it up to 388.x, upon which time I got notified that DirectX could not 'Find The Closest Matching Mode' when I tried to make Battlefield 1 go to fullscreen. It would load into a functioning windowed mode of Battlefield, with sound, but as soon as you click on it to go to fullscreen, as it should and always has, now the DirectX error hits me. It correctly detected that I had driver 388.x. So I rolled back again to 375 and got the same 'your shit is too old' error. So I then used the GeForce app to install the latest driver which is, since last week, now called 390.x. So I run Battlefield in 390 and I get told, again, that it cannot 'Find The Closest Matching Mode.'. And again, DirectX correctly detected me as having driver 390.
alavaz
Trakanon Raider
- 2,003
- 714
That same error is plastered all over the EA and BF forums for all kinds of graphics cards. It sounds like a game bug to me.
DirectX Error: FindClosestMatchingMode - Answer HQ
DirectX Error: FindClosestMatchingMode - Answer HQ
- 1
Brahma
Obi-Bro Kenobi-X
- 12,709
- 47,500
Ok...so I was having issues with my mouse lagging to hell. Nothing worked to fix it. When the extreme route and reformatted. I added everything 1 by one back onto my machine and took notes. No lag. Install Chrome. BOOM! Lag is back.
WTF would Chrome lag my mouse. Especially on video play?
WTF would Chrome lag my mouse. Especially on video play?
Denamian
Night Janitor
- 7,554
- 20,932
Have no idea why chrome would cause it, but if you uninstall chrome, does the lag go away?
Lanx
<Prior Amod>
- 66,100
- 150,632
gpu v sync?
1. Paste/type this into your address bar: chrome://flags/
2. Find “Disable GPU VSync”
3. Click, “Enable”
4. Click “Relaunch Now” at the bottom of the browser
Brahma
Obi-Bro Kenobi-X
- 12,709
- 47,500
Lanx
<Prior Amod>
- 66,100
- 150,632
Noodleface
A Mod Real Quick
- 38,375
- 16,286
Chrome is hitching on videos for me now,.especially twitch. Firefox cleared it up
Something is fucked up with chrome
Something is fucked up with chrome
- 17,781
- 25,897
This was good but it is from a year ago and is for Mass Effect.
That being said, I did still follow the pathway given (although it is slightly different for BF1) and I did edit the ProfOps Profile file to change a value from 1 to 2, however in the BF1 file, unlilke the Mass Effect file, the value is set to 0, not to 1. So I tried changing it to 1 and to 2, both with no different result. Also, this same error is not just an EA thing, it has hit most of my Steam library.
gshurik
Tranny Chaser
- 2,517
- -56
I used Edge for a while but I found it started to fuck up loading certain pages. It was ok, but really felt like it still had the IE jank under the bonnet.
Brahma
Obi-Bro Kenobi-X
- 12,709
- 47,500
I figured it out. CLEAN Chrome install without syncing, so that's without all the extensions. I'm cool and the gang. Soon as I synced, it started fucking up my mouse. Removed all the extensions, uninstall/install and added the ones I MUST have like adblock and shit. I'm good now. Not even sure what extension it was. Think it was the auto HD for YouTube.
alavaz
Trakanon Raider
- 2,003
- 714
At this point you're best bet is probably boot from your win10 disk or recovery partition and running the Windows repair. From an admin command prompt you can also try typing 'sfc /scannow' and see if it repairs anything. If all that fails, then reinstalling completely would be the last resort. Hopefully you have your steam library on a separate disk/partition?
- 1
- 17,781
- 25,897
My Steam library is kept by Steam in their catalog accounting database. Partitions and data aren't the issue. The issue is that Windows 10 is Stalin. It won't allow me to fix this with the gpedit.msc file.
Y'all are trying to diagnose me with porn-itis but that ain't it. It's that I have the correct driver for my device, but DirectX just decided to wipe its ass with that and declare itself God.
The people who made my video card, Nvidia, are saying "Here is the correct driver." The operating system that is supposed to be a conduit to accessibility, Windows, is acting rather more like an obstruction by not allowing itself to be informed by Nvidia.
It looks to me like Nvidia is not allowed to tell my machine what is what in 'Driver Land'. Windows has decided that it is God now, and as you might expect from such a creature, it is fucking it all up. Nvidia seems to be doing what it should.... updating my driver as needed. DirectX (Microsoft) are the ones who are telling me that they forgot how to make shit work that used to work for the last 2 years.
My florist called and he has some windage adjustments he'd like to make to your AR15. Hang on, my plumber is on the other line and needs to give you some advice about roofing tiles.
Y'all are trying to diagnose me with porn-itis but that ain't it. It's that I have the correct driver for my device, but DirectX just decided to wipe its ass with that and declare itself God.
The people who made my video card, Nvidia, are saying "Here is the correct driver." The operating system that is supposed to be a conduit to accessibility, Windows, is acting rather more like an obstruction by not allowing itself to be informed by Nvidia.
It looks to me like Nvidia is not allowed to tell my machine what is what in 'Driver Land'. Windows has decided that it is God now, and as you might expect from such a creature, it is fucking it all up. Nvidia seems to be doing what it should.... updating my driver as needed. DirectX (Microsoft) are the ones who are telling me that they forgot how to make shit work that used to work for the last 2 years.
My florist called and he has some windage adjustments he'd like to make to your AR15. Hang on, my plumber is on the other line and needs to give you some advice about roofing tiles.
Last edited:
- 17,781
- 25,897
I hate Windows 10 not you, Alavaz. I thank you for your patience and advice thus far. I'm just frustrated.