Thank you very much for taking the time to reach the Intel® Communities Team.
I understand you are facing some issues with your system since you are getting BSOD's while the normal use of your computer. I will be more than glad to assist you with this problem you are facing.
I would like to know if you have used this new Motherboard with another known working processor and the same components? In addition, was this processor overclocked? if so, please try using it with the default settings.
Thanks for your replay.
First of all I can work with the system sometimes for several minutes/hours without a BSOD.
The browser Edge doesn't give problems (more or less stable) if I don't get a BSOD of course. Chrome and Inter Explorer are not workable.
I get constantly WHEA-logger warnings. Sometimes every minute.
I did not replace the current processor with a working other one, because I don't have a replacement or spare (too expensive).
We did not use overclocking. Always default motherboard settings (=no overclocking).
I've you need additional information, please let me know.
Thank you very much for your reply and the information provided.
If you do not mind, can you attach a screenshot of the error you are getting? That will be very helpful for me to perform a deeper research regarding this issue.
I first want to give you an update on what I've recently done for testing.
I replaced my memory whit a total other type and brand of memory (I'm sure this memory worked in other devices).
I also replaced my SSD into another working type.
I start-over a clean install.
It get stuck during the Windows 10 installation and I had to start the installation again (two times).
After that I succeed with the installation, but it doesn't mean the system run's well.
Browsers are still crashing and the BSOD's are also still there. Before, during and after I update all the drivers.
I send you some screenshots of BlueScreenView's, Windows EventViewer and Internet Explorer and Chorme crashes.
As I said before, Edge is not crashing but sometimes it get stuck. Youtube viewing has stops while the time-bar is still running.
All tests with the browser are mostly done playing a YouTube file, because that's the fastest way to crash the browser.
I hope this information helps.