Hello dly62 and welcome to Sevenforums.
BSOD Analyse
PCTCore64.sys is being picked up and pointed towards. It's the PC Tools KDS Core Driver, if you're familiar with it, either uninstall it or contact their support or forum.
Code:
2: kd> lmvm PCTCore64
start end module name
fffff880`0109b000 fffff880`01106000 PCTCore64 T (no symbols)
Loaded symbol image file: PCTCore64.sys
Image path: \SystemRoot\system32\drivers\PCTCore64.sys
Image name: PCTCore64.sys
Timestamp: Mon Apr 23 04:32:06 2012 (4F94BF26)
CheckSum: 0007323D
ImageSize: 0006B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
BugCheck 50, {fffff880e5620590, 1, fffffa8006f4c2e6, 5}
*** WARNING: Unable to verify timestamp for PCTCore64.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore64.sys
Could not read faulting driver name
Probably caused by : PCTCore64.sys ( PCTCore64+1b726 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff880e5620590, 1, fffffa8006f4c2e6, 5}
*** WARNING: Unable to verify timestamp for PCTCore64.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTCore64.sys
Could not read faulting driver name
Probably caused by : PCTCore64.sys ( PCTCore64+1b726 )
PC Tools - (Support)
BCCode
Code:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8c07385feb, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030b2e85, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Best Regards,
Frederik.