Morning All, I am having what appears to be an unusual problem with my Windows 10 system that I think Firefox is responsible for causing. Firstly, we recently moved office about two weeks ago and as part of that process, we have switched from Australia's National Broadband Network (NBN hybrid fibre to node network) to a full fibre optic Internet connection which is supposed to be much faster. However, since the move, I have noticed that my connection speed seems to be much slower on Firefox particularly when launching, often having to wait upwards of a minute and a half for Firefox to launch and load my home page (Google) and also similarly slow when loading additional tabs or new pages. Not only is Firefox slow in this but it also causes the entire system to hang while it is loading pages. Further to this, since about last Thursday, I have been having trouble with my Windows 10 operating system. I started the system to get the "mbr not found" black screen and after about two hours, I eventually go the system to boot. I had initially suspected an SSD failure so I booted into Ubuntu to see if I could mount the partition to test if it were working. Ubuntu could not log me in as it reported the Windows was still logged in on the SSD. Eventually I used the Command Line on the system recovery disk to force Windows to log out, fixed the mbr and got back into the system with Firefox still slow and oddly, the system clock was wrong. The system worked fine all day Friday however, this morning, when I started the system it booted normally but when I opened Firefox, it did its usual system freeze and hanging problem and then I got the blue screen with the error message "CRITICAL_PROCESS_DIED". This time however, I when I did the restart, I got the "operating system not found" black screen as opposed to a missing mbr screen. I booted into Ubuntu and got the same Windows still logged in message as I did last Thursday and then moved on to repair the system using the Windows installation disk and oddly again, the system time was incorrect. I then opened Firefox to try and do some research as to what the underlying cause as I was suspecting that it was my SSD on its last when again, Firefox caused the system to hang followed by the "CRITICAL_PROCESS_DIED" blue screen. This happened twice more (once was after I installed a free disk imaging software to back up my SSD which launched Firefox after installation) before I decided to uninstall Firefox to see if that were the cause (I used Revu to rip it out fully). Thus far, it seems to have worked and I have been working off Chrome for the past few hours and it appears to be much faster and not causing the system to freeze or crash. Has anyone else noticed this behaviour? It