Installation of driver disks causing DPC_WATCHDOG_VIOLATION on Windows 10

[JohnW242424]

I installed LV2015 and the drivers on a windows 10 machine. After reboot, when I log in, the OS runs for about 10-20 seconds, then blue screens and states the cause is a DPC_WATCHDOG_VIOLATION. I did a complete uninstall and the issue went away. I installed only LabVIEW and had no issues. Installed the drivers again and got the blue screen again after reboot. It is only after installing the driver disks that the issue occurs.

     I looked at the known compatibility issues and according to the table provided I should be alright with the 32-bit versions of all the modules I installed.

    Has anyone else experienced this issue? Any idea which driver may be causing this issue and why?

[MangeshD]

I too had this issue with my WINDOWS 10 but I am not sure whether it was due to LabVIEW drivers or not.

The issue was related to the Iastor.sys which is Intel Matrix Storage Manager.

I solved this issue by making changes given in this thread.

Please let us know.

[JohnW242424]

Thanks for the reply. Unfortunately, I've tried that one already, as well as several other proposed solutions.

Still the same symptom.

[Bob_Schor]

I've done multiple installations of LabVIEW 2015 on numerous (different) PCs and have never encountered the problem you report.  It is almost certainly a Windows 10/PC hardware/driver issue and probably has nothing to do with LabVIEW itself or its drivers.  Instead, when LabVIEW is installing drivers, it is doing something your system doesn't like (such as writing on a disk block that, for some unexplained reason, causes a crash when Windows reboots and tries to organize itself).

It would be interesting to try to do an installation on another PC -- if you get the same problem, (a) I would be very surprised, and (b) I would say "get a new set of installation disks and try again".

Bob Schor

[JohnW242424]

I've installed numerous version of LabView and Drivers on numerous machines with different OSs and have never seen this either. I'm trying to see if a Windows 10 upgrade will do the trick.

[JohnW242424]

After I removed all the NI-DCPower, DMM, FGEN, etc... Windows 10 is now stable again. I know, there appears to be no rhyme or reason to these kinds of issues but…

Just in case anyone else ever runs into this issue, these items are what was causing the symptom on my machine.

[rolfk]

---

@techinpost wrote:

I found a webpage from which i get rid out of this type of error issue, now you can also check this once for getting rid of it completely from here: Error

---

None of the proposed solutions in that article could be considered specific to this error but are simply common debug operations that "could" help to fix this as a collateral effect.

Basically any of the other errors that they list as recommended reading contains similar or the same generic bugfix solutions. It looks very much like an advertising site that collects all kinds of error descriptions and uses them to create a legit looking solution description, but really simply serving as a platform to push all kind of ads for more or less useful (and potentially adware and scareware contaminated) PC software tools onto users.

The fact that the poster is a one hit wonder doesn't help to consider this as much more than spam.