[SOLVED] Mini PC Crashes

Jeff Drew

Jeff Drew

Contributor
Joined
Jan 22, 2023
Posts
64
Location
Switzerland
Hi Everyone,
I have a mini PC that has been crashing. At first, I thought it was overheating, so I vacuumed it out and logged the core temps. It sometimes hits 100C, but it is between 50 and 70 at the time of crashing, so I don't think that is the issue. I have ordered a new power supply because it is cheap and quick to obtain. I ran the Microsoft memory diagnostics and came up empty. I have run DSIM and sfc, but still no joy. I have attached the files. Do you see anything?
thanks,
j
 

Attachments

Just to be clear - the grills on the outside of the mini pc were coated with dust. It is that dust and the grills themselves that I vacuumed.
 
DxDiagx86 Errors: Dealing with microsoft edge update
Event Name: crashpad_log
MicrosoftEdgeUpdate.exe
P2: 1.3.195.45
P3: OnLogonLaunchError
P4: 0x80070002

Error code 0x80070002 is a common Windows update error that typically indicates a problem with the Windows Update service or a corrupt system file.
 
So, yes, I know not to vacuum the insides. I vacuumed the computer cover after I removed it. I, unfortunately, used shorthand, which sidetracked the conversation. I am not sure what you are suggesting. Did you see any Edge update errors in the logs? I don't see 0x80070002 in the event log. I received the new power supply today, and we are trying it out. Perhaps that was the issue.
 
aha. ok, I will take a look at the updates and see if I can clean that up. So far, the new power supply has been keeping it up and running. Previously it was crashing multiple times a day.
 
The power supply didn't do it. I have now replaced the memory. I can't find any issues with the updates. Running memory diagnostics and burn in tests now.
 
The two dumps suggest to me that bad RAM may well be the cause here. Since you have two 16GB sticks the best way to test is to remove one stick and run on just the one for a few days, or until you get another BSOD. Then swap sticks and run on just the other stick for a few days, or until you get another BSOD. Check with your manual that a single stick is in the correct slot. If it BSODs on each stick on their own then it's probably not RAM and we'll need to look elsewhere.

If you cannot (or don't want to) remove RAM sticks then test your RAM with Memtest86...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
 
I installed new RAM and ran the memtest86. No errors. The computer still spontaneously reboots. I did the reset function from settings. The computer still reboots. Any ideas? It does not seem to be overheating. I am tempted to wipe and start over, but if I can fix it I prefer that. Any ideas?
 
Is it just restarting now or are these restarts BSODs? Re-run the Sysnative data collection app and upload the new output if you're not sure.
 
I ran the collection again. I checked with CrystalDiskInfo and it reads good 94%. I am not sure why it isn't 100%. I also scanned with Samsung Magician. I don't know if the restarts are crashes or BSODs because I haven't seen one. I walk away and come back to a login screen, so I know it rebooted. So far it has been up about 17 hours without a crash.
 

Attachments

System Information > Problem Devices: Microsoft PS/2 Mouse ACPI\PNP0F03\0 This device is not present, is not working properly, or does not have all its drivers installed.

DxDiagx86 > Windows Error Reporting:

2 problems regarding >

Event Name: ShellViewReentered
Response: Not available
Cab Id: 0

Problem signature:
P1: Explorer.EXE
P2: 10.0.26100.3624
P3: 5d22432e

..................

Several problems regarding >

Fault bucket , type 0
Event Name: crashpad_log
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.195.49
P3: OnLogonLaunchError
P4: 0x80070002
+++ WER4 +++:
Fault bucket 1587898500741606410, type 5
Event Name: crashpad_log
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.195.49
P3: OnLogonLaunchError
P4: 0x80070002

Problems regarding >

+++ WER5 +++:
Fault bucket 129337386790, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: ClientOperator.exe
P2: 10.0.14393.0
P3: 57d64ab9
P4: Sku
P5: 10.0.14393.0
P6: 57d64a8b
P7: 289
P8: 0
P9: SQYDCDGCT31QXHYYTMNX42YGPAU1NWTJ
2 problems regarding >

+++ WER9 +++:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: cmw_srv.exe
P2: 12.10.2.12281
P3: 81dc6fe5
P4: System.ServiceProcess
P5: 4.8.9032.0
P6: 6250aaf4
P7: 74
P8: 62
P9: System.InvalidOperationException

and

+++ WER9 +++:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: cmw_srv.exe
P2: 12.10.2.12281
P3: 81dc6fe5
P4: System.ServiceProcess
P5: 4.8.9032.0
P6: 6250aaf4
P7: 74
P8: 62
P9: System.InvalidOperationException
 
Have you done a reinstall since Wednesday? If not, do you run a disk cleanup tool? I ask because in the latest Sysnative upload the two dups we were seeing are gone and the logs only go back as far as the afternoon of 24th (Thursday) when you did a reboot. Much of the problem determination data that we were seeing has gone. Whatever you did, please don't do that again, we need to keep your logs and dumps etc. intact throughout the process of solving this issue.

I'm going to get you to stop Windows auto-restarting when a problem occurs, that way you should be able to see any error messages that may be on the screen.
  1. In the Run command box enter the command sysdm.cpl
  2. In the dialog that opens, click the Advanced tab
  3. Click the bottom Settings button (in Start-up and Recovery)
  4. Make sure that the Write an event to the system log box IS checked
  5. Make sure that the Automatically restart box IS NOT checked
  6. Make sure that the Write debugging information is set to Automatic memory dump
  7. Make sure that the Dump file location is %SystemRoot%\MEMORY.DMP
  8. Make sure that the Overwrite any existing file box IS checked
  9. Make sure that the Disable automatic deletion of memory dumps when disk space is low box IS checked
  10. Then click the OK button
This will stop Windows auto-restarting when a system failure occurs and it will ensure that the correct dumps are written and not auto-deleted. In addition, disable any disk cleanup tools that you may have.

If you get another failure whilst you're away from the PC take a good quality photo of whatever display is on the screen. You can then manually reboot.
 
This is helpful. cmw_srv.exe is part of Hotspot shield, a VPN provider I use. I uninstalled it. Let's see what happens. The mouse is missing because this is my wife's machine and I am working on it at my desk, so her mouse is on her laptop. I am not sure what the clientoperator issues were. It is part of Windows Essentials backup code. I had a firewall issue, so maybe that was it?
 
I was typing when your message came in, ubuysa. Yes, I did a re-install between the 2 dumps. I made the changes you requested. As I stated above, I uninstalled Hotspot Shield, so other than the updates you asked for that is the only change.
 

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

Back
Top