J50C-4 Max - WHEA 'fatal hardware error' & driver issue

T

tonemapped

Member
Hello,

1. WHEA-Logger Event 1 'fatal hardware error'
I have two questions/issues and will send an email to the support address separately. So far, the Minix seems like a good unit, however, I received this error in Event Viewer:
whea-fatal-hw-error.PNG
It's a standard Event 1 WHEA-Logger, either indicating a hardware defect (which would be unlucky as it's a new unit) or a driver error causing this issue. Any solution/thoughts on this?

[SOLVED] (see below for resolution)
2. WAN Miniport IP driver 'yellow triangle'
Upon setting up Windows 10, this is how it's looked in event viewer since. The J50C-4 Max was on 2H20 and updating it to 21H1 makes no difference. The official drive package (1.2GB) contains drivers from 2018 and this doesn't appear to have been updated, which is disappointing.
wan-error.PNG
 
Last edited:
@tonemapped are you using a VPN?

What causes the ‘Windows is still setting up the class configuration for this device. (Code 56)’ Error on Windows 10?
Well, after going through several user reports, from what we have salvaged, the error is often due to the following factors —

  • Third-party VPN. In most of the cases, the error is due to the third-party VPN installed on your system. The VPN conflicts with your network adapter which causes the issue to pop up.

https://appuals.com/fix-windows-is-still-setting-up-the-class-configuration-for-this-device/
 
Villa said:
@tonemapped are you using a VPN?

What causes the ‘Windows is still setting up the class configuration for this device. (Code 56)’ Error on Windows 10?
Well, after going through several user reports, from what we have salvaged, the error is often due to the following factors —

  • Third-party VPN. In most of the cases, the error is due to the third-party VPN installed on your system. The VPN conflicts with your network adapter which causes the issue to pop up.

https://appuals.com/fix-windows-is-still-setting-up-the-class-configuration-for-this-device/
Click to expand...

I did some research and found the same, but I don't use a VPN and never have (I use RDP occasionally, but from a different workstation). This driver issue come as new, before the RAM upgrade and just after setting up Windows for first boot. It was there from the factory.
 
Last edited:
tonemapped said:
I did some research and found the same, but I don't use a VPN and never have (I use RDP occasionally, but from a different workstation). This driver issue come as new, before the RAM upgrade and just after setting up Windows for first boot. It was there from the factory.
Click to expand...
Fixed: this was a factory misconfiguration (as shown in Event Viewer from the manufacturing setup). Deleting the device and scanning for new hardware resolved this issue.
 
You must log in or register to reply here.
Back
Top