• Hallo Gast, du kaufst gerne günstig ein und erfährst oft vor deinen Freunden von interessanten Angeboten? Dann kannst du dein Talent als Schnäppchenjäger jetzt zu Geld machen und anderen PCGH-Lesern beim Sparen helfen! Schau einfach mal rein - beim Test der Community Deals!

[Win7] 2 verschiedene Bluescreens hintereinander

Speeedymauss

Software-Overclocker(in)
Heyho, mein WIndoof macht mal wieder Probleme, diesmal aber anders als sonst.

Ich hoffe ich gebe hier die richtigen Sachen an :D

Ich habe BF3 gespielt

-> erster Bluescreen, Auslöser scheinbar: ntkrnlmp.exe

Genauere Analyse von dem Minidump hier:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0361d000 PsLoadedModuleList = 0xfffff800`038606d0
Debug session time: Fri Apr 11 13:27:08.637 2014 (UTC - 4:00)
System Uptime: 0 days 3:26:29.434
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffffa801834a060

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

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

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003692169 to fffff80003692bc0

STACK_TEXT:
fffff880`03306de8 fffff800`03692169 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff880`03306df0 fffff800`03690632 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03306f30 fffffa80`1834a060 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0955bebb 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`1834a060


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`03690632 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

Danach: Rechner startet neu:

-> Nächster Bluescreen, ausgelöst durch win32k.sys

Genaueres:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0364b000 PsLoadedModuleList = 0xfffff800`0388e6d0
Debug session time: Fri Apr 11 13:29:00.854 2014 (UTC - 4:00)
System Uptime: 0 days 0:00:28.650
*******************************************************************************
* *
* 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: fffff9601506ff46, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff9600007bd7e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (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 fffff800038f8100
GetUlongFromAddress: unable to read from fffff800038f81c0
fffff9601506ff46

FAULTING_IP:
win32k!itrp_InnerExecute+1e
fffff960`0007bd7e 8305cb242b00ff add dword ptr [win32k!LocalGS+0xd0 (fffff960`0032e250)],0FFFFFFFFh

MM_INTERNAL_CODE: 2

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88009f07f00 -- (.trap 0xfffff88009f07f00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c26e90ac rbx=0000000000000000 rcx=fffff900c26e90ac
rdx=0000000000000020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600007bd7e rsp=fffff88009f08090 rbp=0000000000000000
r8=0000000000000000 r9=fffff900c26e7250 r10=0000000000000001
r11=fffff900c26e90a6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
win32k!itrp_InnerExecute+0x1e:
fffff960`0007bd7e 8305cb242b00ff add dword ptr [win32k!LocalGS+0xd0 (fffff960`0032e250)],0FFFFFFFFh ds:fffff960`0032e250=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000373d5e4 to fffff800036c0bc0

STACK_TEXT:
fffff880`09f07d98 fffff800`0373d5e4 : 00000000`00000050 fffff960`1506ff46 00000000`00000001 fffff880`09f07f00 : nt!KeBugCheckEx
fffff880`09f07da0 fffff800`036becee : 00000000`00000001 fffff960`1506ff46 0000007f`ffffff00 fffff900`c26e90c0 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`09f07f00 fffff960`0007bd7e : fffff900`c26e90a4 fffff900`c26e902d 00000003`ffffffff fffff900`0000002a : nt!KiPageFault+0x16e
fffff880`09f08090 fffff960`0007ec0d : fffff900`00000001 fffff900`c228d738 fffff900`c228d610 fffff960`000ad4fa : win32k!itrp_InnerExecute+0x1e
fffff880`09f080c0 fffff960`0007bd95 : fffff900`c26e9037 fffff900`00000000 fffff900`c228da00 fffff900`c2086600 : win32k!itrp_CALL+0x28d
fffff880`09f08130 fffff960`0007ec0d : fffff900`c2086670 fffff960`0007fb03 fffff880`09f08590 fffff900`c228d7c8 : win32k!itrp_InnerExecute+0x35
fffff880`09f08160 fffff960`0007bd95 : fffff900`c26e9f00 fffff900`00000000 fffffff7`00000000 fffff880`09f00000 : win32k!itrp_CALL+0x28d
fffff880`09f081d0 fffff960`0009fa20 : fffff900`c23b6010 00000000`09f08340 00000000`00000005 fffff880`09f089c0 : win32k!itrp_InnerExecute+0x35
fffff880`09f08200 fffff960`0009e710 : fffff900`c26e7250 fffff900`c26e7250 fffff900`c26e9f00 fffff960`00071bc8 : win32k!itrp_Execute+0x390
fffff880`09f08320 fffff960`0009e678 : 00000000`00000040 fffff900`c26e7250 fffff900`c26e9f00 00000000`00000010 : win32k!itrp_ExecutePrePgm+0x78
fffff880`09f08370 fffff960`0009c4d7 : fffff900`c26e2020 fffff900`c26e20d0 00000000`02e22288 fffff900`c26e258c : win32k!fsg_RunPreProgram+0x22c
fffff880`09f083d0 fffff960`0009c22d : fffff900`c26e9f00 fffff900`c26e20d0 fffff880`00000001 00000000`00000000 : win32k!fs__Contour+0x257
fffff880`09f084a0 fffff960`0009d0d8 : fffff900`c2363a20 fffff880`09f088f0 00000000`00000000 fffff900`c26efdfe : win32k!bGetGlyphOutline+0x129
fffff880`09f084e0 fffff960`0009d044 : fffff900`c2363a20 00000000`0000006c 00000000`0000006c 00000000`ffffffff : win32k!lGetGlyphBitmap+0x4c
fffff880`09f086a0 fffff960`0009cd72 : fffff900`00000000 00000000`ffffffff fffff900`c2360ca0 fffff900`c2360ca0 : win32k!ttfdQueryFontData+0x278
fffff880`09f08700 fffff960`00070abe : fffff960`0009cd00 fffff900`c2360ca0 00000000`00000004 00000000`00000000 : win32k!ttfdSemQueryFontData+0x72
fffff880`09f08760 fffff960`002759d6 : 00000000`00000080 fffff880`09f08a10 00000000`ffffffff 00000000`00000000 : win32k!PDEVOBJ::QueryFontData+0x82
fffff880`09f087f0 fffff960`0024e3c1 : 00000000`00000000 fffff960`0011006c 00000000`fffdb001 fffff900`c2360ca0 : win32k!GreGetGlyphOutlineInternal+0x802
fffff880`09f089b0 fffff800`036bfe53 : ffffffff`8d010d78 fffff960`0023006c fffff880`00000080 00000000`0028b050 : win32k!NtGdiGetGlyphOutline+0x105
fffff880`09f08a70 00000000`749e1fba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000adbc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x749e1fba


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!itrp_InnerExecute+1e
fffff960`0007bd7e 8305cb242b00ff add dword ptr [win32k!LocalGS+0xd0 (fffff960`0032e250)],0FFFFFFFFh

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!itrp_InnerExecute+1e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52f4357b

FAILURE_BUCKET_ID: X64_0x50_win32k!itrp_InnerExecute+1e

BUCKET_ID: X64_0x50_win32k!itrp_InnerExecute+1e

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

Danach hat der aber nicht neugestartet, der Bluescreen blieb offen, ich könnte davon nen Foto hochladen, wenn das benötigt wird.

Danach bin ich dann auf den Resetknopf am Rechner gegangen und dann auf Klo, ich kam wieder -> Rechner aus (er ist vorher aber angelaufen, habe das Piepsen gehört)

Naja nochmal An/Aus jetzt geht wieder.


Ne Vermutung/Lösung was das ist?

RAM habe ich vor ner Woche nen 24h Mentest86+ Test unterzogen, der ist OK

Ich habe zwar vor meinen Rechner demnächst neu Aufzusetzen, mich interessiert die Lösung aber trotzdem.

Schonmal Danke im Vorraus für eure Hilfe!
 

slaper688

PC-Selbstbauer(in)
überprüf deinen Speicher einer der Riegel ist defekt( PAGE_FAULT_IN_NONPAGED_AREA ) das ist die Meldung da zu hab ich auch gehabt . Kam nach einem Stromausfall gib das mal im Internet ein dann siehst die Erklärung
 
TE
Speeedymauss

Speeedymauss

Software-Overclocker(in)
Speicher ist aber laut Memtes OK, habe heute morgen nochmal "kurz" Testen lassen:
IMG_20140412_145312.jpg
 

simpel1970

Lötkolbengott/-göttin
Bei den Stopfehlern, würde ich das Undervolting deiner CPU als Fehlerursache mit unter die Lupe nehmen.
Teste, ob die Probleme auch mit Default Einstellungen auftreten.
 
Oben Unten