There is one stop code 124, which is hardware related, please read this article to know what it is and what to try
https://www.sevenforums.com/crash-loc...-what-try.html
However, before doing that, there are several things I want you to try first:
Scan whole system file check:
SFC /SCANNOW Command - System File Checker
There is one exception code c000005, which make me think of memory related. Please download third party called memtestx86, burn it to CD using ISO Recorder v3 , and let it run for 5,6 passes at least. Instruction can be found here --> Memory Diagnostics
You have some drivers that are desperate in need for updating:
Code:
VSTBS26 VSTBS26.SYS Thu Oct 16 07:54:06 2008 (48F690AE)
VSTCNXT6 VSTCNXT6.SYS Thu Oct 16 07:52:22 2008 (48F69046)
VSTDPV6 VSTDPV6.SYS Thu Oct 16 07:57:45 2008 (48F69189)
They are Conexant SoftK56 Modem Driver
Code:
VClone VClone.sys Wed Sep 24 17:29:20 2008 (48DA1680) VirtualCloneCD Driver by Elaborate Bytes AG
Code:
RTCore64 RTCore64.sys Wed May 25 13:39:12 2005 (42941D90) RivaTuner/EVGA Precision
Code:
Amfltx64 Amfltx64.sys Mon Oct 15 10:37:21 2007 (4712E071) A4Tech X-705FS Mouse Driver
Amusbx64 Amusbx64.sys Wed Feb 13 15:20:14 2008 (47B2A83E)
Code:
000 000.fcl Fri Oct 05 09:47:54 2007 (4705A5DA) CyberLink FCL Driver
Window 7 doesn't like out of date drivers and with those out of date drivers average from 2,3 years ago, I bet it would be surprised if you computer hadn't gone through any crashes.
Please remove any virtual CD program such as Deamon tool or Alcohol 120%, they use sptd.sys, which I found in the loaded drivers, well-known for causing BSODs. Please remove Deamon tool completely, then use this tool to remove sptd.sys:
DuplexSecure - Downloads
BUGCHECK SUMMARY:
Code:
BugCheck 3B, {c0000005, fffff8000305601e, fffff880091b0e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
Followup: MachineOwner
---------
BugCheck 50, {fffff900c2fb47a0, 0, fffff960006ddc51, 0}
Unable to load image \SystemRoot\System32\cdd.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Could not read faulting driver name
Probably caused by : cdd.dll ( cdd+dc51 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff8000308701e, fffff88009133e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
Followup: MachineOwner
---------
BugCheck 124, {0, fffffa8004ae6038, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff8000305201e, fffff88009e13e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
Followup: MachineOwner
---------
BugCheck 50, {fffff900c1ee1030, 0, fffff960002bc69d, 0}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+27c69d )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff96000174283, fffff88005d4c060, 0}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c4283 )
Followup: MachineOwner
---------
Regard,
Tuan