Ntoskrnl.exe Blue Screen

Uninstall it completely and reboot. Then turn your computer off, put the card back in and boot. Let Windows detect the hardware. Do you still have anodlwfx renamed? You may have to disable your old card in Device Manager.

Will the new card work with anodlwfx renamed to old or bak?

No, renaming it to anything stops the driver from loading. I have askes for a networking guru to take a look at this thread. I hope to he/she will have some insight.

I know little about Networking so I wouldn't want to attempt helping in that dept. but ...


Did you try the suggestion of testing each RAM stick individually to try and isolate the problem there?

I think at this point you may want to take a step back, and try to find out what exactly is causing all the RAM errors.
If it comes down to a bad RAM module, simply run the PC with the 1 good for now, (if ones is good)

Bad hardware can and will cause all forms instability within Windows, making it much more difficult to isolate other issues.

And it very well may be.

But all I am saying is if the RAM is still throwing all of those errors in MEMtest, it really should be pinpointed before moving on.

All Im saying is Bad RAM can cause all types of issues.
Overall Instability, Driver Crashes, App Crashes, File corruption etc.

Because, it is quite possible you fix one problem, and then another arises. Fix that, now something else.
And it will all come back to unstable or Bad RAM.

Wishmaster is correct. You need to address the RAM issue first and then we can work on that driver issue.