[RESOLVED] BSOD on Windows 10 Build 9879

I experienced the same problem after upgrading to preview build 9879. However, this didn't happen until I updated my nvidia video card drivers. I wish there was an easy way to revert back to build 9860, which was a far more stable build. The reason I upgraded the video driver was because file explorer was failing to launch, it would flash the background so I thought it was a video driver issue. Guess that really wasn't the problem.

hopefully we can get this fixed soon.

Today I got the same BSOD. I got this two BSOD when I turned off Windows. Here's is the link to the first dump file. And after a few hours, I'll provide the link to the second dump file. In the meantime, here's the bugcheck of the second BSOD:

http://1drv.ms/1qK4Yw5 (Link to the first Dump File)

http://1drv.ms/1vgtI5D (Link to the second Dump File)

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

SESSION_HAS_VALID_POOL_ON_EXIT (ab)
Caused by a session driver not freeing its pool allocations prior to a
session unload.  This indicates a bug in win32k.sys, atmfd.dll,
rdpdd.dll or a video driver.
Arguments:
Arg1: 0000000000000002, session ID
Arg2: 0000000000000040, number of paged pool bytes that are leaking
Arg3: 0000000000000000, number of nonpaged pool bytes that are leaking
Arg4: 0000000000000001, total number of paged and nonpaged allocations that are leaking.
 nonpaged allocations are in the upper half of this word,
 paged allocations are in the lower half of this word.

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

Use !poolused 8 to dump allocation info for leaked session pooltags.

TAG_NOT_DEFINED_405: Uspp

BUGCHECK_STR:  0xAB_Uspp

IMAGE_NAME:  win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  545873ca

FAULTING_MODULE: fffff96006200000 win32k

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff96016c14641 to fffff96016c135bd

STACK_TEXT: 
ffffd000`29118940 fffff960`16c14641 : fffff901`40000fb0 00000000`00000001 fffff901`40000fc8 00000000`00000000 : win32kbase!CheckSessionPoolAllocations+0x20d
ffffd000`29118a30 fffff800`0178540b : ffffe000`36334080 ffffe000`2eac7080 ffffd000`20980000 ffffe000`2eac7080 : win32kbase!Win32KDriverUnload+0x361
ffffd000`29118aa0 fffff800`016e2eaf : ffffe000`36334080 00000000`00000000 ffffe000`2eac7080 ffffe000`36334080 : nt!MiDereferenceSessionFinal+0x8f
ffffd000`29118b20 fffff800`016e2a25 : 00000000`0004fdd5 ffffe000`2eac7080 ffffe000`36334080 ffffe000`2eac7080 : nt!MiDereferenceSession+0x3f
ffffd000`29118b50 fffff800`016e2654 : 00000000`00040000 00000000`00000080 00000000`00000000 fffff800`016e205e : nt!MmCleanProcessAddressSpace+0x1ad
ffffd000`29118bb0 fffff800`0167c298 : ffffe000`36334080 ffffc000`c8b3f060 00000000`00000080 00000000`00000000 : nt!PspRundownSingleProcess+0xac
ffffd000`29118c40 fffff800`016a91ff : 00000000`00000000 00000000`00000001 00000000`00000000 ffffe000`36334080 : nt!PspExitThread+0x5f8
ffffd000`29118d30 fffff800`013b4856 : fffff800`015b8180 ffffe000`2eac7080 ffffe000`306e7780 00000000`00000200 : nt!PspTerminateThreadByPointer+0x7b
ffffd000`29118d60 00000000`00000000 : ffffd000`29119000 ffffd000`29113000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

FOLLOWUP_IP:
win32kbase!CheckSessionPoolAllocations+20d
fffff960`16c135bd cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32kbase!CheckSessionPoolAllocations+20d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kbase

IMAGE_VERSION:  6.4.9879.0

FAILURE_BUCKET_ID:  LEAKED_SESSION_POOLTAG_Uspp

BUCKET_ID:  LEAKED_SESSION_POOLTAG_Uspp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:leaked_session_pooltag_uspp

FAILURE_ID_HASH:  {9a92398c-217d-76e8-d97c-29811c41e867}

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

1: kd> !poolused 8
.
 Sorting by Session Tag

               NonPaged                  Paged
 Tag     Allocs         Used     Allocs         Used

 Uspp         0            0          1           64 USERTAG_PNP , Binary: win32k!AllocateAndLinkHidTLCInf

TOTAL         0            0          1           64
1: kd> lmvm win32kbase
start             end                 module name
fffff960`16c00000 fffff960`16cc4000   win32kbase   (pdb symbols)          C:\ProgramData\dbg\sym\win32kbase.pdb\036342FED5844EAF9F268AAF6F08D8DC1\win32kbase.pdb
    Loaded symbol image file: win32kbase.sys
    Image path: \SystemRoot\System32\win32kbase.sys
    Image name: win32kbase.sys
    Timestamp:        Tue Nov 04 07:35:54 2014 (545873CA)
    CheckSum:         000BE959
    ImageSize:        000C4000
    File version:     6.4.9879.0
    Product version:  6.4.9879.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     win32kbase.sys
    OriginalFilename: win32kbase.sys
    ProductVersion:   6.4.9879.0
    FileVersion:      6.4.9879.0 (fbl_release.141103-1722)
    FileDescription:  Base Win32k Kernel Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

If you look at the "raw stack" of each of the errors the igdkmd64.sys (Intel graphics driver) did show up in one of the errors along with the fshs.sys (F-Secure driver)

In the other error the igdkmd64.sys did not show up in the raw stack however both the fshs.sys and KeyCrypt64.sys did show up.

I would suspect the fshs.sys may be the issue as F-Secure may not be fully compatible with this build.

Here's a link on generating the "raw stack":

http://www.sysnative.com/forums/bsod-kernel-dump-analysis-debugging-information/444-the-raw-truth-using-raw-stacks.html

Here's some of the "raw stack" for the error - Sat Nov 15 04:48:58.798 2014:

: kd> !thread
THREAD ffffe0002eac7080  Cid 2394.3fd4  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 1
Not impersonating
DeviceMap                 ffffc000b720c6a0
Owning Process            ffffe00036334080       Image:         csrss.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      2630047        Ticks: 0
Context Switch Count      13             IdealProcessor: 0            
UserTime                  00:00:00.000
KernelTime                00:00:00.015
Win32 Start Address win32kfull!WaitForWinstaRundown (0xfffff96015e3fb50)
Stack Init ffffd00029118d90 Current ffffd00029117ae0
Base ffffd00029119000 Limit ffffd00029113000 Call 0
Priority 13 BasePriority 13 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`29118940 fffff960`16c14641 : fffff901`40000fb0 00000000`00000001 fffff901`40000fc8 00000000`00000000 : win32kbase!CheckSessionPoolAllocations+0x20d
ffffd000`29118a30 fffff800`0178540b : ffffe000`36334080 ffffe000`2eac7080 ffffd000`20980000 ffffe000`2eac7080 : win32kbase!Win32KDriverUnload+0x361
ffffd000`29118aa0 fffff800`016e2eaf : ffffe000`36334080 00000000`00000000 ffffe000`2eac7080 ffffe000`36334080 : nt!MiDereferenceSessionFinal+0x8f
ffffd000`29118b20 fffff800`016e2a25 : 00000000`0004fdd5 ffffe000`2eac7080 ffffe000`36334080 ffffe000`2eac7080 : nt!MiDereferenceSession+0x3f
ffffd000`29118b50 fffff800`016e2654 : 00000000`00040000 00000000`00000080 00000000`00000000 fffff800`016e205e : nt!MmCleanProcessAddressSpace+0x1ad
ffffd000`29118bb0 fffff800`0167c298 : ffffe000`36334080 ffffc000`c8b3f060 00000000`00000080 00000000`00000000 : nt!PspRundownSingleProcess+0xac
ffffd000`29118c40 fffff800`016a91ff : 00000000`00000000 00000000`00000001 00000000`00000000 ffffe000`36334080 : nt!PspExitThread+0x5f8
ffffd000`29118d30 fffff800`013b4856 : fffff800`015b8180 ffffe000`2eac7080 ffffe000`306e7780 00000000`00000200 : nt!PspTerminateThreadByPointer+0x7b
ffffd000`29118d60 00000000`00000000 : ffffd000`29119000 ffffd000`29113000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

1: kd> dps  ffffd00029113000  ffffd00029119000

<snip>

fffd000`291182e8  fffff801`e1c927f8*** ERROR: Module load completed but symbols could not be loaded for fshs.sys
 fshs+0x27f8
ffffd000`291182f0  00000000`00000002
ffffd000`291182f8  00000000`00000000
ffffd000`29118300  00000000`00000e22
ffffd000`29118308  ffffd000`291183a0
ffffd000`29118310  00000000`00000000
ffffd000`29118318  00000000`00000000
ffffd000`29118320  00000000`00000000
ffffd000`29118328  00000000`00000000
ffffd000`29118330  00000000`00000000
ffffd000`29118338  00000000`00000000
ffffd000`29118340  00000000`00000000
ffffd000`29118348  fffff801`e278303b*** ERROR: Module load completed but symbols could not be loaded for KeyCrypt64.sys
 KeyCrypt64+0x303b
ffffd000`29118350  00000000`c0000503
ffffd000`29118358  ffffd000`291184d0
ffffd000`29118360  ffffd000`29118500
ffffd000`29118368  00000000`00000000
ffffd000`29118370  00000000`00000000
ffffd000`29118378  00000000`00000000
ffffd000`29118380  00000000`00000000
ffffd000`29118388  00000000`00000000
ffffd000`29118390  00000000`00000000
ffffd000`29118398  00000000`00000000
ffffd000`291183a0  00001f80`0010000f
ffffd000`291183a8  0053002b`002b0010
ffffd000`291183b0  00000202`0000002b
ffffd000`291183b8  00000000`00000000
ffffd000`291183c0  00000000`00000000
ffffd000`291183c8  00000000`00000000
ffffd000`291183d0  00000000`00000000
ffffd000`291183d8  00000000`00000000
ffffd000`291183e0  00000000`00000000
ffffd000`291183e8  00000000`00000001
ffffd000`291183f0  00000000`000000ab
ffffd000`291183f8  00000000`00000002
ffffd000`29118400  ffffe000`36009000
ffffd000`29118408  ffffd000`29118940
ffffd000`29118410  ffffd000`291189c9
ffffd000`29118418  00000000`00000040
ffffd000`29118420  00000000`00000004
ffffd000`29118428  00000000`00000040
ffffd000`29118430  00000000`00000000
ffffd000`29118438  ffffd000`24b42620
ffffd000`29118440  ffffe000`2eac7080
ffffd000`29118448  00000000`00000000
ffffd000`29118450  00000000`00000001
ffffd000`29118458  00000000`00000000
ffffd000`29118460  00000000`00000001
ffffd000`29118468  fffff960`16c135bd win32kbase!CheckSessionPoolAllocations+0x20d

<snip>

This issue is fixed with the latest WU update for build 9879.

Okay, thank you. I just edited the title with the [RESOLVED] prefix.

Issue appears to be back, at least for me. Display started behaving weird after auto-rotate on my notebook (most annoying feature ever). Running on HP Revolve 810 with Intel graphics. Had just installed (latest), running high CPU app and RDS.

Couldn't boot into system at all anymore. Had to do refresh.