Windows 10: 2 BSOD's on a 24x7 system ever since Win 10 upgrade on August 11, 2015

Ever since upgrading to Windows 10 from Windows 7 Home Premium on August 11, 2015, I've experienced 2 BSOD's which I am attaching which appears to be when the system is very slow like it's out of resources with 16GB RAM with 90% utilized, hopefully someone can point me in the right direction.

:)

 

Windows 10 update 1511 installed twice in my P C

My Toshiba Laptop having Windows 7 Home Prem. 64 bit O S was upgraded to Win. 10 in first week of August 2015.

I also received Cumulative Update for November 1511 for 64 bit system [ kb 3105211] and installed on 18-11-2015.

But surprisingly, the same update [ kb3105211 ] was again installed on 18-11-2015.

Further, update [kb 3120677 ] was first installed on 25-11-2015 and again that update was installed on 26-11-2015.

I would be glad to get any help or guidance. Please note that I am simply a user and not a technologist.

 

Windows 10 failed to install - How do I fix this?

I also have this problem: 0xC1900101 - 0x30017 First Boot Failure

That is the error message displayed when Windows 8.1 is restored after the failed upgrade. The BSOD message from Windows Update is "Page Fault in Non-paged Area"

Here are the things I've tried:

• chkdsk c:
• sfc /scannow
• dism
• shut off all non-MS services
• update nVidia driver
• update all motherboard/chipset firmware
• update all motherboard/chipset drivers
• update mouse driver
• update usb drivers
• update SATA drivers
• turn off system paging!
• turn off Norton Firewall and Antivirus
• install from USB key and install over the network
• Uninstall Samsung Magician SSD Management software
• Update August 2, 2015: Disconnected most USB devices
• Update August 2, 2015: Disconnected all SATA devices except the boot drive to be updated
• Update August 2, 2015: Disconnected second monitor
• Update August 2, 2015: Tried the "reboot interrupt" process suggested below by Arkfyre
• Update August 5, 2015: Uninstalled Norton Internet Security
• Update August 5, 2015: Shut down all networks
• Update August 5, 2015: Changed Motherboard settings to "UEFI Only"
• Update August 10, 2015: Turn off overclocking
• Update August 10, 2015: Installed all optional Windows 8.1 updates
• Updated August 11, 2015: Disabled ASUS Driver for Broadcom WiFi

None of these things had an effect on the problem.

 

The first crash was caused by the Nvidia Video driver
Kernel security check failure crash
Code: 5: kd> lmvm nvlddmkmstart end module name fffff801`b5520000 fffff801`b600f000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Fri Aug 07 05:19:41 2015 (55C423CD) CheckSum: 00AAF86B ImageSize: 00AEF000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] The second crash was caused by the USB Serial Port driver
Memory management
Code: 2: kd> lmvm ftser2kstart end module name fffff800`ad550000 fffff800`ad569000 ftser2k (no symbols) Loaded symbol image file: ftser2k.sys Image path: \SystemRoot\system32\drivers\ftser2k.sys Image name: ftser2k.sys Timestamp: Thu Oct 22 17:09:05 2009 (4AE07591) CheckSum: 0001DDAA ImageSize: 00019000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Have you get these crashes more often?

 

You might want to reduce your startup items in the taskmanager, there are tons of startup items.

 

Thanks, nVidia driver has been updated twice at least. Not sure what manufacturer provided the 2nd driver. Those are the only two BSOD's I've seen when I was on 16GB of memory which was 90+% utilized and only happened when I opened more than 70 tabs in Google Chrome instead of the usual 60 which causes the system to be slow and unresponsive. After going to 24GB, haven't seen any BSOD's yet as memory is 52% utilized, I have Process Hacker running all the time.

Update:
It seems the USB Serial Driver only crashed once as it's a device I plug-in to transmit for a survey scanner for Nielsen Consumer Panel that I plug in once a week on Saturday for a few minutes, it works every time except for that one time when it BSOD and it works correctly today without BSODing either.