BSOD Happening Randomly

Hi Fatherdeath.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
__________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff6fb41f7bf20, 2, 0, fffff80002e69053}

Probably caused by : memory_corruption ( nt!MiFreeWsleList+3d3 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff6fb41f7bf20, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e69053, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b8100
 fffff6fb41f7bf20 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiFreeWsleList+3d3
fffff800`02e69053 488b1f          mov     rbx,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  vsserv.exe

TRAP_FRAME:  fffff88009f1c190 -- (.trap 0xfffff88009f1c190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000098000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e69053 rsp=fffff88009f1c320 rbp=fffffa80055754d0
 r8=0000000000000010  r9=fffffa800af8eb30 r10=0000000000000000
r11=0000000000000010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiFreeWsleList+0x3d3:
fffff800`02e69053 488b1f          mov     rbx,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e80169 to fffff80002e80bc0

STACK_TEXT:  
fffff880`09f1c048 fffff800`02e80169 : 00000000`0000000a fffff6fb`41f7bf20 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09f1c050 fffff800`02e7ede0 : 00000000`0067fcd1 fffff8a0`1eb4c018 fffff880`09f1c658 a2400001`c7c6f005 : nt!KiBugCheckDispatch+0x69
fffff880`09f1c190 fffff800`02e69053 : fffffa80`035e69b0 00000000`00000001 00000000`0011f789 00000001`00000028 : nt!KiPageFault+0x260
fffff880`09f1c320 fffff800`02f885ea : fffffa80`0af8eec8 fffff880`09f1c530 00000000`00000000 fffffa80`00000010 : nt!MiFreeWsleList+0x3d3
fffff880`09f1c510 fffff800`030c956d : fffffa80`0b747b50 ffffffff`00000001 ffffffff`ffffffff fffff880`09f1cb60 : nt!MiEmptyWorkingSet+0x24a
fffff880`09f1c5c0 fffff800`032d543d : 00000000`00000001 00000000`00000000 fffff8a0`00000000 fffff800`02e83e00 : nt!MmAdjustWorkingSetSizeEx+0xad
fffff880`09f1c640 fffff800`031dabab : 00000000`00000008 00000000`00000000 00000000`00000001 00000000`0820fe40 : nt!PspSetQuotaLimits+0x32d
fffff880`09f1c790 fffff800`02e7fe53 : 00000000`00000008 00000000`77c398f0 00000000`001f8b01 00000000`25de58b0 : nt! ?? ::NNGAKEGL::`string'+0x45520
fffff880`09f1cae0 00000000`77be147a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0820fe08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77be147a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiFreeWsleList+3d3
fffff800`02e69053 488b1f          mov     rbx,qword ptr [rdi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiFreeWsleList+3d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiFreeWsleList+3d3

BUCKET_ID:  X64_0xA_nt!MiFreeWsleList+3d3

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

Fatherdeath said:

Not sure if this will help in any way possible, but ..............................

No it will not help you in any way possible.

The only thing that can help you to report a BSOD following the Blue Screen of Death (BSOD) Posting Instructions.

Disable Driver Verifier, and stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Ok, let us wait and see how it goes :)