BSOD ntoskrnl.exe +e6d50

[martinmax3]

Hello,

I have been getting BSOD for the past 1-2 months. I noticed that it happens when I have a browser open. Not sure if that was the case every time.

When it started it happened a few times for a few days. I was using Avast and Mozilla Firefox. After few days like that I changed to Chrome, MSE and Malwarebytes Anti-Malware. It still hapens, but not as often. I got 2 BSOD if I recall correctly this week, one of which, last night while playing Hearthstone and watching Youtube stream.

Thank You in advance!

 

[koolkat77]

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8004ef9ff0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002efbd50 to fffff80002e8abc0

STACK_TEXT:  
fffff880`0bf9e128 fffff800`02efbd50 : 00000000`0000001a 00000000`00041790 fffffa80`04ef9ff0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0bf9e130 fffff800`02e773df : fffffa80`00000000 00000000`0d632fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`0bf9e2f0 fffff800`02e89e53 : ffffffff`ffffffff fffff880`0bf9e5c0 fffff880`0bf9e628 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0bf9e3f0 fffff800`02e86410 : fffff960`000e72e4 00000000`00000001 00000000`00000000 fffff900`c2271cc0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0bf9e588 fffff960`000e72e4 : 00000000`00000001 00000000`00000000 fffff900`c2271cc0 00000000`00000001 : nt!KiServiceLinkage
fffff880`0bf9e590 fffff960`000ef599 : 00000000`00000000 fffff880`00000001 fffff900`c2271cc0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`0bf9e6e0 fffff960`000e6b20 : 00000000`00001300 fffff880`0bf9ea00 fffff900`c21df690 00000000`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`0bf9e740 fffff960`000e6267 : 00000000`00000000 fffff880`0bf9eae0 fffffa80`09ea8800 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`0bf9e7c0 fffff800`0315f0c1 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09ea8800 : win32k!W32pProcessCallout+0x6b
fffff880`0bf9e7f0 fffff800`031452ed : 00000000`c0000005 fffff880`0bf9ea01 00000000`78457300 fffffa80`09eeeb50 : nt!PspExitThread+0x4d1
fffff880`0bf9e8f0 fffff800`02e7d6fa : 00000000`00000001 fffff880`0bf9ea68 00000000`06cae800 fffff880`0bf9eaa0 : nt!PsExitSpecialApc+0x1d
fffff880`0bf9e920 fffff800`02e7da40 : 00000000`0e37fde8 fffff880`0bf9e9a0 fffff800`03145260 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0bf9e9a0 fffff800`02e89ef7 : fffffa80`09ea8800 00000000`fff98000 fffff880`000000c0 00000000`fff98000 : nt!KiInitiateUserApc+0x70
fffff880`0bf9eae0 00000000`77892bba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`06cae7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77892bba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`000e72e4 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`000e7499)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  529478c2

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[martinmax3]

Are you sure about this? I don't think I will be able to manage that. It did not have such problem before? Can it just break down in that way just like that for no reason?

 

[Arc]

If you cannot manage even a memtest, better you don't opt for a troubleshoot.

And, if you ask for whether it is sure or not, remote assistance is not for you. We work based on the supplied data, not having the machine in hand.