Thanks for the update :) .
The quote below details the steps we need to take in order to determine the culprit.
But first update or preferably remove if not in use, the following drivers:
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.
First run it with all the existing/installed RAM modules. If it comes with no error, all is good.
But 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.
If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using
CCleaner looking at Tools > System Restore.
If there is no points,
make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.
The following is for information purposes only:
Code:
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Mon Sep 23 09:59:29.815 2013 (UTC + 3:00)
System Uptime: 0 days 1:32:00.002
BugCheck 109, {a3a039d8a057f5b8, 0, 9c2fe45072850149, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR: 0x109
PROCESS_NAME: System
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Mon Sep 23 08:26:35.521 2013 (UTC + 3:00)
System Uptime: 0 days 6:57:55.317
BugCheck 50, {fffff900c2b5338c, 0, fffff960006200a0, 0}
Probably caused by : cdd.dll ( cdd!memmove+80 )
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Fri Sep 20 09:27:58.674 2013 (UTC + 3:00)
System Uptime: 0 days 3:58:44.860
BugCheck 24, {1904fb, fffff880035935b8, fffff88003592e10, fffff88001894fa0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveHashEntry+c4 )
BUGCHECK_STR: 0x24
PROCESS_NAME: System
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Thu Sep 19 07:57:15.864 2013 (UTC + 3:00)
System Uptime: 0 days 6:47:47.660
BugCheck 1E, {ffffffffc0000005, fffff80003b5ccee, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
BUGCHECK_STR: 0x1E_c0000005_R
PROCESS_NAME: svchost.exe
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Quote