That's alright, I've got the history here and we don't receive many of these!
Would you know what this
protector.sys intercepting the calls is?
Is it the
Bank of China protector.sys or the
trojan protector.sys?
I see you use a disk encryption utility as well.
I would advise you try with a simpler system for the troubleshooting.
Because the call is handled by 4 different parties, removing a few layers would be helpful.
I've trolled the web for that bug check, as everyone does, and I could find that some layers intercepting calls to the hard disk have created similar things in the past:
http://www.sevenforums.com/bsod-help...er-update.html
Kind regards,
Alban
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 8c639750
Arg3: 00000000
Arg4: 00000000