Here is the latest crash report after I switched back to my old account:-
System Information (local)
--------------------------------------------------------------------------------
Computer name: HP
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: HP Pavilion 15 Notebook PC , Hewlett-Packard, 2281
CPU: GenuineIntel Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8516689920 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 15-03-2016 11:35:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031516-27062-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A01F5903ACEA67, 0xB3B72BDF562DA510, 0x1, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 15-03-2016 11:35:05 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A01F5903ACEA67, 0xB3B72BDF562DA510, 0x1, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.