Jump to content

afluffehbunneh

Member
 View Profile  See their activity

  • Posts

    36

  • Joined

  • Last visited

Awards

This user doesn't have any awards

Profile Information

  • Gender
    Male
  • Location
    Fort Wayne, Indiana

System

  • CPU
    Intel Core I7-4790k 4.00GHz
  • Motherboard
    ASUS Z97-A
  • RAM
    16 GB DDR3-1600 Vengeance Corsair
  • GPU
    Radeon 7970 HD Sapphire
  • Case
    NZXT H440 White
  • Storage
    1TB Samsung SSD 850 EVO, 125GB Samsung SSD 840 EVO, 250GB Seagate
  • PSU
    750 Watt Corsair
  • Keyboard
    Razer Black Widow
  • Mouse
    Logitech G910s
  • Sound
    Corsair VOID Wireless Headset
  • Operating System
    Windows 10 64-bit

afluffehbunneh's Achievements

Rookie

Rookie (2/14)

1

Reputation

1

Community Answers

  1. afluffehbunneh
    **Disclaimer** BEFORE YOU READ THE FOLLOWING UNDERSTAND THAT IT IS A LITTLE HARD TO BELIEVE **Disclaimer** I recently updated my PC to the most recent build version 1511 of Windows 10 64-bit Pro. Before updating I was having a issue that was causing my log-in screen to freeze, and if I managed to wait long enough to get it to work everything was fine. After updating it started to get ridiculous. Even after logging in the desktop would freeze and windows wouldn't work. Applications would crash. Quite literally, nothing was working. I tried everything, and the only thing that seemed to work was booting into safe mode. That is when I started comparing the differences of safe mode to normal boot. The major difference is unless you boot with networking, windows automatically disables your wireless drivers and peripherals. I took my case apart and unmounted my WIreless Internet adapter, WIFI Card, and after words EVERYTHING, I repeat, EVERYTHING works perfectly. I haven't tracked whether this is an issue with drivers (I assume it is) or Windows having problems with the wireless cards, but I am posting to help those in desperate need of fixing this issue. If you are stuck at the log-in screen, or windows is lagging the crap out of you. Just try unplugging that treacherous wireless card.
  2. afluffehbunneh
    So...this is gonna sound a little weird...but unplug any Wireless card that you have. Yeah, I know it doesn't seem right. I was having this issue as well. Maybe, at least. When I start up windows it lags for a while at the log-in screen. Then if I manage to get into windows after a little while windows start freezing up. First it is the window that has focus, then it is the window behind it, then the desktop, then I have to wait because nothing is responsive. For some reason Windows 10 is having some issues with Wireless Peripherals right now. If you unplug your wireless card (do this while your system is off to avoid death), the system functions again. I assume this is related to a driver of some sort, but I haven't quite tracked the issue yet. Maybe we arent having the same issue, but if we are I am sure you will be happy to fix it as I was when I figured it out. I am posting a general topic now.
  3. afluffehbunneh
    From the way you described it you said you pulled all but one DIMM when testing for what I assume you thought was a memory error. Did you try testing all the DIMM's one at a time to see if the boot loop goes away. Perhaps, the one you tried is the faulty one? I would do a Memtest to make sure all of your RAM is good to go.
  4. afluffehbunneh
    Yes this still works as of when I got rid of the motherboard. My cpu was running at what I stated above flawlessly under constant stress tests/gameplay. All readings from other programs like HWMonitor, CPUID, System details in CPanel, and BIOS said it was overclocked. The machine seemed faster and the cpu was running perfect. I have a new mobo and cpu now, but at the time this was great for a cheap cpu/mobo combination.
  5. afluffehbunneh
    In Windows 10, the the task manager allows you to see if any startup programs are causing a high impact on your boot time. Press "Ctrl + Shift + Escape" to bring up task manager and go to the "Startup tab". The "Startup Impact" column will tell you if that is the case. Some programs will go into further detail and tell you the amount of milliseconds or seconds the startup programs use. I would go and check these programs to make sure nothing is starting that you don't actually need. Beyond that, make sure all of your drivers are updated to the most recent version. There are plenty of programs out there to check your drivers. I prefer programs from IObit. I trust them as I haven't ever had an issue with anything I have used from them. Sometimes drivers can cause issues like delayed startup time. This includes making sure your BIOS is up to date from your motherboard manufacturer, and that there is no new firmware for your SSD as Techguru before me suggested. Make sure you have all of your Windows Updates installed. If you do all of this and it still seems slow, let us know.
  6. afluffehbunneh
    This issue still has not been solved. I have been working diligently nonetheless. Anybody with networking experience that can shed some light on the situation? I have been trying to deploy several different fixes/patches/programs to computers on the network that result in this same issue where the disk1.cab (or whatever .cab file is storing the installation files) is unreachable/corrupted. Would really like to figure out where this problem originates to possibly fix it.
  7. afluffehbunneh
    I had a server that did this one time. Someone took it apart and put it back together improperly. Xbox 360's do this sometimes as well with the usb pins inside the case cover. If a wrong piece of metal is touching a wrong place, it will cause a short. That short will cause you to have no power. Hopefully, everything looks good from now on. Probably should mark this as solved! I'll be hopping on to the next threat. Get it. Hopping. You know because...nvm.
  8. afluffehbunneh
    I came across this somewhere at one point. I don't know how useful this will be. Windows 7 and Windows 8 had no heat monitor built in for the CPU that caused the hardware to throttle itself back after hitting a certain point. Apparently, Windows 10 has only been out for a while, Windows 10 has a heat throttle at 71 degrees Celsius. Perhaps, download Hardware monitor and check to see what temperature all of your components are reaching while you are gaming. If the CPU reaches anywhere above 71 degrees Celsius, you should try to find a way to cool it down (Cleaning, new thermal paste). FPS issues/performance issues are commonly tied to CPU heat problems, and if Windows 10 is indeed throttling back the components when it reaches these temps, it could be your issue. I have used several things to monitor my heat with issues like this I will provide some links: HWMonitor: http://www.cpuid.com/softwares/hwmonitor.html MSI AfterBurner (Also good with overclocking/fan adjustments): http://gaming.msi.com/features/afterburner If this isn't the issue, make sure you post back. Maybe we can come up with something else.
  9. afluffehbunneh
    svchost.exe is a system process that is common on every Windows machine. However, it is commonly spoofed with virus/malware programs. Does the IP address stay the same every time that message appears? What version of Malwarebytes do you have? Have you observed any other behavior? Regardless, you should probably do a full scan of your PC and post back to us with any results/issues found on the PC. You didn't really give us much to go on.
  10. afluffehbunneh
    Make sure the tightness of the screws/positioning of the screw holders underneath the motherboard are aligned with the grounding circling that the screws fit through on the motherboard. Sounds like when you tighten the screws it is un-aligning the motherboard from the mounting points. If they are no longer on the grounding circles, it will cause a short creating the issue you stated above.
  11. afluffehbunneh
    Continued to try to fix this when in the office today. I went ahead and deployed the package to all the computers. Turns out it works on all of them after trying to deploy it 3-4 times to failed computers. Before hand it replies with an MSI Error 1603, which directs via the log to the above error. Not sure what this problem is...but the work around is to constantly redeploy so far...interesting
  12. afluffehbunneh
    If you refer back to what I said, I asked you to stop the service and set it to manual. I never asked you to disable the service. This will simply make it so that the Windows Update service only "updates" or searches for updates when you want it to. It is a troubleshooting step to see if this helps your performance or not. You can always start the service right after you turn it off if it does not help. The change should take effect immediately, and won't effect anything except for Memory usage. I also stated that it eats memory as it scans for updates. Just because windows releases an update once a month (also not true) doesnt mean the service is not scanning for that update that is not out yet. Again, it is just a troubleshooting step to see if this will help your performance.
  13. afluffehbunneh
    Upon further investigation I found this in the error logs: Logerror.txt
  14. afluffehbunneh
    Tried the installation on the workstation administrative account. It went through once. I uninstalled to make sure it wasn't just a fluke. After trying to reinstall the program I received the same error. It worked, and then it didn't.
  15. afluffehbunneh
    If the computer is booting by itself, is the computer also power cycling? I have had experience with one of my desktops doing this. Turns out it was a RAM issue. If you have any known good RAM, try plugging it in to the machine and see if you still have the issue. Sometimes bad RAM will boot 'sometimes' and then not others. My RAM even passed RAM tests. The best way to check is to use Known Good RAM.
×