[SOLVED] KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe+4f5cae repeatedly.

B

Bearded Blunder

Active member
Joined
Apr 1, 2022
Posts
28
Having just installed Windows I get this repeatedly every few minutes, blue screen view wasn't much help this time, I hope running your tool in safe mode with networking is acceptable, the system won't stay up long enough for it to complete when booted normally.

I've run memtest (48 hours, 46 passes, no errors), the system was fine on Windows 7, & will run 10 either in safe mode, or in a VM under Linux, but I'm having trouble getting it to run natively. I suspect a driver issue, & can't guarantee 10 will be able to be run natively at all, the manufacturer quit building laptops while Windows 7 was current, so no official support for anything later.

System Manufacturer: General Dynamics / Itronix
Form Factor: Laptop
Model: GD8200
OS: Windows 10 21H2 x64 (Retail - Media Creation Tool)
System age ~10 years
Age of OS install less than 10 days (Fresh clean install)
CPU: Core i7 2655LE 2.20GHz
RAM 4GB (The original OEM stuff, sorry brand unknown)
Video: Intel HD Graphics 3000 (integrated)
Driver Verifier: Disabled? (Whatever the Windows default is :p )
Security software: No additional software, just the built-in Windows stuff.
No disk image tools.
No overclocking.
 

Attachments

Last edited:
This certainly appears to be a driver issue due to how consistent the bugchecks are: all Stop 0x1Es with divide by error exception being thrown. The only third-party driver which appears to be present at the time of the crash is your Intel Wi-Fi driver, I would suggest checking for a newer update using the Intel Support Assistant if it is able to run within Safe Mode with Networking.

Rich (BB code): 
0: kd> lmvm NETwew01
Browse full module list
start             end                 module name
fffff800`60e40000 fffff800`61188000   NETwew01   (pdb symbols)          C:\ProgramData\dbg\sym\NETwew01.pdb\AF7F37A6FBFD41B8B488A2BEDDD8BC441\NETwew01.pdb
    Loaded symbol image file: NETwew01.sys
    Mapped memory image file: C:\ProgramData\dbg\sym\NETwew01.sys\54AC0B07348000\NETwew01.sys
    Image path: \SystemRoot\System32\drivers\NETwew01.sys
    Image name: NETwew01.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jan  6 16:19:19 2015 (54AC0B07)
    CheckSum:         003332C4
    ImageSize:        00348000
    File version:     15.16.0.2
    Product version:  1.0.1.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Intel Corporation
        ProductName:      Intel® Wireless WiFi Link Adapter
        InternalName:     .sys
        OriginalFilename: .sys
        FileVersion:      15.16.0.2
        FileDescription:  Intel® Wireless WiFi Link Driver
        LegalCopyright:   Copyright © Intel Corporation 2011
        Comments:         NDIS630_MINIPORT
 
15.16.0.2 was already an alternate driver for that which Windows offered as an optional update, the newest I can locate for that hardware id is 15.18.0.1
Which is what Windows installed to begin with.
The machine behaviour is unchanged with 15.18.0.1 version.

Sometimes I detest Windows 10.. it's doing a typical Windows 10 thing & being "Helpful" every time I uninstall the device it puts it back...
Go to the hardware tab on advanced properties for the machine & set it NOT to automatically install drivers..
Windows 10 ignores the setting & puts it back every time you uninstall it...
Even with the darned thing also disabled in BIOS.
Damn you Microsoft, if I uninstall something I want it uninstalled & to STAY uninstalled (same for the stupid games they keep pushing).

So much for the "simple" test of trying with the device/driver not installed.

I'm starting to think the only way I'll nail down 100% if that's the culprit or not is to dismantle the laptop, physically remove the wireless card, it & reinstall Windows (again).
If that does cure it, it'll be getting a used Broadcom (or other non-Intel) mini-pcie card in place of the existing one from evilbay or somewhere & side-step the issue.

I really wish Windows would actually respect my wishes & run with the stupid thing uninstalled to confirm it, I'd actually rather not pull the laptop to bits without confirmation I need to first, it might prove a pointless exercise & there's always risk of breakage pulling laptops to bits.

I'm going to try with it disabled, it's not nearly as good a test as uninstall & reboot to make sure it's unloaded would have been, but I'd prefer not to get the screwdrivers out just yet.
 
OK, round two.

With the WiFi card (and associated driver) removed, I'm still getting BSODs though at longer intervals, & sometimes the machine just locks up instead.

At least it stayed up long enough to have the file collection script complete when booted normally though this time.
 

Attachments

Both of the crashes are both Stop 0x1Es again with the divide by zero exception. It seems to only crash when the power state of the processor is changed.

Rich (BB code): 
1: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffff9301`4f4d2158 fffff805`1caf5cae     nt!KeBugCheckEx
01 ffff9301`4f4d2160 fffff805`1ca004e2     nt!HvlpVtlCallExceptionHandler+0x22
02 ffff9301`4f4d21a0 fffff805`1c8e6f97     nt!RtlpExecuteHandlerForException+0x12
03 ffff9301`4f4d21d0 fffff805`1c8e5b96     nt!RtlDispatchException+0x297
04 ffff9301`4f4d28f0 fffff805`1c9f84b2     nt!KiDispatchException+0x186
05 ffff9301`4f4d2fb0 fffff805`1c9f8480     nt!KxExceptionDispatchOnExceptionStack+0x12
06 ffff8a01`34e30678 fffff805`1ca096a5     nt!KiExceptionDispatchOnExceptionStackContinue
07 ffff8a01`34e30680 fffff805`1ca0230a     nt!KiExceptionDispatch+0x125
08 ffff8a01`34e30860 fffff805`1c923376     nt!KiDivideErrorFault+0x30a << Crash here!
09 ffff8a01`34e309f0 fffff805`1c92319e     nt!PpmPerfSelectProcessorState+0x1a6 << Change power state of processor
0a ffff8a01`34e30b10 fffff805`1c81f5c0     nt!PpmPerfSelectProcessorStates+0x5e
0b ffff8a01`34e30b40 fffff805`1c89a40e     nt!PpmCheckRun+0x40
0c ffff8a01`34e30bb0 fffff805`1c8996f4     nt!KiExecuteAllDpcs+0x30e
0d ffff8a01`34e30d20 fffff805`1c9fe665     nt!KiRetireDpcList+0x1f4
0e ffff8a01`34e30fb0 fffff805`1c9fe450     nt!KxRetireDpcList+0x5
0f ffff8a01`37a8b490 fffff805`1c9fdb1e     nt!KiDispatchInterruptContinue
10 ffff8a01`37a8b4c0 00000000`00000000     nt!KiDpcInterrupt+0x2ee << Software interrupt issued

I did notice that HeavyLoad appears to have been running during both crashes. It looks like it's some processor performance testing software from Jam Software? Does the system only crash while this software is running?
 
HeavyLoad is pretty much what you describe it as, I tend to use it as a quick & dirty stress test.
Without it running mostly the machine locks up solid & has to be hard reset, which doesn't create dumps, but is every bit as inconvenient.

If this were a desktop system I'd look into possibly disabling the processor changing power state (I'd need to search how to do that) based off what you've said, but that's er.. "less than optimal" on a laptop.
 
Bearded Blunder said:
Without it running mostly the machine locks up solid & has to be hard reset, which doesn't create dumps, but is every bit as inconvenient.
Click to expand...
Since you've removed the Intel network driver, I wonder what the system will behave like without running HeavyLoad?

Bearded Blunder said:
If this were a desktop system I'd look into possibly disabling the processor changing power state (I'd need to search how to do that) based off what you've said, but that's er.. "less than optimal" on a laptop.
Click to expand...
There should be an configuration option under the ACPI settings of your BIOS.
 
x BlueRobot said:
Since you've removed the Intel network driver, I wonder what the system will behave like without running HeavyLoad?
Click to expand...
It freezes randomly, clock stops, mouse freezes, won't recognise any input, not control alt delete nothing.. reset power is the only fix.. that can happen literally any time from pre-login.. to after several hours sitting idle at the desktop. It's usually sooner rather than later if you actually try doing anything on there though. Last time it managed to do so in a manner which also brought down my entire (wired) network.

I'll look at what ACPI settings the manufacturer deigned to expose, you know how laptops are, they love hiding any and all settings they think a user won't have reason to set, citing simplification.. though I actually think it's to reduce support calls resulting from misconfigurations.
 
Last edited:
Update: the BSODs don't go away without running HeavyLoad it appears after all, couple of new minidumps.

There are no BIOS settings for ACPI exposed, nor anything I could find in any of the menus regarding processor speed or power.

Would there possibly be any more or extra useful info if I were to enable Driver Verifier?
 

Attachments

OK, collection with Driver Verifier enabled per those instructions.
A cursory glance with BlueScreenView leads me to think you're correct about it not finding anything new.
It hardly locks up, but BSODs more often. Safe Mode to get the app to complete again. Dumps created booting normally.

The question is what next? Unless you have any other suggestions I'm leaning toward the conclusion that this particular hardware is incompatible with Windows 10, at least running directly. Regardless that it's comfortably powerful enough.


I know it will run Linux (dual booted for ages with 7). I know it'll run Windows 10 in VirtualBox, at least in pre-activated trial state, that was stable as you like, Windows 7 or Linux host OS.

Puts me in a potentially expensive spot for activation though, the hardware has legit licences for 7 (OEM / refurbisher), and for 10 (digital, from upgrading briefly when 10 came out, then back down to 7 owing to the BSODs). The key from the 7 COA isn't going to activate in VirtualBox (or I strongly doubt it), & the digital licence for 10 isn't going to see it as the same machine & activate either.

Trying to avoid the expense of a new retail licence to run 10 on a machine that's already licenced to run 10, without me resorting to dodgy methods ... They're not exactly bargain basement (at least not from legitimate sources, & I want to finance dodgy sources even less than I want to use hackery).

Maybe if it comes to it the nice person at Microsoft on the activation phone line might be sympathetic, one instance of Windows on a machine already licenced for 1 instance isn't trying to cheat them.. & it's not my fault I seem to need a hypervisor for it to run properly. I also don't want to be stuck running 7 as the main OS on there because of the security implications.

I'd like to take the chance to thank you for your help so far, and any other that you offer, most routine things on a computer I can sort out, but this level is outside my skillset.
 

Attachments

What is connected via USB ports?

Were / are smart cards being used during the BSOD?


The log files are loaded with these errors: WudfUsbccidDriver and your smart card or reader may not be functioning correctly


Please remove smart cards and hardware connected via USB ports.

If the computer becomes stable comment into this thread.

If BSOD continue despite the removal of the smart card and USB devices comment into this thread.



Monitor the computer using Reliability Monitor:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using



Post results for steps 2 - 5 in this link:

Windows Update Forum Posting Instructions



Consider looking up WudfUSBccidDriver troubleshooting.




Code: 
Event[79]:
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2022-04-06T04:05:39.2220000Z
  Event ID: 11
  Task: Driver
  Level: Error
  Opcode: Ioctl
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-D9G5U5T
  Description: 
A Request has returned failure.
MsgType: 0x80
ICCStatus: 0x1
CmdStatus: 0x1
Error: 0xFE
SW1: 0x0
SW2: 0x0


Code: 
Event[83]:
  Log Name: System
  Source: WudfUsbccidDriver
  Date: 2022-04-06T04:05:39.0290000Z
  Event ID: 11
  Task: Driver
  Level: Error
  Opcode: Ioctl
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-D9G5U5T
  Description:
A Request has returned failure.
MsgType: 0x80
ICCStatus: 0x1
CmdStatus: 0x1
Error: 0xFE
SW1: 0x0
SW2: 0x0




Code: 
Event[3181]:
  Log Name: System
  Source: Microsoft-Windows-Smartcard-Server
  Date: 2022-04-02T13:45:07.4040000Z
  Event ID: 610
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-D9G5U5T
  Description:
Smart Card Reader 'Generic EMV Smartcard Reader 0' rejected IOCTL POWER: The smart card is not responding to a reset.  If this error persists, your smart card or reader may not be functioning correctly.

Command Header: 01 00 00 00



Code: 
Event[3172]:
  Log Name: System
  Source: Microsoft-Windows-Smartcard-Server
  Date: 2022-04-02T13:45:07.6540000Z
  Event ID: 610
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-D9G5U5T
  Description:
Smart Card Reader 'Generic EMV Smartcard Reader 0' rejected IOCTL POWER: The smart card is not responding to a reset.  If this error persists, your smart card or reader may not be functioning correctly.

Command Header: 01 00 00 00
 
zbook said:
What is connected via USB ports?
Click to expand...
Externally, a wireless keyboard & mouse, for pure convenience, I can disconnect them, experience tells me it won't make a scrap of difference, but I'll do so anyway since you asked... Also non-disconnectable built-in stuff like I believe the touch screen, card reader, etc., show up as USB devices. Nothing obvious I can do about those being connected.

I'm afraid I can't remove any smart card, since I don't and never have owned one. I'm consequently unable to say if the reader does or doesn't work, or even if it ever has under other operating systems.

I'm completely unsurprised that a (non-present) smart card would fail to respond to a request Windows decided to send to an empty reader though.
I'm far less surprised by Windows sending such a request apparently without any check to see if there was actually a card in there first.. because Microsoft.

WudfUsbccidDriver.dll is one of the driver files listed for the Smartcard reader in Device Manager. Quite how to troubleshoot with no card or way to test the reader I'm unsure.
I suppose I could try disabling the reader in device manager? Unlike the WiFi card, I can't physically remove it.


zbook said:
Post results for steps 2 - 5 in this link:
Click to expand...
I hope running them in safe mode will do, no way that system is staying up long enough for any except possibly 5 to complete when booted normally especially with DriverVerifier active.

2) SFC: did not find any integrity violations.

3) DISM: The operation completed successfully.

4) SFCFix: Found something to do, also unsurprising since I had two bugchecks (BSOD) before starting this right after WU got to 100% on some update, ended up at recovery options, & went to safe-mode with the update presumably incomplete.
I'm guessing whatever SFCFix tries to do after it runs DISM is something that doesn't work in Safe Mode, because once that ran again.. successfully, again, SFCFix then sat, apparently doing nothing, and after waiting way longer than the estimated scan/fix time first, looking at Task Manager & Resmon, showed it using 0% CPU, the system as a whole idling at 1% CPU, & minimal disk activity.
Side note. If the tool doesn't work in Safe Mode, perhaps that should be stated, or better yet the tool could check the system isn't in Safe Mode & put up an error message if it is.
Sorry I can't give you the log from that, since none was produced. I left it sitting quite literally hours.
I did see the word error flash by, but the message was there for a split-second only, & since there's no back-scroll, I couldn't go back & look at what it said.

5) CBS.zip attached as requested, I don't envy you, looking at CBS logs is no fun, at least, not in a simple text editor.

I'll disable verifier & give SFCFix a few goes booted normally.. If it completes I'll post the output, but don't hold your breath, I've severe doubts I'll stay booted long enough for it to finish even with verifier disabled again.
 

Attachments

Well several BSODs after removing the externally plugged in USB device, along with disabling the SmartCard reader in device manager, I can confidently say.. that made no difference at all.
 
I'm quite certain that this is a compatibility issue between the BIOS and Windows 10. All of the bugchecks (including with Driver Verifier enabled) are consistently Stop 0x1E with the exact same exception being thrown each time. Do you have the latest BIOS update? I know they officially only supported Windows 7, I'm just wondering if you haven't got the latest version, wherever it make any difference. This increasingly doesn't appear to be a software related issue.
 
Finding if i have the latest BIOS is proving harder to determine than I thought it'd be.
The support site www.gd-itronix.com no longer exists.. playing with the wayback machine shows they passed the support & driver/bios downloads to www.flextronicssupport.com which it appears also no longer exists.. & in neither case did the wayback machine capture enough details for me to find it & make a version comparison at this point.

Which leaves looking at third party sites.. who're all linking back to those disappeared ones... so I can't even seem to download the flash utility & unpack it to look at dates...

I actually don't think it is.. the difficulty is actually finding it & it's flash utility at all..
Reference here: Itronix Corp GD8200 - Geekbench Browser suggests there's a Ver.110 & the the BIOS itself is showing 108

Searching is turning up places claiming to have the 109 or 110 flash utility.. but they're all turning out just to be dead links pointing back to the disappeared support sites.
 
Ok found what appears to be (after extracting with 7zip) the correct flash utility & image for v110 on a site/domain in Poland.
Given BIOS flashing is one of those potentially bricking operations, the system is unstable, & the utility is designed for XP/7 I think I'm going to install an earlier OS before I try flashing it.

Will report back if it helped in due course, I see a couple of Windows installs in my near future.
 
BIOS updated, it has made a difference, in that the lockups have gone away, unfortunately the bugchecks remain.

With many thanks for the help, and since I do have other options to run a supported OS, I think it's time to call it on this one. It's not even like this is a mass-market laptop where lots of users would potentially gain from spending time & effort digging deep into it. These ruggedized units were always a bit of a niche product.

For ongoing use from now Debian Security are pretty good when it comes to keeping the stable branch patched, and for my Windows needs, Win 10 will run inside VirtualBox, I might have preferred the other way around or dual boot, but that's certainly a very workable setup. I don't think it's worth taking more of your attention from people you can help to pursue "perfection" at this point.
 

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

Back
Top