BSOD Error on oa002afx.sys, oa002ufd.sys and ndis.sys

Page 2 of 6 FirstFirst 1234 ... LastLast

  1. Posts : 28,845
    Win 8 Release candidate 8400
       #11

    christianb9632 said:
    The most recent BSOD is attached

    Driver verified and Related to vwififlt.sys Virtual WiFi Filter Driver from Microsoft Corporation.

    Since it is an OS file and you have updated to SP-1 I would run a system file check to verify and repair OS files.

    SFC /SCANNOW Command - System File Checker

    How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
      My Computer


  2. Posts : 467
    Seven ultimate 32bit
       #12

    I using WinDbg:6.12.0002 x86 from a xp machine right now..

    Now got ntoskrnl.exe on the last dmp.. What did you get then.??

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C4, {40, 0, fffff98034dc0378, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+7cc40 )

    Followup: MachineOwner


    Advise me how to fix this..

    How do I get the right symbols.
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #13

    SmurofNeves said:
    I using WinDbg:6.12.0002 x86 from a xp machine right now..

    It matters. Do you have the most recent symbol packs?

    Feel free to pm me if you need help
      My Computer


  4. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #14

    Is it helpful if I do the System File Check everytime a BSOD crashes the computer?
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #15

    christianb9632 said:
    Is it helpful if I do the System File Check everytime a BSOD crashes the computer?
    Nope. It usually isnt the system. It is usually a 3rd party driver.
      My Computer


  6. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #16

    @ zigzag3143

    Hello again,

    1st:
    I do not seem to get anymore BSODs, BUT ever since the BSODs started, my computer has gotten VERY SLOW... There are no more 'instant processes' and everything is delayed for about 3 to sometimes 30 seconds (maybe i am going a little over the top ). ANYWAY, is there any way my computer will go back to 'normal speed' (if not better ) or is there any free program that can do this?

    2nd:
    Do you (or anybody) know a good free Driver Software (a software which checks for drivers and updates for devices)?
    I have tried out many, but sooner or later I have to Buy the fulllversion/license key, or they do not display correct information about drivers.

    Thanx again,
    Regards,
    Christian
    Last edited by christianb9632; 15 Mar 2012 at 03:15.
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #17

    Try this Microsoft Fix It for Windows 7: Fix Windows system performance problems on slow Windows computers

    There are a lot of driver software update programs out there. I do not trust them because I have seen many instances (including on my own machine testing one out) where they find drivers for other hardware than what is on the machine being updated. The "update" ends up causing problem devices to occur and can cause conflicts resulting in crashes. If you want help finding driver updates for specific drvers, see Drivers - Windows 7 Forums and start a new thread there asking for the driver update you are looking for.

    That forum may also have experts who can advise a free driver update program (I recommend that you not take the advice of new members, only Gurus), but I imagine you will get the same information from them.
      My Computer


  8. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #18

    Hello,

    I have gotten 2 more BSODs, but somehow i cannot upload the dump files:
    (File not found or no read permission)

    1st BSOD: ndis.sys
    2nd BSOD: UnlockerDriver5.sys

    It's like a chain...
    I think that ndis.sys is destroying all other drivers...
    It all started with ndis.sys, then webcam drivers (OA002Afx/Ufd.sys have caused BSODs...
    After that there were 2 more BSODs caused by ndis.sys and then a few more drivers caused BSODs...

    Yesterday I had a BSOD of ndis.sys... It came when I entered 'Sleep' mode...(I read somewhere that ndis.sys has something to do with Networking, but what does Sleep mode have in common with Network drivers?!)
    And today I had a BSOD from UnlockerDriver5.sys (Unlocker is a software I use to Unlock.Kill processes (to delete files which are open in another program etc.))

    ndis.sys BSOD always seems to come up when I enter Sleep mode on my computer, all other driver problems happen randomly...

    Would it be of use to delete ndis.sys?


    Thanx for everything so far, and I am looking forward to finish this problem
    Regards,
    Christian
    Last edited by christianb9632; 16 Mar 2012 at 00:55.
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #19

    Have you followed the https://www.sevenforums.com/crashes-d...tructions.html to see if the executable provided there can collect your .dmp files?
      My Computer


  10. Posts : 46
    Windows 7 Home Premium 64-bit
    Thread Starter
       #20

    Hello again,

    Yesterday, I deleted the ndis.sys file and downloaded a new one of Sysfiles-Download
    This is what I went through:
    1. I restarted computer (just because)
    2. I deleted ndis.sys
    3. I restarted computer (and ran Startup Repair in middle of restart)
    4. After Startup Repair, I restarted computer again, and ran Startup Repair for a second time
    5. After Startup Repair, I restarted computer again, without Startup Repair (Normal Start)
    6. After the computer started up, I put the newly downloaded ndis.sys in C:\Windows\System32\drivers
    7. I restarted computer again, with Startup Repair
    8. After Startup Repair, I restarted Computer again and Normally Started Computer

    I thought this would fix the problem, but guess what, after I tried to enter Sleep mode, I met another BSOD

    Attached are files of last BSOD that happened (which I've been talking about just then)


    I'm looking forward to some good answers,
    Regards,
    Christian
      My Computer


 
Page 2 of 6 FirstFirst 1234 ... LastLast

  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 22:44.
Find Us