BSOD Unknown cause

Additional information is required - not just .dmp files.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8010b1a610, fffffa8010b1aa20, 4410010}

*** WARNING: Unable to verify timestamp for FileLock.sys
*** ERROR: Module load completed but symbols could not be loaded for FileLock.sys
Probably caused by : FileLock.sys ( FileLock+236b )

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

6: kd> lmvm Filelock
start             end                 module name
fffff880`0119d000 fffff880`011ad000   FileLock T (no symbols)           
    Loaded symbol image file: FileLock.sys
    Image path: \SystemRoot\system32\DRIVERS\FileLock.sys
    Image name: FileLock.sys
    Timestamp:        Thu Mar 25 21:22:49 2010 (4BAB4081)
    CheckSum:         00019086
    ImageSize:        00010000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

Start Menu\Programs\GiliSoft\File Lock Pro	Public:Start Menu\Programs\GiliSoft\File Lock Pro	Public

The problem in both BSOD's is caused by the outdated version of File Lock Pro. Either update the software, or uninstall it.

Site:
Encryption Software, Video/Audio Editing Software, System Optimize Software Free Download - Gilisoft