New
#21
I am seeing the same driver bug in all the latest dumps.
Please uninstall the display driver as suggested in Post #2 and then install GeForce 306.23 DriverCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {91, 2, fffffa800f980b50, 0} *** 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+1b775d ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. Arg2: 0000000000000002 Arg3: fffffa800f980b50 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0xc4_91 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: CivilizationV. CURRENT_IRQL: 2 TAG_NOT_DEFINED_c000000f: FFFFF8000D40DFB0 LAST_CONTROL_TRANSFER: from fffff8000ccd64ea to fffff8000cc7fc00 STACK_TEXT: fffff800`0d407ff8 fffff800`0ccd64ea : 00000000`000000c4 00000000`00000091 00000000`00000002 fffffa80`0f980b50 : nt!KeBugCheckEx fffff800`0d408000 fffff800`0cd24605 : 00000000`00000004 fffff800`0d4080d0 00000000`00000003 fffff800`0d4080d8 : nt! ?? ::FNODOBFM::`string'+0x4884 fffff800`0d408040 fffff800`0cd4271d : fffff880`06f56000 fffff880`06f5c000 fffff800`0d4080b0 fffff880`04a4eacc : nt!RtlEnoughStackSpaceForStackCapture+0x15 fffff800`0d408070 fffff800`0cd435bb : 00000000`00000001 fffff800`0d4080f0 00000000`00000000 fffff880`04abd2dd : nt!RtlWalkFrameChain+0x4d fffff800`0d4080a0 fffff880`04a7275d : 00000000`00000000 fffff800`0d408130 fffffa80`0e02e000 00000000`00040120 : nt!RtlCaptureStackBackTrace+0x4b fffff800`0d4080d0 00000000`00000000 : fffff800`0d408130 fffffa80`0e02e000 00000000`00040120 fffff800`0d408150 : nvlddmkm+0x1b775d STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+1b775d fffff880`04a7275d ?? ??? SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: nvlddmkm+1b775d FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 50f94c87 FAILURE_BUCKET_ID: X64_0xc4_91_nvlddmkm+1b775d BUCKET_ID: X64_0xc4_91_nvlddmkm+1b775d Followup: MachineOwner --------- 0: kd> lmvm nvlddmkm start end module name fffff880`048bb000 fffff880`05362000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Fri Jan 18 18:52:15 2013 (50F94C87) CheckSum: 00A92B69 ImageSize: 00AA7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4