Hey guys, let me start from the beginning.
About a month ago I upgraded my PC with new parts and it ran fine for about 2 weeks, and then suddenly the both monitors would go black, flash for about 2 seconds and take me back to the log in screen. When I log back in, every program I had open has been closed and my second monitor is no longer being recognized and I have to reboot. If you are familiar with the "graphics card drivers has stopped working" process, thats exactly how it looked like, and it even has that USB sound thing, except it logs me out and closes all programs down.
I did not think much of it and nothing else happened for about a week and it happened again, and again, this time more frequently, so far about 3 times this week. This even happens during usage, like while im playing a game or browse the internet.
This just happened again, and every time this happens, I check the Event Manager and the same error shows up. This time however it never took me back to the log in screen, instead it just outright froze my computer during the black screen and I had to force reboot.
Things I have done: I ran memtest for about 3 hours, nothing came out of it, safe to say its not memory related. Completely uninstalled graphic drivers in safe mode and reinstalled it. All this I assume its something to do with the graphics. I have not done a format (I reinstalled windows 10 clean when I set up this new computer).
Screenshot of the Device manager:
Is that icon in the Graphics card supose to be there?
Event Manager:
I got this graphics card this year so its relatively new. I never had this issue on my older computer that I had this graphics card in for 5 months maybe? It only started in this new setup about a few weeks in.
I very much would love some support on this matter. Thank you for reading.
Edit:I forgot to mention, as of right now Im running "sfc /scannow" to check if it gives any error for dwmcore.dll.
Edit 2:The "sfc /scannow" finished and i got this message:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windirLogsCBSCBS.log. For example C:WindowsLogsCBSCBS.log. Note that logging is currently not supported in offline servicing scenarios.
The log is super long, a quick search found nothing about dwm, do you want me to pastebin the log?
Edit 3:I have not updated to the Anniversary Update yet, do you think that might fix it by fixing the files, if its related to that?
I'll just comment on this: many have a variety of new problems you don't want after the upgrade, widely reported if you search. MS is working on some of these.Edit 3:I have not updated to the Anniversary Update yet, do you think that might fix it by fixing the files, if its related to that?
As you have Pro, defer the upgrade for now.
I don't know what disk you have, but to deal with basics, do this please:
From an admin command prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Make sure the result is clear or fixed.
Post back the result, which you can get after a restart as follows:
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
Look at your cbs.log - you may see failures related to opencl.dll - this is a long-standing bug.
If you have other errors, please quote a sample. Look for 'error' or 'failed' not dwm. Some recommend running sfc /scannow a couple of times more before proceeding with further recovery methods (DISM command and in-place upgrade repair install).
Hey man thanks for the reply. Sorry I should had added my disks, My windows are on an SSD, does the chkdsk work on SSDs?
What I have done since my last edit: Updated to Anniverysary Update, seems to be going fine so far.
Checked for BIOS drivers, I was a few versions behind, updated all that to latest, some of the changelogs improved the PCI graphic card slot I believe, that might fix it im not sure. I guess I will report back if it happens again. I will wait for a clean windows 10 if it happens again.
Thats all the errors I had, if you look at the screenshot I linked in the OP. The previous ones below the dwm ones were hours before that, doesnt seem related.
Ok, your new copy of Windows should mean sfc /scannow should pass, of course, except maybe for opencl.dll.
Chkdsk is a check on file system structure so whilst failure mechanisms based on hardware will be entirely different, and likely to be less probable I'd have thought on SSD, still worthwhile. And much faster than with a HDD of course.
Good you've updated the BIOS- a very few people have found that an issue with the upgrade.
Assuming you've got a working situation, now's the time to consolidate and start using disk imaging routinely, if you haven't already.
Yea all my important stuff are being backed up so im good on that front.
I will run the sfc scan and chkdsk and see how that goes. Hopefully it has fixed itself.
Thanks
Edit: sfc scan finished with no error, unlike the last time. Looking good!
