[SOLVED] Windows 2016 server: random crashes/restarts FIX: Uninstalled MBAM

B

Butters76

Member
Joined
May 19, 2020
Posts
23
We have a Dell PowerEdge R440 that started doing random crash/restarts in february. Then it was fine for 2 months and started happening again late april.

I am unable to figure out what the problem is, but think it is a software problem, since Dell Pre-boot system assessment pass all tests.

Event viewer doesn't give me anything worth wild. I get the event 41, kernel power. But that just tell me that the system shut down unexpectedly.
Dell server manager and dell IDRAC logs OEM software event at each crash. but its unable to tell me anything more about the OEM software event. And it logs "a runtime critical stop occured".

When I run chkdsk all drives are reported fine.
When I run SFC /scannow it does not find any intergrity violations
When I run dism /checkhealth it says repairable
When I run dism /restorehealth it says not enough storage to complete operation.
When i run dism /startcomponentcleanup it says can't find specified file.


I guess my first step will be to get the last two commands to succeed, even though I don't think thats the reason for the crashes, since SFC says everything is fine.
I will try to increase the IRPStackSize to solve the /restorehealth problem. But im not sure its going to work. And I can't restart the server during business hours.

All help here are appreciated.
 
Hi!

Please do the following:


Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
CBS.log . there were lots of errors.
Again the dism failed With error code 14: not enough Storage is available to Complete this command.
 

Attachments

I see some errors:


FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4338822;KB4525236 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 

Attachments

Nope, you will have to fully uninstall it because of the drivers.

This fix will require a reboot, so please run it after hours and reboot afterwards when requested. It would be great if you could remove Malwarebytes then as well.

Afterwards, run DISM again and attach CBS.log.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

BTW: I had a pending restart when I ran the /dism restorehealth due to an Windows update I installed this morning. Maybe I should restart and do a new dism and give you the cbs.log again before running the fix you made?
 
softwaremaniac said:
Just restart before the fix, then run the fix and it will ask for a reboot again.

Then run DISM and attach CBS.log.
Click to expand...

Oh yeah, you're good.

Dism finished successfully. here are the 2 logs you asked for.

Thank you so much for Your help. You rule!
MBAM is removed, allthough I'd really like to have it there.
 

Attachments

Should I just reinstall MBAM? And see if it crashes again then?
Also noticed Windows search use lots of cpu during business hours. Windows search (services) and Microsoft Windows search indexer (process) can use 50% cpu between them at times. On 2x xeon 4110 cpus. They take half of all 16 cores now and then.
Have reindexed, and then its fine for 10 minutes before it starts using cpu like crazy again.
Could both this and the crashes be due to some corrupt user file(s)?
 
softwaremaniac said:
You can try reinstalling. If there was a corrupt file SFC would have caught it.
Click to expand...

I'm thinking a user file, not a systemfile. So when either MBAM or Serarchindexer use the file it can crash, or that the indexer get stuck on that file and use lots of cpu because f it. Is that a possibility?
 

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

Back
Top