Immer mal verschiedene Bluescreens, verschiedene Zeiten / Tage / Ursachen / Whatever

dotDA

dotDA

Enthusiast
Thread Starter
Mitglied seit
09.03.2010
Beiträge
257
Hallo

habe - ja muss ich zugeben - seit bestimmt bald 1,5 Jahre Bluescreens die mal oder mal nicht auftauchen, mal direkt zwei Tage in Folge, mal 4 Monate Ruhe bei immer gleicher Rechnernutzung (zwei Spiele, surfen blablupp oder Leerlauf).

Selten bei direkter Nutzung (spielen) aber kommt vor, öfter beim Hochfahren vor Windows-Login.

Erst mal ein paar Daten:

CPU: Intel i7 875K Non-OC
RAM: 8 GB A-DATA (2x4 9-9-9-24) Non-OC
Netz: 800 W SuperFlower 80+ Gold
MoBo: EVGA P55 SLI (Meine Vermutung das es die Ursache ist #1)
SoundKa: Creative X-Fi Titanium PCIe (Meine Vermutung das es die Ursache ist #2)
GraKa: GTX 680 (bluescreens aber auch davor mit SLI 295)
HDD-OS: OCZ Vertex 2 128GB (aktuelle FW)
OS: Win7 Prof SP1 + Updates

RAM habe ich mal getestet - keine Auffälligkeiten, auch diverse Stresstests haben nichts gebracht - ist >völlig< zufällig.

Windows-Neuinstallation hat keine Abhilfe geschaffen.

MoBo-Bios-Update hatte gefühlt(!!!) mehr Bluescreens verursache, des Weiteren fehlte ab und an die Soundkarte - war zwar im Gerätemanager, aber Creative-Treiber meinten: Keine Creative-Hardware, des Weiteren fehlte beim aktuellen Bios von EVGA ab und an LAN-Anschluss 1 oder 2 beim Kaltstart - ist aber bekannt (im Forum) wird aber nicht gefixt (wahrscheinlich Mobo "zu alt"). Daher bin ich eine Version zurück.

Mir fällt nur noch ein die Creative-Karte für 1 Jahr zu entfernen und schauen was passiert... wobei ich halt ungern auf die Qualität der Karte verzichten möchte, die Realtek-HD Audio-Sache (ALC888 glaube) hört sich zwar okay an... aber hmm... irgendwie klingt Creative mehr nach "im Spiel wirklich dabei".

Hätte noch eine alte SoundBlaser Live! PCI Karte hier rumliegen *lach*

Abhilfe haben auch diverse Creative-Treiber oder Mod-Treiber (Daniel K) keine gebracht.

###>>> Nun folgen mal ein paar Inhalte aus der Crash-Dump die halt immer wieder verschieden sind <<<###


## Von Heute --->>>

Code: 
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03296670
Debug session time: Sat Jul 21 09:24:36.943 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:12.896
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80052fff50
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000313cb40 to fffff800030d11c0

STACK_TEXT:  
fffff880`08595958 fffff800`0313cb40 : 00000000`0000001a 00000000`00041790 fffffa80`052fff50 00000000`0000ffff : nt!KeBugCheckEx
fffff880`08595960 fffff800`030bd9af : fffffa80`00000000 00000000`03d5ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x355e4
fffff880`08595b20 fffff800`030d0453 : ffffffff`ffffffff 00000000`0396f640 00000000`0396f648 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`08595c20 00000000`773114fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0396f608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773114fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+355e4
fffff800`0313cb40 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+355e4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4

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

## Vom 17.07.2012

Code: 
Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Primary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032ab670
Debug session time: Tue Jul 17 07:03:04.843 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:08.781
*******************************************************************************
*                                                                             *
*                        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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1e_0

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c128 -- (.exr 0xfffff80000b9c128)
ExceptionAddress: fffff880047c578a (USBPORT!USBPORT_GetRootHubPdoExt+0x0000000000000046)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c1d0 -- (.trap 0xfffff80000b9c1d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fbfffa8008f2c050 rbx=0000000000000000 rcx=fffffa800892b578
rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880047c578a rsp=fffff80000b9c360 rbp=fffffa800892b102
 r8=000000004f444648  r9=0000000000000000 r10=fffff80003067000
r11=fffffa800892b1a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
USBPORT!USBPORT_GetRootHubPdoExt+0x46:
fffff880`047c578a 488b7840        mov     rdi,qword ptr [rax+40h] ds:fbfffa80`08f2c090=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030ddbbe to fffff800030e6190

STACK_TEXT:  
fffff800`00b9b208 fffff800`030ddbbe : 00000000`00000000 fffff800`03111320 fffff800`032ec95c fffff800`030f4b0f : nt!KeBugCheck
fffff800`00b9b210 fffff800`03110e2d : fffff800`032ec770 fffff800`032292f0 fffff800`03067000 fffff800`00b9c128 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b240 fffff800`0310fc05 : fffff800`0322cfac fffff800`00b9b2b8 fffff800`00b9c128 fffff800`03067000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b270 fffff800`03120b81 : fffff800`00b9c128 fffff800`00b9b980 fffff800`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
fffff800`00b9b950 fffff800`030e5842 : fffff800`00b9c128 fffffa80`0892b1a0 fffff800`00b9c1d0 fffffa80`0892b050 : nt!KiDispatchException+0x135
fffff800`00b9bff0 fffff800`030e414a : fffff800`0326d700 fffffa80`00000000 fffff880`01b939a0 fffffa80`07b2bbc0 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c1d0 fffff880`047c578a : fffffa80`0892b050 fffff800`030dc3de 00000000`00000000 fffffa80`0892b1a0 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c360 fffff880`047c47a4 : fffffa80`0892c6a0 fffffa80`0892b1a0 fffffa80`0892b050 fffffa80`0892c6a0 : USBPORT!USBPORT_GetRootHubPdoExt+0x46
fffff800`00b9c390 fffff880`101f179f : fffffa80`0892c6a0 fffffa80`0892c6a0 00000000`00000001 00000000`0000000e : USBPORT!USBPORT_Ev_Rh_IntrEp_Invalidate+0x80
fffff800`00b9c3f0 fffff880`047b32c2 : fffffa80`0892b1a0 00000000`00000000 00000000`00000001 fffffa80`0892b050 : usbuhci!UhciPollController+0xbb
fffff800`00b9c430 fffff800`030f4b0f : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`08914bb8 : USBPORT!USBPORT_DM_IoTimerDpc+0x72
fffff800`00b9c460 fffff800`030f0e3c : 00000000`00000002 fffff800`00b9c600 00000000`00000001 00000000`00000001 : nt!IopTimerDispatch+0x132
fffff800`00b9c570 fffff800`030f0cd6 : fffff800`032e27c0 00000000`00000232 00000000`00000000 fffff800`035e9817 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`030f0bbe : 00000000`053be994 fffff800`00b9cc58 00000000`00000232 fffff800`0325b8c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030f09a7 : 00000000`01b030c1 00000000`00000232 00000000`01b03022 00000000`00000031 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030ddeca : fffff800`03258e80 fffff800`03266cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbuhci!UhciPollController+bb
fffff880`101f179f ffc7            inc     edi

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  usbuhci!UhciPollController+bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbuhci

IMAGE_NAME:  usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0bff

FAILURE_BUCKET_ID:  X64_0x1e_0_usbuhci!UhciPollController+bb

BUCKET_ID:  X64_0x1e_0_usbuhci!UhciPollController+bb

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


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Crash Code Links

Loaded Module List

Raw Stack Contents

Dump Header Information

Strings

## Vom 16.05.2012

Code: 
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`0328f670
Debug session time: Wed May 16 06:38:24.173 2012 (UTC - 4:00)
System Uptime: 0 days 0:55:29.111
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a109fd1388, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88004d43507, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f9100
GetUlongFromAddress: unable to read from fffff800032f91c0
 fffff8a109fd1388 Paged pool

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
fffff880`04d43507 488908          mov     qword ptr [rax],rcx

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  rift.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a6c3480 -- (.trap 0xfffff8800a6c3480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a109fd1388 rbx=0000000000000000 rcx=fffff8a009fd1388
rdx=fffffa800acdd000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004d43507 rsp=fffff8800a6c3610 rbp=0000000000000001
 r8=fffffa800ace33e8  r9=0000000000000001 r10=0000000000000040
r11=fffff8800a6c35e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f:
fffff880`04d43507 488908          mov     qword ptr [rax],rcx ds:fffff8a1`09fd1388=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003070f1f to fffff800030ca1c0

STACK_TEXT:  
fffff880`0a6c3318 fffff800`03070f1f : 00000000`00000050 fffff8a1`09fd1388 00000000`00000001 fffff880`0a6c3480 : nt!KeBugCheckEx
fffff880`0a6c3320 fffff800`030c82ee : 00000000`00000001 fffff8a1`09fd1388 fffffa80`0c3ef500 fffffa80`0cb93740 : nt! ?? ::FNODOBFM::`string'+0x43d51
fffff880`0a6c3480 fffff880`04d43507 : fffffa80`0cb93740 fffffa80`0cb93740 fffff8a0`145ff0e0 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`0a6c3610 fffff880`04d29ecc : fffff8a0`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f
fffff880`0a6c36e0 fffff880`04c6bccc : 00000000`00000000 fffff8a0`02a50000 fffff8a0`02a50000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0a6c3710 fffff880`04c6b65f : fffff8a0`02a50000 fffff8a0`02a51300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0a6c3800 fffff880`04c6b8e1 : fffff8a0`02a50000 fffff8a0`02a50000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0a6c3850 fffff880`04c6f79c : fffff8a0`0a77d600 fffff880`0a6c3ca0 fffffa80`0acc1000 fffff880`04c363af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0a6c38a0 fffff880`04c71e57 : fffff8a0`02a50000 fffff880`0a6c39b0 00000000`ff6cd001 fffff880`0f312001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`0a6c3930 fffff960`001bf7ce : 00000000`00000000 fffffa80`0b6f7060 00000000`00000020 00000000`74be6168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0a6c3bf0 fffff800`030c9453 : fffffa80`0b6f7060 00000000`00001120 00000000`00000000 fffffa80`07039690 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0a6c3c20 00000000`74c0141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`23e6e218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74c0141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
fffff880`04d43507 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

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


Hab noch eine ganze Palette an Auswertungen irgendwo rumliegen falls Bedarf besteht ;)

Also - wer mag mein (Computer)-Held sein, hm? <3


Liebe Grüße,
Kevin.

/edit: Falls falsches Forum, bitte verschieben - danke.
 
Zuletzt bearbeitet:
Wenn Du diese Anzeige nicht sehen willst, registriere Dich und/oder logge Dich ein.
Ich hatte fast das selbe Problem mit meiner Creative Titanium + onBoard Soundkarte
Deaktiviere die onBoard Soundkarte mal im Bios und schau obs da geht.
Dann solltest du noch unter Wiedergabegeräte alles mit Rechtsklick -> Deaktivieren ausmachen was du nicht brauchst.
 
Zuletzt bearbeitet:
Anmelden, um zu antworten.
Hardwareluxx setzt keine externen Werbe- und Tracking-Cookies ein. Auf unserer Webseite finden Sie nur noch Cookies nach berechtigtem Interesse (Art. 6 Abs. 1 Satz 1 lit. f DSGVO) oder eigene funktionelle Cookies. Durch die Nutzung unserer Webseite erklären Sie sich damit einverstanden, dass wir diese Cookies setzen. Mehr Informationen und Möglichkeiten zur Einstellung unserer Cookies finden Sie in unserer Datenschutzerklärung.


Zurück
Oben Unten refresh