Windows 10: Event ID's associated to BSOD 7001, 7000 & 1000

Since the upgrade to WIN 10 from WIN 7, I have continually gotten these errors following a BSOD. I am not 100% sure what to do to "fix" these errors since they happen quite frequently, sometimes 2 or 3 times a day sometimes things will be fine a a week or so.
Under the Event Viewer, Windows Logs, System it shows a total of 4,698 errors I have only been focusing on the red ones which are 7001, 7000 and 1000.
Error code for 7001 - The NetTcpActivator service depends on the NetTcpPortSharing service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Error code for 7000- The VBoxAswDrv service failed to start due to the following error: The system cannot find the path specified.
Error code for 1000 - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000010, 0x0000000000000002, 0x0000000000000001, 0xfffff803218db924). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 139d5ded-2b48-43e5-96cc-1fa3e6a87d06.

Also I keep getting an error related to Kernel PnP, I have no idea how to even approach that:
L: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
L: - <System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-06-18T04:31:19.829491700Z" />
<EventRecordID>1520</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="200" />
<Channel>System</Channel>
<Computer>Anastasia-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
L: - <EventData>
<Data Name="DriverNameLength">124</Data>
<Data Name="DriverName">SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_HP&Prod_c310w&Rev_0119#047F33C6A426543432CE95C1&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WudfRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>

Attachment 95576
I could really use help with this, thank you!*Smile*Smile*Smile

:)

 

Event ID's lead to BSOD 7001, 7000 & 1000

Since the upgrade to WIN 10 from WIN 7, I have continually gotten these errors following a BSOD. I am not 100% sure what to do to "fix" these errors since they happen quite frequently, sometimes 2 or 3 times a day sometimes things will be fine a a week or
so.

Under the Event Viewer, Windows Logs, System it shows a total of 4,698 errors I have only been focusing on the red ones which are 7001, 7000 and 1000.

Error code for 7001 - The NetTcpActivator service depends on the NetTcpPortSharing service which failed to start because of the following error: The service cannot be started,
either because it is disabled or because it has no enabled devices associated with it.

Error code for 7000- The VBoxAswDrv service failed to start due to the following error: The system cannot find the path specified.

Error code for 1000 - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000010, 0x0000000000000002, 0x0000000000000001, 0xfffff803218db924). A dump
was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 139d5ded-2b48-43e5-96cc-1fa3e6a87d06.

Please help, WIN 10 in not the best experience so far :-/

 

Event ID's lead to BSOD 7001, 7000 & 1000

Read the Wiki.

 

Hi stacchz,

Welcome to the 10forums *Smile

Please note, only the red onces in the event logs are errors, any others are information event logs.

For the 7001 event, I would suggest to create a new thread at the General Support forum.
In the BSOD Crashes and Debugging forum we focus on BSODs only, rarely do we also handle restart/shutdown/freeze crashes but usually only when they are mixed with BSODs.

For the 7000 event, the driver 'VBoxAswDrv.sys' is from Avast. I would suggest to download the Avast uninstall tool to get rid if left behinds *Arrow Avast Uninstall Utility | Download aswClear for Avast Removal

For the BSOD event, the last one was on the 22th of previous month, unless you experience new BSODs anytime soon I do not see a reason to worry about it *Smile

 

I have had 2 BSOD today...

 

Then please upload a new zip created by the DM Log Collector, with the zip from the 11th we cannot provide help for recent BSODs.

 

one more question, Somehow I changed the parameters to only include up to the 22nd, how do I undo that date restriction? I have had many more BSOD's but they are not showing because of the change I made. *cry

 

Be more specific, what parameters?

 

When i was giving myself, the administrator, full control of the files i accidentally restricted the minidump file to only read between the first of June and the 22nd of June. I retraced my steps as best i could in order to be able to pull the whole dump file and it still only pulls through the 22nd of June.

 

Also i installed the uninstall tool for avast and it did not remove all the files. so I went in and tried to delete any and all folders that had anything to do with avast will that be good enough?

 

Usually while playing video games of some sort...World of Warcraft, etc.

 

In fact all the errors I get are during gaming

 

First off, you don't need to take control of those files in that folder. Simply copy/paste the files to a different location via command prompt or something.