question

AliPrice-9340 avatar image
0 Votes"
AliPrice-9340 asked TeemoTang-MSFT answered

Frequent BSOD, no particular pattern and I can't figure out the cause.

Hello, I have a Dell Precision laptop that keeps having BSODs and I can't figure out why. I've tried every update for BIOS, drivers, and Windows for months now. I've tried uninstalling things and still no difference. It would be amazing if someone could help me figure out why. I've uploaded the recent crash dumps as well as system info profile. https://www.dropbox.com/s/q6nvgvtzm5frz1e/Mike%20laptop%20BSOD.zip?dl=0 Also if it helps it's a Dell Precision laptop and I also use a Dell Thunderbolt docking station with 2 external monitors. And in terms of software I'm mostly using Autocad and Office 365 software. Thank you to anyone! Ali

windows-10-general
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SSengupta-4080 avatar image
0 Votes"
SSengupta-4080 answered

Kindly go through the following Microsoft reference:

How to read the small memory dump file that is created by Windows if a crash occurs


The following is free application. You may download and install to biew the exact cause of BSOD:

 [BlueScreenView v1.55][2]


[2]: https://www.nirsoft.net/utils/blue_screen_view.html

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MotoX80 avatar image
0 Votes"
MotoX80 answered

Do you have any of the KB updates installed that are mentioned in these 2 links? Dump analysis shows win32kfull.sys and a process name of splwow64. Looks very similar. I'd suggest that you try uninstalling the most recent update.

https://www.bleepingcomputer.com/news/microsoft/microsoft-halts-rollout-of-windows-10-kb5001649-emergency-update/

https://www.bleepingcomputer.com/news/microsoft/windows-10-crashes-when-printing-due-to-microsoft-march-updates/



 *******************************************************************************
 *                                                                             *
 *                        Bugcheck Analysis                                    *
 *                                                                             *
 *******************************************************************************
    
 Use !analyze -v to get detailed debugging information.
    
 BugCheck 50, {ffff86823c8474cc, 0, ffffa093c58e99f6, 2}
    
    
 Could not read faulting driver name
 Probably caused by : win32kfull.sys ( win32kfull!UMPDOBJ::vClient+6 )
    
 Followup:     MachineOwner
 ---------
    
 4: kd> !analyze -v
 *******************************************************************************
 *                                                                             *
 *                        Bugcheck Analysis                                    *
 *                                                                             *
 *******************************************************************************
    
 PAGE_FAULT_IN_NONPAGED_AREA (50)
 Invalid system memory was referenced.  This cannot be protected by try-except.
 Typically the address is just plain bad or it is pointing at freed memory.
 Arguments:
 Arg1: ffff86823c8474cc, memory referenced.
 Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
 Arg3: ffffa093c58e99f6, If non-zero, the instruction address which referenced the bad memory
     address.
 Arg4: 0000000000000002, (reserved)
    
 Debugging Details:
 ------------------
    
    
 Could not read faulting driver name
    
    
 BUILD_VERSION_STRING:  10.0.19041.868 (WinBuild.160101.0800)
 SYSTEM_MANUFACTURER:  Dell Inc.
 SYSTEM_PRODUCT_NAME:  Precision 7730
 SYSTEM_SKU:  0832
 BIOS_VENDOR:  Dell Inc.
 BIOS_VERSION:  1.14.4
 BIOS_DATE:  10/21/2020
 BASEBOARD_MANUFACTURER:  Dell Inc.
 BASEBOARD_PRODUCT:  00MWX2
 BASEBOARD_VERSION:  A00
 DUMP_FILE_ATTRIBUTES: 0xc
   Insufficient Dumpfile Size
   Kernel Generated Triage Dump
 DUMP_TYPE:  2
 BUGCHECK_P1: ffff86823c8474cc
 BUGCHECK_P2: 0
 BUGCHECK_P3: ffffa093c58e99f6
 BUGCHECK_P4: 2
 READ_ADDRESS: fffff802532fb390: Unable to get MiVisibleState
 Unable to get NonPagedPoolStart
 Unable to get NonPagedPoolEnd
 Unable to get PagedPoolStart
 Unable to get PagedPoolEnd
  ffff86823c8474cc 
    
 FAULTING_IP: 
 win32kfull!UMPDOBJ::vClient+6
 ffffa093`c58e99f6 6644394a4c      cmp     word ptr [rdx+4Ch],r9w
    
    
 DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 BUGCHECK_STR:  AV
 PROCESS_NAME:  splwow64.exe
 CURRENT_IRQL:  0
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TeemoTang-MSFT avatar image
0 Votes"
TeemoTang-MSFT answered

I check your memory dump, and find that PROCESS_NAME: splwow64.exe.
Splwow64.exe is a Windows core system file. The program runs in the background and is not normally visible. It is a trustworthy resource created by Microsoft. Task Manager lists it as the “Printer driver host for 32-bit applications.” In other words, splwow64.exe allows 32-bit applications to connect with the 64-bit printer spooler service on x64 Windows builds.
Therefore, try to stop and restart print spooler service and troubleshooting your printer.

 PAGE_FAULT_IN_NONPAGED_AREA (50)
 Invalid system memory was referenced.  This cannot be protected by try-except.
 Typically the address is just plain bad or it is pointing at freed memory.
 Arguments:
 Arg1: ffff83868f12f4cc, memory referenced.
 Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
 Arg3: fffff3659c9c9806, If non-zero, the instruction address which referenced the bad memory
     address.
 Arg4: 0000000000000002, (reserved)
    
 Debugging Details:
 ------------------
    
    
 Could not read faulting driver name
    
 KEY_VALUES_STRING: 1
    
     Key  : Analysis.CPU.mSec
     Value: 3265
    
     Key  : Analysis.DebugAnalysisManager
     Value: Create
    
     Key  : Analysis.Elapsed.mSec
     Value: 64303
    
     Key  : Analysis.Init.CPU.mSec
     Value: 499
    
     Key  : Analysis.Init.Elapsed.mSec
     Value: 160905
    
     Key  : Analysis.Memory.CommitPeak.Mb
     Value: 90
    
     Key  : WER.OS.Branch
     Value: vb_release
    
     Key  : WER.OS.Timestamp
     Value: 2019-12-06T14:06:00Z
    
     Key  : WER.OS.Version
     Value: 10.0.19041.1
    
    
 BUGCHECK_CODE:  50
    
 BUGCHECK_P1: ffff83868f12f4cc
    
 BUGCHECK_P2: 0
    
 BUGCHECK_P3: fffff3659c9c9806
    
 BUGCHECK_P4: 2
    
 READ_ADDRESS: fffff8022aafb390: Unable to get MiVisibleState
 Unable to get NonPagedPoolStart
 Unable to get NonPagedPoolEnd
 Unable to get PagedPoolStart
 Unable to get PagedPoolEnd
 unable to get nt!MmSpecialPagesInUse
  ffff83868f12f4cc 
    
 MM_INTERNAL_CODE:  2
    
 BLACKBOXBSD: 1 (!blackboxbsd)
    
    
 BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
 BLACKBOXPNP: 1 (!blackboxpnp)
    
    
 BLACKBOXWINLOGON: 1
    
 CUSTOMER_CRASH_COUNT:  1
    
 PROCESS_NAME:  splwow64.exe
    
 TRAP_FRAME:  ffff83868f0aa6b0 -- (.trap 0xffff83868f0aa6b0)
 NOTE: The trap frame does not contain all registers.
 Some register values may be zeroed or incorrect.
 rax=fffff306c6517910 rbx=0000000000000000 rcx=0000000000000000
 rdx=ffff83868f12f480 rsi=0000000000000000 rdi=0000000000000000
 rip=fffff3659c9c9806 rsp=ffff83868f0aa848 rbp=ffff83868f0aaa80
  r8=ffff83868f12f480  r9=0000000000000000 r10=0000000000000000
 r11=ffff83868f0aa7a0 r12=0000000000000000 r13=0000000000000000
 r14=0000000000000000 r15=0000000000000000
 iopl=0         nv up ei pl zr na po nc
 win32kfull!UMPDOBJ::vClient+0x6:
 fffff365`9c9c9806 6644394a4c      cmp     word ptr [rdx+4Ch],r9w ds:ffff8386`8f12f4cc=????
 Resetting default scope
    
 STACK_TEXT:  
 ffff8386`8f0aa408 fffff802`2a21ebbb     : 00000000`00000050 ffff8386`8f12f4cc 00000000`00000000 ffff8386`8f0aa6b0 : nt!KeBugCheckEx
 ffff8386`8f0aa410 fffff802`2a00c960     : fffff802`2aa514c0 00000000`00000000 ffff8386`8f0aa730 00000000`00000000 : nt!MiSystemFault+0x1f43ab
 ffff8386`8f0aa510 fffff802`2a203c5e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
 ffff8386`8f0aa6b0 fffff365`9c9c9806     : fffff365`9c9c8d1c fffff306`c6517910 00000000`00000000 fffff306`c6517910 : nt!KiPageFault+0x35e
 ffff8386`8f0aa848 fffff365`9c9c8d1c     : fffff306`c6517910 00000000`00000000 fffff306`c6517910 fffff306`c6610f90 : win32kfull!UMPDOBJ::vClient+0x6
 ffff8386`8f0aa850 fffff365`9c9c8c89     : 00000000`00000000 fffff306`c4a0e620 00000000`00000000 00000000`00000001 : win32kfull!UMPDOBJ::bCleanupWorker+0x84
 ffff8386`8f0aa890 fffff365`9c6537a6     : ffff8386`8f0aa920 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!UMPDOBJ_bCleanupWrap+0x9
 ffff8386`8f0aa8c0 fffff365`9c65374e     : fffff306`c6517910 ffff8386`8f0aaa80 00000000`031b6300 00000000`00000000 : win32kbase!UMPDOBJ::bCleanup+0x3a
 ffff8386`8f0aa8f0 fffff365`9c9c8b57     : fffff306`c6517910 00000000`031b6300 00007ffe`7f075140 00007ffe`7efe0000 : win32kbase!UMPDOBJ::vRelease+0xbe
 ffff8386`8f0aa950 fffff365`9cf4d106     : 00000000`00000000 fffff802`2a4d944c ffffcb05`66eec080 00000000`048f00c0 : win32kfull!NtGdiSetPUMPDOBJ+0x237
 ffff8386`8f0aa9c0 fffff802`2a2074b5     : ffffcb05`66eec080 00000000`00000000 ffff8386`00000001 ffffcb05`00000000 : win32k!NtGdiSetPUMPDOBJ+0x16
 ffff8386`8f0aaa00 00007ffe`ff3272c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
 00000000`02f0f618 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`ff3272c4
    
    
 SYMBOL_NAME:  win32kfull!UMPDOBJ::vClient+6
    
 MODULE_NAME: win32kfull
    
 IMAGE_NAME:  win32kfull.sys
    
 IMAGE_VERSION:  10.0.19041.805
    
 STACK_COMMAND:  .thread ; .cxr ; kb
    
 BUCKET_ID_FUNC_OFFSET:  6
    
 FAILURE_BUCKET_ID:  AV_R_INVALID_win32kfull!UMPDOBJ::vClient
    
 OS_VERSION:  10.0.19041.1
    
 BUILDLAB_STR:  vb_release
    
 OSPLATFORM_TYPE:  x64
    
 OSNAME:  Windows 10
    
 FAILURE_ID_HASH:  {d2a843d7-b242-5105-8422-17214b6c47ba}
    
 Followup:     MachineOwner
 ---------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.