Ntoskrnl.exe Blue Screen

[CarlTR6]

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.

 

[cemcilfa]

it was the same with the old card
I had the DWA-140, then baught an "g" pci wireless, then you told me to upgrade so I got an "n"
I think that the anodlwfx is definitely the cause of all these Blue screens

 

[CarlTR6]

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

 

[cemcilfa]

it only works when it is renames as sys
bak (doesnt work)
old (havent tried yet)
would you like me to rename it to bak??

 

[CarlTR6]

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.

 

[Wishmaster]

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.

 

[cemcilfa]

But I am sure it is anodlwfx
I tried for a whole day with it on .bak (not loading the drivers) and has no Blue screens
When ever It is .sys (and loading) I get blue screens.

 

[Wishmaster]

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.

 

[CarlTR6]

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

 

[cemcilfa]

Yes I agree,
But I do not trust myself with the inside of the machine.
I will be asking a computer technician for him to do things with the RAM
I understand what you are saying, but I would just like to get this driver issue sorted

 

[CarlTR6]

We need to get the RAM issued sorted first. It can affect the driver issue.

 

[cemcilfa]

Are there any tests such as MEMtest that could identify which RAM(s) is/are causing the problem
The person I brought my pc from says that I can only send back 1 Memory stick back (i have 4x4gb)

 

[Wishmaster]

I just realized you have 16GB of RAM.

As mentioned, a Bad stick could be a possibility.

It is also possible, that having all the DIMM slots populated with that much RAM could be the issue (depending on what the RAM is rated for & speed its set at) as it could be too much of a strain at default settings)

As already suggested, the best way is to test each stick individually.

If they all test good, try running with just 2x4 (8GB) and see if passes then.

 

[reventon]

I agree, you do need to fix the RAM at some stage.

Duplicate thread, for reference - Constant BSOD's...HELP NEEDED - Tech Support Forum

 

[cemcilfa]

ok, I have taken out one of my RAM sticks and havent received a BSOD yet (1day)
What would you like me to do now?
thanks

 

[CarlTR6]

Let it run another day like it is and then add one more RAM stick and see how it does.

 

[cemcilfa]

At this moment I have 3 RAM in there. I only took one stick out

 

[CarlTR6]

OK. I am not a hardware Guru at all. I will ask the hardware guys to take a look at this thread and offer their help.

 

[yowanvista]

At this moment I have 3 RAM in there. I only took one stick out

The other RAM stick may be defective, I suggest replacing it

 

[Dave76]

Carl is right, when running that much RAM you will likely need to adjust some settings.

First ensure all the RAM sticks are good.
Use this tutorial for guidance: How to Test and Diagnose RAM Issues with Memtest86+

I'm afraid that if RAM passes one or two memtest86+ doesn't guarentee there are no RAM problems.
If you follow the above tutorial your chances of finding the correct fix will be much better.

Test each RAM card one at a time, looking for RAM cards that pass and motherboard slots that pass.
If you are not comfortable removing and testing RAM cards then you will need to find someone to help you or take it to a local repair shop. After reading through this thread, the RAM issue needs to be explored first. This can cause the errors and BSoDs you are having.

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums


Have you been checking your temperatures?

Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the North Bridge (NB) voltages are, look under the M.I.T. page you should see 'CPU NB VID Control'.
It's on page 43 of your motherboard manual.
Gigabyte Motherboard Manual GA-MA78LMT-US2H

There known issues with AMD integrated memory controllers, the CPUZ tabs will give the information needed to check this, that much RAM will usually require a NB (memory controller) voltage bump.

Post the revision number of your motherboard.
If you don't know it, then open your case and look in the lower left corner on the motherboard, it is printed there.

Do your BSoDs happen when you first start your computer or randomly?