Windows 10: sudden BSOD, PC is like 1 week old

Hi, I ran to a BSOD with my 1 week old pc yesterday.


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b 0x00000000c0000005, 0xfffff80136520d1e, 0xffffe780c558f920, 0x0000000000000000. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 044aed0e-81b3-4f96-bda7-ba9db529a25b


Here is the dmp file: Here

:)

 

What is causing sudden BSODs

In the past week or 2, I've gotten 3 BSODs. This is unusual for my lapotp that's gotten maybe 2 others in it's whole life (around 4 years). All 3 of these errors occurred while I was using the computer doing normal things such as browsing chrome.

1st bsod: kernel security check error

2nd bsod (~5 days later): kernel security check error

3rd bsod (~10 days later): unexpected store exception

This is an HP Dv7t-7000 laptop running windows 10 build 1607.

Things that changed in the system before BSODs started occurring:

1. A week or so prior to the first bsod, I upgraded my ram from the stock 8 GB, to 16 GB purchased from here. 1 pass of Memtest86 (6 hrs long) comes up clean.
   
2. A few days prior to the first bsod I hooked up this new usb 3 hub. It has been functioning as expected, and one of the kernel security check errors happened while not connected to it.
   
3. A week or so prior to the first bsod I took apart the whole laptop to replace the screen which had been broken. After putting it back together it unexpectedly shut off twice within 30 mins of each other and wouldn't come back on until I reseated the ram (old 8-gig sticks at the time). After that there were no more unexpected shut offs and I assumed I had put the ram in poorly or something
   

Events from the System category of Event Viewer surrounding the last bsod (unexpected store exception):

1. Error ~2 minutes before bsod: "The Delivery Optimization service hung on starting"
   
2. Two Informations right before bsod:
   
   --The access history in hive \??\C:\Users\blain\AppData\Local\Packages\SpotifyAB.SpotifyMusic_zpdnekdrzrea0\SystemAppData\Helium\User.dat was cleared updating 26 keys and creating 2 modified pages.
   
   --The access history in hive \??\C:\Users\blain\AppData\Local\Packages\SpotifyAB.SpotifyMusic_zpdnekdrzrea0\SystemAppData\Helium\UserClasses.dat was cleared updating 14 keys and creating 1 modified pages.
   
3. Two identical Errors on startup after bsod:
   
   --The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
   {C2F03A33-21F5-47FA-B4BB-156362A2F239}
   and APPID
   {316CDED5-E4AE-4B15-9113-7055D84DCC97}
   to the user BLAINE-WIN-10\blain SID (S-1-5-21-347453058-3377039792-1896365341-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-1861897761-1695161497-2927542615-642690995-327840285-2659745135-2630312742). This security permission can be modified using the Component Services administrative tool.
   

UPDATE: 2 days later, another kernel security check error has occored when waking it from sleep mode. Here's the dump file. Worth noting that I tried reseating the ram before rebooting it and it wouldn't post. I reseated it again, and it started working fine.

UPDATE: 9 days after the last BSOD, and still going fine. Maybe reseating the ram fixed it

 

Unlink an old android phone from my pc

I go thru the suggested steps: Start - Settings - Phone - Unlink this PC.

When I first open the "your phone" screen the old phone is listed. Not sure if the phone listed is suppose to be selectable or not, but my is not. When I select "Unlink this PC" the phone listed is removed. When I select "Add Phone" the old phone still
shows. I have removed the old phone from my Microsoft Account. I have rebooted after unlink this pc but I still cannot remove my old phone.

 

Windows 10 1 week old PC 100% disk usage at 10+ MB/s

Hi Pention,

This issue usually occur when there is something wrong with the hard disk; it's either been damaged, or faulty. It usually happens when there's been some sudden activities such as hard reset, then it would get damages to some extend. Check your hard disk's
Original Equipment Manufacturer as they should have a diagnostic tool to check its health with.

In the meantime, as an initial troubleshooting we suggest that you run
chkdsk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
• Type chkdsk x: /f, where x: is your drive, the /f command will fix errors found on the disk.

Let us know if you need further assistance.