Random BSOD's and Screen Freezing/Crashing Please Help

Aha !!

What new RAM's did you buy ?? are they the same as the one installed.

Remove the 4GB and start using the 8 GB one (based on your specs posted )

I've only got the gskill ram in there now 2x4gb

Dakka said:

I've only got the gskill ram in there now 2x4gb

ok just use one 4 gb and remove the other and start the system

Ok 1 second

It's taking its time!

OK its back on now! heres a pic of the BSOD now which files do you want? All of them grabbed or any in particular?

Dakka said:

Ok 1 second

It's taking its time!

OK its back on now! heres a pic of the BSOD now which files do you want? All of them grabbed or any in particular?

Yes all of them again.. i mainly need the MSInfo, the logs and the dumps

centaur78 said:

Dakka said:

Ok 1 second

It's taking its time!

OK its back on now! heres a pic of the BSOD now which files do you want? All of them grabbed or any in particular?

Yes all of them again.. i mainly need the MSInfo, the logs and the dumps

Here are the files attached

I don't know if it is relevent but my RAM windows index score is 7.4 with 4gb 8gb and even 12gb, that can't be right can it???

Well its memory corruption ... Since these are new RAM ... i am leaning towards the slots on the motherboard...
Now try putting in the other RAM in the same slot as the previous 4gb.. and start the system with this RAM..

You should propbaby get a BSOD soon... try doing the test on the other slot as well while using just 1 RAM at a time

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffffff8, 0, fffff960002557e2, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: fffffffffffffff8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960002557e2, 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 fffff800040c3100
GetUlongFromAddress: unable to read from fffff800040c31c0
fffffffffffffff8

FAULTING_IP:
win32k!vSpUpdateDxAccumRgn+1a
fffff960`002557e2 c83bdd0f enter 0DD3Bh,0Fh

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88007211cf0 -- (.trap 0xfffff88007211cf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88007211ec8 rbx=0000000000000000 rcx=fffff900c1fd9270
rdx=fffff88007211ef0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002557e2 rsp=fffff88007211e80 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000913 r10=0000000000000000
r11=fffff900c07da060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!vSpUpdateDxAccumRgn+0x1a:
fffff960`002557e2 c83bdd0f enter 0DD3Bh,0Fh
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003e3beec to fffff80003e93fc0

STACK_TEXT:
fffff880`07211b88 fffff800`03e3beec : 00000000`00000050 ffffffff`fffffff8 00000000`00000000 fffff880`07211cf0 : nt!KeBugCheckEx
fffff880`07211b90 fffff800`03e920ee : 00000000`00000000 ffffffff`fffffff8 fffff900`c1c14400 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4514f
fffff880`07211cf0 fffff960`002557e2 : fffff880`07211fd4 00000000`00000000 00000000`00000000 fffff900`c1fd9270 : nt!KiPageFault+0x16e
fffff880`07211e80 fffff960`00255d1b : 00000000`00000001 00000000`00000001 fffff880`07211fd4 00000000`65010913 : win32k!vSpUpdateDxAccumRgn+0x1a
fffff880`07211ed0 fffff960`00256f9a : 00000000`00000004 fffff900`c07f87d0 fffff900`c1fd92e0 fffff900`c06d1218 : win32k!vSpUpdateDirtyRgn+0x38f
fffff880`07211f70 fffff960`00257c14 : fffff900`c00bf010 00000000`00010064 00000000`010f07f3 00000000`00000000 : win32k!GreUpdateSprite+0x6a2
fffff880`07212100 fffff960`001097af : fffff880`07212500 00000000`00000000 0000001e`00000780 fffff900`c00bf010 : win32k!GreUpdateSpriteDevLockEnd+0x444
fffff880`072123b0 fffff960`00279168 : fffff900`c0661010 fffff900`c24a56a0 fffff900`746c7847 fffff900`c24a56a0 : win32k!DEVLOCKBLTOBJ::~DEVLOCKBLTOBJ+0x4b
fffff880`072123e0 fffff960`001576e7 : 00000000`65010913 fffffa80`092935c0 fffff880`07212720 00000000`02edf6b8 : win32k!NtGdiBitBltInternal+0xdd8
fffff880`072125c0 fffff800`03e93253 : 00000000`00000000 fffff880`07212720 00000000`00000004 00000000`00000000 : win32k!NtGdiBitBlt+0x5b
fffff880`07212630 000007fe`fe3625ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02edf698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe3625ba


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
fffff960002557e2 - win32k!vSpUpdateDxAccumRgn+1a
[ 48:c8 ]
1 error : !win32k (fffff960002557e2)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

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

I will do that now! Thank you

Dakka said:

I don't know if it is relevent but my RAM windows index score is 7.4 with 4gb 8gb and even 12gb, that can't be right can it???

Thats most probably due to your Graphics card.

centaur78 said:

Dakka said:

I don't know if it is relevent but my RAM windows index score is 7.4 with 4gb 8gb and even 12gb, that can't be right can it???

Thats most probably due to your Graphics card.

My Graphics card is 7.8 but the ram doesn't change from 7.4. So you don't think it is my graphics card then? I was hoping it wasn't as that was the most expensive part.