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

christianb9632 · Mar 13, 2012

Hello, I have a problem.

A few weeks ago, I became a BSOD Error when I put my computer on sleep mode, but back then I didn't know what that was (BSOD), and on the BSOD message, it said "If this is your first time, restart your computer"
So I did, and pretended nothing happened.
NOW, a few days ago, I became another BSOD, again from putting my Computer on sleep mode, so I researched about BSOD and found something on How to fix BSOD, and it said something about DriverVerifier, I followed the steps... After the DriverVerifier finished, and the computer restarted, I then started to become more and more BSOD Error messages. I use "BlueScreenView" to see what driver the BSOD caused:

First BSOD I ever got when put on Sleep mode (I got about 2-3 of those BSOD's) :
DRIVER_IRQL_NOT_LESS_OR_EQUAL - Caused by: ndis.sys

After I used DriverVerifier, those BSOD's came when i click on Computer, or ControlPanel etc...(I got about 5-6 of those because I kept trying different things to see why those messages come up) :
DRIVER_VERIFIER_DETECTED_VIOLATION - Caused by: OA002Afx.sys

Then my brother thought the BSODs would go away by deleting OA002Afx.sys, and so we did, and the BSODs disappeared

. And during all this, my computer started to get real slow, so i thought i would clean the disks, and stuff, I also used Norton to Scan for malware, spyware, viruses... and also done Disk optimization (through Norton), AND during the scans, (Norton hasn't even finished) I didn't knopw why, I clicked on the Dell Webcam Central, and guess what, BSOD came up :cry:

... but this time it was :
DRIVER_VERIFIER_DETECTED_VIOLATION - Caused by: OA002Ufd.sys

(but now i don't have to click on Computer or ControlPanel to get a BSOD, it comes up everytime I start up the Computer itself..., like, once all files are loaded on desktop, and it finished loading, suddenly BSOD appears, in the moment im writing in this forum through "SafeMode with Networking".

I have read somewhere that it would fix the BSOD by deleting ndis.sys and getting another ndis.sys from a working computer (I used my parents's computer) BUT it didn't fix it...

Please help me fix this, if i need new drivers, give me links or tell me where to find it, if you got a driver that i would need.

Im new with all this BSOD stuff, so dont make things to hard for me to understand

I have just found out about BSOD since i have been researchinbg it on the internet, which is only about 3 days...

Thanks in advance.

Regards,
Christian

PS: Windows 7 Home Premium 64-bit,
Dell SX2210 Flat Panel Monitor (built in webcam)

zigzag3143 · Mar 13, 2012

Related to OA002Ufd.sys Advanced Audio FX Driver (64-bit) same as OA002Afx.sys from Creative Technology Ltd. Yours is from 2008!!
Update to current or remove.

many other old drivers.

Code:

OA002Ufd.sys    6/3/2008 5:30:37 AM    OA002Ufd.sys+266cb    fffff880`04a00000    fffff880`04a293a0    0x000293a0    0x48450f3d                        
OA002Vid.sys    8/1/2008 5:34:52 AM        fffff880`04b90000    fffff880`04bdad80    0x0004ad80    0x4892d8bc                        
wsimdx.sys    3/17/2009 2:19:55 AM        fffff880`04a93000    fffff880`04aa9000    0x00016000    0x49bf410b                        
CtClsFlt.sys    6/15/2009 1:06:41 AM    CtClsFlt.sys+2497a    fffff880`04eca000    fffff880`04ef42a0    0x0002a2a0    0x4a35d6e1                        
LHidFilt.Sys    6/17/2009 12:49:39 PM        fffff880`05c73000    fffff880`05c86000    0x00013000    0x4a391ea3                        
LMouFilt.Sys    6/17/2009 12:49:43 PM        fffff880`05c93000    fffff880`05ca7000    0x00014000    0x4a391ea7                        
LUsbFilt.Sys    6/17/2009 12:49:46 PM        fffff880`05c31000    fffff880`05c41000    0x00010000    0x4a391eaa                        
PxHlpa64.sys    6/23/2009 7:16:35 PM        fffff880`01378000    fffff880`01383e00    0x0000be00    0x4a416253

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

Click to expand...

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

christianb9632 · Mar 13, 2012

There is also another one: OA002Vid.sys
Do I delete that too?
And do I HAVE to find a newer version or does the computer find one itself?
And what about ndis.sys?
Do I just leave it?

Thanx,
Regards,
Christian

christianb9632 · Mar 14, 2012

Hello again,
I deleted oa002ufd.sys and there no BSODs in the moment.
I went into DeviceManager and I saw 2 yellow icons :warn::
(See Attachment)
I thought this would help you.

Cheers,
Christian

zigzag3143 · Mar 14, 2012

The two devices in device manager with the yellow exclamation are both related to your web cam and shouldnt have any bearing on the crashes.

SmurofNeves · Mar 14, 2012

NDIS.sys seems to be one of your problems it is related to a windows update.

Description: File NDIS.sys is located in the folder C:\Windows\System32\drivers. Known file sizes on Windows 7/XP are 182,912 bytes (80% of all occurrence), 182,656 bytes and 5 more variants.
The driver can be started or stopped from Services in the Control Panel or by other programs. The file is a Windows core system file. The program is not visible. There is no detailed description of this service. It is a trustworthy file from Microsoft. NDIS.sys seems to be a compressed file. Therefore the technical security rating is 2% dangerous.

Important: Some malware camouflage themselves as NDIS.sys, particularly if they are located in c:\windows or c:\windows\system32 folder. Thus check the NDIS.sys process on your pc whether it is pest.

zigzag3143 · Mar 14, 2012

SmurofNeves said:
NDIS.sys seems to be one of your problems it is related to a windows update.
Description: File NDIS.sys is located in the folder C:\Windows\System32\drivers. Known file sizes on Windows 7/XP are 182,912 bytes (80% of all occurrence), 182,656 bytes and 5 more variants.
The driver can be started or stopped from Services in the Control Panel or by other programs. The file is a Windows core system file. The program is not visible. There is no detailed description of this service. It is a trustworthy file from Microsoft. NDIS.sys seems to be a compressed file. Therefore the technical security rating is 2% dangerous.

Important: Some malware camouflage themselves as NDIS.sys, particularly if they are located in c:\windows or c:\windows\system32 folder. Thus check the NDIS.sys process on your pc whether it is pest.

WinDbg points to the OA002Ufd.sys in all 5 of these. The only way you may be seeing ndis is if you are using Blue screen view or Who crashed (or similar) and they are often wrong.

christianb9632 · Mar 14, 2012

@ zigzag3143
The yellow icons came AFTER I deleted oa002ufd.sys

@ SmurofNeves
Check attachement, thats all the ndis files in C:\Windows\System32\drivers

PS: I use BlueScreenView

zigzag3143 · Mar 14, 2012

christianb9632 said:
@ zigzag3143
The yellow icons came AFTER I deleted oa002ufd.sys

@ SmurofNeves
Check attachement, thats all the ndis files in C:\Windows\System32\drivers

PS: I use BlueScreenView

I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

If you arent using the webcam they dont matter.

Have you stopped crashing? If not upload the DMP's

christianb9632 · Mar 14, 2012

The most recent BSOD is attached

PS: Can you give me the download like of WinDbg, because I have found to many different ones and I do not know which is the correct one.

PPS: There and then I am using the webcam...

Christian

zigzag3143 · Mar 14, 2012

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.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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

SmurofNeves · Mar 14, 2012

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

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.

zigzag3143 · Mar 14, 2012

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

christianb9632 · Mar 14, 2012

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

zigzag3143 · Mar 14, 2012

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.

christianb9632 · Mar 15, 2012

@ 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

writhziden · Mar 15, 2012

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.

christianb9632 · Mar 16, 2012

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 :hot:

Regards,
Christian

writhziden · Mar 16, 2012

Have you followed the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to see if the executable provided there can collect your .dmp files?

christianb9632 · Mar 16, 2012

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 :cry:

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

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

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

MS SQL DB Developer

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

MS SQL DB Developer

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

New member

My Computer My Computer

Closed by request.

My Computer My Computer

New member

My Computer My Computer

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer