Notn4

Only one device in the recording tab that has a level meter next to it ant it's the one I want to use, Realtek Audio Default Device. Also only one playback device outputting audio. I'm still taking suggestions but the issue is partially resolved, after 2 days of troubleshooting I finally lost my mind and did the sensible thing, threw money at it... Went and bought a cheap USB soundcard, when using it the audio is fine, so maybe the Realtek audio chip on the mobo if faulty, maybe it has a bad ground somewhere? I don't feel like doing a warranty claim on it since it's second hand so I suspect it would be a hassle. As long as that little USB dongle thingy works, I'm happy even if it's not a real solution.

At first rear, then front, both have same issue.

Hello, I have a weird audio issue, my girlfriends pc is somehow echoing her sounds to her mic input. So far no amount of googling has helped so I decided to admit defeat and ask here. I noticed it when we were playing games and talked over discord, every now and then I'd hear parts of her game over her voice chat, but it somehow sounds weird. It's not at all like a clear replication of her output that gets picked up on her mic input. Almost like it's some kind of interference. After trying pretty much everything I could think of I finally just took two 3.5mm audio extension cables, nothing plugged into one end and the other ends I plugged to the PC, still got the same issue. So there are no speakers/headphones connected, just a short 3.5mm extension and then there's also no microphone connected, just a short 3.5mm extension in that port too and windows still records audio out as audio in, just very distorted like. This makes me think hardware fault? It's an Asus PRIME B450-PLUS mobo with a Ryzen 3600. I might still try booting into a live linux distro to see if this is something windows specific... Things tried thus far: Bunch of settings, stereo mix and listen to this device are both disabled. Different speakers, headsets, adapters and cables. Reinstalling audio drivers. Any help would be massively appreciated!

This is what I ended up doing, or what I'm currently doing. The array seems fine for now, I can access all my files and they are currently being transferred over to an external drive. After I have everything backed up I'll just nuke the entire array and start fresh with the two new drives. New drives + new array and then just restoring the backup from the external drive (just a snapshot, not a clone image). Maybe then I'll finally have some peace of mind, been pulling my hair out with this one. Still can't believe I got 2 drive failures almost simultaneously... Or is this a common thing with RAID1? The drives see identical activity, right? But are they manufactured that identically that if one fails after X amount of usage then its brother will die almost instantly after, if it has had an identical life?

I have a backup of the important stuff but there's alot of content on the volume that is in the "not vital but would be nice to have" category. I guess I'll see where the verification process is at once I get home from work, if it's complete and the volume works fine then I'll just go ahead and replace the second drive with my fingers crossed and go from there. The dirty bit currently is not that big of an issue, as you said I can just skip it but in the case that I manage to salvage the volume to a healthy state, I'd like it cleared just so I don't need to worry about skipping CHKDSK on every reboot but I'm still worried about clearing the bit using CHKDSK even with a 100% intact volume. One option would be to backup everything on the drive to an external 3TB drive and reformat the array, this I assume would clear the bit.

Hi, I seem to have the shittiest luck recently with hardware and I might be slightly in over my head on this one. Maybe someone here can help me. This might get a bit long winded so I'll put a TL;DR at the end. So first a quick recap, I have 2 3TB in a RAID1 array and one of the drives failed recently, so naturally I immediately ordered 2 replacement drives since both of the original drives were bought simultaneously and if one failed due to age then the other one might be just around the corner. The new drives arrived and the plan was to plug one in, let Intel RST rebuild the array with the new drive, then shutdown and replace the second drive. Sounds simple right? BUT when I went to turn my pc off so I could replace the first one I noticed that some of my desktop shortcuts were blank white icons and only those for software installed on the array, a quick check in explorer showed that the entire volume had vanished and Intel RST confirmed that the second drive had also failed but not entirely, it just had a failed state warning that I could click ignore on and that made the volume available again. After quickly checking that the volume was accessible and had all of my files I turned the PC off and proceeded to replace the first faulty drive (I had already confirmed which was the first to fail so no risk of accidentaly replacing the wrong one). Intel RST rebuild the array fine and everything seemed ok but when I went to check on the files on the volume I had a few folders say that the path was inaccessible so there clearly was some corruption, checked Intel RST and it was running the verification process so I just let it be for a few hours. Then comes the current troubles. When I came back to the PC I just barely saw the verification % at 5% and then it suddently rebooted and went to do a CHKDSK on the volume, first I thought that was fine and was planning on letting it finish the check but then I did some googling on my phone about CHKDSK and RAID, found out that CHKDSK could seriously damage the array if the array was already compromised so I quickly did a hard reset and skipped the CHKDSK promt on reboot, everything booted fine and Intel RST returned to the verification process. I then did a dirty query with fsutil and found that my RAID volume had the dirty bit set and apparently the only way to clear the bit is with CHKDSK which I don't want to run, at least not until the volume is verified to be healthy but since the dirty bit is set that then means that CHKDSK will try to scan and repair the drive on every reboot, right? My current plan is to leave the PC on and let it finish the verification process, which btw takes ages, then once it completes, turn the PC off and reboot with only one drive, run the CHKDSK to clear the dirty bit, put the second new drive in and then let Intel RST rebuild the volume again. Thoughts and/or suggestions regarding that plan? I found that it is possible to manually clear the dirty bit with a hex editor but information on this is inconsistent at best, mentions that different OSes have different locations for the bit with mentions of the location for Win7 and 8 but nothing about Win10 and I'm not entirely confident in my skills with a hex editor to be messing around with entire logical volumes. I currently have 6h left of my shift at work before getting home to the PC. Any input on the matter would be welcome, even if it's just to call me an idiot because I sure feel like one now... I should just have turned the PC off when the first drive failed and left it untouched until the new drives arrived. Oh and if it wasn't obvious already, this is my first and only RAID array, no prior experience with them, kind of outside my comfort zone with this one. System specs: Asus Z170M-Plus Intel i5 6600K 16gb DDR4 GTX1070ti 500gb SSD 2x 3TB in RAID1 using Intel RST Win 10 Pro x64 TL;DR RAID1 reports one failed drive, 2 new drives ordered, before installing new drives the second drive in the array also fails but seems saveable. After possibly saving the volume windows sets the dirty bit forcing CHKDSK check which might further damage the already compromised array. Plan is to get the array up and running with only one of the new drives then running CHKDSK to clear the bit after which proceeding with rebuilding array with second new drive.

Huh, didn't even know that this was an issue in some countries. At home I pay for 100mb down and 20mb up, I get 98-99mb down and 19-20mb up, this is also really consistent, never have I seen a dip below 80mb down. I also got the same speeds for my phone's LTE and those occasionally dip quite a bit but that's because of reception strength. In my opinion advertising up to speeds is just a shitty way to sell connections to people, so these new rules are certainly a step in the right direction.

Yeah not surprising. AFAIK PUBG's game engine is made by Epic and Bluehole use it under license, probably not the smartest idea to sue the people who made and licensed the engine for your game.

This tick almost all of the boxes for me, almost. No headphone jack is a HUGE dealbreaker, Google could make a quantum processor equipped phone with a 1TB SSD and 64GB RAM, slap a pricetag of $99.99 on it and it would still be useless if it didn't have a headphone jack.

Wait Norway got vega 64 for 626USD launch and 754USD with the 2x game bundle? I thought Norway was supposed to be expensive... Here in Finland we got a lovely 899.79USD launch price on the black edition, no idea what it's gonna be later as the site I'm looking at is still only listing launch stock which they have at -8. Oh and the same site has 1080 at 702.43USD and the 1080Ti at 877.01USD. So AMD is selling their Vega 64 Black edition at a higher price than Nvidia is selling their 1080Ti here in Finland.

So google made fun of apple and then made a phone that looks identical to the iphone and slapped a 1000€ price tag on it... Maybe I'll get the Apple Nexus next year for 399€.

I want one just so I could open it up and see what makes it tick, it has to have some sort of OS and internal storage and I don't think Nintendo really put any effort in securing any of it. So hacking one to play all NES games could be possible. Wouldn't be surprised at all if all it was is an ARM board with maybe 64MB of NAND, that would be very easy to work on.

Yeah I see your point but I'm still very disappointed, with both performance and price (the 480 costs 309.94USD here), guess I just let the hype get to me.

The 480 just appeared on local webstores (Finland). It costs exactly the same as a GTX970 (comparing cheapest of both), so there's absolutely no point in buying the 480 if you're from Finland. Such a shame too, was really rooting for team red.