- Thread Author
- #1
Hi there,
I experience repeating KERNEL_MODE_EXCEPTION_NOT_HANDLED_M caused by ntkrnlpa.exe. It happened about every 2nd to 4th time we used the computer.
The last BSOD happened at logoff processing, for earlier I don't know anymore when.
The unhandled exception was always the same c0000005. But the relative location differed: one time 00000082, two times 00000068.
ntkrnlpa.exe is not old. It's from Sat Jun 19 05:55:24 2010.
The earliest of four BSODs is different but might be related:
vsdatant.sys - DRIVER_CORRUPTED_EXPOOL (c5), {4, 2, 1, 82d5b067}
vsdatant.sys may come with Zonelabs Zonealarm, my firewall.
This incident looks related as the stack shows addresses of vsdatant.sys surrounded by addresses of ntkrnlpa.exe (nt). WinDbg again names nt (ntkrnlpa.exe) as the faulting module.
I appreciate any help.
-Peter
View attachment 102510-23509-01.dmpView attachment 102110-25552-01.dmpView attachment 092510-25537-01.dmpView attachment 081910-26348-01.dmp
I experience repeating KERNEL_MODE_EXCEPTION_NOT_HANDLED_M caused by ntkrnlpa.exe. It happened about every 2nd to 4th time we used the computer.
The last BSOD happened at logoff processing, for earlier I don't know anymore when.
The unhandled exception was always the same c0000005. But the relative location differed: one time 00000082, two times 00000068.
ntkrnlpa.exe is not old. It's from Sat Jun 19 05:55:24 2010.
The earliest of four BSODs is different but might be related:
vsdatant.sys - DRIVER_CORRUPTED_EXPOOL (c5), {4, 2, 1, 82d5b067}
vsdatant.sys may come with Zonelabs Zonealarm, my firewall.
This incident looks related as the stack shows addresses of vsdatant.sys surrounded by addresses of ntkrnlpa.exe (nt). WinDbg again names nt (ntkrnlpa.exe) as the faulting module.
I appreciate any help.
-Peter
View attachment 102510-23509-01.dmpView attachment 102110-25552-01.dmpView attachment 092510-25537-01.dmpView attachment 081910-26348-01.dmp