Bluescreens, Messages from BSODs below.

coovargo

Honorable
Nov 22, 2012
106
0
10,710
I seem to be having several different modules causing crashes here. I believe that the issue resides in one of the memory modules but I'm going to post it here in hopes I can get more input.

The last BSOD occured an hour ago. The fault occured in MijXfilt.sys. The message was
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

The most information I could give on that BSOD is it was caused by DS3_tool.exe (A software which controls PS3 remotes via custom bluetooth drivers.)

The next minidump occured on 7/20 by module Win32k.sys. The message given was
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

This error occured on 7/20, 7/4, 6/21, 6/17, 6/16, 6/5, 5/30, 5/15, and 5/5.

These crashes seem to be related to the windows 7 User Interface changing.

On 5/30,
Another service called ntkrnlmp.exe caused the same exception:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

I've had a Phenom X6 Watercooled for the last 2 years and it's been running fine at 4.2Ghz. The upgrades I've performed have been the following since 5/01: SSD Upgrade, RAM Upgrade (2 additional DIMMs), and Video Card upgrade (Gtx680).

The errors only occur when I'm at the computer.
 
Solution
May well be the DRAM, you said you ADDED 2 sticks so you have mixed sets, try raing the DRAM voltage + 0.05 and the CPU/NB voltage + 0.10, it may well straighten things out....then with the system running open a command prompt as administrator and run the command SFC /SCANNOW this will check all system files and ensure they aren't corrupt

Tradesman1

Legenda in Aeternum
May well be the DRAM, you said you ADDED 2 sticks so you have mixed sets, try raing the DRAM voltage + 0.05 and the CPU/NB voltage + 0.10, it may well straighten things out....then with the system running open a command prompt as administrator and run the command SFC /SCANNOW this will check all system files and ensure they aren't corrupt
 
Solution