Solved BSOD Windows 7 - ntoskrnl.exe+7cc40

[writhziden]

Oh, I did not read those as two different letters...

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\030212-20872-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0280f000 PsLoadedModuleList = 0xfffff800`02a54670
Debug session time: Fri Mar  2 14:39:27.390 2012 (UTC - 7:00)
System Uptime: 0 days 0:10:22.185
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff98002ad0e46, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4977d )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff98002ad0e46, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+3534363563383837
fffff980`02ad0e46 ff              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

BUGCHECK_STR:  0x1E_c000001d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800028d7588 to fffff8000288bc40

FAILED_INSTRUCTION_ADDRESS: 
+3534363563383837
fffff980`02ad0e46 ff              ???

STACK_TEXT:  
fffff880`06b1bb38 fffff800`028d7588 : 00000000`0000001e ffffffff`c000001d fffff980`02ad0e46 00000000`00000000 : nt!KeBugCheckEx
fffff880`06b1bb40 fffff800`0288b2c2 : fffff880`06b1c318 fffff980`0a220890 fffff880`06b1c3c0 fffff900`c00b9728 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`06b1c1e0 fffff800`0288941f : fffff880`06b1c3c0 00000000`00000000 00000000`00000000 fffff960`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`06b1c3c0 fffff980`02ad0e46 : 00000000`00000000 00000000`00000001 00000000`00000001 00000029`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff880`06b1c550 00000000`00000000 : 00000000`00000001 00000000`00000001 00000029`00000000 00000000`00000027 : 0xfffff980`02ad0e46


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4977d
fffff800`028d7588 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4977d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_c000001d_VRF_BAD_IP_nt!_??_::FNODOBFM::_string_+4977d

BUCKET_ID:  X64_0x1E_c000001d_VRF_BAD_IP_nt!_??_::FNODOBFM::_string_+4977d

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\030212-22729-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0284d000 PsLoadedModuleList = 0xfffff800`02a92670
Debug session time: Fri Mar  2 14:11:42.410 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:22.830
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {62, fffffa8005cb8218, fffffa8005cb74c0, 1}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys

Followup: MachineOwner
---------

3: 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: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: fffffa8005cb8218, name of the driver having the issue.
Arg3: fffffa8005cb74c0, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
	Type !verifier 3 drivername.sys for info on the allocations
	that were leaked that caused the bugcheck.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_62

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4edd8367

MODULE_NAME: atikmdag

FAULTING_MODULE: fffff8800488d000 atikmdag

VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY fffffa8005cb74c0
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d533dc to fffff800028c9c40

STACK_TEXT:  
fffff880`031cb2e8 fffff800`02d533dc : 00000000`000000c4 00000000`00000062 fffffa80`05cb8218 fffffa80`05cb74c0 : nt!KeBugCheckEx
fffff880`031cb2f0 fffff800`02d6254a : 00000000`00000001 00000000`00000000 fffff880`0488d000 00000000`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031cb330 fffff800`029b6340 : 00000000`00000000 00000000`00000000 fffff880`02fd5180 00000000`00000000 : nt!VfPoolCheckForLeaks+0x4a
fffff880`031cb370 fffff800`02c7c0ee : fffffa80`05cb8010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfTargetDriversRemove+0x160
fffff880`031cb410 fffff800`02ca0b43 : 00000000`00000000 00000000`000e0082 00000000`00000000 00000000`00000001 : nt!VfDriverUnloadImage+0x2e
fffff880`031cb440 fffff800`02ca0fbd : 00000000`00000000 fffffa80`05cb8010 00000000`00000000 00000000`00010200 : nt!MiUnloadSystemImage+0x283
fffff880`031cb4b0 fffff800`02d424d1 : 00000000`00000000 00000000`00000000 fffffa80`0441ec90 00000000`00000000 : nt!MmUnloadSystemImage+0x4d
fffff880`031cb4f0 fffff800`028d3af4 : 00000000`00000000 00000000`00000000 fffffa80`0441ec90 fffffa80`05c18e00 : nt!IopDeleteDriver+0x41
fffff880`031cb520 fffff800`029422d2 : 00000000`00000000 fffffa80`05cb8940 fffffa80`05cb8d70 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`031cb580 fffff800`02bc6417 : fffffa80`05cb8620 fffffa80`05cb8620 00000000`00000001 fffffa80`0441e9f0 : nt! ?? ::FNODOBFM::`string'+0x4176f
fffff880`031cb630 fffff800`028d3af4 : fffff880`042d1068 00000000`00000015 fffffa80`0441e9f0 00000000`00000015 : nt!IopDeleteFile+0x1a7
fffff880`031cb6c0 fffff880`042b4b79 : 00000000`00000015 fffff880`042d1068 fffff880`042d0cd0 00000000`00010246 : nt!ObfDereferenceObject+0xd4
fffff880`031cb720 00000000`00000015 : fffff880`042d1068 fffff880`042d0cd0 00000000`00010246 fffff880`007a0078 : atikmpag+0x2fb79
fffff880`031cb728 fffff880`042d1068 : fffff880`042d0cd0 00000000`00010246 fffff880`007a0078 fffff880`04286550 : 0x15
fffff880`031cb730 fffff880`042d0cd0 : 00000000`00010246 fffff880`007a0078 fffff880`04286550 fffffa80`05cda020 : atikmpag+0x4c068
fffff880`031cb738 00000000`00010246 : fffff880`007a0078 fffff880`04286550 fffffa80`05cda020 fffff880`042e3aca : atikmpag+0x4bcd0
fffff880`031cb740 fffff880`007a0078 : fffff880`04286550 fffffa80`05cda020 fffff880`042e3aca fffffa80`05cda020 : 0x10246
fffff880`031cb748 fffff880`04286550 : fffffa80`05cda020 fffff880`042e3aca fffffa80`05cda020 00000000`c0000001 : 0xfffff880`007a0078
fffff880`031cb750 fffffa80`05cda020 : fffff880`042e3aca fffffa80`05cda020 00000000`c0000001 00000000`00000015 : atikmpag+0x1550
fffff880`031cb758 fffff880`042e3aca : fffffa80`05cda020 00000000`c0000001 00000000`00000015 00000000`c0000001 : 0xfffffa80`05cda020
fffff880`031cb760 fffff880`0435c296 : fffffa80`05c18e10 fffff880`0435c248 00000000`00000010 00000000`00010246 : dxgkrnl!DpiDxgkDdiUnload+0x22
fffff880`031cb790 fffff800`02cb27b8 : 00000000`00000000 00000000`00000015 00000000`00000000 00000000`00000020 : dxgkrnl!DpiDriverUnload+0x4e
fffff880`031cb7d0 fffff800`02cb2a52 : fffffa80`05c18f60 fffffa80`05c18f60 fffff800`02bcab01 fffff800`02bbd800 : nt!IopUnloadDriver+0x3c6
fffff880`031cb9a0 fffff800`029c61c2 : fffff8a0`06ea1d00 ffffffff`ffffffc0 ffffffff`ffffffc0 fffff8a0`006c7df0 : nt!PnpUnloadAttachedDriver+0x92
fffff880`031cb9f0 fffff800`02cb2ac4 : fffffa80`054016e0 00000000`00000000 00000000`00000002 fffffa80`05402a10 : nt!PnpRemoveLockedDeviceNode+0x232
fffff880`031cba40 fffff800`02cb2bd0 : 00000000`00000000 fffff8a0`06f4d001 fffff8a0`06ed5720 ffffdffd`dd589b4e : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`031cba70 fffff800`02d43a34 : 00000000`00000002 00000000`00000000 fffffa80`054016e0 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`031cbae0 fffff800`02d4408c : fffff880`00000000 00000000`00010200 fffff880`031cbc00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
fffff880`031cbc20 fffff800`02c2d34e : 00000000`00000000 fffffa80`0654caf0 fffff8a0`06abe0b0 fffff800`02a6a200 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`031cbc50 fffff800`028d4001 : fffff800`02b33998 fffff8a0`06f4d010 fffff800`02a6a2b8 fffffa80`0441a680 : nt! ?? ::NNGAKEGL::`string'+0x5b3cb
fffff880`031cbcb0 fffff800`02b64fee : 00000000`00000000 fffffa80`0441a680 00000000`00000080 fffffa80`0398fb30 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`028bb5e6 : fffff880`02f64180 fffffa80`0441a680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xc4_62_VRF_LEAKED_POOL_IMAGE_atikmdag.sys

BUCKET_ID:  X64_0xc4_62_VRF_LEAKED_POOL_IMAGE_atikmdag.sys

Followup: MachineOwner
---------

[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\Windows_NT6_BSOD_jcgriff2\030212-22230-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a5a670
Debug session time: Fri Mar  2 14:08:12.513 2012 (UTC - 7:00)
System Uptime: 0 days 0:12:59.292
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88002d21f8c, fffff880098e5790, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+3c )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88002d21f8c, Address of the instruction which caused the bugcheck
Arg3: fffff880098e5790, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+3c
fffff880`02d21f8c 488b4268        mov     rax,qword ptr [rdx+68h]

CONTEXT:  fffff880098e5790 -- (.cxr 0xfffff880098e5790)
rax=fffff880098e6258 rbx=0000000000000000 rcx=fffffa8005938000
rdx=0000000000000246 rsi=0000000000000246 rdi=0000000000000000
rip=fffff88002d21f8c rsp=fffff880098e6170 rbp=fffff8800a810000
 r8=0000000007a80000  r9=0000000000000000 r10=0000000000000246
r11=fffff8a00a42b000 r12=fffffa80057e4000 r13=000000000000a43c
r14=fffffa8005938000 r15=fffffa80060b8000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x3c:
fffff880`02d21f8c 488b4268        mov     rax,qword ptr [rdx+68h] ds:002b:00000000`000002ae=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  javaw.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88002d21f8c

STACK_TEXT:  
fffff880`098e6170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x3c


FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+3c
fffff880`02d21f8c 488b4268        mov     rax,qword ptr [rdx+68h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff880098e5790 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+3c

BUCKET_ID:  X64_0x3B_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+3c

Followup: MachineOwner
---------


[/list]

1. I am always concerned when I see a Verifier enabled crash that points to Windows system files. This typically means a hardware related crash... I wish we could determine which hardware was at fault.
2. Points to a graphics card driver or the card itself...
3. Points to DirectX/the graphics card/the graphics card drivers.

Just for something we have not yet tried: use Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details to re-install DirectX. Disable Verifier afterward and see if the system runs more stable.

 

[garthrs]

Once the new heat sink comes in, i'll give that a shot. I did some research and found that my chip should idle at 35-45 degrees, not 60... the max operating temp is 62 degrees celius.

I'll install the new sink, re-install direct x and disable DV... hopefully that will help me stablize a bit. Thanks again for all the help.

 

[writhziden]

Which chip idles at 60 C? Your CPU range was 29-59 C. You said you were getting 71 C for something; was that the GPU? The Radeon HD 6850 runs nominally at 74 C under stress in most systems and the max is 85-90 C, so that should not be a concern.

Radeon HD 6850 & 6870 review

 

[garthrs]

I was talking about my CPU. The radeon actually runs fairly cool. I think it maxed out at like 72 during the furmark test.

OCCT showed my CPU temps hitting 82-84 right before a crash.

 

[writhziden]

That is definitely too high. Anything over 70 C could potentially damage the CPU. I would definitely go with your first instinct to inspect all cooling for the CPU.

 

[garthrs]

Got the new heat sink installed. I am running much cooler and the usual programs that crash me are running fairly well atm...

I did crack open my Liquid cooling system (Fan from main radiator unit) and found a VERY thick layer of dust that was not visible from the outside. The was almost no surface area visible. FYI: Make sure you you get in your radiator when you blow the dust out of your systems... Mine was cleaned about every three weeks and I had massive buildup... LOL! This means that my colling unit is probably fine, just had too much dust in it. I'll stick with the sink anyway, just in case.

I'll let you know once I make it a week.

 

[writhziden]

Alright, best wishes!

 

[garthrs]

Looks solid. Lesson here: When blowing dust out of your pc... don't forget to check INSIDE your liquid cooling system. Thanks a million for all the help, especially for sticking with me through the craziness! I'd rep you all day, but it only let's me do it once...

 

[writhziden]

Awesome! Glad it all worked out in the end.

Thanks for posting back and marking the thread solved.