Erbitte Hilfe bei Blluescreen-Analyse

[jfheins]

Hallo erstmal (bzw. zum zweiten mal ^^)

Ich habe in letzter Zeit ein paar Probleme mit meinem Notebook (Ja - sie fingen 1 Monat nach Ablauf der Garantie an )

Unter anderem ständige Bluescreens - und ich weiß nicht genau was ich da am besten mache.

Sie treten sporadisch und nicht reproduzierbar auf - LineRider, VisualStudio und die DP im Opera können eigentlich keine Bluescreens verursachen, oder?
Also hab ich mir mal WinDbg runtergeladen und die Memdumps analysiert (Kernelspeicherabbild) und einn paar analysiert. Eine Analyse hab ich noch vorrätig, der zweite ist ganz frisch (er trat eben auf, als ich diesen Post zum erstenmal posten wollte )

Ich hab schonmal den Grafiktreiber neu drübergebügelt, hat nicht geholfen

Hier der "alte" Bluescreen:

Code:

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\symbols;SRV*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Mar 24 09:53:34.125 2008 (GMT+1)
System Uptime: 0 days 18:07:50.708
Loading Kernel Symbols
....................Page 803eca too large to be in the dump file.
..
Loading User Symbols

Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {89340920, 880a4dc8, b35e8cb4, 1}

*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll
Page 803eca too large to be in the dump file.


Page 803eca too large to be in the dump file.


Probably caused by : ati2cqag.dll ( ati2cqag+111b7 )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: 89340920, Pointer to a stuck thread object.  Do .thread then kb on it to find
   the hung location.
Arg2: 880a4dc8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: b35e8cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred.  If a debugger is attached,
   this error is not always fatal -- see DESCRIPTION below.  On the
   blue screen, this will always equal 1.

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

Page 803eca too large to be in the dump file.


Page 803eca too large to be in the dump file.



FAULTING_THREAD:  89340920

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 804f8e6e to 80540b9f

STACK_TEXT:  
b36981c0 804f8e6e b35e8b40 b35e8b70 00000000 nt!KiUnlockDispatcherDatabase+0x77
b36981d4 bac40a67 b35e8b94 00000000 00000000 nt!KeSetEvent+0x74
b36984c8 804fd18b b35e8b40 b3698514 b3698508 watchdog!WatchdogKernelApc+0x13b
b3698518 806d0c35 00000000 00000000 b3698530 nt!KiDeliverApc+0xb3
b3698518 806d6dad 00000000 00000000 b3698530 hal!HalpApcInterrupt+0xc5
b36985a8 806d6dd8 b3698620 bf819a26 00000000 hal!HalpQueryPerformanceCounter+0x1d
b36985b0 bf819a26 00000000 00000f10 bfa251b7 hal!HalpPmTimerQueryPerfCount+0x8
b36985bc bfa251b7 b36985dc 00000f08 e2200000 win32k!EngQueryPerformanceCounter+0xd
WARNING: Stack unwind information not available. Following frames may be wrong.
b3698608 804fce0b b37e5460 06f30b80 b37e5460 ati2cqag+0x111b7
b3698620 b3698630 e2200000 e22001c0 022231fa nt!KeRestoreFloatingPointState+0x3f
b3698628 e22001c0 022231fa 00000000 00000000 0xb3698630
b369862c 022231fa 00000000 00000000 00000000 0xe22001c0
b3698630 00000000 00000000 00000000 00000000 0x22231fa


STACK_COMMAND:  .thread 0xffffffff89340920 ; kb

FOLLOWUP_IP: 
ati2cqag+111b7
bfa251b7 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  ati2cqag+111b7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ati2cqag

IMAGE_NAME:  ati2cqag.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  43150b19

FAILURE_BUCKET_ID:  0xEA_IMAGE_ati2cqag.dll_DATE_2005_08_31

BUCKET_ID:  0xEA_IMAGE_ati2cqag.dll_DATE_2005_08_31

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

kd> lmvm ati2cqag
start    end        module name
bfa14000 bfa4d000   ati2cqag T (no symbols)           
    Loaded symbol image file: ati2cqag.dll
    Image path: \SystemRoot\System32\ati2cqag.dll
    Image name: ati2cqag.dll
    Timestamp:        Wed Aug 31 03:42:49 2005 (43150B19)
    CheckSum:         000459B6
    ImageSize:        00039000
    Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0

Und der von gerade eben:

Code:

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\symbols
Executable search path is: 
Missing image name, possible paged-out or corrupt data.
*** WARNING: Unable to verify timestamp for Unknown_Module_018e4378
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_018e4378
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Tue Mar 25 10:48:50.687 2008 (GMT+0)
System Uptime: 0 days 0:41:07.279
WARNING: Unable to reset page directories
Missing image name, possible paged-out or corrupt data.
*** WARNING: Unable to verify timestamp for Unknown_Module_018e4378
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_018e4378
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

Loading unloaded module list
.
WARNING: .reload failed, module list may be incomplete
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {888ff8a8, 89f83a98, ba5c7cb4, 1}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: 888ff8a8, Pointer to a stuck thread object.  Do .thread then kb on it to find
   the hung location.
Arg2: 89f83a98, Pointer to a DEFERRED_WATCHDOG object.
Arg3: ba5c7cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred.  If a debugger is attached,
   this error is not always fatal -- see DESCRIPTION below.  On the
   blue screen, this will always equal 1.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00920031 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

FAULTING_THREAD:  888ff8a8

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

BUGCHECK_STR:  0xEA

LAST_CONTROL_TRANSFER:  from 00000000 to 804f8aef

STACK_TEXT:  
ba5c7b9c 00000000 00000000 00000000 00000000 0x804f8aef


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

Wie gesagt: DP in Opera, Vorschau, Scollbalken angefasst > Bluescreen

[edit=sakura] Ein paar Punkte im Dump entfernt, so dass die Seite besser dargestellt werden kann Mfg, sakura[/edit]