Hi zacardo.
Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
Code:
[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows
Daemon Tools, Alcohol 120% and Power Archiver Pro uses
SCSI Pass Through Direct (
SPTD), which is a well known BSOD causer. Uninstall
Daemon Tools at first. Then download SPTD standalone installer from
Disk-Tools.com, and execute the downloaded file as guided below :
- Double click to open it.
- Click this button only:
-
- If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
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 start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If memtest results 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. Post it following the
Blue Screen of Death (BSOD) Posting Instructions.
__________________________________________________________________________________
Code:
BugCheck 50, {fffff890009d7df0, 0, fffff80002fbc070, 5}
Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1e4 )
Followup: Pool_corruption
-------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff96000273453, fffff8800be11bb0, 0}
Probably caused by : win32k.sys ( win32k!GrePtInSprite+253 )
Followup: MachineOwner
---------
