Latitude 9420 - BSOD every day with different description

hamar

Active member
Joined
Oct 25, 2021
Posts
26
Hello,

I am having issues with my Dell Latitude 9420. I had BSODs in W10 so I have decided to update to W11 and also do RESET to get rid off all data and start from scratch.
But I am still having BSODs and they are not all same unfortunetly.

I am mostlikely able to reproduce the BSOD onl when I play same video from youtube or other web. But i am not 100 sure if this is the only way.

I did try to run SFC /snannow with this result:

Code:
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

There is a problem:
Code:
2021-10-25 21:34:33, Info                  CSI    000000b2 [SR] Cannot repair member file [l:12]'mingliub.ttc' of Microsoft-Windows-Font-TrueType-MingLiUB, version 10.0.22000.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-10-25 21:34:34, Info                  CSI    000000b4 [SR] Cannot repair member file [l:12]'mingliub.ttc' of Microsoft-Windows-Font-TrueType-MingLiUB, version 10.0.22000.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-10-25 21:34:34, Info                  CSI    000000b5 [SR] This component was referenced by [l:125]'Microsoft-Windows-Client-Desktop-Required-Package0411~31bf3856ad364e35~amd64~~10.0.22000.282.436ae9204ef839b56ffd07391dda87eb'
2021-10-25 21:34:34, Info                  CSI    000000b8 [SR] Could not reproject corrupted file \??\C:\WINDOWS\Fonts\\mingliub.ttc; source file in store is also corrupted

I did try to run scf /scannow also before boot. This time no error discovered. I did also run diagnostics test from DELL before boot. No HW issue found (it also check the RAM).
Also tried the command restorehealth. No success with getting rid of that corruped files.

  • Laptop
  • Latitude 7420
  • OS Windows 11
  • x64 (64bit)
  • What was original installed OS on system = Windows 10
  • OS an OEM version
  • 3-4 months
  • Age of OS install = less then week
  • Have you re-installed the OS - I did RESET (using option to delete all files).
  • CPU - Core I7, 11. gen 1185G7
  • RAM - integrated 32 GB
  • Intel Iris XE
  • Is driver verifier enabled or disabled??? Do not know
  • What security software are you using? Just Windows default
  • Are you using proxy, vpn, ipfilters or similar software? - sometime open VPN.
  • Are you using Disk Image tools? No
  • Are you currently under/overclocking? Are there overclocking software installed on your system - NO
 

Attachments

and another one just after 9 min, different BSOD message: IRQL_NOT_LESS_OR_EQUAL. No video playback, i was just reading this forum. Nothing else was on.
 

Attachments

It appears that your webcam and wireless NIC driver are causing issues here. I've noticed that you've upgraded to Windows 11, therefore there may be some compatibility problems with drivers.

Rich (BB code):
3: kd> lmvm iacamera64
Browse full module list
start             end                 module name
fffff801`75050000 fffff801`75ad5000   iacamera64 T (no symbols)          
    Loaded symbol image file: iacamera64.sys
    Image path: \SystemRoot\System32\drivers\iacamera64.sys
    Image name: iacamera64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Apr 16 04:21:34 2021 (607902BE)
    CheckSum:         00A8AE53
    ImageSize:        00A85000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Rich (BB code):
3: kd> lmvm Netwtw10
Browse full module list
start             end                 module name
fffff803`462a0000 fffff803`467ff000   Netwtw10 T (no symbols)          
    Loaded symbol image file: Netwtw10.sys
    Image path: \SystemRoot\System32\drivers\Netwtw10.sys
    Image name: Netwtw10.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Sep 13 09:13:59 2021 (613F0847)
    CheckSum:         004F845F
    ImageSize:        0055F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:


Please check for any updates using the Intel support assistant - Download Intel Drivers and Software
 
thank you for you investigation. Unfortunetly I have latest driver already installed. I will try to re-install the drivers.
 
So it went wrong. Today another BSOD - IRQL_NOT_LESS_OR_EQUAL.
Video was playing on background, I was reading some article on internet.
 

Attachments

The latest dump file indicated a WDV BSOD caused by smbco10x64.

smbcosvc SmbCoSvc c:\windows\system32\drivers\smbco10x64.sys


Uninstall and reinstall:
SB Traffic Control developed by Rivet Networks, LLC.

Then restart WDV to see if there are any additional misbehaving drivers.

The log files displayed the following bugchecks:
  • 133
  • 139
  • 1A
  • 1E
  • 3B
  • A
  • D1
  • FC
  • 193
  • 141
  • 117
  • 1B

If BSOD continue consider testing RAM:
MemTest86 - Official Site of the x86 Memory Testing Tool

Code:
10/21/2021  10:47 PM    <DIR>          KERNEL~1     Kernel_193_729357d37cebf068ec2e96cecf379f262a9d3d_00000000_cab_a9e1b217-0a3d-4ae5-904e-5857512eba85
10/21/2021  10:58 PM    <DIR>          KERNEL~2     Kernel_1a_57c48b51cf568293b231fabda8591809e874a4_00000000_cab_8251dc0b-0604-4605-881e-1376f9428274
10/21/2021  11:15 PM    <DIR>          KERNEL~3     Kernel_141_85febc94a33642a865c21e31d94546c1f86381_00000000_cab_709b1ad4-1105-408e-a011-f3620eb1e41f
10/21/2021  11:59 PM    <DIR>          KERNEL~4     Kernel_1a8_302e20c64fe8f86c2579643b6b7bc6d1caf7831_00000000_cab_1821b239-f3af-4714-9267-c4caf4b57fc2
10/21/2021  11:59 PM    <DIR>          KE5BA9~1     Kernel_3b_de6a3ffe50deb65591afe567cd51369b8dfd458_00000000_cab_6bebb206-e02a-4299-a41d-087091711130
10/22/2021  12:05 AM    <DIR>          KE8804~1     Kernel_fc_ad774a199a3ccfe9ef27c3199d5502f8d44abe1_00000000_cab_ab8871e4-bbd9-4c8d-8208-726b7891dc94
10/22/2021  12:14 AM    <DIR>          KE7433~1     Kernel_133_508e5a1e9f26be178837c065c75690b210c254f1_00000000_cab_3174436b-d4ae-4555-9b31-0bb6221ac8cf
10/22/2021  12:24 AM    <DIR>          KE0473~1     Kernel_139_a26da14963373a23df31c8f2ad9af99f475177_00000000_cab_a60a36e4-439c-4008-a4b5-d0e0475a797e
10/22/2021  12:28 AM    <DIR>          KEDCAC~1     Kernel_d1_501757226f909245bb7d62dc4813645bf562413_00000000_cab_f7b64c34-d89d-49a5-8e5d-073783d7cedf
10/22/2021  01:13 AM    <DIR>          KEFF88~1     Kernel_193_cb2e8b8a048c73fdff037a1fa2ef9d02e6d07a_00000000_cab_35502bab-5fef-4e3a-bbae-3993553ad2a0
10/22/2021  01:16 AM    <DIR>          KE372C~1     Kernel_141_bc41ea55767a5b6deb19fa9ec04eb2a6e436e824_00000000_cab_61098ab4-d4c0-4bbd-857d-77ca63ccb2d4
10/22/2021  09:44 PM    <DIR>          KE5F26~1     Kernel_3b_335a07786819829f1b50e42fe790694cfee61b_00000000_cab_47b09545-a62e-4dac-96a8-04cf6cc95404
10/22/2021  10:16 PM    <DIR>          KEDBEB~1     Kernel_1e_9d51b79d328239fe3f304ae61d2e44390d7c41d_00000000_cab_644197f1-d81a-4f05-a34e-60fd81caffcb
10/22/2021  10:57 PM    <DIR>          KE5C4D~1     Kernel_3b_fea865c9cd99e7e66c1e9d68a35aecbb17368b3e_00000000_cab_ba73d562-7e98-4eb4-8c72-2c3e08c855d0
10/22/2021  10:57 PM    <DIR>          KE5C30~1     Kernel_1a8_302e20c64fe8f86c2579643b6b7bc6d1caf7831_00000000_cab_f2b7e285-8822-4a2f-86b8-0ac85e456a3d
10/22/2021  10:57 PM    <DIR>          KEB16A~1     Kernel_1b8_74c04b731e6e5d9382815ef7b2fbbb9519692d_00000000_cab_5cc6c172-96fc-412b-98b2-bc6f89a8fa3e
10/22/2021  10:58 PM    <DIR>          KEDC3A~1     Kernel_1b8_74c04b731e6e5d9382815ef7b2fbbb9519692d_00000000_cab_dd5f9ee9-df4c-4b05-9a28-a4bcbfd91f4b
10/22/2021  10:58 PM    <DIR>          KE7374~1     Kernel_1a8_302e20c64fe8f86c2579643b6b7bc6d1caf7831_00000000_cab_9918aa8c-0195-430d-80ca-7d49a35557c3
10/24/2021  01:03 PM    <DIR>          KEBAE1~1     Kernel_a_452d302425246c1f1e656dcd1f433441a59abb_00000000_cab_705325bf-f923-4ad4-a2fd-c519500416c9
10/24/2021  01:03 PM    <DIR>          KE4666~1     Kernel_3b_fea865c9cd99e7e66c1e9d68a35aecbb17368b3e_00000000_cab_b9ae608a-7ef3-44ca-8e20-c4f46d79b34d
10/24/2021  01:04 PM    <DIR>          KE1B01~1     Kernel_3b_3221d82aa1f77e4e92cd81f9f96ee3458ce1bd1_00000000_cab_d3dfa008-b90b-41ff-b89e-4a3b85d209f8
10/24/2021  01:04 PM    <DIR>          KE8DED~1     Kernel_a_452d302425246c1f1e656dcd1f433441a59abb_00000000_cab_0b4399d8-8fed-4000-bb42-1a04f944ecb2
10/24/2021  01:04 PM    <DIR>          KE7087~1     Kernel_3b_fea865c9cd99e7e66c1e9d68a35aecbb17368b3e_00000000_cab_9b19a82c-7f64-4680-aa5c-456f32b65a9b
10/24/2021  01:51 PM    <DIR>          KECA70~1     Kernel_3b_80fb5dbf2e639787db7dcdea13612c4d5c4d958_00000000_cab_8258f2fe-06a7-431e-a7c5-8ba11e8d2878
10/24/2021  02:09 PM    <DIR>          KEC323~1     Kernel_3b_3ad08248ca6789e153c0ce19343d0318bbc9b47_00000000_cab_7d3f1edf-4c48-4834-b36d-9f3c43f9437b
10/24/2021  11:07 PM    <DIR>          KE8A2A~1     Kernel_d1_33a51ba6f46e9c0bed4dfdf1a375fa9e8ca0be_00000000_cab_bdd899e5-73f7-4fbe-84ab-874efca7c42f
10/24/2021  11:55 PM    <DIR>          KE2CB5~1     Kernel_193_b9add15641354fdc53730abeca9707e9c26a122_00000000_cab_6a5976f3-1acd-4bab-9c7a-161b01e8af2e
10/25/2021  12:31 AM    <DIR>          KEFACB~1     Kernel_141_d32c1c2762edb205cceb7114163de67136b1051_00000000_cab_a5c12de5-c8ea-4c13-b2de-56dcd63bc735
10/25/2021  12:31 AM    <DIR>          KE926E~1     Kernel_117_443aa6c967f1d9d9cd6d9bdad1a17987bd489_00000000_cab_29d5f01f-40b1-49bb-a264-ff1e65f7374a                   .
10/25/2021  09:26 PM    <DIR>          KE190D~1     Kernel_139_e74613126b52f886ae31b890fc795adbf44d7c_00000000_cab_9a98b14f-a538-47bd-a76b-1ca344912aac
 
Last edited by a moderator:
thanks for diagnostic. I have uninstalled ExpressConnect Drivers and Services from Rivet Networks completly, then I have also restarted WDV.
Another BSOD appeard during video playback on fullscreen.

SYSTEM_SERVICE_EXCEPTION, win32kbase.sys
 

Attachments

How long have you had this computer? I work at an MSP and we've had to RMA a surprising number of the Latitudes we get in, for a variety of issues including faulty display and hard drive. A few full MOBO replacements as well. It's been like this for the last ~6 months. Latitudes coming out of the factory just seem to not be in good quality for what our order desk lady told us was issues with changing suppliers and parts.
 
Approx 3-4 months. I had problems since buy. Then it was ok for 2 months but it started again recently.

I am testing ram, so far so good. I need more time to finish the test.

20211028_021408.jpg
 
Have you ran the Dell built-in hardware diagnostics? Should be a key you press on boot to enter them. It's hit or miss imo but still worth it to consider.
 
Ah, I should really read the first post more clearly, eh? 😬

If hardware diagnostics don't find anything then dell support may become difficult to work with, especially for a non-commercial customer. Sorry about that.
 
I was worried even before buying this laptop that it will be bad. And unfortunately i was right. But there is not much selection right now on market and dell have still one of the best support and hw. That is why i bought it. But i made a mistake as i just cannot work with this think. So for normal work i am using my old latitude.

It seems to me that drivers are not good. Or? What do you think?
 
1) Please turn off WDV.

2) Run the compatibility check > post images or share links
Upgrade to the New Windows 11 OS | Microsoft

3) Run a second Memtest86 for 4 passes.

4) Run the Dell Full Test:
Support for Latitude 9420 | Diagnostics | Dell US

Post images or share links.

5) Place the computer in safe mode (shift + restart) > run continuously for several days

6) Report into the thread whether the computer is more stable in safe mode or whether there are still BSOD while in safe mode

7) For any BSOD post a new Sysnative log collector result.
 
The latest dump file indicated a WDV BSOD caused by smbco10x64.
That crash was not caused by Windows Driver Verifier detecting an issue, if that is what you're referring to with WDV? The reason why the driver crashed the system is because it caused at a page fault when the IRQL was at DISPATCH_LEVEL, hence the bugcheck of Stop 0xA.

Rich (BB code):
3: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffcf8d`a35bceb8 fffff802`544341a9 nt!KeBugCheckEx
01 ffffcf8d`a35bcec0 fffff802`54430300 nt!KiBugCheckDispatch+0x69
02 ffffcf8d`a35bd000 fffff802`542f054f nt!KiPageFault+0x440 << Illegal page fault
03 ffffcf8d`a35bd190 fffff802`54619a5f nt!KeAcquireInStackQueuedSpinLock+0x5f
04 ffffcf8d`a35bd1c0 fffff802`54a8823a nt!DifKeAcquireInStackQueuedSpinLockWrapper+0xcf
05 ffffcf8d`a35bd210 fffff802`6fd32390 nt!VerifierKeAcquireInStackQueuedSpinLock+0x5a << DV grabs a spinlock, which raises the IRQL Level to 2
06 ffffcf8d`a35bd250 00000000`00000000 SmbCo10X64+0x2390 << Faulty driver

Rich (BB code):
3: kd> !pte ffffe702070c4ff8
                                           VA ffffe702070c4ff8
PXE at FFFFFC7E3F1F8E70    PPE at FFFFFC7E3F1CE040    PDE at FFFFFC7E39C081C0    PTE at FFFFFC7381038620
contains 0A00000054BDB863  contains 0A00000388293863  contains 0A0000043C722863  contains 0000000000000000
pfn 54bdb     ---DA--KWEV  pfn 388293    ---DA--KWEV  pfn 43c722    ---DA--KWEV  not valid

As we can see, the referenced address was invalid, hence the page fault being caused. The user appears to have experiencing issues with several drivers causing almost the exact same problem.




Looks like the Stop 0x3B crash was caused by an invalid opcode fault.

Rich (BB code):
6: kd> !error c000001d
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

Rich (BB code):
6: kd> .cxr 0xfffff309341566a0
rax=fffff309341570e8 rbx=0000000000002000 rcx=0000000000002000
rdx=fffff30934157100 rsi=0000000000000000 rdi=0000000000000007
rip=fffffb3409ab2f02 rsp=fffff309341570c0 rbp=fffff30934157230
 r8=ffff800a62c6b5d0  r9=0000000000000014 r10=ffff800a6421e520
r11=0000000000000000 r12=0000000033010dec r13=000000f8661fe780
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
win32kbase!GreStackExpansionRequired+0x12:
fffffb34`09ab2f02 33ff            xor     edi,edi

It doesn't appear that opcode is correct (shown in red), 33 is XOR and I believe FF is actually CALL.




and after 20 minutes another BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL, igdkmdn64.sys
You've attached the same file twice in your post. However, that driver you're referring to is the Intel graphics card driver.

These have already been run by the user. There wasn't any reported issues.

2) Run the compatibility check > post images or share links
Upgrade to the New Windows 11 OS | Microsoft
The user is already running Windows 11 and has been mentioned by myself and in the initial post.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top