It is not advisable to run the tests on Windows drivers
as it can frequently cause false positives.
The one crashdump you provided is most likely just that. It looks like it's that a driver
was in violation of an IRP STATUS_PENDING check. I believe this is caused by selecting the Force Pending I/O Requests
check. Is this true? Remember, do not
select that check, nor Low Resource Sim,
nor IRP Logging
in your list of DV checks.
If you still wanna go after this, it blames your Daemon Tools drive emulation driver (dtsoftbus01.sys
). It's dated from January so find and update. You may even need to end up uninstalling it and switching to another solution for your drive emulation needs, as Daemon Tools has been known to cause driver conflicts and eventually BSODs for a number of people. Though honestly, this may very well be a false positive and not the cause of your crashes.
Given that minidumps are not being produced from the 'legit' bluescreen crashes, this most likely means a disk I/O issue of some sort or the driver was loaded very early during Windows startup. I recommend some hardware tests just to get them out of the way, though starting with Seatools preferably since this seems more conducive of drive problems.
- 7+ passes
- Torture Test; Large FFTs; overnight (9+ hours)
- Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK
as it requires OpenCL)
- All basic tests aside from the Fix all
or the advanced ones.
All of these (excluding MemtestCL) are included in the UBCD
if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the UBCD. Also, please provide us temps/voltages using HWInfo
with Sensors only
option checked. Log two 30-minute instances: one for idle, and one for high load.