BSOD Dell Laptop - Please Help

Jase475 · Oct 3, 2022

A while back, took the laptop for an upgrade to SSD. Was running and working perfectly.
Then unfortunately borrowed to a relative for their work. Got it back and since then every time we try to run Fortnite for example, the system will crash with BSOD or we will get an error and the game will crash but system does not. Very very frustrating.

Most common occurrence of BSOD is from shut down and switch on = immediately begins with BSOD

Also seem to see crashes when playing games with AMD, and also when not using AMD.

Have done a clean install of Windows, literally wiped the entire machine to use it like it's brand new and these issues are still happening.

• Dell Inspiron 5537
• Windows 10 (current)
• Have had the laptop since 2015

speccy System Information:
http://speccy.piriform.com/results/FdfdAMQ7ud5tinl6At3Gyt4

ubuysa · Oct 3, 2022

Four of the five dumps point very clearly at the amdkmpfd.sys driver as the cause...

Rich (BB code):

3: kd> knL
# Child-SP RetAddr Call Site
00 ffff9e0b`e583d928 fffff803`64c0af69 nt!KeBugCheckEx
01 ffff9e0b`e583d930 fffff803`64c07269 nt!KiBugCheckDispatch+0x69
02 ffff9e0b`e583da70 fffff803`66608886 nt!KiPageFault+0x469
03 ffff9e0b`e583dc00 ffffe303`7e3cd900 amdkmpfd+0x8886
04 ffff9e0b`e583dc08 ffffe303`8bf8b400 0xffffe303`7e3cd900
05 ffff9e0b`e583dc10 ffffcd0b`61184370 0xffffe303`8bf8b400
06 ffff9e0b`e583dc18 00000000`00000000 0xffffcd0b`61184370

This is a component of your chipset driver package, and the version you have installed in now 18 months old...

Rich (BB code):

3: kd> lmDvmamdkmpfd
Browse full module list
start end module name
fffff803`66600000 fffff803`66619000 amdkmpfd T (no symbols)
Loaded symbol image file: amdkmpfd.sys
Image path: \SystemRoot\System32\drivers\amdkmpfd.sys
Image name: amdkmpfd.sys
Browse all global symbols functions data
Timestamp: Thu Feb 4 17:55:29 2021 (601C18F1)
CheckSum: 00021C26
ImageSize: 00019000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

I suggest that you visit the AMD Driver & Support page and see whether there are updated chipset drivers for your build.

The remaining dump points at bedaisy.sys as the probably cause...

Rich (BB code):

0: kd> knL
*** Stack trace for last set context - .thread/.cxr resets it
# Child-SP RetAddr Call Site
00 ffff870e`a632a510 fffff804`1108e6c1 nt!KiExitDispatcher+0x1ad
01 ffff870e`a632a580 fffff806`391e87b1 nt!KeInsertQueueApc+0x151
02 ffff870e`a632a620 00000000`00000200 BEDaisy+0x3287b1
03 ffff870e`a632a628 ffff9b88`4f5f3578 0x200
04 ffff870e`a632a630 ffff890d`63b0b010 0xffff9b88`4f5f3578
05 ffff870e`a632a638 00000000`00000002 0xffff890d`63b0b010
06 ffff870e`a632a640 00000000`00000000 0x2

This is the Battle Eye Anti-Cheat driver (BEDaisy.sys). The version of this driver that you have installed is quite recent...

Rich (BB code):

0: kd> lmDvmBEDaisy
Browse full module list
start end module name
fffff806`38ec0000 fffff806`391f1000 BEDaisy T (no symbols)
Loaded symbol image file: BEDaisy.sys
Image path: \??\C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys
Image name: BEDaisy.sys
Browse all global symbols functions data
Timestamp: Tue Apr 19 20:09:51 2022 (625EECDF)
CheckSum: 0033D7DC
ImageSize: 00331000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

I don't believe in there being two different problems an a system at the same time, although BattleEye has caused problems on many systems - so perhaps this is two separate problems. I would suggest that you visit the BattleEye download site and see whether there is an updated version.

Jase475 · Oct 3, 2022

Hi ubuysa. I really appreciate your time.

I have uninstalled all AMD related stuff, downloaded the Auto Detect tool and installed the latest everything.
I cannot seem to install the chipset driver separately as it says "This installer is intended to be deployed only on an AMD system. Exiting installation as the requirement is not satisfied.
Regarding the Battle Eye one, no idea what to do there. Their download page has nothing related to latest software versions, apparently the game client handles that.

I've run a new scan and attached it

ubuysa · Oct 4, 2022

I'm afraid I misled you concerning the AMD chipset drivers, you have an Intel build of course and that's why it wouldn't install. My mistake.

You're still seeing 0xD1 BSODs caused by amdkmpfd.sys, and that is an AMD driver. The only AMD product you have installed is the AMD Radeon HD 8600M graphics card, but it appears to be disabled - it's not shown in either the Dxdiag nor msinfo32 outputs. Most gaming laptops allow the dedicated GPU (the AMD Radeon in your case) to be disabled to conserve battery power, is that what you've done?

I'd like you to enable the AMD Radeon GPU and then run the AMD Auto-Detect tool again, with the AMD Radeon card enabled it should update the necessary drivers.

Regarding the BattleEye anti-cheat tool, I would suggest that you contact BattleEye Support and explain that the BEdaisy.sys driver has caused a 0x139 BSOD. Tell them the game in which the BSOD happened and offer to upload the dump file (092922-7656-01.dmp) for them to examine, and/or paste the following into your request for help...

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff870ea632a380, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff870ea632a2d8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

*** WARNING: Unable to verify timestamp for BEDaisy.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3265

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 29407

Key : Analysis.Init.CPU.mSec
Value: 2093

Key : Analysis.Init.Elapsed.mSec
Value: 3259

Key : Analysis.Memory.CommitPeak.Mb
Value: 120

Key : FailFast.Name
Value: CORRUPT_LIST_ENTRY

Key : FailFast.Type
Value: 3

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

FILE_IN_CAB: 092922-7656-01.dmp

BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: ffff870ea632a380

BUGCHECK_P3: ffff870ea632a2d8

BUGCHECK_P4: 0

TRAP_FRAME: ffff870ea632a380 -- (.trap 0xffff870ea632a380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9b8847ab92a0 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8041102205d rsp=ffff870ea632a510 rbp=ffff9b8847f9e0c0
r8=0000000000000001 r9=0000000000000002 r10=ffff9b883f4c8d00
r11=fffff8040dd86180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!KiExitDispatcher+0x1ad:
fffff804`1102205d cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffff870ea632a2d8 -- (.exr 0xffff870ea632a2d8)
ExceptionAddress: fffff8041102205d (nt!KiExitDispatcher+0x00000000000001ad)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
ffff870e`a632a058 fffff804`1120af69 : 00000000`00000139 00000000`00000003 ffff870e`a632a380 ffff870e`a632a2d8 : nt!KeBugCheckEx
ffff870e`a632a060 fffff804`1120b390 : 00000000`00000000 ffff9b88`3f27a080 00000000`02000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff870e`a632a1a0 fffff804`11209723 : 00000000`0000000f 00000000`00000000 00000000`00000000 55555555`55555555 : nt!KiFastFailDispatch+0xd0
ffff870e`a632a380 fffff804`1102205d : 00000000`00000000 ffff870e`a632a5c1 ffff9b88`51224000 fffff804`11011e83 : nt!KiRaiseSecurityCheckFailure+0x323
ffff870e`a632a510 fffff804`1108e6c1 : fffff804`0dd86180 00000000`00000000 fffff804`0dd86101 fffff804`117b2094 : nt!KiExitDispatcher+0x1ad
ffff870e`a632a580 fffff806`391e87b1 : 00000000`00000200 ffff9b88`4f5f3578 ffff890d`63b0b010 00000000`00000002 : nt!KeInsertQueueApc+0x151
ffff870e`a632a620 00000000`00000200 : ffff9b88`4f5f3578 ffff890d`63b0b010 00000000`00000002 00000000`00000000 : BEDaisy+0x3287b1
ffff870e`a632a628 ffff9b88`4f5f3578 : ffff890d`63b0b010 00000000`00000002 00000000`00000000 00000000`00000000 : 0x200
ffff870e`a632a630 ffff890d`63b0b010 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff9b88`4f5f3578
ffff870e`a632a638 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff890d`63b0b010
ffff870e`a632a640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2

SYMBOL_NAME: BEDaisy+3287b1

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 3287b1

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {59d8eb10-b2e4-7df6-f6a5-49968226dbb8}

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

I think your only alternatives are to put up with the occasional BSOD or to uninstall BattleEye completely.

The latest Sysnative file collection zip file contains five new dumps. Four of them are 0xD1 bugchecks identifying amdkmpfd.sys again (which wasn't updated when you ran the AMD auto-detect tool the first time). The fifth dump is a Driver Verifier 0xC4 bugcheck that identifies the farflt.sys driver as the faulty driver...

Rich (BB code):

FAILURE_BUCKET_ID:  0xc4_62_VRF_LEAKED_POOL_IMAGE_farflt.sys

This is a component of the Malwarebytes AntiMalware product. Malwarebytes needs to be kept updated, the version you have installed is quite recent, but I'd advise checking Malwarebytes for updates...

Rich (BB code):

3: kd> lmDvmfarflt
Browse full module list
start             end                 module name
fffff805`634a0000 fffff805`634db000   farflt     (no symbols)      
    Loaded symbol image file: farflt.sys
    Image path: \SystemRoot\system32\DRIVERS\farflt.sys
    Image name: farflt.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jul 12 15:21:45 2022 (62CD6759)
    CheckSum:         0003331E
    ImageSize:        0003B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Jase475 · Oct 7, 2022

ubuysa said:
I'm afraid I misled you concerning the AMD chipset drivers, you have an Intel build of course and that's why it wouldn't install. My mistake.

You're still seeing 0xD1 BSODs caused by amdkmpfd.sys, and that is an AMD driver. The only AMD product you have installed is the AMD Radeon HD 8600M graphics card, but it appears to be disabled - it's not shown in either the Dxdiag nor msinfo32 outputs. Most gaming laptops allow the dedicated GPU (the AMD Radeon in your case) to be disabled to conserve battery power, is that what you've done?

I'd like you to enable the AMD Radeon GPU and then run the AMD Auto-Detect tool again, with the AMD Radeon card enabled it should update the necessary drivers.

Regarding the BattleEye anti-cheat tool, I would suggest that you contact BattleEye Support and explain that the BEdaisy.sys driver has caused a 0x139 BSOD. Tell them the game in which the BSOD happened and offer to upload the dump file (092922-7656-01.dmp) for them to examine, and/or paste the following into your request for help...

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff870ea632a380, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff870ea632a2d8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

*** WARNING: Unable to verify timestamp for BEDaisy.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3265

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 29407

Key : Analysis.Init.CPU.mSec
Value: 2093

Key : Analysis.Init.Elapsed.mSec
Value: 3259

Key : Analysis.Memory.CommitPeak.Mb
Value: 120

Key : FailFast.Name
Value: CORRUPT_LIST_ENTRY

Key : FailFast.Type
Value: 3

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

FILE_IN_CAB: 092922-7656-01.dmp

BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: ffff870ea632a380

BUGCHECK_P3: ffff870ea632a2d8

BUGCHECK_P4: 0

TRAP_FRAME: ffff870ea632a380 -- (.trap 0xffff870ea632a380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9b8847ab92a0 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8041102205d rsp=ffff870ea632a510 rbp=ffff9b8847f9e0c0
r8=0000000000000001 r9=0000000000000002 r10=ffff9b883f4c8d00
r11=fffff8040dd86180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!KiExitDispatcher+0x1ad:
fffff804`1102205d cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffff870ea632a2d8 -- (.exr 0xffff870ea632a2d8)
ExceptionAddress: fffff8041102205d (nt!KiExitDispatcher+0x00000000000001ad)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
ffff870e`a632a058 fffff804`1120af69 : 00000000`00000139 00000000`00000003 ffff870e`a632a380 ffff870e`a632a2d8 : nt!KeBugCheckEx
ffff870e`a632a060 fffff804`1120b390 : 00000000`00000000 ffff9b88`3f27a080 00000000`02000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff870e`a632a1a0 fffff804`11209723 : 00000000`0000000f 00000000`00000000 00000000`00000000 55555555`55555555 : nt!KiFastFailDispatch+0xd0
ffff870e`a632a380 fffff804`1102205d : 00000000`00000000 ffff870e`a632a5c1 ffff9b88`51224000 fffff804`11011e83 : nt!KiRaiseSecurityCheckFailure+0x323
ffff870e`a632a510 fffff804`1108e6c1 : fffff804`0dd86180 00000000`00000000 fffff804`0dd86101 fffff804`117b2094 : nt!KiExitDispatcher+0x1ad
ffff870e`a632a580 fffff806`391e87b1 : 00000000`00000200 ffff9b88`4f5f3578 ffff890d`63b0b010 00000000`00000002 : nt!KeInsertQueueApc+0x151
ffff870e`a632a620 00000000`00000200 : ffff9b88`4f5f3578 ffff890d`63b0b010 00000000`00000002 00000000`00000000 : BEDaisy+0x3287b1
ffff870e`a632a628 ffff9b88`4f5f3578 : ffff890d`63b0b010 00000000`00000002 00000000`00000000 00000000`00000000 : 0x200
ffff870e`a632a630 ffff890d`63b0b010 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff9b88`4f5f3578
ffff870e`a632a638 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff890d`63b0b010
ffff870e`a632a640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2

SYMBOL_NAME: BEDaisy+3287b1

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 3287b1

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {59d8eb10-b2e4-7df6-f6a5-49968226dbb8}

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

I think your only alternatives are to put up with the occasional BSOD or to uninstall BattleEye completely.

The latest Sysnative file collection zip file contains five new dumps. Four of them are 0xD1 bugchecks identifying amdkmpfd.sys again (which wasn't updated when you ran the AMD auto-detect tool the first time). The fifth dump is a Driver Verifier 0xC4 bugcheck that identifies the farflt.sys driver as the faulty driver...

Rich (BB code):

FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_farflt.sys

This is a component of the Malwarebytes AntiMalware product. Malwarebytes needs to be kept updated, the version you have installed is quite recent, but I'd advise checking Malwarebytes for updates...

Rich (BB code):

3: kd> lmDvmfarflt Browse full module list start end module name fffff805`634a0000 fffff805`634db000 farflt (no symbols) Loaded symbol image file: farflt.sys Image path: \SystemRoot\system32\DRIVERS\farflt.sys Image name: farflt.sys Browse all global symbols functions data Timestamp: Tue Jul 12 15:21:45 2022 (62CD6759) CheckSum: 0003331E ImageSize: 0003B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:

Hi there ubuysa, sorry for the delayed reply.
Thank you for your efforts and suggestions.

It's been a bit of a nightmare. I had no idea how to manually enable the AMD Radeon GPU. Eventually found online some people suggesting "Switchable Graphics" option in the AMD settings. Did not have this option.
Then removed AMD -> Installed Older Version with the Switchable Graphics option -> Then used Auto-Detect Tool -> Then install latest, which froze.
Tried this all again. Nothing seemed to have worked. Bit of a mission.

Re Battleye, I did contact them and have not had a reply since.
Their FAQ section does suggest BSOD could be the result of Driver Verifier (which I turned off) and needing to update the BIOS, which was already on the latest.

So I just am giving up now

ubuysa · Oct 9, 2022

Don't despair, I've not forgotten you. :)

ubuysa · Oct 14, 2022

Sorry for the delay in replying but it's difficult to pinpoint any particular cause.

I want to approach your problem from a different direction. You said that it BSODs most often on boot up? In that case I'd like to disable auto-start for all third-party programs that are not absolutely essential for the operation of the laptop. This will indicate whether the BSODs are being generated by something that auto-starts. Note that this will limit some of the functionality of the laptop, because programs that are expected to be running won't be, but it will do no harm. You can always restore auto-start after this testing.

I'd like you first to display all the third-party programs that auto-start, and then we can suggest which ones you should disable from auto-starting. To do that please right-click on the taskbar and select Task Manager from the pop-up menu.

In Task Manager click on the Startup tab. This will display the third-party programs that are auto-starting. Please expand the Task Manager window so that everything is shown. Take a screenshot and post it here. If there are more programs than will fit on screen then take two (or more) screenshots so we see all programs in that list.

BSOD Dell Laptop - Please Help

Jase475

Active member

Attachments

ubuysa

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

Jase475

Active member

Attachments

ubuysa

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

Jase475

Active member

ubuysa

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

ubuysa

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

BSOD Dell Laptop - Please Help

Jase475

Active member

Attachments

ubuysa

Sysnative Staff BSOD Kernel Dump Senior AnalystContributor

Jase475

Active member

Attachments

ubuysa

Sysnative Staff BSOD Kernel Dump Senior AnalystContributor

Jase475

Active member

ubuysa

Sysnative Staff BSOD Kernel Dump Senior AnalystContributor

ubuysa

Sysnative Staff BSOD Kernel Dump Senior AnalystContributor

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor