Witam ponownie! Znów problem z blue screenem. Mam podejrzenia co do kompatybilności mojej płyty głównej GA-MA790FXT-UD5P z Vistą. Proszę o zweryfikowanie moich podejrzeń. Czy może to być wina nowego (w miare) chipset'u?
http://www.microsoft.com/windows/compatibility/Search.aspx?type=Hardware&s=GA-MA790FXT-UD5P&results=50&page=2
poniżej zawartość minidump'a:
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {fffffa80066286b0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa80066286b0, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
FAULTING_THREAD: fffffa80066286b0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff9800852b1ef to fffff80001c4e250
STACK_TEXT:
fffff980`0a316578 fffff980`0852b1ef : 00000000`000000ea fffffa80`066286b0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff980`0a316580 fffff980`0852b39e : fffff980`0a316650 fffff980`080dfbf3 fffff980`0a316650 00000000`00003f00 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff980`0a3165f0 fffff980`07ebfd97 : 00000000`00000000 fffff980`080dfbd8 fffff980`0a316780 00000000`01c9c380 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff980`0a316630 00000000`00000000 : fffff980`080dfbd8 fffff980`0a316780 00000000`01c9c380 00000000`00000028 : atikmdag+0x30d97
STACK_COMMAND: .thread 0xfffffa80066286b0 ; kb
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff980`0852b1ef cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b774
FAILURE_BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: X64_0xEA_IMAGE_dxgkrnl.sys
Followup: MachineOwner
---------
3: kd> lmvm dxgkrnl
start end module name
fffff980`08524000 fffff980`08600000 dxgkrnl (pdb symbols) c:\symbole\dxgkrnl.pdb\CBB59D3CA0C54796BACC0476BF4294D61\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Mapped memory image file: c:\symbole\dxgkrnl.sys\4549B774dc000\dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Thu Nov 02 10:16:36 2006 (4549B774)
CheckSum: 000DE4E9
ImageSize: 000DC000
File version: 6.0.6000.16386
Product version: 6.0.6000.16386
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgkrnl.sys
OriginalFilename: dxgkrnl.sys
ProductVersion: 6.0.6000.16386
FileVersion: 6.0.6000.16386 (vista_rtm.061101-2205)
FileDescription: DirectX Graphics Kernel
LegalCopyright: © Microsoft Corporation. All rights reserved.
PS1. Poprzedni problem został rozwiazany, poprzez zmiane sterowników. Tutaj to nic nie daje.
PS2. Memtest nic nie wykrył.
PS3. Jeśli to kwestia kompatybilności to co zrobić?
