Tower Plus EBT2250 crashes, new

Screen turn off after 10 min

Sleep after 10 min

Get latest Windows updates ASAP: OFF

Notify me when a restart is required to finish updating : Was OFF, I turned it ON.

Update history shows some update activity that MIGHT have been the cause of at least one of the reboots.

MANY thanks for your suggestions. I'll keep an eye out.

it has happened to me at least 4 times and i have no idea why.

Most likely what others have said. More than likely Windows Update doing an update and you might have missed it was going to reboot or do NOT have it set to show you.

This setting in Windows Setting SHOULD be on:

That will put a dialog box on the top of the right side of the Taskbar alerting you that a reboot will take place in a short period of time.... that notification is off, it would proceed to do the reboot. In that Dialog box you can DELAY the reboot, and it shrinks to an icon on the Systray with a red dot on it if you choose to do it later... you can open that icon and boot from there, do it manually, or just shutdown, MS Update will do its part and power off, and the next time you power on, it will complete the update (and may reboot one or more times as well).

To 'verify' the 'problem' was caused by MS Update, in the Windows Settings for Update main page is a bar to look at the Update History. Note the time of the reboots and see is it was installing something at that time to be sure it was.

I have the same issue. I'm just sitting at my computer (EBT2250 I got in July), the screen goes black because it's rebooting. This is long after any windows updates, sleep settings, or anything else. I can be typing a document or surfing the web, and it just shuts down (and restarts). This issue is not solved...sorry.

Go into the system properties, advanced tab and under startup and recovery, uncheck the automatic restart.  The next time the system encounters an error, it should write a crash file.  Use something like Who Crashed (Resplendence Software, the free version will do the job) to parse the crash file so you can see what's causing the issue.

How to Disable Automatic Restart in Windows 11: A Step-by-Step Guide

Thank you for that. I'll be working on this and will post results if/when it happens. Hopefully good ones, and soon.

@me9798​ 

There is a GOOD chance a DUMP file was created...

How to find one if it is there:

OPEN a COMMAND PROMPT.

Make sure it is on C: at the root. If it shows C:\ you'll be OK, but it might also show "C:\Windows\System32>C:\Windows\System32>" as well. In that case, just enter "cd \" and you'll be back at the C: root. Now enter "dir *.dmp /s /p"

If you do find any, and you probably will, look at the TIMESTAMPS for the files... one that matches closely the time that it happened is probably it.

More than likely it will be a Device Driver, with the Video one a high probability.

You might also want to run in a Adminstrator CMD prompt these commands:

======================

these are the commands, you have to enter line by line.

Open Start, type: CMD

Right click CMD

Click Run as administrator

Type in at the prompt OR Copy and Paste these one at a time : (Hit enter after each)

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

Also run the System File Checker utility:

Open Start, type: CMD

Right click CMD

Click Run as administrator

At the Command Prompt, type: sfc /SCANNOW

This will check for any integrity violations

Restart your system

======================

Since you probably have an RTX4060 card, have you applied any NEW driver for it? One Dell posted or one from Nvidia? Some recent drivers for that card have been causing some problems. 

I have the 3050 card, but I did (stupidly) install Nvidia's version of the driver which I later uninstalled using Display Driver Uninstaller in safe mode, and then reinstalling Dell's proprietary Nvidia drivers with Windows Update paused. But a day later, I got the reboot. Next, I'll be looking into your suggestions. Thank you.

@me9798​ 

From my XPS8940 experience, and working with Dell Support, it was not 'stupid' to do that. 

From what I learned Dell does NOT build a special driver. My RTX2060 is also made by MSI. MSI's site doesn't post card drivers. They tell you to use Nvidia's Site.

Dell DOES test occasional Nvidia drivers and if 'OK', they post those. Only then, will they 'Support' the system, otherwise if you installed a non-posted video driver, they will instruct you to use the Dell posted one and test again.

I had a 'booting' problem where my desktop blanked out right after appearing on boot for a few seconds.. Dell driver being used, was told to try the Nvidia latest, didn't help... 'playing around' after Dell replaced my video card and then the motherboard after that with no help, I had to wait for a higher level of support to contact me... I used DDU to remove all vestiges of the Dell video driver and installed the latest Nvidia again. Problem solved.

Later, when a new Dell BIOS dropped in 2020, I and other Nvidia users experienced lock-ups/freezes of our PC... Dell couldn't 'repeat' the problem, and many of us tried different things... it took months, new BIOS, new Nvidia drivers, maybe for at least 6 months... and many people had different solutions. For me, it was the Nvidia Control Panel. Had to set the Power settings in the 3D Settings to Max. Power. FIXED... but some new driver installs will set that back to the DEFAULT setting. If I forget to check after a driver install, I will still have the lock-up happen it seems... quick check, power at DEFAULT, and set it back to Max Power, problem solved.

You 'might' be interested in scanning this Nvidia driver forum web page, https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/574380/geforce-grd-58129-feedback-thread-released-91025/. and it is people reporting problems with the latest Nvidia Driver (good for all cards). It is version 581.29, and almost all card model's have had problems. Last suggested driver that was known to be good was V366.45. I had used that one for a long time... but now, I am on the latest one released on Sept. 10th and I've had no problems. The web page IS for that release, and I recall some RTX 30 series users have had problems.

In that forum page, you will see things like this:

===============================

===============================

Although for a 3070, it generally could be a problem for any 30 series card... however, most of the problems since the V580 series of the driver are for 40 and 50 series cards.

If the .DMP file (my experience with the RTX2060 was NO .DMP file was created) doesn't exist, I'd go to the Nvidia site and get the older driver and test, or at least an older driver version.

Might want to check the Power setting in the Control Panel as well... Max. Power is OK for a desktop as there is no battery to drain and see if that helps (just a suggestion based on my experience).

@ispalten​ below is my latest crashdump as analyzed by Copilot (it does mention nvidia among other things), in case your curious. I will also run DISM and SFC as you recommend:

Thanks for the full dump output — this is a CLR FailFast triggered by coreclr.dll, specifically at EEPolicy::HandleFatalError. Here's a breakdown of what you're seeing and what it likely means:

🧠 Root Cause Summary

• Exception Code: 0x80131623
  This is a .NET FailFast code, meaning the runtime encountered a fatal condition and forcibly terminated the process to avoid corruption.

• Failure Bucket:
  CLR_FAILFAST_80131623_coreclr.dll!EEPolicy::HandleFatalError
  Indicates the failure originated in the .NET Core runtime's policy handler — typically due to an unhandled exception, corrupted state, or a critical violation.

• Process Name: Copilot.exe
  This was the crashing process, likely a managed .NET Core app.

• Stack Trace Highlights:

  coreclr!EEPolicy::HandleFatalError
  coreclr!Environment_FailFast
  System_Private_CoreLib
  

  This shows a direct call to Environment.FailFast() — either explicitly in code or triggered by a runtime panic (e.g., corrupted heap, invalid thread state, or security violation).

🔍 Key Clues

• Repeated GetThreadStoreData FAILED 80131c49
  This suggests the runtime couldn’t retrieve thread store data — possibly due to a corrupted thread context or invalid state during JIT execution.

• "Failed to request MethodData, not in JIT code range"
  Indicates the crash occurred outside of JIT-compiled code, possibly in native interop or during a transition between managed and unmanaged code.

• Unverified NVIDIA modules (nvwgf2umx.dll, nvldumdx.dll, etc.)
  These warnings aren’t directly causal but could hint at GPU-related hooks or overlays (e.g., GeForce Experience, ShadowPlay) interfering with managed code execution.

🛠️ Diagnostic Path

🧩 Possible Triggers

• A corrupted object passed to a native method
• A race condition during app startup (note: crash occurred ~14s after process start)
• A failed interop call or invalid P/Invoke signature
• A security violation or AppDomain unload mishap

@ispalten​ Interesting and I might be jumping the gun on all this stuff. I might use DDU to uninstall the Dell driver and try the latest driver from Nvidia (since it came a day after my black screen/reboot)...not sure yet. I might just wait a bit since I don't get a random reboot every day. Thanks again for all the suggestions!

@me9798​ 

That looks complicated to me?

On one hand, it sort of implied that CoPilot crashed? But it appears to be because an Nvidia Driver didn't work well with it?

Now was the Crash Dump a *.DMP file that was near the time the PC rebooted or later? Like after you ran CoPilot?

That file, a .DMP can be hard to read? I think I had to install the Windows Debugger and used it to view the file?

I found this link, https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file which was probably what I had to do years ago?

Still, to me it sort of indicates CoPilot had a problem, more than Nvidia was the problem?

@ispalten​ when I re-read the part of your post saying that the latest Nvidia driver posted on 9/10 seems OK, I decided to, remove the Dell driver in safe mode with DDU and reinstall the latest Dell driver (esp. since you mentioned Dell just verifies the drivers, doesn't write/modify them, so it's more of a certification process). So I just did that about 2 hrs ago, but I can definitely say the computer responds much faster. I also removed/reinstalled the PhysX component in DDU, which for some reason is unchecked as a default. Now, only time will tell what will really happen.

Thanks for all the help/suggestions, I really appreciate it, and certainly don't want to box this thing back up and send it in!!

@me9798​ 

There is another Nvidia Utility program out there that might be of interest to you? NV CLEAN INSTALL (https://www.techpowerup.com/nvcleanstall/).  An Nvidia driver release does install a LOT of other stuff. This program will allow you to pick and choose what parts you want to install, from the driver alone,  some minimal parts, or even the whole set. It also gives you information about the components to be installed. Check it out. I have it installed, and it alerts me to new drivers and allows me to bypass it or delay installing if I wish.