Blue screens are back

New crash. Folder updated.

It'll take a while for me to track down the cause of the crash, meanwhile could you remove the 2x4gb RAM modules.

Will do.

[BGCOLOR=transparent]Thanks in advance.[/BGCOLOR]

The best I've been able to find is the nvidia driver being blamed. I have somewhat of a hard time to believe it.

Assuming it's the nvidia driver taking the action, it's trying to free memory.
Driver verifier catches a one bit error within the same page, but I can't find any single bit error, I do have to note I'm not very well versed with the memory management but still.

Thanks for taking the time to go through the dump.

Do you think diagnosing this is coming to an end?

I tried another Nvidia card not so long ago and it crashed within minutes.
Assuming it’s the Nvidia driver, this cannot be video card specific? It’s any Nvidia driver?

This is also to do with RAM? How come changing the freq to 1333Mhz stopped the crashes for a month?

How is the error being made?

Is changing Nvidia driver perhaps a lucky shot in hope that errors stop being made?

I don’t know enough on this so it’s difficult for me to fully comprehend.

Thanks for anything you can add to helping me fix this.

Mismatched RAM is always something that needs to be taken care of IMO. Even though it's pretty much the same model it's the small detail that is the difference. I can't say if the RAM is truly involved, I don't know 100% certain until it is tested.

How come changing the freq to 1333Mhz stopped the crashes for a month?

Click to expand...

Various reasons, like newly installed Windows updates, driver changes, hardware failure after the month, etc.

How is the error being made?

Click to expand...

When the Special Pool option in driver verifier is selected, the system allocates reserved memory for the selected drivers. Driver verifier checks if everything within the pool goes smoothly. The driver wrote memory prior to beginning a buffer and attempted to free it, this is an action that is not allowed and results in a 0xC1 crash, it just so happened that the page wherein the driver wrote had an address with a single bit corruption which was detected.
I do not think it was a software crash, but a crash that was caused by possibly the RAM or some other part of hardware.

Interesting.

I once put the RAM and GPU in another system and it crashed with a typical message.

But I couldn’t get it to crash with either one or the other installed.

If it makes any difference, the two Corsair kits are identical except for GB size.
I tested each module individually running 8 passes on Memtest86, and in different DIMM slots. 0 errors

[BGCOLOR=transparent]I’m gonna use this system until I decide on building a new one. There is no point in me spending money on DDR3 (or anything else)[/BGCOLOR][BGCOLOR=transparent] when I will have to buy DDR4 shortly after for a whole new platform...[/BGCOLOR]

[BGCOLOR=transparent]Thanks for your efforts Axe. If anything comes to mind don’t hesitate posting here.[/BGCOLOR]
[BGCOLOR=transparent][/BGCOLOR]
Cheers

Did you also test the modules simultaneously?

I have tested them a bunch of times.

8 passes on all modules together
8 passes on all modules together but switching their channels.
8 passes on each module, on their own DIMM. So 4GB DIMM_1, 8GB DIMM 2 etc...

I did not test them in any random order afterwards.

If an error had shown on an 8GB module I would have no choice but to keep using it.
I need all my RAM tbh, but 4GB’s I don’t care about losing that much.