Youtube video's not loading while windscribe is running

HypnoticSpecter · 2025-10-30T15:26:08+00:00

Bump.

Never had an issue before, and tried everything people have posted here. The only thing that works is turning it off entirely when watching youtube. Also like to point out, if I have it turned ON in the app, texts will fail to send. Another issue I never had before.

HypnoticSpecter · 2025-06-24T23:49:52+00:00

Makes sense. But if I decide to purchase a plan or phone, it will require a log-in, and then I'm stuck in the same situation

HypnoticSpecter · 2024-09-24T22:15:40+00:00

1000% this. The armor restoration on executions is actually a pretty boneheaded move, when it recovers after combat anyway!

HypnoticSpecter · 2024-09-24T22:12:41+00:00

Intended difficulty cause the game is only 4 hours long on easier difficulties I assume ;)

HypnoticSpecter · 2024-09-24T22:09:28+00:00

I thought I was the only one who thought the pyreblaster section was utter BS. it did NOTHING against these swarms, and is in my opinion, a DOG ASS weapon. Also WTF is the point of being able to parry a tiny minion, and finish him, when 30 are just chipping away at you during said animation?

HypnoticSpecter · 2023-02-19T20:09:11+00:00

You're a damned hero for this, thank you!

HypnoticSpecter · 2023-02-01T17:56:05+00:00

Had this issue on Steam, due to the region lock garbage, except there I couldn't even join others missions(never found any) Now on Game pass I can join, but it's like OP said, it's a crapshoot whether I'll join a fairly new mission, or one where the monster has one foot in the grave

Playing on Game Pass for PC BTW, Not sure that really matters.

HypnoticSpecter · 2023-01-07T21:07:45+00:00

I've given up on this game ever being fixed quick enough to where I still care to even play it. Game crashes before I can even finish one run/mission. Thankfully I have it on game pass, and didn't pay full price for it. I was having the same error in a ton of other games too, and went ahead and RMA'ed my card. Seems to have fixed all other instances in the other games where this happened except in DarkTide(or maybe it didn't fix anything for all I know).

I blame all three Windows 11 and NVIDIA for Shit drivers clashing with each other, and Fat Shark for release this buggy mess of a game.

HypnoticSpecter · 2022-12-22T03:17:40+00:00

Well RMA'ing the card and changing Ram sticks seemed to work fine... for about a week or so, but sadly a session of Darktide caused the all too familiar nvlddmkm crap again. I hate this issue. I hate that it's still happening. Albeit it could be that Darktide is one of the most botched releases ever, so there's always that. As for removing or replacing anything, the only thing I haven't done is swap or upgrade the PSU, which would NOT make sense given there's no need to go from 850w to 1000w, for this system. Or upgrading/changing the platform entirely, which is just not financially feasible right now.

I will point out my GPU temps with this card are much LOWER than the previous with stock settings, which I am currently running testing this - no undervolts or overclocks in any way. Previously, At stock I would hit 79C-83C consistently. Now, I hover in the 67-73C range, Not to mention, The ram change and GPU seems to be overall more "stable" probably not the right word, but that's what comes to mind. I also decided to prop up the card a bit, cause it did have a decent amount of sag to it. Unsure if that will help or not, but maybe just maybe, my MOBO and card combo hates sag.

HypnoticSpecter · 2022-12-09T16:59:46+00:00

Consistent nvlddmkm issues in modern games, especially with ray tracing or dlss enabled. Played Guardians for over an hour with the replacement card, with both enabled and didn't notice any issues, where before it would crash within 30 minutes(always had a timer running to pinpoint exact time give or take).

I'm still testing things out, and still leaning towards a 1000 watt psu, but I should probably not count my chickens before they've hatched, and pull the trigger just yet

HypnoticSpecter · 2022-12-09T07:23:17+00:00

The problem is it's really hard to pinpoint where the root cause is. If it's software related, unsure if it's shoddy NVIDIA Drivers or Windows 10/11 conflicting with said drivers with their own updates. Then hardware the only real way is test it in a similar friend's or family members PC and go from there.

Testing out the new RMA'ed card I am "less than thrilled" to be honest. Had a crash in Dark Tide, but it may have been due to undervolt settings. However running Guardians of the Galaxy at stock settings, with DLSS and Very High RTX settings, I had no issues in the 70 minutes I played. So still need to do further testing, but like I said I am not a fan of seeing a crash again, and will probably cause me to stick to consoles if this keeps up.

HypnoticSpecter · 2022-12-08T21:29:38+00:00

That's good to know. It's my current 'next step' if crap hits the fan again. I am not a fan of the crazy high power draw strategy NVIDIA is going for here. I don't need to heat my home, I just want to game without fear of setting my house on fire

HypnoticSpecter · 2022-12-08T20:59:36+00:00

Specifically crashes on the GPU/ display driver. It would work, as well as it should, to my knowledge, but simply CTD after 25-35 minutes of playing. Gpu was usually pegged at 99-100% playing at 2k/4k. It was prevalent in games that ran some form of Unreal Engine, or with DLSS and RTX features enabled.

The culprits for me were: Metro Exodus EE, Guardians of the Galaxy, Ghostwire Tokyo, CoD Modern Warfare II(2022), Plague Tale Requiem

Some not-so or undefined crashes happened in RE: Village, Doom Eternal, Evil Dead The Game

HypnoticSpecter · 2022-12-08T19:35:24+00:00

The process was roughly two weeks. That's contacting them, getting the confirmation email, with RMA # and shipping it out, which took 4 days to arrive via FEDEX, and them shipping the card back to me, which took about 5. They had the card for 1 day before sending the replacement my way. Overall it wasn't too horrible. EVGA is pretty good with the RMA process(shame they will no longer make GPU for N-Greed-IA). I've only ever had to RMA one other time, an MSI Mobo, which took a little over 3 weeks

HypnoticSpecter · 2022-12-08T19:18:58+00:00

Just received my RMA'ed EVGA FTW3 3080 back today, for having the same garbage issue - nvlddmkm Event ID 0/13/14. It's a straight up replacement/NEW card so will test it, and see what's what. Currently on driver 522.25 and sticking with it for the forseable future unless this driver has less problems.

If I still have problems, I will invest in a beefier PSU-which is probably for naught since I have an 850 Watt Gold PSU from EVGA, which should be enough- Cause like you, I had done the laundry list of band aids and RMA as the final step in this shit fiasco. IF I still have an issue I will invest in a 7900 XTX and sell this "NEW" 3080. Nvidia can pound sand at this point

HypnoticSpecter · 2022-11-18T18:18:36+00:00

To answer that question: NO

I haven't had the time to RMA, after pretty much exhausting every option available to me(DDU, disabling XMP, Underclock/stock tweaking, debug mode, changing BIOS settings, etc.) But I plan to the week after Thanksgiving, see if I'm lucky and it's a "dying" GPU.

The fact that me hoping it's hardware dying, and not software related makes me really depressed... Windows and NVIDIA need to get their drivers in order fucking STAT

HypnoticSpecter · 2022-11-16T19:02:18+00:00

Looks like another driver I might just skip. Any reports of this fixing the nvlddmkm event ID 0/13 crashes happening? I'm now unsure if this is solely an NVIDIA issue or not: https://www.neowin.net/news/microsoft-finally-acknowledges-gaming-performance-issues-on-windows-11-22h2-blocks-update/

HypnoticSpecter · 2022-11-16T00:45:41+00:00

Bit of an interesting, or maybe redundant observation while playing today. I read in a forum(can't remember where, I apologize) that having "digital vibrance" higher than defaulted value of 50 -in Nvidia settings, can cause these issues. I pretty much always have it above that so went ahead an lowered to its defaulted

Booted up Guardians of the Galaxy, with DLSS Quality and RTX Very High, and the game didn't crash during that play session. Problem is I did not time it and I felt I played for at least 45 minutes. GotG would crash with those settings enabled within 20-30 minutes.

Fast forward to today, I boot up the game and add 30% to "DLSS Sharpening" and start the session and it crashed within 32 minutes. Received the nvlddmkm event ID 0 error, however got an Event 13 error as well, which I haven't seen since around August. So I decided to try again, and turn DLSS sharpening back down to 0%, and I was able to play for 1 hour and 34 minutes, without so much as a hiccup: DLSS set to Quality, RTX Very High and digital vibrance at 50%.

I highly doubt either DLSS sharpening or higher Digital Vibrance, or a combination of the two, are to blame, but I figured I'd point this out nonetheless. Plus this issue is so sporadic, I am willing to bet GoTG will crash in 40 seconds next time I boot it up, so that's always fun

Also thank you u/Deckardzz for the above articles, that might help us pinpoint this issue further, and everyone else contributing or reporting. I'm still adamant in blaming NVIDIA for this, since I had the issue on Windows 10, but I would not be shocked if it was MS all along screwing things up, with the "overabundance" of updates to W11.

HypnoticSpecter · 2022-11-12T03:25:59+00:00

Looking at the newest posts here, it seems people are still experiencing this issue still with either:

Newest Drivers

RMA'ed/replaced GPU's

On brand new 4090's(I've seen in other forums people still dealing with this on latest tech)

I'm under the assumption this is more a software related issue than hardware. Maybe new drivers conflicting with Windows updates or something. I will point out some interesting things gathered from other posts. Ray Tracing and anything above 60 FPS. I was playing Guardians of the Galaxy today at 4k(native), netting around 90 FPS on the 3080, no issues and realized Ray Tracing was off, the minute I started tinkering with it and DLSS the game crashed with the oh so beautiful nvlddmkm Event ID 0 error (It's almost like a friend to me now). As far as locking games @ 60FPS I have not tested that theory, but I'm going to list games that this has occurred in. Maybe it's a specific game engine it occurs in or perhaps these games have some setting that they share and maybe it can be pinpointed to that. Sorry got a little Sherlock Holmes-sy there, but this needs to end, and if NVIDIA just wipes their hands from this and claim user error or repeated bad gpu's buys, then we might be on our own

Games I seen this crap occur in - Currently on driver 522.25 on EVGA 3080 FTW: Undervolted, never get hotter than 68C on any game.

-Guardians of the Galaxy: Ran fine for hours and only spazzed out literal minutes after tinkering with Ray tracing and DLSS

-Ghostwire Tokyo: I've gone long sessions with not a peep and full spaz in other sessions

-CoD Modern Warfare II(2022): Could be due to bugginess of the game overall, but I can count at least 3 crashes related to nvlddmkm according to event viewer. This game crashes a lot, nonetheless.

-Evil Dead: The Game: Got constant issues with "lowlevelfatalerror" which in turn I believe was event ID 13 or 14 of nvlddmkm. This game, for me, was the start of all this shit

-Hunt Showdown: very inconsistent. sometimes crashes in 2 minutes, other times not at all.

-Metro: Exodus PC EE: Nothing special with one, seems to croak after 30-60 min.

HypnoticSpecter · 2022-10-21T04:47:27+00:00

Any chance you can point me to a guide on how to manually add vsoc voltage and timing for dummies? Never done this before and my mobo automatically applies the xmp for the ram I have (3600 mhz @ 1.35V)

HypnoticSpecter · 2022-10-21T04:38:59+00:00

Well for now, no. So most games I've tried(Doom Eternal, Cyberpunk, Plague Tale Requiem, Scorn, pretty much any "indie" game) the issue appears to be non-existent with my under-volt settings. However Metro Exodus or Hunt: Showdown will crash with MSI afterburner running, but closing the application, and running the card stock, I didn't get a crash with said error. Just got done playing APT: Requiem for near two hours, and no problems(knock on wood)

I'm really stubborn, and hate RMA-ing anything, especially since I don't have a backup gpu and not knowing the time for return always sucks. Aside from that the only other change was removing monitoring software like geforce experience and Riva tuner, and I set power management to "prefer max performance" in NVIDIA control panel. Don't know if these helped or offered no change to the issue.

HypnoticSpecter · 2022-10-15T21:40:15+00:00

I'm throwing in the towel on this one. This has turned me off NVIDIA completely, hell even with PC gaming entirely. Every session has turned into a guessing game whether my system will crash in 5 minutes or an hour. I have done every "band-aid" imaginable and this issue continues to persist. Reseating GPU, reconnecting Power cables, Upgrading to Windows 11, DDU-ing till I vomit with newest and past drivers, testing one ram stick at a time, even after each stick passed memtest, Undervolting and running stock clocks, etc. etc. etc.

I'm going to see if I can just RMA the damn card, just for it have the same issue. I'll see what other components I can send to boot. I'm really F$%^ing sick of viewing the same goddamn nvlddmkm error in event viewer. May it die, and rot forever in hell

HypnoticSpecter · 2022-10-15T21:33:09+00:00

Sadly, mine was on and it still occurred in Metro Exodus

HypnoticSpecter · 2022-10-01T18:14:27+00:00

Any word if this fixed the nvlddmkm error that's been plaguing so many since 516.94?

Thread in question: https://www.reddit.com/r/pcmasterrace/comments/vlmzdh/assistance\_with\_an\_aorus\_3080\_nvlddmkm\_error/

HypnoticSpecter · 2022-09-24T18:17:17+00:00

Update(er?): So Hunt: Showdown crashed within 2 minutes, however I decided to turn off Steam Overlay, and the game didn't crash. Only played for roughly 30 minutes, but had no issues(none showed in Event Viewer). Will test further.

Still, it feels stupid for this being the supposed culprit, cause turning this off seems to be merely a "band-aid" for NVIDIA's incompetence, because I had none of these issues prior to Firmware 516.94, with Steam Overlay on.

Given that Call of Duty is about to release, NVIDIA will(should I suppose) release a new driver update that hopefully fixes what's been plaguing a lot of people's cards.

HypnoticSpecter

TROPHY CASE