BSOD Appearing Randomly

yagamikira · 26 Jun 2015

I purchased a new computer November 2014. No hardware changes or newly installed hardware were made since then. From April 7, 2015, suddenly I experienced a BSOD for the first time. So far there were 4 instances of BSOD (April 7, May 29, June 9, and June 25).

I tried using BlueScreenView, but I have difficulties to pinpoint what exactly causing it because it will always pinpoint to ntoskrnl.exe or Ntfs.sys. Everything is random.

I uploaded herein the collected dmp files. Can you help me verify what program or driver that is causing the BSOD? Thanks

Arc · 26 Jun 2015

Apparently this program is causing the issue.

FSPro Labs d:\program files\my lockbox\mylbx.exe

Code:

fffff880`035476e8  fffff880`010d28b2Unable to load image \SystemRoot\System32\Drivers\FSPFltd2.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FSPFltd2.sys
*** ERROR: Module load completed but symbols could not be loaded for FSPFltd2.sys
 FSPFltd2+0x38b2

I would suggest you to uninstall it and see how the computer runs.

I would suggest you two more things, namely .....

1. Uninstall Daemon Tools. 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.

2. 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.

Report us for any further issue after doing these.
__________________________________________________

Code:

BugCheck A, {80, 2, 1, fffff800030ca82f}

Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f )

Followup: MachineOwner
---------

yagamikira · 12 Sep 2015

Just for update, two months after you found the culprit: I updated instead of uninstalling both MyLockbox program and Daemon Tools softwares, and voila the bluescreen so far is no longer appearing for more than 2 months.

Thanks so much Arc for identifying the softwares that are causing the issue :)

Arc · 14 Sep 2015

Thanks for letting us know.