Question Windows 10 BSOD: NMI_Hardware_failure

Jun 9, 2024
3
0
10
Greetings,
I've prowled and lurked through here for various answers to PC issues for years and am usually pretty successful with what's already been asked.
This time I am in a position where I am wracking my brain and Would need some specific help looking into what recently started causing these blue screens in varying frequency about 6 days ago. I've tried a few things ( gone through most of my used drivers reseated hardware etc etc.) Trying to figure out the cause of this recently started bluescreen. The last step being removing what I had thought was a faulty stick of ram due to staving the blue screen off for about 24 hours. Below Are both of the most recent crash dumps
(Both crash dump addresses are as: NTOSKRNL.exe+3fdaf0)
Any help is greatly appreciated

Update with additional info: I have received a new error when attempting to POST out of bios of a "USB device over current"
Which I isolated to the madkatz R.A.T. Mouse I was using, I am going to dig into this further, if this is the cause I will further update this.

Crash dump post ram removal:
https://drive.google.com/file/d/1LcyvgqRqTi6LCDExsOTFqSOmuwNCpoA5/view?usp=drive_link

Crash dump before removing one of my 16GB g.skill ram sticks:
https://drive.google.com/file/d/1GJRsfCqWfyW5Fx5hOKM_Q4hfwvbuO9Qo/view?usp=drive_link
 
Last edited:
Solution
In both dumps the nfextlag.sys driver would appear to be at fault. It's referenced in the lead-up to both bugchecks, in fact it's the last driver call before the bugchecks. Both dumps show considerable networking activity in the lead-up to the bugchecks too.

The nfextlag.sys driver is a component of ExitLag, which is described as a 'virtual VPN', that fits well of course with the copious networking activity we can see. The version of nfextlag.sys that you have installed is almost 9 months old now, dating from Oct 2023...
Code:
1: kd> lmvmnfextlag
Browse full module list
start             end                 module name
fffff807`39570000 fffff807`3958b000   nfextlag T (no symbols)         
    Loaded symbol image file: nfextlag.sys...

ubuysa

Distinguished
In both dumps the nfextlag.sys driver would appear to be at fault. It's referenced in the lead-up to both bugchecks, in fact it's the last driver call before the bugchecks. Both dumps show considerable networking activity in the lead-up to the bugchecks too.

The nfextlag.sys driver is a component of ExitLag, which is described as a 'virtual VPN', that fits well of course with the copious networking activity we can see. The version of nfextlag.sys that you have installed is almost 9 months old now, dating from Oct 2023...
Code:
1: kd> lmvmnfextlag
Browse full module list
start             end                 module name
fffff807`39570000 fffff807`3958b000   nfextlag T (no symbols)         
    Loaded symbol image file: nfextlag.sys
    Image path: nfextlag.sys
    Image name: nfextlag.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Oct 12 10:33:19 2023 (6527A13F)
    CheckSum:         0001E979
    ImageSize:        0001B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
I would advise contacting ExitLag for an update or for assistance. Alternatively, remove ExitLag from your system completely.
 
  • Like
Reactions: Emyrryl
Solution
Jun 9, 2024
3
0
10
Going to try and update first, if I receive it after updating uninstall time. I couldn't stay in the machine long enough to prowl through the dump. I owe you a beer, mate, thank you for the response, I will update on next blue screen or if a few hours pass with no issues!
 
Last edited:
Jun 9, 2024
3
0
10
In both dumps the nfextlag.sys driver would appear to be at fault. It's referenced in the lead-up to both bugchecks, in fact it's the last driver call before the bugchecks. Both dumps show considerable networking activity in the lead-up to the bugchecks too.

The nfextlag.sys driver is a component of ExitLag, which is described as a 'virtual VPN', that fits well of course with the copious networking activity we can see. The version of nfextlag.sys that you have installed is almost 9 months old now, dating from Oct 2023...
Code:
1: kd> lmvmnfextlag
Browse full module list
start             end                 module name
fffff807`39570000 fffff807`3958b000   nfextlag T (no symbols)        
    Loaded symbol image file: nfextlag.sys
    Image path: nfextlag.sys
    Image name: nfextlag.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Oct 12 10:33:19 2023 (6527A13F)
    CheckSum:         0001E979
    ImageSize:        0001B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
I would advise contacting ExitLag for an update or for assistance. Alternatively, remove ExitLag from your system completely.
Absolutely owe you a drink of your choice, reinstallation has stopped the issue, Both ram sticks are back in and things seem to be on the working side. Thank you, Ubuysa.