Jump to content

Ocfos

Honorary Members
  • Posts

    83
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

2,369 profile views
  1. Sorry for the week of delay, I've been a bit busy. Sadly, these changes didn't do anything at all. Tried the thread and guide, but nothing's changed.
  2. I tried. Sadly, nothing happens. My headset is a wireless USB headset, but it never gave me any issues before that windows update. Undoing the update back then fixed my issue, too, so I know for sure it's not something to do with the headset itself, thankfully. But, changing any of the things to Enabled, doesn't do anything to fix it.
  3. I attempted to install "0009-64bit_Win7_Win8_Win81_Win10_R282" from Realtek's website, but it doesn't appear to have made any difference. I did however discover something very weird; My microphone gets picked up by Windows, if I tell Windows to "Listen to this device", which allows me to hear myself at a slight delay. Sadly, as soon as I toggle that off, Windows refuse to acknowledge any incoming noise from the Microphone. It's definitely an issue with Windows itself, and not the hardware. In case anything was misunderstood about the settings, it shouldn't be in here the issue rests. This is how the sound window looks, and that audio bar doesn't register anything coming in. The "Ingående Linje" is my TV audio jack, and is irrelevant. Just in case you wondered what it was.
  4. While that sounds a bit strange for a Windows Update to cause, I don't actually know how to make fully sure I have the latest sound driver installed. I'll see what I can do and report back.
  5. After a Windows update at some point before September, I had the issue that if it updated, my Microphone would stop functioning. However, if I didn't update, Apps wouldn't function. I much preferred having a microphone, as I use it quite often to play games and such. The issue is; I can't revert the windows update that *caused* the problem, as Windows 10 for some reason decided "You can't reverse updates before September now" on a whim, and I can't prevent updates either, so it just forced me to accept I now have a microphone that works just fine, but Windows just refuses to register any incoming noise from it. I've got zero idea why it doesn't pick up anything, as it's been an issue with two different headsets now, and the microphones work just fine on their own. I know this for sure, as the headsets both have "Sidetone" that plays my voice back into the headset to prevent speaking loudly, and that absolutely works just fine on both headsets I've used. The only issue there really is, appears to me to be Windows being stubborn about it, with no real idea why it would be. I hope someone is able to help me out, because I've tried reinstalling Logitech G HUB, completely removing registry for Logitech Gaming Software from the previous headset, and trying to plug it out and back in in several different ways, all to no use.
  6. Hey, I've been having a bunch of issues lately in terms of my Windows 10 ceasing to work out of nowhere, and I've tried plenty of things online to see if it was a simple fix, but I can't seem to actually determine what's wrong at all. I was hoping someone here knows exactly what's up, and would be able to help me. I don't know if it's caused by Malware or not, but I'm running both Premium Avast and Malwarebytes, so I'd be surprised if something actually got through them. Either way, I'm getting the "Code: 0x80072EE7" error whenever I try to use the Microsoft Store, and it tells me "Check Your Connection - The Store needs to be Online. It looks like you're not." but nothing I've tried actually fixes it, and I've had no internet issues whatsoever. It isn't either of my security programs either as far as I'm aware, as I haven't been able to find anything in them that would prevent my apps from working. Addition.txt FRST.txt scan.txt
  7. Thank you for the help, I definitely have my hopes up right now. I honestly thought that I had already removed XFastUSB as it came with my motherboard setup, but hopefully it'll be gone now.
  8. The newest motherboard update is all the way back from 2012, so I'm sure it's probably the motherboard that is to blame for part of the issues - Considering Windows 10 is far younger. I've fixed all the other things, considering I actually forgot I even tried to install the Wingman I own, only to discover it was broken. I've manually updated some drivers for the installed devices as well, which might do some more work to cause stability in the system.
  9. I'm sadly not in the mental capability to allow myself to open up my computer right now, so I can't run the diagnostics you suggest @usasma However, I have done what @1PW told me I missed, and I am sorry for forgetting. Here you go. Here's the other bits from that post; · OS - Windows 10· x64· What was original installed OS on system? Windows 7.· Original is Win7, upgraded from Win7 to Win10 with the free upgrade.· Age of entire computer is about 6 years.· Age of OS installation - A year at most.· Intel i7-2600K CPU @ 3.40GHz· GeForce 970· ASRock Fatal1ty Z68 Professional Gen3· Corsair Enthusiast Series TX850 V2· Custom built· I'm not sure I can provide such, since I built it myself.· Desktop. MWBreports.zip
  10. I'm not entirely sure what's causing the bluescreens, as they seem to happen randomly. I've been running memtest on Windows 10, but it says there's nothing wrong at all. I've been using WhoCrashed and SanityCheck to try and figure out what's wrong, but WhoCrashed seems to point at a driver going through the kernel. I'm not sure how to figure out exactly which driver is causing the issue, which is why I'm writing here in hopes someone can help me narrow it down. I've attached the dumps from my crashes, if they're of any help. I look forward to hearing from anyone, and please let me know if I've missed adding something of relevance. 061417-157046-01.dmp 061817-41296-01.dmp 061917-43109-01.dmp
  11. Oh, and sorry for the delay in posting - I've had some stuff to keep up with in a game I volunteer as a guide in, as a big update just launched here a little week ago. I'll keep you updated on what happens with the driver update, but here's to hoping it'll do the trick, and it's just been a faulty driver.
  12. That option is the only one greyed out for me, but I checked Nvidia and saw there had been a driver update since my last. I'm going to try to install it, and as usual, set it to completely remove the old driver before installing the new one. I had another bluescreen while helping my mom downstairs just half an hour ago, but there's no log in the minidump folder this time either.
  13. I tried all the methods whilst in safe mode with no net, but I sadly keep getting the same error as earlier.
  14. Yeah, it's running with that, but it doesn't do anything different when I use "Open With" instead of pressing Merge.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.