Windows 10: YouTube Crashes My Computer In Full Screen Mode

After trying some things (that didn't work) that seemed like they would work I decided to ask for help. I have two monitors, a large 1080p one which is plugged into my graphics card and a smaller 4:3 VGA monitor for secondary tasks that's plugged into my motherboard. Although I have not tested this issue with other video streaming services, it seems that YouTube (although it could be other services as well) will crash whenever I put a video in full screen mode on my larger (primary) monitor.

That being said, my computer will NOT crash when I use full screen mode on my smaller, secondary monitor.

My computer also does not crash while playing/using any games or programs in full screen, with the exception of WildStar (more on that later).

I have gone through device manager and searched for every update I could find for my devices, and I have also ran through GeForce Experience to update my video drivers as well, so none of my hardware is out of date.

I have tried disabling certain devices to see if there was an issue with those (I had gotten some new peripherals at the time) and it has not fixed the problem either.

I have ran a memtest through windows, and although most people say that memtest86 (or whatever it's called) is more reliable, I figured that since the windows memtest came clean, and an issue with RAM causing a blue screen just from YouTube, I decided that it would be extremely unlikely that RAM would be the issue since I can run pretty much every program I have just fine in full screen.

Like I said earlier, the only other thing I have a problem with is a BSOD with WildStar. I thought I would include this information because I have no idea if the attached file will have any sort of information dealing with the dump files caused by that game rather than YouTube. It would be interesting to know whether or not the crashing from WildStar and YouTube are caused by the same problem, because then I could kill two birds with one stone. *Smile

The only other option that I haven't tried yet for reasons I am willing to explain, is updating my BIOS. I have seen limited, but some information that tells me this could be a possible fix. A serious thank you to anyone willing to provide any help!

:)

 

YouTube not playing in IE11

Update (to update) . . .

Well, I just made a little discovery.

It seems that the 'glitched screen' I mentioned in my previous message only occurs if:

I enter 'full-screen mode' from a *maximized* YouTube window.

If I command YouTube to enter 'full-screen mode' from a non-maximized window, then I see no glitch, and it looks the way I would expect it to look.

But understand, that just a few days ago, I had no problems whatsoever watching YouTube videos under *any* circumstances.

*

 

Nokia N79 v31.0.101 Bugs/Fix/Errors (Please Post Them Here)

Major bug in v31.002. Youtube videos won't play in full screen mode.

 

The latest dump indicates a problem with ddkmd.sys.

Code: *** WARNING: Unable to verify timestamp for ddkmd.sys *** ERROR: Module load completed but syAmbols could not be loaded for ddkmd.sys Probably caused by : ddkmd.sys ( ddkmd+1192f )[/quote] This seems to belong to Osbase iDisplay software. Current installed driver is dated Tue Aug 11 14:23:52 2015.
A newer version is available dated 5/23/2016, give it a try (from above link).

 

This seems to belong to Osbase iDisplay software. Current installed driver is dated Tue Aug 11 14:23:52 2015.
A newer version is available dated 5/23/2016, give it a try (from above link).[/quote] Thank you for the response, do you by chance know where I can find the driver so I can uninstall it? I can't seem to locate it on my computer and the wizard will not let me continue without removing the current outdated driver.

 

Could also be from a Belinda USB to VGA adapter.
Or OSBASE WDDM Software developed by OSBASE
Or
- Display Link

- Duet Display (link display iPad <-> PC)

- Twomon (link display iPad <-> PC)

- Other Display link Utillity

 

Aha! I have Duet Display installed on my computer. I haven't used it in a while so I will uninstall it. I also managed to update the driver, and I now get a new BSOD error: PAGE_FAULT_IN_NONPAGED_AREA. Any information that you can provide about this bluescreen would be beneficial while I also look up how to fix this issue. I'm glad I'm getting somewhere though, at least the error changed. I will uninstall Duet Display and report back.

 

Once you uninstall it, the driver will be gone so should not cause any more problems.

 

Sadly, after unintalling Duet Display, re plugging in my RAM, checking if Windows Defender is on, and updating some Windows updates as well as updating that display driver, the newer BSOD error still stands.Attachment 85505 There is an updated version of the log.

UPDATE: I tried completely uninstalling everything related to Nvidia and reinstalling everything, and I got another bluescreen, however, I am almost positive that it said the error was caused by ddkmd.sys instead of what it WAS being caused by (dxgkrnl.sys) but Blue Screen View says otherwise? All of the issues still stand as well, according to Blue Screen View.

 

Should have bumped this to you.

 

OKAY! So after performing a full system malware scan I was able to get rid of 1/3 of the errors I was dealing with, then I noticed that there were still some things left over from the OSBASE display driver. After completely ridding my computer of anything to do with any display driver that didn't belong to the default driver that runs my display, all of the errors are gone and I can finally run full screen again! For anyone dealing with this issue I suggest looking over your drivers for anything that doesn't look like your default drivers, as well as running a FULL malware scan (I used Malwarebytes) to rid anything off of your hard drive (In my case, I performed a custom scan for my SSD and 1TB Hard Drive).

 

Good work on your part.

How did you look over the drivers to determine what should be there and what should not be there?

 

Well I remember when I built my computer, and I also remember (I could also just track) when I installed different hardware, so I looked through my drivers and found the ones that seemed more recent than the date that I set up the hardware that is paired with the driver. It was kinda a guess and check, but there were a couple of things I looked for when trying to find which drivers didn't need to be there, like if they were third party, if they had a website that seemed a little sketch, or if I didn't recognize the company.

 

Hi people! I had a very similar problem. When trying to switch to full screen with various videoplayers I'd get a bsod on my windows 10 64 bit pro installation. After reviewing recently installed apps, chrome remote desktop seemed to have caused the issue and uninstalling it has solved the issue for me. Maybe this info will help someone!