BSOD at least once a day caused by ntoskrnl.exe

Hello,

Lately I have been getting the BSOD a fair bit. At first it was about once a couple of weeks, then it started increasing. I did a full format of the HDD in an effort to stop it, it didn't work. It just started occurring more often. I've tried updating all of the drivers, didn't work. I've tried updating my BIOS, it didn't work. I've done a memory test, it showed up as no errors. I've tried swapping the HDD's, and same problem. Today I've just got 3 of them. Attached is a copy of the BSOD reports.

I looked up the CACHE_MANAGER error on google and it said it was either a video card driver issue or an anti-virus issue. I updated the driver, and still got it. I've never had a problem with the NOD32 before, so I didn't think it was that. I'm hoping it doesn't mean that my video card is about to die.

I also have another question which could be a stupid one. Would having 2 different brands of RAM cause problems like this? 2 sticks are the Kingmax Hercules DDR3 2100 ram, the other 2 are GSKILL Ripjaws DDR3 1600 ram.

I'm hoping someone can help me find the problem that's causing the crashes. Any help would be appreciated.

I noticed all of these problems started happening when I tried to reset the cmos. A lot of other errors have happened since then. I can't play a game because there is an error in the disc read, even though there is no disc in the DVD drive. I can't extract anything without corrupt file errors, even though I know for a fact that they're not corrupt. I can't mount image files, I can't burn anything, I can't use an internet browser without it crashing repeatedly. The internet drops out at random times, and sometimes the internet icon on the bottom right of the screen disappears completely and control panel doesn't pick up any connection. I can't view anything I put on the desktop without going to the desktop folder. It's just getting really frustrating. I've got a very basic understanding of computer repairs, but this is just way out of my depth.

Welcome to SF JacobT89 :).

The bug checks are memory related, please remove the Kingmax Hercules DDR3 2100 kit and observe
the system stability. If the system is still unstable try it the other way around switching the two kits.
Other than that I recommend testing the RAM.

Arc said:

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

No, it would be a tough nut even for the manufacturer.

Thanks for the update :).
Just to clarify, you are now using just one of kits (two modules/sticks)?

Hmm OK, I still have a feeling its the modules, most probably the different timings / Voltages.

Please run the system with only one kit at a time and asses the situation.

Reset the BIOS back to default:

• CLR CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

   Note

If any component is overclocked reset it back to stock speeds!