Faulting module name: KERNELBASE.dll

Anonymous
2024-02-05T20:23:13+00:00

This is a brand new Windows 11 Pro installation on a brand new machine that I built a couple weeks ago. Everything was working fine up until just a few days ago when my Logitech Gaming Software (lcore.exe) began crashing. Here's the event log:

Faulting application name: LCore.exe, version: 9.4.49.0, time stamp: 0x627cc454

Faulting module name: KERNELBASE.dll, version: 10.0.22621.3085, time stamp: 0x98257e11

Exception code: 0xc0000005

Fault offset: 0x0000000000026d9e

Faulting process id: 0x0x2E20

Faulting application start time: 0x0x1DA586A4572825E

Faulting application path: C:\Program Files\Logitech Gaming Software\LCore.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: e7582a89-0f94-40ef-8de0-e4d9e8fda493

Faulting package full name: 

Faulting package-relative application ID: 

I have done the following in an elevated command prompt:

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

sfc /scannow

None of those report any problems. I then tried:

regsvr32 kernelbase.dll

It says "The module 'kernelbase.dll' was loaded but the entry-point DllRegisterServer was not found"

I have uninstalled/reinstalled the software numerous times. It always works initially when Windows starts, but only for about a minute before it crashes again. I'll add that the create/modified timestamps on kernelbase.dll are ‎Wednesday, ‎January ‎31, ‎2024, ‏‎4:09:20 PM. That seems to correspond to the date that I started having this problem.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2024-02-27T18:08:24+00:00

    This is also affecting one our services.

    Faulting application name: svcServer.exe, version: 2.5.0.128, time stamp: 0x449938a3

    Faulting module name: KERNELBASE.dll, version: 10.0.17763.5458, time stamp: 0xbadca4ac

    Exception code: 0xe06d7363

    Fault offset: 0x00125e12

    Faulting process id: 0xb04

    Faulting application start time: 0x01da698dc7327572

    Faulting application path: C:\MICROS\ProfessionalServices\StoredValueCard\svcServer.exe

    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

    Report Id: 68b8274c-714c-4c55-94d8-bdff0da2b79b

    Faulting package full name: 

    Faulting package-relative application ID:

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-06T07:39:32+00:00

    Hi aaaa,

    Welcome to Microsoft Community.

    I'm Hahn and I'm here to help you with your concern.

    Based on the error message you provided, it seems that the Logitech Gaming Software (LCore.exe) is crashing due to a fault in the KERNELBASE.dll module. The file KernelBase.dll is a DLL (Dynamic Link Library) file stored in the system folder of Windows operating system. It is usually created automatically during the installation of the Windows operating system. The file KernelBase.dll contains a set of procedures and driver functions, so it is essential for the normal function of the Windows operating system.

    The error message "The module 'kernelbase.dll' was loaded but the entry-point DllRegisterServer was not found" typically indicates that you cannot manually register the kernelbase.dll file using the regsvr32 command. This is expected behavior for system DLLs like kernelbase.dll.

    Since kernelbase.dll is a critical system file, it's not meant to be registered or modified by users. The DllRegisterServer entry-point is not applicable to many system DLLs, and attempting to register them can lead to problems.

    Since you have already tried running DISM and SFC scans, and re-registering the KERNELBASE.dll module, I would suggest trying the following steps:

    1. Restore the KernelBase.dll file: You can fix this issue by restoring the KernelBase.dll file from a trustworthy source or you can copy the file KernelBase.dll from another trustworthy computer running the same version and edition of Windows operating system.
    2. Run the program compatibility troubleshooter:

    This issue may also be triggered by a poor written program. If your program crashes with the KernelBase.dll error when opening or closing a program, or just when a program is running, it’s time to run the program compatibility troubleshooter.

    The program compatibility troubleshooter can check whether that program is compatible for your current Windows operating system or not. Just follow the steps to run the program compatibility troubleshooter:

    1. Right click the shortcut of the problematic program on your desktop and select Properties.
    2. Click the Compatibility tab and click Run compatibility troubleshooter.
    3. Click Try recommended settings to test-run program using recommended compatibility settings. Follow the on screen instructions to see whether this troubleshooting option works or not.
    4. If it still doesn’t work, then run compatibility troubleshooter again and select the second option to choose compatibility settings based on problems you notice.
    5. If the problem persists, adjust the following settings manually and select OK when you’re done.
    • Compatibility mode: If your program is not designed for your current Windows system, the program may crash with the KernelBase.dll error. Click the drop-down list to select a previous version of Windows system to test run the program.
    • **Run this program as an administrator:**If the program is not given administrator privileges, it may not run properly and may even crash with the KernelBase.dll error. Try this setting to give the program the administrator privileges.

    If this fix works, your program won’t crash with the KernelBase.dll error.

    I hope this helps.  If there is anything not clear, please do not hesitate to let me know.

    Your Sincerely

    Hahn - MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-07-28T09:24:37+00:00

    I spent three days solving this problem and tested the following tips which worked

    1- Building the trust of game installation paths by antivirus by (Add or remove exclusions)

    2-add msfs in Allowed app firewall in windows

    3- Test disabling the antivirus

    4- Give admin access to the kernelbase.dll file (tutorial is on YouTube)*

    5- Disable xmp in bios, but first watch the tutorial on YouTube

    6- Don't rush and act calmly to think better :)

    7- There is no need to reinstall or fresh, first you should consider all the possibilities

    8- Remove and install game service and xbox service in Windows through PowerShell (YouTube)

    9- Important point** The Microsoft account that you log in to the game must be logged in to the Xbox Windows program...exactly the same account....I even logged in the same account in Windows itself...it worked for me

    10- Be sure to do the ninth item carefully

    11- Try to temporarily delete miscellaneous mods from the community folder

    12- Remove the graphics driver with the ddu program in safe mode and install the updated driver

    13- If you have already downloaded the packages and encountered this problem during the update, you can temporarily rename the packages folder and delete the game and reinstall it.... Note that we delete the game, not the packages that It is in the path of appdata

    14- You can delete all the files in the path below, except for the packages folder, because they will be created again when the game is run.

    C:\Users\username\AppData\Roaming\Microsoft Flight Simulator

    15- In the settings of the Windows region, select United State

    16 - In the language settings of the system, download the text and audio packages of the English language (YouTube).

    17-Use vpn or dns to log in if there is a problem

    18- Be sure to run Steam program and msfs game with run as admin mode

    19 I hope you are successful and if you solve the problem, teach others the tips (be kind)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-07-17T14:44:09+00:00

    Hi aaaa,

    Welcome to Microsoft Community.

    I'm Hahn and I'm here to help you with your concern.

    Based on the error message you provided, it seems that the Logitech Gaming Software (LCore.exe) is crashing due to a fault in the KERNELBASE.dll module. The file KernelBase.dll is a DLL (Dynamic Link Library) file stored in the system folder of Windows operating system. It is usually created automatically during the installation of the Windows operating system. The file KernelBase.dll contains a set of procedures and driver functions, so it is essential for the normal function of the Windows operating system.

    The error message "The module 'kernelbase.dll' was loaded but the entry-point DllRegisterServer was not found" typically indicates that you cannot manually register the kernelbase.dll file using the regsvr32 command. This is expected behavior for system DLLs like kernelbase.dll.

    Since kernelbase.dll is a critical system file, it's not meant to be registered or modified by users. The DllRegisterServer entry-point is not applicable to many system DLLs, and attempting to register them can lead to problems.

    Since you have already tried running DISM and SFC scans, and re-registering the KERNELBASE.dll module, I would suggest trying the following steps:

    1. Restore the KernelBase.dll file: You can fix this issue by restoring the KernelBase.dll file from a trustworthy source or you can copy the file KernelBase.dll from another trustworthy computer running the same version and edition of Windows operating system.
    2. Run the program compatibility troubleshooter:

    This issue may also be triggered by a poor written program. If your program crashes with the KernelBase.dll error when opening or closing a program, or just when a program is running, it’s time to run the program compatibility troubleshooter.

    The program compatibility troubleshooter can check whether that program is compatible for your current Windows operating system or not. Just follow the steps to run the program compatibility troubleshooter:

    1. Right click the shortcut of the problematic program on your desktop and select Properties.
    2. Click the Compatibility tab and click Run compatibility troubleshooter.
    3. Click Try recommended settings to test-run program using recommended compatibility settings. Follow the on screen instructions to see whether this troubleshooting option works or not.
    4. If it still doesn’t work, then run compatibility troubleshooter again and select the second option to choose compatibility settings based on problems you notice.
    5. If the problem persists, adjust the following settings manually and select OK when you’re done.
    • Compatibility mode: If your program is not designed for your current Windows system, the program may crash with the KernelBase.dll error. Click the drop-down list to select a previous version of Windows system to test run the program.
    • **Run this program as an administrator:**If the program is not given administrator privileges, it may not run properly and may even crash with the KernelBase.dll error. Try this setting to give the program the administrator privileges.

    If this fix works, your program won’t crash with the KernelBase.dll error.

    I hope this helps.  If there is anything not clear, please do not hesitate to let me know.

     

    Your Sincerely

    Hahn - MSFT | Microsoft Community Support Specialist

    HAHN, your instructions came in handy for me today.
    I had a similar issue where I could not get some software to work. It was consistently crashing after starting up.

    Here's what unravelled.
    I bought a Blackmagic Design ATEM MINI PRO Video Switcher for my YouTube channel live broadcast.
    Everything went well until I wanted to control the switcher remotely via Ethernet.
    I downloaded the latest version of the software which comes in 2 parts.
    One to do the initial hardware connection configuration and the other the Control Software.
    The latter was constantly crashing.

    The connections are the video switcher and a Windows 11 PC connected to a router/switch.

    I configured the router/switch and confirmed everything worked in order by pinging the IP addresses.
    All ok but the software kept crashing immediately after starting up.

    I spent hours troubleshooting network configuration with all possible settings.
    Finally opened the event viewer and saw the crash log.

    "Faulting application name: ATEM Software Control.exe, version: 0.0.0.0, time stamp: 0x66725b8f
    
    Faulting module name: KERNELBASE.dll, version: 10.0.22621.3155, time stamp: 0x8c2ee5db
    
    Exception code: 0xe06d7363
    
    Fault offset: 0x0000000000065b0c
    
    Faulting process id: 0x0x1260
    
    Faulting application start time: 0x0x1DAD83F12479E5D
    
    Faulting application path: C:\Program Files (x86)\Blackmagic Design\Blackmagic ATEM Switchers\ATEM Software Control\ATEM Software Control.exe
    
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    
    Report Id: 84457d63-d808-46fb-ad6d-8cc7f428c955
    
    Faulting package full name: 
    
    Faulting package-relative application ID: "
    

    As you can see it the similar issue with the KERNELBASE.dll

    Since the Blackmagic Design support assures their software is current and is compatible with Windows 11, it never crossed my mind of any incompatibility issues.
    Apprently it is so :)

    This is the first instance I had faced with an issue with BMD. Their products are robust and have little to no technical problems.

    The Compatibility helper set the version to Windows 8 which surprised me because this software update was released on 25 June 2024.

    Thank you for your esteem detailed guidance.

    Was this answer helpful?

    0 comments No comments