Bluescreen *verzweiflung*

[roki26]

Sehr geehrte Community,

nach langer suche in eigener Person, habe ich mich jetzt entschlossen Hilfe anzufordern Kriege es nicht bewältigt.

Ich kriege seit geraumer Zeit ständig Bluescreens. Es passiert sporadisch und nicht bei bestimmten Tätigkeiten.

Einmal ist es PAGE FAULT NOT PAGED AREA oder sowas, ein anderes mal SYSTEM_SERVICE_EXCEPTION

Ich habe durch diese Seite Instant Online Crash Analysis, die Minidump hochgeladen.


Das seltsame ist, trotz einer Neuinstallation treten die Bluescreens auf !

Ich habe auch schon die Rams einzeln raus um zu schauen ob es an denen liegt. Ist trotzdem abgestürzt. Egal welcher drin war.





System :

System Model: P67A-D3-B3
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~3.6GHz
Memory: 8192MB RAM 1333 Corsair 2x4 GB
Card name: NVIDIA GeForce GTX 560 Ti
Festplatte: SSD M4 Crucial 128GB



Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`0329ee50
Debug session time: Thu Feb 6 16:48:40.159 2014 (UTC - 5:00)
System Uptime: 0 days 11:19:21.283
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000134283, Address of the instruction which caused the bugcheck
Arg3: fffff88006e8a020, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
win32k!HmgLockEx+a3
fffff960`00134283 0fb7430c movzx eax,word ptr [rbx+0Ch]

CONTEXT: fffff88006e8a020 -- (.cxr 0xfffff88006e8a020)
rax=fffff900c0200090 rbx=0000000000000000 rcx=fffffa8008336b60
rdx=fffff900c0200090 rsi=0000000000200000 rdi=fffff900c0200090
rip=fffff96000134283 rsp=fffff88006e8aa00 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000006 r10=0000000000000012
r11=fffff88006e8aa68 r12=000000000daf9500 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`00134283 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960002ec6b0 to fffff96000134283

STACK_TEXT:
fffff880`06e8aa00 fffff960`002ec6b0 : fffff900`c2ce72a0 00000000`00000001 ffffffff`e2121c83 fffff900`c3205be0 : win32k!HmgLockEx+0xa3
fffff880`06e8aa70 fffff960`002ebbae : fffff900`c2ce72a0 00000000`00000000 00001c83`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`06e8aaa0 fffff960`002ecab3 : 00000000`00000000 ffffffff`e2121c83 fffff900`c2ce72a0 00000000`0daf952c : win32k!SFMLOGICALSURFACE:eInitialize+0x4e
fffff880`06e8aae0 fffff960`002495ff : 00000000`00000000 fffff900`c00b5010 fffff900`c2ce72a0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`06e8ab20 fffff960`0026a908 : 00000000`00000001 00000000`00000001 fffff880`06e8ac60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`06e8ab60 fffff800`030d2153 : fffffa80`08336b60 fffff880`06e8ac60 00000000`03a4f9f0 00000000`00000001 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`06e8abe0 000007fe`ff7c4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`027df668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff7c4efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00134283 0fb7430c movzx eax,word ptr [rbx+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HmgLockEx+a3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

STACK_COMMAND: .cxr 0xfffff88006e8a020 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

Followup: MachineOwner





__________________________________________________ __________________________________________________ ________________________________________________

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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`0305c000 PsLoadedModuleList = 0xfffff800`03298e70
Debug session time: Sat Feb 8 12:58:53.775 2014 (UTC - 5:00)
System Uptime: 0 days 0:31:40.117
************************************************** *****************************
* *
* 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: fffff900c30417a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600074dc51, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033030e0
GetUlongFromAddress: unable to read from fffff80003303198
fffff900c30417a0

FAULTING_IP:
cdd!CddBitmapHw::Release+31
fffff960`0074dc51 483b9080070000 cmp rdx,qword ptr [rax+780h]

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: game.dll

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800d458670 -- (.trap 0xfffff8800d458670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c3041020 rbx=0000000000000000 rcx=fffff900c08cad30
rdx=fffffa800ea41060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600074dc51 rsp=fffff8800d458800 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=000000000000c87f
r11=fffff8800d458820 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cdd!CddBitmapHw::Release+0x31:
fffff960`0074dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:fffff900`c30417a0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000314b694 to fffff800030cb880

STACK_TEXT:
fffff880`0d458508 fffff800`0314b694 : 00000000`00000050 fffff900`c30417a0 00000000`00000000 fffff880`0d458670 : nt!KeBugCheckEx
fffff880`0d458510 fffff800`030c996e : 00000000`00000000 fffff900`c00b5010 fffff900`c025b700 fffff800`030d7622 : nt! ?? ::FNODOBFM::`string'+0x41db7
fffff880`0d458670 fffff960`0074dc51 : 00000000`00000000 00001250`00000000 000042d5`0d4588a8 fffff900`c097f990 : nt!KiPageFault+0x16e
fffff880`0d458800 fffff960`001a7278 : 00000000`00000001 fffff900`c00b5010 00000000`00000001 fffff900`c60ea270 : cdd!CddBitmapHw::Release+0x31
fffff880`0d458840 fffff960`001af53d : 00000000`00000000 00000000`00000001 fffff900`c60ea270 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x358
fffff880`0d458990 fffff960`001a6b1c : 00000000`00001250 00000000`00000000 fffff900`c59abce0 fffff960`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`0d4589f0 fffff960`001a6263 : fffffa80`0ad7f900 00000000`00000001 fffffa80`0ea41060 fffffa80`0bfea530 : win32k!GdiProcessCallout+0x200
fffff880`0d458a70 fffff800`033aaccd : fffffa80`0ad7f900 00000000`00000000 00000000`00000000 fffffa80`0ea41060 : win32k!W32pProcessCallout+0x6b
fffff880`0d458aa0 fffff800`033841fb : 00000000`00000001 00000000`00000001 fffffa80`0bfea500 00000000`00000000 : nt!PspExitThread+0x561
fffff880`0d458b60 fffff800`030caad3 : fffffa80`0bfea530 00000000`00000001 00000000`7efdb001 fffffa80`0ea41060 : nt!NtTerminateProcess+0x25b
fffff880`0d458be0 00000000`77cdf97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cdf97a


STACK_COMMAND: kb

FOLLOWUP_IP:
cdd!CddBitmapHw::Release+31
fffff960`0074dc51 483b9080070000 cmp rdx,qword ptr [rax+780h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: cdd!CddBitmapHw::Release+31

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: cdd

IMAGE_NAME: cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fbfc6

FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31

BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31

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





____________________________________________
____________________________________________



==================================================
Dump File : $RDTBD8W.dmp
Crash Time : 08.02.2014 18:58:53
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff900`c30417a0
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`0074dc51
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f880
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17273 (win7_gdr.130318-1532)
Processor : x64
Crash Address : ntoskrnl.exe+6f880
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\$RDTBD8W.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291.280
Dump File Time : 08.02.2014 19:00:50
==================================================

==================================================
Dump File : 020614-8985-01.dmp
Crash Time : 06.02.2014 22:48:40
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`00134283
Parameter 3 : fffff880`06e8a020
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c4283
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020614-8985-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 295.672
Dump File Time : 06.02.2014 22:50:18
==================================================

 

[Timmi]

Zufällig noch ne normale Festplatte zur Hand, um dort Windows zu installieren und zu testen?
Wenn du die RAM Riegel schon einzeln getestet hast, würde ich als nächstes die SSD verdächtigen.

 

[roki26]

Ja Ram hab ich getestet, SSD hab ich durch Seatools getestet, hat auch nichts ergeben. So wie ich die Fehler durchgelesen habe, liegt es an der Grafikkarte oder?

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT war bei einer Fehlermeldung gestanden

 

[frogger9]

Crucial M4 Firmware Bug?

http://edge.crucial.com/firmware/m4/0309/DE_ProductFlyer-letter_m4-firmware0309.pdf