Archief - Verschillende BSOD's

hallo,

Ik heb al een paar maanden last van verschillende BSOD's, soms verschillende keren per dag, dan weer aantal dagen niet. Het feit dat vrij uiteenlopende foutmeldingen en locaties geeft wil ik wel eens weten wat er scheelt.

Mobo: ASUSTEK p8p67 PRO DDR3 Socket 1155
CPU: Intel Core I7 2600k
RAM: Corsair 8GB 1866MHZ DDR3
GPU: AMD Radeon 7800 Series
Voeding: Corsair HX650

Ik heb een paar minidumps van de verschillende BSOD's

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


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: fffff900c22227a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600063dc51, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec00e0
fffff900c22227a0

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

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: lotroclient.ex

CURRENT_IRQL: 0

TRAP_FRAME: fffff880059b9660 -- (.trap 0xfffff880059b9660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c2222020 rbx=0000000000000000 rcx=fffff900c00dc420
rdx=fffffa800749a240 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600063dc51 rsp=fffff880059b97f0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000002b0e
r11=fffff880059b9810 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cdd!CddBitmapHw::Release+0x31:
fffff960`0063dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:e288:fffff900`c22227a0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d091e4 to fffff80002c89f00

STACK_TEXT:
fffff880`059b94f8 fffff800`02d091e4 : 00000000`00000050 fffff900`c22227a0 00000000`00000000 fffff880`059b9660 : nt!KeBugCheckEx
fffff880`059b9500 fffff800`02c87fee : 00000000`00000000 fffff900`c00be010 fffffa80`0749a200 fffff880`009b2180 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`059b9660 fffff960`0063dc51 : 00000000`00000000 000009f8`00000000 00000e5a`00000000 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`059b97f0 fffff960`000c5080 : 00000000`00000001 fffff900`c00be010 00000000`00000001 fffff900`c2655690 : cdd!CddBitmapHw::Release+0x31
fffff880`059b9830 fffff960`000cd4a9 : 00000000`00000000 00000000`00000001 fffff900`c2655690 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x358
fffff880`059b9980 fffff960`000c4920 : 00000000`000009f8 00000000`00000000 fffff900`c2141ce0 fffff960`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`059b99e0 fffff960`000c4063 : fffffa80`08d1bd00 00000000`00000001 fffffa80`0749a240 fffffa80`072ecb30 : win32k!GdiProcessCallout+0x200
fffff880`059b9a60 fffff800`02f6c5e1 : fffffa80`08d1bd60 00000000`00000000 00000000`00000000 fffffa80`0749a240 : win32k!W32pProcessCallout+0x6b
fffff880`059b9a90 fffff800`02f45cb8 : 00000000`00000000 00000000`00000001 fffffa80`072ecb00 00000000`00000000 : nt!PspExitThread+0x2b1
fffff880`059b9b60 fffff800`02c89153 : fffffa80`072ecb30 00000000`00000000 fffffa80`0749a240 00000000`00000004 : nt!NtTerminateProcess+0x138
fffff880`059b9be0 00000000`7750017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7750017a


STACK_COMMAND: kb

FOLLOWUP_IP:
cdd!CddBitmapHw::Release+31
fffff960`0063dc51 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: 4a5bde94

FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31

BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31

Followup: MachineOwner


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


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: fffff900c29e77a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600076dc51, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0e0e0
fffff900c29e77a0

FAULTING_IP:
+3632366562393638
fffff960`0076dc51 483b9080070000 cmp rdx,qword ptr [rax+780h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

TRAP_FRAME: fffff880066df660 -- (.trap 0xfffff880066df660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c29e7020 rbx=0000000000000000 rcx=fffff900c1d7e720
rdx=fffffa8012ce1b60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600076dc51 rsp=fffff880066df7f0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=000000000000555c
r11=fffff880066df810 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff960`0076dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:c460:fffff900`c29e77a0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d571e4 to fffff80002cd7f00

STACK_TEXT:
fffff880`066df4f8 fffff800`02d571e4 : 00000000`00000050 fffff900`c29e77a0 00000000`00000000 fffff880`066df660 : nt!KeBugCheckEx
fffff880`066df500 fffff800`02cd5fee : 00000000`00000000 fffff900`c00be010 fffff800`02e50e00 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`066df660 fffff960`0076dc51 : 00000000`00000000 000013e4`00000000 00001c74`c0229f48 00000000`00001bf8 : nt!KiPageFault+0x16e
fffff880`066df7f0 00000000`00000000 : 000013e4`00000000 00001c74`c0229f48 00000000`00001bf8 00000000`00000820 : 0xfffff960`0076dc51


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42907
fffff800`02d571e4 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42907

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+42907

BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+42907

Followup: MachineOwner


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


BugCheck 3B, {c0000005, fffff80002e435fe, fffff88007edee00, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )

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

6: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff80002e435fe, Address of the instruction which caused the bugcheck
Arg3: fffff88007edee00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP:
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
fffff800`02e435fe f00fba3100 lock btr dword ptr [rcx],0

CONTEXT: fffff88007edee00 -- (.cxr 0xfffff88007edee00)
rax=fffffa8009e24550 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8009e24550 rsi=00000000ffffffff rdi=fffffa8009e24550
rip=fffff80002e435fe rsp=fffff88007edf7d0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000003444
r11=fffff88007edf820 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=fffff900c2665030
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26:
fffff800`02e435fe f00fba3100 lock btr dword ptr [rcx],0 ds:002b:00000000`00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: lotroclient.ex

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002e435fe

STACK_TEXT:
fffff880`07edf7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26


FOLLOWUP_IP:
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
fffff800`02e435fe f00fba3100 lock btr dword ptr [rcx],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147dc36

STACK_COMMAND: .cxr 0xfffff88007edee00 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26

BUCKET_ID: X64_0x3B_nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26

Followup: MachineOwner


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


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

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


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`00104283 0fb7430c movzx eax,word ptr [rbx+0Ch]

CONTEXT: fffff880066a5020 -- (.cxr 0xfffff880066a5020)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800a401b60
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000104283 rsp=fffff880066a5a00 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff880066a5a68 r12=0000000003943600 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
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`00104283 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960002bc6b0 to fffff96000104283

STACK_TEXT:
fffff880`066a5a00 fffff960`002bc6b0 : fffff900`c2157800 00000000`00000001 00000000`03121433 fffff900`c23c1010 : win32k!HmgLockEx+0xa3
fffff880`066a5a70 fffff960`002bbbae : fffff900`c2157800 00000000`00000000 00001433`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`066a5aa0 fffff960`002bcab3 : 00000000`00000000 00000000`03121433 fffff900`c2157800 00000000`039436f0 : win32k!SFMLOGICALSURFACE:eInitialize+0x4e
fffff880`066a5ae0 fffff960`002195ff : 00000000`00000000 fffff900`c00be010 fffff900`c2157800 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`066a5b20 fffff960`0023a908 : 00000800`00000001 00000000`00000001 fffff880`066a5c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`066a5b60 fffff800`02cc7153 : fffffa80`0a401b60 00000000`0231f8f0 000007fe`fc01d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`066a5be0 000007fe`fdd94efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0231f348 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdd94efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00104283 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 0xfffff880066a5020 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

Followup: MachineOwner


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Doe eens memtest86, lijkt mij ramprobleem.

ik ga deze nacht de memtest voor een 8 uur laten lopen, kzal dan morgen de resultaten posten.

Memtest86 heeft 9 uur gedraaid, 4 Passes, geen errors

Heb je dat per lat gedraaid?
of alles samen?
beter 1 lat per keer.
check eens uw HDD met chksdk ook.

chkdsk heeft al paar keer gedraaid, vond geen problemen. Aangezien dat ik zeker ben dat het geen software probleem is en HDD en CPU in orde zijn, vermoed ik dat het ram probleem gaat zijn. Als ik BSOD krijg dan is het altijd op dezelfde actie. Alt tab of afsluiten van intensief programma.