The Gaer

updated

6 years ago

TG

The Gaer

1 Rookie

13 Posts

0

2403

January 22nd, 2021 07:00

Optipex 5040 Intel Ethernet Connection keeps crashing.

Hi

I hope some one can help me.

The Intel Ethernet Connection keeps crashing, to get it back I have to disable and then re-enable the driver.

Some times I get a message " Windows has stopped this device because it has reported problems Code 43"

I have installed the latest driver version 12.18.9.10 from the Dell Support web site, but it is still happening about once or twice a day.

Any help would be much appreciated.

  • speedstep

    11 Legend

    46969 Posts

    1034

    0

    Posted January 22nd, 2021 07:00

    Full Error Message

    Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)

    Run the chkdsk /r /f  admin command-line command together on the disk that contains the registry hive files. This command helps verify that the area of the disk that contains the registry hive files is not involved in the problem.

    Cause

    The system hive has exceeded its maximum size and new devices cannot work until the size is reduced. The system hive is a permanent part of the registry associated with a set of files that contains information related to the configuration of the computer on which the operating system is installed. Configured items include applications, user preferences, devices, and so on. The problem might be specific devices that are no longer attached to the computer but are still listed in the system hive.

    Recommended Resolution

    Uninstall any hardware devices that you are no longer using.

    1. Set Device Manager to show devices that are no longer connected to the computer.

      • From Start, click Run.

      • In the Open box, type cmd. The Command Prompt window opens.

      • At the prompt, type the following command, and then press Enter: set devmgr_show_nonpresent_devices=1

    2. In Device Manager, click View, and then click Show hidden devices. You will now be able to see devices that are not connected to the computer.

    3. Select a non-present device. On the Driver tab, choose Uninstall.

    4. Repeat step 3 for any non-present devices that you are no longer using. Then restart your computer.

    5. Check the device Properties dialog box in Device Manager to see whether the error is resolved.

       

      The error that you’ve encountered can also be caused by files in the driver that are corrupted or missing.

      • Make sure that your computer has enough space for the update. The device requires at least 16 GB of free space to upgrade 29 GB for a 64-bit OS.
      •  
      • Run Windows Update a few times. Try to download and install any available updates in Windows Update. You can use the Windows Update Troubleshooter tool if just in case you’ll encounter an error.
      • Unplug extra hardware. If there are external storage devices and drives that are connected, unplug them so it won’t cause any conflicts with the update process.
      • Check Device Manager for driver errors. Type Device Manager in the Search box on the taskbar, then select it from the results. In the window that will pop up, try to look for any device with a yellow exclamation mark beside it (you may have to select each category to switch to the list of devices). Right-click the device name and select either Update Driver Software or Uninstall it to correct these errors.
      • Remove or disable third-party security software. Make sure to least disable the third-party antivirus software that’s installed on your computer. Then, check for updates again.
      • Repair hard drive errors. In the Search box on the taskbar, type command prompt and right-click on the result, then select Run as administrator. And, type chkdsk/f C: in the Command Prompt window and press Enter. This will repair your hard drive automatically and you’ll be asked to restart your device.
      • Restore and repair system files. Run the System File Checker tool. Follow these steps:
      1. Type Command Prompt in the Search box from Start.
      2. Right-click on it, then select Run as administrator.
      3. Enter DISM.exe /Online /Cleanup-image /Restorehealth (note the spaces before each "/").
      4. Enter sfc /scannow (note the space between "sfc" and "/").
      5. Once done, try to check if it resolved the concern.

       

  • The Gaer

    1 Rookie

    13 Posts

    1018

    0

    Posted January 22nd, 2021 10:00

    Thank you for your reply.

    The error message I am getting is Code 43 not Code 49.

    Are you saying run chkdsk/r /f  admin as the first step to eliminate a registry problem.

    Thank you

  • The Gaer

    1 Rookie

    13 Posts

    1008

    0

    Posted January 24th, 2021 10:00

    Hi

    Is it OK to run chkdsk/r /f  on an SSD hardrive.

    Thanks

     

  • The Gaer

    1 Rookie

    13 Posts

    982

    0

    Posted January 29th, 2021 02:00

    Hi Thank you for your help. I hadn't replied earlier as I thought I would test it for a few days. Thanks again.
  • The Gaer

    1 Rookie

    13 Posts

    980

    0

    Posted January 29th, 2021 03:00

    As soon as I said the problem had been fixed it crashed again. It hasn't done this for at least 4 days.

    Do you have any more ideas.

    Regards

  • speedstep

    11 Legend

    46969 Posts

    968

    0

    Posted January 29th, 2021 05:00

    error code 43 means that a device driver is either missing, corrupt

    you need a new hard drive and clean install of windows

  • The Gaer

    1 Rookie

    13 Posts

    961

    0

    Posted January 29th, 2021 08:00

    Hi

    When it first stated crashing I updated the network driver, so I have discounted that.

    I have replaced the old hard drive with a new SSD drive but I can't remember if it crashed with the old drive, I suppose I could swap it back. If it didn't then crash I still wouldn't know if it was the SSD drive or the operating system. 

    Is there a way of testing the SSD drive, it is Crucial MX500 which I bought in August this year, so still under warranty.

    Thanks

     

     

     

  • speedstep

    11 Legend

    46969 Posts

    936

    0

    Posted January 31st, 2021 09:00

    There are no soft fixes for physically bad , corrupted drives.

    SSD or HDD doesnt make a difference.

     

  • bradthetechnut

    9 Technologist

    9649 Posts

    40713 Points

    925

    1

    Posted January 31st, 2021 14:00

    One idea to check SSD:  Go into the F12 Boot Menu.  For some reason, that's where the diagnostic options are.

    If you run full diagnostics and not just quick, it'll take a few hours.  You might want to let it run overnight.

  • The Gaer

    1 Rookie

    13 Posts

    510

    0

    Posted February 2nd, 2021 09:00

    I have run all the diagnostics that you have recommended.

    sfc /scannow found corrupt files and repaired them. I have the CBS log but don’t understand it.

    I am not sure if the other diagnostic commands find problems and repair them without reporting them.

    I’ll let you know if this has solved the problem, but if it hasn’t I assume the next step would be to do a clean install of windows 10.