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.
You have MagicISO installed, too.I would suggest you to not use it too. It also causes some same issues, for the mcdbus.sys driver.
Among the three recent BSODs, one is stop 0x24, which is related to HDD/SSD.
Do some Disc checks.
- Update your Samsung 840 Series SSD's Firmware
- Reseat the sata and power.
- Run chkdsk /f/r, following the option two of the tutorial Disk Check
- Seatool for dos: SeaTools | Seagate download
- Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
- You can use Win32 DiscImager to create a bootable USB and run Seatools for DOS. Follow this post to know how to make a bootable Seatools USB.
Intel(R) 82579V Gigabit Network Connection driver is failing here.
Code:
fffff880`03b4d178 fffff880`08234552Unable to load image \SystemRoot\system32\DRIVERS\e1c62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=e1c62x64.sys"]e1c62x64.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=e1c62x64.sys"]e1c62x64.sys[/URL]
e1c62x64+0x34552
And the driver is old.
Code:
fffff880`08200000 fffff880`08257000 e1c62x64 T (no symbols)
Loaded symbol image file: e1c62x64.sys
Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
[COLOR=Red] Image name: e1c62x64.sys
Timestamp: Wed Jul 20 22:07:53 2011[/COLOR] (4E270461)
CheckSum: 00057931
ImageSize: 00057000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update it from
https://downloadcenter.intel.com/default.aspx
As the disc and network error ar present together in a same crash dump, scan the system for possible virus infection with the following programs.
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.
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
The old version of Xbox driver ais very well known cause of BSOD.
Code:
fffff880`0a890000 fffff880`0a8a2100 xusb21 (deferred)
Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
[COLOR=Red] Image name: xusb21.sys
Timestamp: Fri Aug 14 03:40:17 2009[/COLOR] (4A848F49)
CheckSum: 0001398B
ImageSize: 00012100
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update it from
Software Downloads | Microsoft Hardware
Let us know the results.
______________________________________________________________________________
BSOD ANALYSIS:
Code:
BugCheck 1A, {41201, fffff68000065518, 1, fffffa8015a3bab0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )
Followup: MachineOwner
----------------------------------------------------------------------------------------
BugCheck 1A, {5003, fffff70001080000, c490, d954000189a0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2984f )
Followup: MachineOwner
-----------------------------------------------------------------------------------------
BugCheck 24, {1904fb, fffff88003b4d558, fffff88003b4cdb0, fffff80003443852}
Probably caused by : ntkrnlmp.exe ( nt!FsRtlUninitializeFileLock+ca )
Followup: MachineOwner
---------
