PC keeps shutting down ERROR 41

Megahertz · 30 May 2020

Use Open Hardware Monitor.
It's a portable, don't need to be installed. Extract and run.
It will show current ,Max and min temperatures, fans etc.
You can set to run on startup.

skeetz · 30 May 2020

HD Full Scan is going to take forever to complete. It's been running
for 40 mins and this is as far as I have gotten. I did run a quick scan.

Seatools has been running for over 25 mins and shows no progress.

I'm going to bypass these scans and go on to the other things
you have posted.

As far as the unknown device. I think that might have been
for a USB stick I had plugged in. I deleted the device and
unplugged the stick.

zbook · 30 May 2020

Please run the scans over night and into the next day as needed.

skeetz · 30 May 2020

OK Here are the other test results. I lost track of everything
I was supposed to run besides those full scans.
I need help on how to attach the dmp file. Do I save it as
a desktop shortcut? Then what do I do after that?
Please let me know if I am missing anything else.

- - - Updated - - -

OK I will run both full scans later tonight. Can I run them both at the same time?

zbook · 30 May 2020

Update the progress with steps#27 and #28.

The memory dumps: see if you can be right click > save to downloads folder > right click as needed to zip > post share links using one drive, drop box, or google drive

NickosD · 30 May 2020

btw temps looks okay. Checking the cpu cooler at the shop is not necessary.

skeetz · 30 May 2020

I was just going to ask if all these tests show any reason why it will automatically
keep shutting down.

Completed SeaTools scan

27) Open the Dell website > support > enter service tag > view drivers >
install Intel GPU drivers and re-install Nvidia GPU drivers COMPLETED

Not sure what I need to do here

28) Read these links on Windows driver verifier:
a) learn how to use the Windows Recovery Environment (RE)
commands: reset and bootmode to turn off the tool
b) do not use the tool until it is communicated in the thread

Thanks

zbook · 30 May 2020

When available please post a share link for the memory dump.

Make a new restore point:
Create System Restore Point in Windows 10

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) start with the 3 customized test settings in the Ten Forums link
e) increase the customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

skeetz · 30 May 2020

Here is the link for the memory.dmp file

Restore points are something I make when doing tests
like these, so I have created quite a few.

I have installed and uninstalled drivers for this pc
is there a reason I need to do all this again?

Is there any indication that this is a driver problem?

I am really confused on all the other things you want me to run.
I think my brain is a bit overloaded running all these tests.
I am going to go have dinner and spend some time with my
family. I need to take a break now.

If we are not any closer to finding out the problem after
all these tests, I think I should just take it into the shop
and have them look at it.

I do appreciate all your expertise and lengthy time you
have spent on assisting me with this.

Thank you very much!

zbook · 30 May 2020

BSOD were identified in the logs.

Most BSOD are caused by misbehaving drivers.
Other causes of BSOD are malfunctioning hardware and BIOS problems.

In this thread unexpected shutdowns and restarts were reported without BSOD.
Again BSOD were found in the logs.
Running third party software you were able to identify BSOD.
Dump files were collected and you just uploaded a memory dump file.

The more the dump files the more debugging that can be performed.
The debugging is done on the collected files to find misbehaving drivers or malfunctioning hardware.

Windows driver verifier is designed to stress drivers and cause misbehaving drivers to crash.
If dump files are created they can be debugged.
The misbehaving driver(s) is(are) uninstalled or uninstalled and reinstalled.
Then the tool is restarted to find the next misbehaving driver.