BSOD whenever I run Matlab - happened 3 times in one day

[InquilineKea]

So I've now been getting an increased number of BSoDs whenever I run Matlab. The version I run is R2012b. For many months, Matlab seemed to work without ever BSoDing, but it just suddenly started to frequently produce BSoDs for some reason. One BSoD happened in the middle of coding, and another BSoD happened right when I shut down the program. I've attached three BSoD files here.

I do use Matlab to analyze very large (0.5 GB size) datasets, although I'm careful to make sure that they don't take up too much virtual memory. I have installed quite a few toolboxes on there, though many of them are vital for what I need to do.

My computer hasn't produced any BSoDs for any other application.

I've attached the dump logs of three of them . I've updated all my drivers to the latest version, and the BSoDs still happen. Hard drive and RAM are totally fine. I've also attached what BlueScreenView displays below (just look at the December 2013 ones - the other ones are unrelated).

 

[Arc]

Hi InquilineKea.

It is a security issue. Whenever you rum Matlab, Asus Data Security Manager fails; with different bugchecks like stop 0x19 and 0x3B.

BugCheck 19, {20, fffff8a00f3f3000, fffff8a00f3f3410, 5410200}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=AsDsm.sys"]AsDsm.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=AsDsm.sys"]AsDsm.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=AsDsm.sys"]AsDsm.sys[/URL] ( AsDsm+7f8a )

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

And the driver is extremely old.

fffff880`013d2000 fffff880`013df000   AsDsm    T (no symbols)           
    Loaded symbol image file: AsDsm.sys
    Image path: AsDsm.sys
[COLOR=Red]    Image name: AsDsm.sys
    Timestamp:        Fri Feb 13 11:44:26 2009[/COLOR] (49950FC2)
    CheckSum:         0001216E
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Asus Data Security Manager is nothing but a factory bloatware. You need to uninstall them all.

Start Menu\Programs\ASUS Utility
Start Menu\Programs\ASUS Utility\ASUS Data Security Manager 
Start Menu\Programs\ASUS Utility\ASUS Live Update 
Start Menu\Programs\ASUS Utility\SmartLogon
Start Menu\Programs\ASUS Utility\VirtualCamera

Plus, you have a lot of unnecessary items in startup. 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.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

There are other BSODs, not necessarily during running Matlab. And caused by some leftovers of some previous antivirus installation which is later uninstalled (as it is appearing).

BugCheck 1E, {ffffffffc0000005, fffff8800139de18, 0, ffffffffffffffff}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=vsdatant.sys"]vsdatant.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=vsdatant.sys"]vsdatant.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=vsdatant.sys"]vsdatant.sys[/URL] ( vsdatant+8e104 )

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

It is Zone Alarm TrueVector Firewall, used by Zone alarm (and Kaspersky, too). But no further tress of that antivirus in your system. So you cannot uninstall that antivirus anymore, and it appears to be a leftover only.

Try to delete it, manually, in the location c:\windows\system32\drivers\vsdatant.sys.

Seeing everything, I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

 

[InquilineKea]

Okay - thanks so much for the suggestions! I'll try those out.