Zufällige Bluescreens

dadonking · 8. September 2011

Werde momentan von zufälligen Bluescreens heimgesucht, seitdem ich von 2x1 GB auf 2x8 GB Ram gewechselt habe und den Ati Grafiktreiber aktualisiert habe.

Habe jetzt MemTest ein bisschen testen lassen und damit auch nichts finden können.

Leider weiß ich nicht, wie man ein Dumpfile liest, daher habe ich es mal in den Anhang gesetzt. Habs als zip-Archiv gepackt, da man es hier sonst nicht hochladen kann.

Könnte mir einer von euch sagen, wo das Problem für diese zufälligen Bluescreens liegt?

WickedWeazel · 8. September 2011

Mehr Infos zum System bitte.

xxMuahdibxx · 8. September 2011

Welches BS .... welche Treiber @ Graka ... was für Ram / Mainboard / CPU Congfig .

Ansonsten könnte es alles sein .

dadonking · 8. September 2011

Mein System:
Win 7 64 SP1
ASRock M3A785GM-LE 128M 785G AM3 µATX
AMD Athlon II X3 440
320GB Hitachi Deskstar 7K1000.C
1024MB Club 3D Radeon HD 5750

zuvor 2GB (2x 1024MB) Kingston ValueRAM DDR3-1333
nun 8GB (2x 4096MB) TeamGroup Elite DDR3-1333

nun aktuellste ATi Treiberversion Catalyst 11.8

Hier das Dumpfile nochmal als Text, von der ich nicht weiß, wie sie zu deuten ist.

Code:

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


Loading Dump File [C:\Windows\Minidump\090811-18281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`0344c670
Debug session time: Thu Sep  8 11:31:28.858 2011 (GMT+2)
System Uptime: 0 days 1:30:54.108
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................................................
Loading unloaded module list
.......
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000328a959, fffff88008874010, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for kdcom.dll
*** ERROR: Module load completed but symbols could not be loaded for kdcom.dll
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Unable to load image \SystemRoot\system32\drivers\cmudaxp.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
Probably caused by : dxgmms1.sys ( dxgmms1+28986 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005
Arg2: fffff8000328a959
Arg3: fffff88008874010
Arg4: 0000000000000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

MODULE_NAME:  dxgmms1

FAULTING_MODULE: fffff80003207000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

CONTEXT:  fffff88008874010 -- (.cxr fffff88008874010)
rax=fffffa8008ed8b60 rbx=fffffa8007df0680 rcx=fffffa8007df0680
rdx=0000000000000000 rsi=0000000080000000 rdi=fffff88003164180
rip=fffff8000328a959 rsp=fffff880088749f0 rbp=0000000000000000
 r8=00fffa8008f99c00  r9=0000000000000000 r10=0000000000000033
r11=fffffa8007df06b0 r12=fffffa800962c060 r13=0000000000000001
r14=0000000000000001 r15=0000000000000001
iopl=0         nv up di pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210006
nt+0x83959:
fffff800`0328a959 418b4808         mov     ecx,[r8+0x8] ds:002b:9c08=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x3B

LAST_CONTROL_TRANSFER:  from fffffa8009446a00 to fffff8000328a959

STACK_TEXT:  
fffff880`088749f0 fffffa80`09446a00 : fffffa80`08ed8c68 fffff880`08874a50 fffffa80`09446a60 00000000`00000000 : nt+0x83959
fffff880`088749f8 fffffa80`08ed8c68 : fffff880`08874a50 fffffa80`09446a60 00000000`00000000 00000000`00000000 : 0xfffffa80`09446a00
fffff880`08874a00 fffff880`08874a50 : fffffa80`09446a60 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`08ed8c68
fffff880`08874a08 fffffa80`09446a60 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`09446a60 : 0xfffff880`08874a50
fffff880`08874a10 00000000`00000000 : 00000000`00000000 00000000`00000001 fffffa80`09446a60 fffff880`08874b10 : 0xfffffa80`09446a60
fffff880`08874a18 00000000`00000000 : 00000000`00000001 fffffa80`09446a60 fffff880`08874b10 ffffffff`c000000d : 0x0
fffff880`08874a20 00000000`00000001 : fffffa80`09446a60 fffff880`08874b10 ffffffff`c000000d fffffa80`09609a40 : 0x0
fffff880`08874a28 fffffa80`09446a60 : fffff880`08874b10 ffffffff`c000000d fffffa80`09609a40 fffffa80`096099e0 : 0x1
fffff880`08874a30 fffff880`08874b10 : ffffffff`c000000d fffffa80`09609a40 fffffa80`096099e0 00000000`80000011 : 0xfffffa80`09446a60
fffff880`08874a38 ffffffff`c000000d : fffffa80`09609a40 fffffa80`096099e0 00000000`80000011 fffff880`043c1986 : 0xfffff880`08874b10
fffff880`08874a40 fffffa80`09609a40 : fffffa80`096099e0 00000000`80000011 fffff880`043c1986 00000000`00000001 : 0xffffffff`c000000d
fffff880`08874a48 fffffa80`096099e0 : 00000000`80000011 fffff880`043c1986 00000000`00000001 fffffa80`093791b0 : 0xfffffa80`09609a40
fffff880`08874a50 00000000`80000011 : fffff880`043c1986 00000000`00000001 fffffa80`093791b0 fffff880`08875180 : 0xfffffa80`096099e0
fffff880`08874a58 fffff880`043c1986 : 00000000`00000001 fffffa80`093791b0 fffff880`08875180 fffff880`042a6122 : 0x80000011
fffff880`08874a60 00000000`00000001 : fffffa80`093791b0 fffff880`08875180 fffff880`042a6122 00000000`75182401 : dxgmms1+0x28986
fffff880`08874a68 fffffa80`093791b0 : fffff880`08875180 fffff880`042a6122 00000000`75182401 ffffffff`c000000d : 0x1
fffff880`08874a70 fffff880`08875180 : fffff880`042a6122 00000000`75182401 ffffffff`c000000d 00000000`00000001 : 0xfffffa80`093791b0
fffff880`08874a78 fffff880`042a6122 : 00000000`75182401 ffffffff`c000000d 00000000`00000001 00000000`00000002 : 0xfffff880`08875180
fffff880`08874a80 00000000`75182401 : ffffffff`c000000d 00000000`00000001 00000000`00000002 fffff8a0`0bb41e00 : dxgkrnl+0x1122
fffff880`08874a88 ffffffff`c000000d : 00000000`00000001 00000000`00000002 fffff8a0`0bb41e00 fffff880`04314eeb : 0x75182401
fffff880`08874a90 00000000`00000001 : 00000000`00000002 fffff8a0`0bb41e00 fffff880`04314eeb 00000000`00000000 : 0xffffffff`c000000d
fffff880`08874a98 00000000`00000002 : fffff8a0`0bb41e00 fffff880`04314eeb 00000000`00000000 00000000`00000200 : 0x1
fffff880`08874aa0 fffff8a0`0bb41e00 : fffff880`04314eeb 00000000`00000000 00000000`00000200 fffff880`08875180 : 0x2
fffff880`08874aa8 fffff880`04314eeb : 00000000`00000000 00000000`00000200 fffff880`08875180 00000000`00000000 : 0xfffff8a0`0bb41e00
fffff880`08874ab0 00000000`00000000 : 00000000`00000200 fffff880`08875180 00000000`00000000 00000000`00000001 : dxgkrnl+0x6feeb
fffff880`08874ab8 00000000`00000200 : fffff880`08875180 00000000`00000000 00000000`00000001 fffff880`088750d8 : 0x0
fffff880`08874ac0 fffff880`08875180 : 00000000`00000000 00000000`00000001 fffff880`088750d8 fffff880`08874b50 : 0x200
fffff880`08874ac8 00000000`00000000 : 00000000`00000001 fffff880`088750d8 fffff880`08874b50 fffffa80`08f0b000 : 0xfffff880`08875180
fffff880`08874ad0 00000000`00000001 : fffff880`088750d8 fffff880`08874b50 fffffa80`08f0b000 fffff880`08875270 : 0x0
fffff880`08874ad8 fffff880`088750d8 : fffff880`08874b50 fffffa80`08f0b000 fffff880`08875270 00000000`00000000 : 0x1
fffff880`08874ae0 fffff880`08874b50 : fffffa80`08f0b000 fffff880`08875270 00000000`00000000 fffffa80`08f0b000 : 0xfffff880`088750d8
fffff880`08874ae8 fffffa80`08f0b000 : fffff880`08875270 00000000`00000000 fffffa80`08f0b000 fffff8a0`037c9f10 : 0xfffff880`08874b50
fffff880`08874af0 fffff880`08875270 : 00000000`00000000 fffffa80`08f0b000 fffff8a0`037c9f10 00000000`00000000 : 0xfffffa80`08f0b000
fffff880`08874af8 00000000`00000000 : fffffa80`08f0b000 fffff8a0`037c9f10 00000000`00000000 00000000`00000000 : 0xfffff880`08875270
fffff880`08874b00 fffffa80`08f0b000 : fffff8a0`037c9f10 00000000`00000000 00000000`00000000 fffff880`05d60000 : 0x0
fffff880`08874b08 fffff8a0`037c9f10 : 00000000`00000000 00000000`00000000 fffff880`05d60000 fffff8a0`0af85010 : 0xfffffa80`08f0b000
fffff880`08874b10 00000000`00000000 : 00000000`00000000 fffff880`05d60000 fffff8a0`0af85010 fffffa80`07d20140 : 0xfffff8a0`037c9f10
fffff880`08874b18 00000000`00000000 : fffff880`05d60000 fffff8a0`0af85010 fffffa80`07d20140 00000000`00000001 : 0x0
fffff880`08874b20 fffff880`05d60000 : fffff8a0`0af85010 fffffa80`07d20140 00000000`00000001 fffff8a0`0d37a000 : 0x0
fffff880`08874b28 fffff8a0`0af85010 : fffffa80`07d20140 00000000`00000001 fffff8a0`0d37a000 fffff800`033b2fbd : 0xfffff880`05d60000
fffff880`08874b30 fffffa80`07d20140 : 00000000`00000001 fffff8a0`0d37a000 fffff800`033b2fbd 00000000`12f34000 : 0xfffff8a0`0af85010
fffff880`08874b38 00000000`00000001 : fffff8a0`0d37a000 fffff800`033b2fbd 00000000`12f34000 fffff8a0`03e00000 : 0xfffffa80`07d20140
fffff880`08874b40 fffff8a0`0d37a000 : fffff800`033b2fbd 00000000`12f34000 fffff8a0`03e00000 fffff8a0`022b9210 : 0x1
fffff880`08874b48 fffff800`033b2fbd : 00000000`12f34000 fffff8a0`03e00000 fffff8a0`022b9210 fffff880`042e6469 : 0xfffff8a0`0d37a000
fffff880`08874b50 00000000`12f34000 : fffff8a0`03e00000 fffff8a0`022b9210 fffff880`042e6469 00000000`064e0000 : nt+0x1abfbd
fffff880`08874b58 fffff8a0`03e00000 : fffff8a0`022b9210 fffff880`042e6469 00000000`064e0000 fffff880`00000b08 : 0x12f34000
fffff880`08874b60 fffff8a0`022b9210 : fffff880`042e6469 00000000`064e0000 fffff880`00000b08 00000000`00000000 : 0xfffff8a0`03e00000
fffff880`08874b68 fffff880`042e6469 : 00000000`064e0000 fffff880`00000b08 00000000`00000000 00000000`00000000 : 0xfffff8a0`022b9210
fffff880`08874b70 00000000`064e0000 : fffff880`00000b08 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl+0x41469
fffff880`08874b78 fffff880`00000b08 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x64e0000


FOLLOWUP_IP: 
dxgmms1+28986
fffff880`043c1986 ??               ???

SYMBOL_STACK_INDEX:  e

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  dxgmms1+28986

IMAGE_NAME:  dxgmms1.sys

STACK_COMMAND:  .cxr fffff88008874010 ; kb

BUCKET_ID:  WRONG_SYMBOLS

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

Ergänzung (8. September 2011)

Also ich vermute einen Treiberfehler durch dxgmms1.sys.

Wüsste jetzt aber nicht, wie ich diesen beheben könnte.

Inzersdorfer · 8. September 2011

BUCKET_ID: WRONG_SYMBOLS Um die .dmp korrekt auszuwerten braucht WinDbg Symboldateien, die können heruntergeladen werden oder durch Eingabe eines Pfades zu einem MS Server während des debuggens nachgeladen werden, dazu mußt du aber dabei online bleiben:
In WinDbg unter File/Symbol File Path gibst du folgenden Pfad ein (über copy&paste):
SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION eine Ausnahme während einer Routine zur Rechteerhöhung eines Codes.
Parameter1: 0xc0000005 Eine Speicherzugriffsverletzung
Verursacher dxgmms1 (DirectX)
Soll heißen, insofern die Ergebnisse zuverläßig währen, ein Problem des Grafiktreibers oder des RAM.

BTW: wie hast du die .dmp "gepackt", 7zip und winrar zeigen "unbekannte Methode".

dadonking · 8. September 2011

Habe die mit den Voreinstellungen von 7zip gepackt.

Hier nochmal der Code mit den Verweisen.

Code:

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


Loading Dump File [C:\Windows\Minidump\090811-18281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServe
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`0344c670
Debug session time: Thu Sep  8 11:31:28.858 2011 (GMT+2)
System Uptime: 0 days 1:30:54.108
Loading Kernel Symbols
.....................................................................................................................................................
Loading unloaded module list
.......
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000328a959, fffff88008874010, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+62 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005
Arg2: fffff8000328a959
Arg3: fffff88008874010
Arg4: 0000000000000000

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


CONTEXT:  fffff88008874010 -- (.cxr fffff88008874010)
rax=fffffa8008ed8b60 rbx=fffffa8007df0680 rcx=fffffa8007df0680
rdx=0000000000000000 rsi=0000000080000000 rdi=fffff88003164180
rip=fffff8000328a959 rsp=fffff880088749f0 rbp=0000000000000000
 r8=00fffa8008f99c00  r9=0000000000000000 r10=0000000000000033
r11=fffffa8007df06b0 r12=fffffa800962c060 r13=0000000000000001
r14=0000000000000001 r15=0000000000000001
iopl=0         nv up di pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210006
nt!ExAcquireResourceSharedLite+0xfd:
fffff800`0328a959 418b4808         mov     ecx,[r8+0x8] ds:002b:9c08=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x3B

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880043c1986 to fffff8000328a959

STACK_TEXT:  
fffff880`088749f0 fffff880`043c1986 : 00000000`00000001 fffffa80`093791b0 fffff880`08875180 fffff880`042a6122 : nt!ExAcquireResourceSharedLite+0xfd
fffff880`08874a60 fffff880`04314eeb : 00000000`00000000 00000000`00000200 fffff880`08875180 00000000`00000000 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x62
fffff880`08874ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x263


FOLLOWUP_IP: 
dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+62
fffff880`043c1986 488b4308         mov     rax,[rbx+0x8]

SYMBOL_STACK_INDEX:  1

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+62

MODULE_NAME:  dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr fffff88008874010 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+62

BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+62

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

Inzersdorfer · 8. September 2011

Sehr schön, es bleibt bei: Grafiktreiber oder RAM als mögliche Ursachen.

RAM prüfen mit Memtest86+ via Boot-CD mindestens 7 komplette Durchgänge (kann einige Stunden dauern, wenn Fehler angezeigt werden kann abgebrochen werden, um das defekte Modul zu finden den Test mit nur jeweils 1 RAM-Modul wiederholen) https://www.computerbase.de/downloads/systemtools/memtest86-plus/

Zur zip Datei, hier ein Screenshot:

dadonking · 8. September 2011

Ok, dann werde ich das mal tun...
Kamen jetzt noch weitere Bluescreens, die wohl aber nicht durch dxgmms1.sys ausgelöst wurden.

Code:

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


Loading Dump File [C:\Windows\Minidump\090811-23593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServe
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`0324a000 PsLoadedModuleList = 0xfffff800`0348f670
Debug session time: Thu Sep  8 16:08:05.975 2011 (GMT+2)
System Uptime: 0 days 1:13:09.225
Loading Kernel Symbols
...................................................................................................................................................
Loading unloaded module list
.......
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

1: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.

FAULTING_IP: 
+0
00000000`00000000 ??               ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x1E

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032d237e to fffff800032d2442

STACK_TEXT:  
fffff880`0311b5e0 fffff800`032d237e : 0000000a`382eac73 fffff880`0311bc58 00000000`0004494e fffff880`009ebf48 : nt!KiProcessExpiredTimerList+0x72
fffff880`0311bc30 fffff800`032d2167 : 00000003`a8c068c1 00000003`0004494e 00000003`a8c068a8 00000000`0000004e : nt!KiTimerExpiration+0x1be
fffff880`0311bcd0 fffff800`032be96a : fffff880`009e9180 fffff880`009f3f80 00000000`00000000 fffff880`04264588 : nt!KiRetireDpcList+0x277
fffff880`0311bd80 00000000`00000000 : fffff880`0311c000 fffff880`03116000 fffff880`0311bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`032be5fe 90               nop

SYMBOL_STACK_INDEX:  1

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

MODULE_NAME:  nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .trap fffff8800311b450 ; kb

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner

Code:

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


Loading Dump File [C:\Windows\Minidump\090811-18343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServe
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`02665000 PsLoadedModuleList = 0xfffff800`028aa670
Debug session time: Thu Sep  8 16:11:26.406 2011 (GMT+2)
System Uptime: 0 days 0:02:42.937
Loading Kernel Symbols
.........................................................................................
Loading unloaded module list
......
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {973e7fe74, 2, 1, fffff8000262b77e}

Probably caused by : win32k.sys ( win32k!RawInputThread+6ed )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000973e7fe74, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8000262b77e, address which referenced memory

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


OVERLAPPED_MODULE:  Dxapi

WRITE_ADDRESS: unable to get MiSystemVaType - probably bad symbols
 0000000973e7fe74 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!KeQueryPerformanceCounter+8a
fffff800`0262b77e 360084c07407e873 add     ss:[rax+rax*8+0x73e80774],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff800026e11e9 to fffff800026e1c40

STACK_TEXT:  
fffff880`0784d2b8 fffff800`026e11e9 : 00000000`0000000a 00000009`73e7fe74 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0784d2c0 fffff800`026dfe60 : fffff900`c00c2060 00000000`00000000 fffff900`c00c2060 8b4dc68b`4d102454 : nt!KiBugCheckDispatch+0x69
fffff880`0784d400 fffff800`0262b77e : fffffa80`0809fb60 00000000`00000002 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0784d590 fffff800`027e68d2 : fffff880`009f3f80 fffffa80`069dd7c0 00000000`00000001 fffff880`0784d620 : hal!KeQueryPerformanceCounter+0x8a
fffff880`0784d5c0 fffff800`026e49e5 : 00000000`00000001 fffff880`009e9180 fffff880`0784ddb0 fffffa80`0809fb60 : nt!EtwTraceContextSwap+0x92
fffff880`0784d620 fffff800`026e44da : fffff880`07617700 fffff960`00174899 00000001`00000014 00000c80`00000c80 : nt!SwapContext_PatchXRstor+0x103
fffff880`0784d660 fffff800`026e6f32 : fffff900`c0616da0 fffffa80`0809fb60 fffff900`00000000 00000000`00000005 : nt!KiSwapContext+0x7a
fffff880`0784d7a0 fffff800`026e644a : fffffa80`080e5980 000000c2`000000d5 fffffa80`00000000 ffffffff`ffffffff : nt!KiCommitThreadWait+0x1d2
fffff880`0784d830 fffff960`00173a99 : 00000000`00000004 fffffa80`07f5a200 00000000`00000001 00000000`0000000d : nt!KeWaitForMultipleObjects+0x272
fffff880`0784daf0 fffff960`001047ac : fffffa80`0000007b 00000000`0000000f fffff880`00000003 ffffffff`800002c4 : win32k!RawInputThread+0x6ed
fffff880`0784dbc0 fffff960`0018469a : fffffa80`00000002 fffff880`0781ff40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`0784dbf0 fffff800`026e0ed3 : fffffa80`0809fb60 00000000`00000004 000007ff`fffd4000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`0784dc20 000007fe`fd151eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`007efc18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd151eea


FOLLOWUP_IP: 
win32k!RawInputThread+6ed
fffff960`00173a99 8bf8             mov     edi,eax

SYMBOL_STACK_INDEX:  9

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  win32k!RawInputThread+6ed

MODULE_NAME:  win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4df2dbd1

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xA_W_win32k!RawInputThread+6ed

BUCKET_ID:  X64_0xA_W_win32k!RawInputThread+6ed

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

Code:

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


Loading Dump File [C:\Windows\Minidump\090811-17937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32; c:\windows\system\System32; http://www.alexander.com/SymServe
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`0321f000 PsLoadedModuleList = 0xfffff800`03464670
Debug session time: Thu Sep  8 16:12:59.250 2011 (GMT+2)
System Uptime: 0 days 0:01:05.468
Loading Kernel Symbols
...................................................................................................................................................
Loading unloaded module list
.....
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!IdeProcessCompletedRequests+a4 )

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

2: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.

FAULTING_IP: 
+0
00000000`00000000 ??               ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x1E

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8800115b104 to fffff8800115b3d4

TRAP_FRAME:  fffff8800318c8b0 -- (.trap fffff8800318c8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed.
rax=fffffa8007898b01 rbx=fffffa80069f0750 rcx=fffffa80078811a0
rdx=fffffa80095727a0 rsi=fffffa8009572750 rdi=fffff88000e8af1e
rip=fffff8800115b3d4 rsp=fffff8800318ca40 rbp=fffffa80078987d0
 r8=0000000000000000  r9=0000000000000001 r10=fffffa8007882610
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ataport!IdeProcessCompletedRequests+0xa4:
fffff880`0115b3d4 884321       mov [rbx+0x21],al ds:7d00:fffffa80`069f0771=??
Resetting default scope

STACK_TEXT:  
fffff880`0318ca40 fffff880`0115b104 : fffffa80`078811a0 00000000`00000000 fffffa80`078811a0 fffffa80`095727a0 : ataport!IdeProcessCompletedRequests+0xa4
fffff880`0318cb70 fffff880`00e8b4ce : fffffa80`069e8000 fffff880`0318cc58 fffffa80`07881050 fffffa80`069e8750 : ataport!IdePortCompletionDpc+0x1a8
fffff880`0318cc30 fffffa80`069e8000 : fffff880`0318cc58 fffffa80`07881050 fffffa80`069e8750 fffff880`03164180 : sptd+0x424ce
fffff880`0318cc38 fffff880`0318cc58 : fffffa80`07881050 fffffa80`069e8750 fffff880`03164180 00000000`00000000 : 0xfffffa80`069e8000
fffff880`0318cc40 fffffa80`07881050 : fffffa80`069e8750 fffff880`03164180 00000000`00000000 fffff880`03168f00 : 0xfffff880`0318cc58
fffff880`0318cc48 fffffa80`069e8750 : fffff880`03164180 00000000`00000000 fffff880`03168f00 00000000`00000022 : 0xfffffa80`07881050
fffff880`0318cc50 fffff880`03164180 : 00000000`00000000 fffff880`03168f00 00000000`00000022 00000000`00000000 : 0xfffffa80`069e8750
fffff880`0318cc58 00000000`00000000 : fffff880`03168f00 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffff880`03164180
fffff880`0318cc60 fffff880`03168f00 : 00000000`00000022 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffff880`0318cc68 00000000`00000022 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07881118 : 0xfffff880`03168f00
fffff880`0318cc70 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`07881118 fffffa80`07881050 : 0x22
fffff880`0318cc78 00000000`00000000 : 00000000`00000000 fffffa80`07881118 fffffa80`07881050 fffffa80`069e90dd : 0x0
fffff880`0318cc80 00000000`00000000 : fffffa80`07881118 fffffa80`07881050 fffffa80`069e90dd fffffa80`07881118 : 0x0
fffff880`0318cc88 fffffa80`07881118 : fffffa80`07881050 fffffa80`069e90dd fffffa80`07881118 fffff880`0115af5c : 0x0
fffff880`0318cc90 fffffa80`07881050 : fffffa80`069e90dd fffffa80`07881118 fffff880`0115af5c 00000000`00000002 : 0xfffffa80`07881118
fffff880`0318cc98 fffffa80`069e90dd : fffffa80`07881118 fffff880`0115af5c 00000000`00000002 fffff880`03164180 : 0xfffffa80`07881050
fffff880`0318cca0 fffffa80`07881118 : fffff880`0115af5c 00000000`00000002 fffff880`03164180 00000000`00000002 : 0xfffffa80`069e90dd
fffff880`0318cca8 fffff880`0115af5c : 00000000`00000002 fffff880`03164180 00000000`00000002 fffff800`032a70ac : 0xfffffa80`07881118
fffff880`0318ccb0 00000000`00000002 : fffff880`03164180 00000000`00000002 fffff800`032a70ac fffffa80`07881118 : ataport!IdePortCompletionDpc
fffff880`0318ccb8 fffff880`03164180 : 00000000`00000002 fffff800`032a70ac fffffa80`07881118 fffffa80`07881050 : 0x2
fffff880`0318ccc0 00000000`00000002 : fffff800`032a70ac fffffa80`07881118 fffffa80`07881050 00000000`00000000 : 0xfffff880`03164180
fffff880`0318ccc8 fffff800`032a70ac : fffffa80`07881118 fffffa80`07881050 00000000`00000000 00000000`00000000 : 0x2
fffff880`0318ccd0 fffff800`0329396a : fffff880`03164180 fffff880`0316ef80 00000000`00000000 fffffa80`069e90a0 : nt!KiRetireDpcList+0x1bc
fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


FOLLOWUP_IP: 
ataport!IdeProcessCompletedRequests+a4
fffff880`0115b3d4 884321           mov     [rbx+0x21],al

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  ataport!IdeProcessCompletedRequests+a4

MODULE_NAME:  ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79293

STACK_COMMAND:  .trap fffff8800318c8b0 ; kb

FAILURE_BUCKET_ID:  X64_0x1E_ataport!IdeProcessCompletedRequests+a4

BUCKET_ID:  X64_0x1E_ataport!IdeProcessCompletedRequests+a4

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

Ergänzung (8. September 2011)

Es ist wohl wirklich der neue Arbeitsspeicher. Schon nach wenigen Minuten hatte MemTest86 die ersten Fehler gefunden. Habe dann bei ca. 25 Fehlern aufgehört.

Vielen Dank an Inzersdorfer

Suche

Zufällige Bluescreens

dadonking

Cadet 1st Year

Anhänge

WickedWeazel

Lieutenant

xxMuahdibxx

Fleet Admiral

dadonking

Cadet 1st Year

Inzersdorfer

Gast

dadonking

Cadet 1st Year

Anhänge

Inzersdorfer

Gast

dadonking

Cadet 1st Year

Ähnliche Themen

Passend zum Thema

Wer erinnert sich? Heute vor 25 Jahren erschien Windows 2000 alias „NT 5.0“

Noch nicht ausgestorben Heute vor 10 Jahren erhielt Windows XP das letzte Update

Windows Update Neues Projekt bringt Windows 95 bis XP auf den neusten Stand