Enabling TCPIP6 service causes 0x0000000a BSOD on boot


  1. Posts : 3
    Windows 7 Ultimate x64
       #1

    Enabling TCPIP6 service causes 0x0000000a BSOD on boot


    I've been trying to fix some problems I've had for a while in 7, and this one has me stumped.

    Any time I enable the TCPIP6 service through the registry, I get a 0x0000000a BSOD on restart.

    When I enable it and try to start it via the command line (net start tcpip6), I get the following entry in Event Viewer:

    Code:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
     <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> 
     
     <EventID Qualifiers="49152">7000</EventID> 
     
     <Version>0</Version> 
     
     <Level>2</Level> 
     
     <Task>0</Task> 
     
     <Opcode>0</Opcode> 
     
     <Keywords>0x8080000000000000</Keywords> 
     
     <TimeCreated SystemTime="2010-09-04T03:57:40.295616800Z" /> 
     
     <EventRecordID>11278</EventRecordID> 
     
     <Correlation /> 
     
     <Execution ProcessID="468" ThreadID="5428" /> 
     
     <Channel>System</Channel> 
     
     <Computer>Powerhouse-PC</Computer> 
     
     <Security /> 
     
     </System>
     
     
    - <EventData>
     <Data Name="param1">Microsoft IPv6 Protocol Driver</Data> 
     
     <Data Name="param2">%%2</Data> 
     
     </EventData>
     
     
     </Event>
    And I get the following message via the command prompt:
    System error 2 has occurred.
    The system cannot find the file specified.
    Stumped here, any ideas?



    *EDit* jcgriff2 files attached. Couldn't do a performance monitor report, it errored out.

    Windows 7 Ultimate x64 (Not upgrade, not OEM/VLK)(OS Reinstalled 6 months ago)
    Q6700 processor, 6GB RAM
    Last edited by BrentNewland; 04 Sep 2010 at 00:54.
      My Computer


  2. Posts : 62
    Windows 7
       #2

    It could be your network drivers are broken...
    Try to reinstall your network drivers.

    Also you might want to try to restart TCP/IP Protocol: How to reset Internet Protocol &#40;TCP&#47;IP&#41;
      My Computer


  3. Posts : 3
    Windows 7 Ultimate x64
    Thread Starter
       #3

    I reset the TCP and the IP interfaces, and reset the winsock catalog. Updated to the latest driver available (WNDA3100v2) and still no dice.

    *Edit* Attached a Process Monitor log of when I ran "net start tcpip6" the latest time. Needs to be opened with Process Monitor.
    Last edited by BrentNewland; 04 Sep 2010 at 16:48.
      My Computer


  4. Posts : 62
    Windows 7
       #4

    If there is a BSOD, Than you got to have a mini dump...
    Mini dump files are files created before your system crash...

    Mini dumps can be found in this folder: c:\windows\minidump Or C:\Windows\LiveKernelReports\WATCHDOG

    Archive them into zip and upload them here.
      My Computer


  5. Posts : 3
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Nope, checked both spots and even did a search on the entire drive, only 2 Windows crash dumps and neither one is from the right time period. Remember, the BSOD happens at boot during driver/service loading, it's probably happening before windows has loaded the tools needed to catch a crash dump.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:26.
Find Us