nice one, thanks chaps, well just before it BSOD i seen "check your firewall" so removed zonealarm.....looks like vsdatant is the culprit maybe? part of zonealarm..
here's the rest of the log..
On Wed 23/03/2011 20:41:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032311-33103-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003394411, 0xFFFFF88006730F70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 23/03/2011 20:41:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003394411, 0xFFFFF88006730F70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 19/03/2011 09:53:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031911-35786-01.dmp
This was probably caused by the following module: vsdatant.sys (vsdatant+0xF933)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880042DD933, 0xFFFFF8800337B978, 0xFFFFF8800337B1D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vsdatant.sys .
Google query:
vsdatant.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M