New
#191
EDIT: Sorry Steve, didn't see you reply while I was typing.
The nVidia driver again.My last suggestion on that would be to try the 350.12 driver linked below and follow NVIDIA Drivers - Avoid ProblemsHaving said that, the other dump is a 0x7F which happens to be a double fault, that's either a stack overflow or a hardware problem. I'm leaning towards the GPU being faulty.Code:BugCheck D1, {200139, 9, 0, fffff88005bcbf71} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+19cf71 ) Followup: MachineOwner --------- 0: kd> lmvm nvlddmkm start end module name fffff880`05a2f000 fffff880`0643a000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Fri Mar 13 15:39:56 2015 (550304CC) CheckSum: 009CE879 ImageSize: 00A0B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4Could you borrow a GPU from someone to test in your system?Code:UNEXPECTED_KERNEL_MODE_TRAP (7f) 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050033 Arg3: 00000000000406f8 Arg4: fffff8a00315c130