Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Gill

Member
  • Content Count

    38
  • Joined

  • Last visited

Awards


This user doesn't have any awards

About Gill

  • Title
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That's the WiFi in my place. My ssid is the Asus. I was too lazy to configure all the clients with the TP link ssid name, so I reused the Asus ssid. I'm lost.
  2. I don't have a cordless phone. I could be watching a youtube movie at 12 AM and suddenly connection drops. So nothing in the house gets triggered at this hour to cause such issues. I thought about maybe a neighbour is using some new device that causes these issues, but at such random times like middle of the night? Like, it needs to be a person who's arriving at that time and I hardly believe it's the case. If it's a router, then this should cause disconnections every second. I started to think about conspiracy theories I recently started to watch about the true secrets of the pyramids and the disclosure project, with steve greer and interviews with david adair and all those men-in-black UFO stuff, so people who don't want me to know about this are disconnecting me ? when I can't find a reasonable answer, I look elsewhere... hi, don't judge I'm desperate to solve this... Many suggested to get the Ubiquiti, but I do need a router since my main PC must be wired to a router. AFAIK, the Ubiquiti are just AP's. I also need a router that can provide NAS abilities for my HDD media drive. Not sure that Ubiquiti AP's have that.
  3. All devices comply with b/g/n and some ac standard. The only g standard in my old Wii. However, I ran with the Asus router for 10 months with no issue on the 2.4Ghz and during all the time, no new devices were introduced. The only real change was updating my Android phone from 7.1.2 to Android 9. So all this time I was using the same devices and I didn't have any network config changes. I didn't move the router's location... absolutely nothing. This issue started last month. I returned the router and am using the backup router and I get the same results... this drives me nuts. I used wifi analyzer and the best channel is 1. This backup router doesn't have MIMO technology but I did try the 40Hz as well. It still happens.
  4. Hi all. In the last month, I started to encounter wifi dropouts on the 2.4ghz only. By dropouts I mean the iOS, Android and IoT devices would lose connection and try to regain connection with no success. Mobile devices would show the WiFi icon with an exclamation mark. This would happen randomly throughout the day. Sometimes at 12:13 AM sometimes at 18 PM, and the frequency will vary. It can happen every 15 minutes, where a router reboot will sort it out for the next ~15 minutes. It can work for 2 or 3 days and then it happens again. I couldn't find a cause for this. I couldn't boil it down to one thing. I'm lost as to why this happens, so much that I replaced my Asus DSL-AC88U with a backup router and it happens with that router as well. So if it's not a router issue, what could cause the 2.4Ghz band to drop the connection and then disappear entirely from the list of available wifi access points? I have about 12 wifi clients. My main PC is using LAN cable so I don't experience connectivity issues. My current tp-link backup router supports on 2.4Ghz, however, my previous Asus router had 5Ghz and there were NO issues with the 5Ghz band. I would appreciate any help with trying to figure this out. I'm also in need of a new daily driver router out of this list Thank you.
  5. Hi all, Over this weekend I've been testing my RAM modules due to a request I got from technical support. I use Private Internet Access VPN and if I leave my VPN running for 24 hours, at some point its process will get killed. The support told me that I probably have a memory leak due to log files warnings, and I was asked to test my RAM. I own 4x4GB Corsair Vengeance 1600MHz on XMP profile over Z97 chipset. I used latest Memtest86 build and I tested each RAM module individually on each DIMM slot. Each RAM module was tested to 10 passes, which I believe is enough to establish an issue. No errors were presented. Ye, memtest86 is not enough because I don't really stress the RAM controller in dual channel mode. So I installed all RAM modules back in place, ran Win10 and disabled all 3rd party processes that boot with windows. I also killed every process which is not required. I launched latest Prime95 build and did a Custom test and allocated 14500MB (no FFT) and have only fixed 1024MB of virtual memory (manually handled, that is, not handled by Windows). I started the test on Aug 27, 08:57AM Worker #6 stopped working on Aug 28, 6:05AM with the following message: Cannot initialize FFT code, errorcode=1005 Unable to allocate memory. One possible cause is the operating system's swap area is too small. Torture test completed 276 tests in 21 hours, 7 minutes - 0 errors, 0 warnings. Worker stopped. All other workres are still running. Is this a HW issue? Configuration issue? or some OS corruption?
  6. I don't know what is the creator update. Is it windows update? How do I turn game mode off?
  7. Hi all,Running latest Win10 64 update has ruined my FPS and also my 2nd GPU is not scaling up.I use two R9 290 with latest AMD recommended drivers.I use GPU-Z 1.20 and I run the Render Test. I can see how both GPU's show:GPU 1 - PCI-Express x16 3.0 @ x8 1.1GPU 2 - PCI-Express x16 3.0 @ x8 1.1BIOS hasn't changed and I use strictly AMD GPU's and not intel iGPU, though it does get detected by GPU-zI don't know how to capture screenshot while the render test runs.I disable ULPS manually through the entire registry.The driver installation was made after cleaning previous driver with DDU.Crossfire option is enabled by default under global settings in AMD control panel. Under stress, the 2nd GPU is not being used. Anyway, can someone please assist me??
  8. You missed my point because I probably didn't explain myself better. The iGPU never showed up in Device Manager. Because I never installed the drivers for it. It's only when I first plugged in a monitor to the onboard HDMI port, that windows suddenly knew of its existence and suddenly it appeared in Device Manager. Since it's appearance, I'm getting issues with correct performance reading on GPU-Z. I'm not using beta drivers, I'm using latest official drivers by AMD. The BSOD I got was: thread stuck in device driver Now, if I set both GPU's to GEN 3 in BIOS, windows won't boot. Furthermore, removing the intel iGPU drivers will cause windows not to boot. I have no idea what's going on here.
  9. However it seems that it does. here is why: Up until few days ago, Win10 didn't have the iGPU hardware in device manager at all. It didn't know of it's existance. Since the issue I had with BSOD, I then had to use the iGPU with the onboard HDMI port to connect one of the monitors. Since then, the iGPU appears on the Device Manager section and since then, GPU-z reports 1.1 on GPU's under load, instead of x8 3.0 Is there way to remove it altogether and make windows unaware of the iGPU? removing the drivers is not enough, it keeps finding it's hardware.
  10. could the intel iGPU share the same bus lane with my PCI-E? I think it somehow interferes with scaling the GPU's on load
  11. great question. to my eyes, not really thought I'm in battle to sort drivers after system restore. so I didn't open a game to check. Furmark seems to run fine but I have not base for comparison
  12. Hi all. Windows 10, 64bit. 2x Gigabyte R9 290 water cooled. Motherboard: Asus P8Z77-V-Deluxe I upgraded to latest AMD driver from October. I used to have the previous one from September. I noticed some issues where things would get stuck in games. I used DDU in safe mode to remove AMD drivers and installed the latest October driver. I didn't reboot immediately after install. After a reboot, I got a BSOD with error message: thread stuck in device driver I pushed the rest button and it booted normally. I use GPU-Z to run a quick benchmark where I can see that both GPU operate at full capacity. The 1st GPU shows: PCI-E 3.0 X 16 @ X8 3.0 The 2nd GPU shows: PCI-E 3.0 X 16 @ X2 1.1 !!!!!!! <-- This suppose to show PCI-E 3.0 X 16 @ X8 3.0 . The 2nd GPU always had PCI-E 3.0 X 16 @ X8 3.0 on load. ULPS is disabled BIOS settings displayed X8 for the main GPU and X2 for the 2nd GPU. I had to remove the GPU's from the motherboard and let the PC boot and use the onboard iGPU (Intel graphics 4000. I use Ivy Bridge i7). After doing so, I connected the GPU's back in place and now BIOS displays X8 for both as it always used. BTW, GPU's are connected on the fastest PCI-E slots. I then had to flash a new Gigabyte R9 290 OC ROM on the 2nd GPU and reinstall the drivers and disabled ULPS. However, when running the GPU-Z load test, it displays as x8 1.1, instead of x8 3.0 as it always used to be for both GPU's. Can someone please help me understand what's going on? What should I do? How come it shows 1.1? Thanks.
  13. if you look at the diagram, you'd see that if I flip the front rad, so that the ports are at the top, then the ports will be slightly higher than the bottom part of the reservoir, meaning that lots of liquid will still be available in the radiator, isn't it?
×