Blue screen of death help!

[carnageX]

Copy the minidump to your desktop from C:\Windows\Minidump and then either add it to a zip file or attach it to your post.

https://msdn.microsoft.com/en-us/li...949(v=vs.85).aspx?f=255&MSPPError=-2147217396

Related to GPU again.

Cause

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

 

[Joe C]

Do you have all your windows updates?, I had something of a similar issue and this helped my situation
https://support.microsoft.com/en-us/kb/2978092

 

[Slothraki]

it says its an invalid file type unfortunately! I'm probably doing something wrong sorry, and I'm not sure, I'll take a look! Thanks!

 

[carnageX]

it says its an invalid file type unfortunately! I'm probably doing something wrong sorry, and I'm not sure, I'll take a look! Thanks!

You'll have to add it to a zip file then, and upload the zip file.

Just right click it -> Send to -> Compressed (zipped) folder

Then upload the zip file you just made.

 

[Slothraki]

Thanks! Here you go! Hoping we can get this resolved! View attachment 032415-21777-01.zip

 

[Slothraki]

Like to point out I just had the exact same blue screen again. From the looks of things they're appearing much more regularly now! :s Any suggestions?

 

[carnageX]

Do you by chance have any Razer products or software on your system? The analysis mentions RzStats.Manage, a Razer product:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000330e5a2, fffff88006b1dba0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

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

4: 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: fffff8000330e5a2, Address of the instruction which caused the bugcheck
Arg3: fffff88006b1dba0, 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!KxWaitForLockOwnerShip+12
fffff800`0330e5a2 48890a          mov     qword ptr [rdx],rcx

CONTEXT:  fffff88006b1dba0 -- (.cxr 0xfffff88006b1dba0;r)
rax=0000000000000000 rbx=fffffa80085a1c00 rcx=fffff88006b1e620
rdx=0020000000000000 rsi=fffff880009b3180 rdi=fffff88006b1e620
rip=fffff8000330e5a2 rsp=fffff88006b1e580 rbp=fffffa8007a69b50
 r8=fffff88006b1e620  r9=0000000000000000 r10=0000000000000000
r11=fffff8a00f5ae400 r12=0000000007a69b50 r13=00000000c0020000
r14=fffff8a003b34600 r15=00000000c0020001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff800`0330e5a2 48890a          mov     qword ptr [rdx],rcx ds:002b:00200000`00000000=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa80085a1c00 rcx=fffff88006b1e620
rdx=0020000000000000 rsi=fffff880009b3180 rdi=fffff88006b1e620
rip=fffff8000330e5a2 rsp=fffff88006b1e580 rbp=fffffa8007a69b50
 r8=fffff88006b1e620  r9=0000000000000000 r10=0000000000000000
r11=fffff8a00f5ae400 r12=0000000007a69b50 r13=00000000c0020000
r14=fffff8a003b34600 r15=00000000c0020001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff800`0330e5a2 48890a          mov     qword ptr [rdx],rcx ds:002b:00200000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  RzStats.Manage

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

LAST_CONTROL_TRANSFER:  from fffff800032e6e2d to fffff8000330e5a2

STACK_TEXT:  
fffff880`06b1e580 fffff800`032e6e2d : fffffa80`085a1c00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x12
fffff880`06b1e5b0 fffff800`032bb629 : fffffa80`07a69b50 fffffa80`085a1c10 fffffa80`095b5870 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`06b1e600 fffff800`035eb336 : fffff8a0`0f5ae300 fffff8a0`0f5ae300 00000000`00000000 00000000`00000000 : nt!AlpcpQueueIoCompletionPort+0x29
fffff880`06b1e680 fffff800`035ed8be : 00000000`c0020000 00000000`00000000 fffffa80`074cfa80 fffffa80`00000000 : nt!AlpcpCompleteDispatchMessage+0x5b6
fffff880`06b1e710 fffff800`035ed631 : fffffa80`c0020000 fffff8a0`03b34688 00000000`005b7f10 fffff8a0`0f5ae300 : nt!AlpcpDispatchNewMessage+0x24e
fffff880`06b1e770 fffff800`035efd96 : 00000000`00000000 00000000`005b7f10 00000000`08e072f8 fffff8a0`03caf801 : nt!AlpcpSendMessage+0x907
fffff880`06b1e880 fffff800`035edbdb : fffffa80`072dfaa0 fffffa80`c0020000 00000000`005b7f10 00000000`08e072f8 : nt!AlpcpProcessSynchronousRequest+0x2f3
fffff880`06b1e9c0 fffff800`032dc153 : fffffa80`07a69b50 fffff880`06b1eb60 00000000`0053fd20 fffff880`06b1eae0 : nt!NtAlpcSendWaitReceivePort+0x1ab
fffff880`06b1ea70 00000000`771d1b0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0053e178 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771d1b0a


FOLLOWUP_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`0330e5a2 48890a          mov     qword ptr [rdx],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54d0317d

IMAGE_VERSION:  6.1.7601.18741

STACK_COMMAND:  .cxr 0xfffff88006b1dba0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nt!kxwaitforlockownership+12

FAILURE_ID_HASH:  {2e15fe1f-699a-d4f8-3ab5-02a0d5759015}

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

 

[Slothraki]

I do, i have used several razer products and I'm currently using the razer chroma blackwidow ultimate keyboard and razer chroma naga mouse. Could it be down to out dated drivers with that? I also just read that malwarebytes is often an issue in this category and I have that installed. Would it be worth uninstalling that also?

Edit - I have just installed the latest razer synapse update as I was slightly behind.

 

[carnageX]

Make sure Razer device drivers are updated, yeah. If you still get them...then you may want to try uninstalling all Razer software/removing Razer drivers and see if you can just use a regular mouse/kb for a while to see if you still get the BSOD's.

You could try uninstalling MBAM to see if it helps as well.

 

[Slothraki]

Only keyboard and mouse I now own unfortunately are these ones, I've updated razer synapse and removed malwarebytes and rebooted my stystem, I'll see if it works any better now! Let me know if you find anything!