Random Freezes and BSOD

Hello,

Recently I've been getting random freezes and lockups of varying circumstances. The most common one would be windows would stop responding when I'm either browsing the web or watching a video or gaming. It would stop responding to any keyboard commands but the mouse would still be movable and any clicks (say on the maximise button) would look to have been clicked but would never actually do anything.

The same scenario would occur another time but instead of non responsive buttons, the cursor would spin, and Ctrl + Alt + Del would bring up "Preparing Security Options" and stay like that until I give up and hit the power button.

I've run Memtest86 with no issues over 7 passes, I think all my drives are up to date, and I've run CCleaner. I've also run Verifier on all non-Microsoft drivers which immediately BSOD as soon as Windows started back up.
"SF scannow" came up with nothing as well as AV scan with MSE and Malwarebytes.

Any help would be greatly appreciated.

Thanks

Code:

*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
Unable to load image dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88004545324, The address in the driver's code where the error was detected.
Arg3: fffff98003a56e10, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1324
fffff880`04545324 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1324
fffff880`04545324 4053            push    rbx

IRP_ADDRESS:  fffff98003a56e10

DEVICE_OBJECT: fffffa8009dffa30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000350b3dc to fffff80003084fc0

STACK_TEXT:  
fffff880`035ae1d8 fffff800`0350b3dc : 00000000`000000c9 00000000`0000023e fffff880`04545324 fffff980`03a56e10 : nt!KeBugCheckEx
fffff880`035ae1e0 fffff800`0351547a : fffff800`035099f0 fffff880`04545324 fffff980`03a56e10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`035ae220 fffff800`0351634e : 00000000`0000023e 00000000`00000000 fffff980`03a56e10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`035ae270 fffff800`0352171f : fffffa80`0a2ce620 fffffa80`0a1e9a20 fffffa80`0a1e9ad8 fffff880`04549228 : nt!VfErrorReport6+0x6e
fffff880`035ae340 fffff800`03521b63 : fffffa80`0a1e9a20 00000000`00000002 fffffa80`09dffa30 fffff880`045453f4 : nt!IovpCallDriver2+0x13f
fffff880`035ae3a0 fffff800`03527c2e : fffff980`03a56e10 fffff980`03a56e10 00000000`00000002 fffffa80`09dffa30 : nt!VfAfterCallDriver+0x353
fffff880`035ae3f0 fffff800`03526c42 : fffff980`03a56f28 00000000`00000002 fffffa80`0a284190 fffffa80`0a1e9a20 : nt!IovCallDriver+0x57e
fffff880`035ae450 fffff800`03527c16 : fffff980`03a56e10 00000000`00000002 fffffa80`0a284040 fffff800`035233f5 : nt!ViFilterDispatchGeneric+0x62
fffff880`035ae480 fffff880`01dcd16e : 00000000`00000000 fffff880`035ae560 fffffa80`0a284da0 fffffa80`0778f850 : nt!IovCallDriver+0x566
fffff880`035ae4e0 00000000`00000000 : fffff880`035ae560 fffffa80`0a284da0 fffffa80`0778f850 fffffa80`00000020 : iaStorF+0x116e


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1324

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10358a

FAILURE_BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1324

BUCKET_ID:  X64_0xc9_23e_dtsoftbus01+1324

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

Update intel Rapid Storage Technology Filter driver - x64.

Uninstall DAEMON Tools Lite.

This should solve your problem

Done that and so far, no freezes for the entire night which hasn't happened in a while! Thanks!

:)
Evaluate the system for a few days and post back the results.

Unfortunately, whilst I was on a Skype call this morning, the computer froze up again! This time, there was no response from any keyboard or mouse commands (although the cursor was movable). I left it as it was in the hopes that it would produce a BSOD or anything but no luck after 10 hours so I hit the power button to force restart.

Uninstall/update Intel Rapid Storage Technology Filter driver - x64

The dump blames this driver.

uninstall daemon tools. This is also making the computer crash

update it from here

http://downloadcenter.intel.com/Sear...ntel%C2%AE+RST)

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88004545324, fffff98003a56e10, 0}

*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
Unable to load image dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

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