BSOD's

Hi fromheine and welcome to SF!
Please follow the Memtest86+ - Test RAM with guidelines.

Code:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e97e90
Debug session time: Sat Jun 11 20:50:32.672 2011 (UTC - 3:00)
System Uptime: 0 days 2:13:58.373
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, 0, fffff88009c59110, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: 0000000000000000, Address of the instruction which caused the bugcheck
Arg3: fffff88009c59110, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A instru  o no 0x%08lx fez refer ncia   mem ria no 0x%08lx. A mem ria n o p de ser %s.

FAULTING_IP: 
+13
00000000`00000000 ??              ???

CONTEXT:  fffff88009c59110 -- (.cxr 0xfffff88009c59110)
rax=00000000c4d8ffca rbx=000000000000080c rcx=000007fef830c640
rdx=fffff0a108cf07b0 rsi=000000000223fb70 rdi=0000000000000030
rip=0000000000000000 rsp=fffff88009c59af8 rbp=fffff88009c59ca0
 r8=0000000000000000  r9=0000000000000000 r10=0000000300000001
r11=000007fef830c610 r12=0000000000000000 r13=000000000223fa78
r14=0000000000000000 r15=fffffa800650f000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
00000000`00000000 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880077013da to 0000000000000000

STACK_TEXT:  
fffff880`09c59af8 fffff880`077013da : 00000000`0000080c 00000000`0000080c 00000000`0223fb70 00000000`000a59ff : 0x0
fffff880`09c59b00 fffff960`0020c2a7 : fffffa80`06cda340 00000000`00000001 00000000`c4d8ffca 00000000`f63a6b60 : dxgkrnl!DxgkGetPresentHistory+0x5ca
fffff880`09c59bf0 fffff800`02cd18d3 : fffffa80`00000800 00000000`0223fae0 000007fe`f830c610 fffffa80`00000000 : win32k!NtGdiDdDDIGetPresentHistory+0x17
fffff880`09c59c20 000007fe`fd95120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0223fa38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd95120a


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
3 errors : !nt (fffff80002cd2361-fffff80002cd23e9)
fffff80002cd2360  0f *ef  50  70  66  44  0f  6f  98  80  00  00  00  66  44  0f ..PpfD.o.....fD.
fffff80002cd2370  6f  a0  90  00  00  00  66  44  0f *ef  a8  a0  00  00  00  66 o.....fD.......f
...
fffff80002cd23e0  0f  1f  84  00  00  00  00  00  66 *e6  66  66  66  66  66  0f ........f.fffff.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88009c59110 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption

Let us know the results.

I tested the ram and in 1 slot there were lots of errors 15k~ and in other slot there were none. Now I sticked Ram into that slot without errors, but restarting problem doesn't fix... This time Blue screen didn't pop up.

Note: I have 1 chip 4GB ram and 2 motherboard slots.


EDIT: second time PC restarted and I didn't get blue screen. But these restarts keep anoying me, they happen like every 2 hours

Hi fromheine. :)
Go to Windows Start Orb and type "eventvwr.msc" in search box without quotes and hit enter. Will open a window as shown below.
Left pane > Event Viewer > Custom Views > Administrative events.
Right pane > Save events in the Custom View as ... > Name it "Event Viewer" and save it as Event Archives ( *.evtx ) as shown below.
Attach it in your next post.

Here you go :)

EDIT: I ran Action Center and there was 1 error in there (checking Ram or something) and it said taht there is problems with my hardware, what should I do now?

Hi fromheine. :)
Today at 3:38 a.m. you must have had a BSOD. Please upload the dump file. One more thing: ram stick is still in slot 2?!...

Slot1 = without errors
Slot2 = errors

So RAM is in slot1. And I don't know if dump files are here, I'll upload it anyways. :) If this isn't what are you looking for let me know where to find it :P

Attachment 159499

EDIT: I changed pc cable (Power supply one) and I hadn't restart for 3h. I should not scream too early but I think it's fixed, I'll let you know :)

EDIT2: I thought that blue screen will never appear... And finally it did ;/

Hi fromheine.
Bad news... It's time to shop another ram stick - which has been tested on your motherboard model by the manufacturer preferably.
Of the eight dump files dated today, June 13, 5 show a direct reference to memory corruption and the other, write errors in memory.
If the memory is under warranty, I recommend you to request a RMA. I also recommend you to do a clean installation of Windows for the new memory stick.
Best wishes and come back to tell us the news!