Frequently 0x0A error when first boot of the system


  1. Posts : 4
    Windows 7 Ultimate x64
       #1

    Frequently 0x0A error when first boot of the system


    My PC frequently 0x0A error when its first boot in system. It happen before it show the account selection, the page for me to click on my account and enter the password.

    I have tried update my display card driver, windows update is on.
    I also done the sfc /scannow, it return some file is damaged but can't be fix. I have uninstalled the related windows update but it still the same. Please also see the CBS log.
      My Computer


  2. Posts : 26,863
    Windows 11 Pro
       #2

    Hello, edmondhk. If you would, I need your detailed system specs

    Please fill out your System Specs

       Information
    Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

    If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

    I looked at your last 5 dump files this is what they said. Each was one or the other.

    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {10, 2, 0, fffff80004c5e509}
    
    *** WARNING: Unable to verify timestamp for kltdi.sys
    *** ERROR: Module load completed but symbols could not be loaded for kltdi.sys
    Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+24f )

    Code:
    Followup: MachineOwner
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 0, fffff80004cd4cd6}
    
    Probably caused by : tcpip.sys ( tcpip!IppRestructureHashTableUnderLock+39 )
    
    Followup: MachineOwner
    NETIO is a windows file provided by windows update that controls all network I/O operations.

    tcpip is another windows update file that deals with networking. It seems to be network related and either failed updates or corrupted ones.

    Please open installed updates from Windows update and see if you have either of these Windows updates. I know you said you uninstalled an update, but make sure both of these is uninstalled. KB3022345 and KB3068708. Then please run sfc /scannow again from an elevated command prompt.You may have to run it 3 times with reboots in between each time.

    I would also update yout Lan driver from your motherboard's web site. Try that and let me know how it goes.
      My Computer


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

    essenbe said:
    Hello, edmondhk. If you would, I need your detailed system specs

    Please fill out your System Specs

       Information
    Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

    If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

    I looked at your last 5 dump files this is what they said. Each was one or the other.

    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {10, 2, 0, fffff80004c5e509}
    
    *** WARNING: Unable to verify timestamp for kltdi.sys
    *** ERROR: Module load completed but symbols could not be loaded for kltdi.sys
    Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+24f )
    Code:
    Followup: MachineOwner
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 0, fffff80004cd4cd6}
    
    Probably caused by : tcpip.sys ( tcpip!IppRestructureHashTableUnderLock+39 )
    
    Followup: MachineOwner
    NETIO is a windows file provided by windows update that controls all network I/O operations.

    tcpip is another windows update file that deals with networking. It seems to be network related and either failed updates or corrupted ones.

    Please open installed updates from Windows update and see if you have either of these Windows updates. I know you said you uninstalled an update, but make sure both of these is uninstalled. KB3022345 and KB3068708. Then please run sfc /scannow again from an elevated command prompt.You may have to run it 3 times with reboots in between each time.

    I would also update yout Lan driver from your motherboard's web site. Try that and let me know how it goes.
    Thank you sir, I will try to deal with my NIC, which is a boardcom one.
    I have also updated my PC spec.
      My Computer


  4. Posts : 26,863
    Windows 11 Pro
       #4

    Check your Windows Updates too. Both of those are Windows Update files. It could be a corrupted OS or a bad network driver. Also, I see you have a Gigabyte Motherboard. If you have any of the Gigabyte Utilities, I would uninstall every one of them. Gigabyte utilities are known to cause BSODs.
      My Computer


  5. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #5

    Just noticed.

    From system specs.

    PSU Antec EA380
    Recommended min. for Graphics Card MSI NVDIA GTX660 is a 450W.
      My Computer


  6. Posts : 8
    W10, 8.1
       #6

    Kaspersky driver kltdi.sys caused at least 1 bsod . it can be seen in first code box.

    update Kaspersky programs or remove them using removal tool. I would go for removal - Service articles

    tcpip.sys and netio.sys are Microsoft networking related drivers. neither is at fault here nor is either corrupted nor is os corrupted (if so, 0x109 kernel corruption bsods would be the order of the day). tcpip.sys and netio.sys are just defaults here, just like other ms drivers that show up in dumps are.
      My Computer


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

    Dear all,

    I have update my boardcom NIC driver, remove KB3022345 and KB3068708.
    Now I get my sfc clean. Now see will it happen again in tormorrow.
    Thanks you all for your kindly help.
      My Computer


  8. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #8

    Unfortunately, It happen again.
    Here is the fresh dump
      My Computer


  9. Posts : 26,863
    Windows 11 Pro
       #9

    edmondhk, this is what your dump file said

    Code:
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {10, 2, 0, fffff80004c6c509}
    *** WARNING: Unable to verify timestamp for kltdi.sys
    *** ERROR: Module load completed but symbols could not be loaded for kltdi.sys
    Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+24f )
    Followup:     MachineOwner
    kltdi is your Kaspersky Network Filtering, NETIO is the Network Manager. You arte obviously having some kind of network problems, possibly caused by your illegal operating system.

    You have an OEM_SLP version of windows from an HP computer installed on a Retail Gigabyte motherboard, which is not possible without a hackers exploit to make it activate. A hackers exploit alters system files which will eventually cause problems.

    Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.





    My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them
      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 03:05.
Find Us