Error 0x0000000a caused by ntoskrnl.exe

Page 2 of 2 FirstFirst 12
  1.    #11

    DirectX shouldn't be a problem, the only problems I know potentially caused by DirectX, were related to Stop 0x119's and handling of Fence IDs, however I believe these were patched with Service Pack 1.
      My Computer


  2. Posts : 6
    Windows 7 Home Premium SP1 x64
    Thread Starter
       #12

    i dont see bsod in safe mode
      My Computer


  3. Posts : 17,796
    Windows 10, Home Clean Install
       #13

    Great,
    Use a clean boot, make sure there is still no BSOD. If there is no BSODs, then one by one put your software back. Check each software thoroughly to be sure it is not the cause of the BSOD. Start with the anti virus, that is the most likely candidate
    Troubleshoot Application Conflicts by Performing a Clean Startup
    If you get BSODs in clean boot that indicates that the problem is caused by a driver, that is essential to the operation of your computer, we will have to find out which one.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 08:58.
Find Us