Random Restart of PC
-
This is impossible to reproduce as it's completely random. All I am sure of is that it has happened at least three times while editing a forum post in Vivaldi. I have never seen it happen while using any other program, only when using Vivaldi. I have done the obvious like checking for loose power cables. Windows updates were applied several hours earlier, and I have since restarted my PC to apply them. (VB-22159) Random PC Restart While Editing
-
Are there any entries in the Windows Event Logs that seem to correspond to the restarts and that might provide better definition of what occurred?
-
Is very rare that an user level program triggers a reset or a BSOD.
A browser can, indirectly, if there are underlying problems to VGA drivers. But still hardly the browser itself is the problem
Faulty RAM, heat (dirty heatsinks, dried silicon paste…), messed FS and so on are more likely culprits.
-
Similar thing happened to ma about year ago with one of my PCs in my work.
I was getting totally random BSODs + restarts after opening many tabs in Vivaldi / Firefox / Opera. Frequency was between one restart per week up to 6 BSODs per day… it was driving me crazy... :pinch:Problem happened only when RAM usage was high / very high (for FF the high risk zone started above 1,5 GB per process)
So I thought that it's a memory problem and swapped RAM between PCs... and same story again...
And once I found some info on the internet that this particular error code can be something about drivers...I have updated graphics driver and... BINGO! :woohoo:
Since this moment it is not a problem for this PC to achieve uptime > 1 monthI have inherited this PC from other co-worker and I never had idea to update drivers
My OS was 32-bit and my grapgic card was some ancient nVidia 8400 GS -
Are there any entries in the Windows Event Logs that seem to correspond to the restarts and that might provide better definition of what occurred?
I have saved the selected events that occurred yesterday from about 20:00 until the end of the day,.
I have checked for Display Adaptor updates, and already have the latest drivers.
-
Are you running win10 insider preview? I installed it yesteday and got 1 restart just like that today.
-
Are there any entries in the Windows Event Logs that seem to correspond to the restarts and that might provide better definition of what occurred?
I have saved the selected events that occurred yesterday from about 20:00 until the end of the day,.
I have checked for Display Adaptor updates, and already have the latest drivers.
Start checking your HW temperatures, using speedfan, coretemp or alike.
If you have a notebook and its radiator was never cleaned, almost surely you have a "carpet" of dust behind it
If your PC is a desktop is straight forward to remove the CPU fan and check the heatsink.
If your VGA card is a discrete one check it as well
If you never did that and your pc is more than one year old you should really do that, no matter if it will fix your actual problem or not.
Then isn't said that the latest drivers are the better ones, usually that's true, but usually != always
Another check can be done with some utilities meant to overclock your VGA, just use them to do the opposite, underclock your video card and check if the problem is gone…
-
Are there any entries in the Windows Event Logs that seem to correspond to the restarts and that might provide better definition of what occurred?
I have saved the selected events that occurred yesterday from about 20:00 until the end of the day,.
I have checked for Display Adaptor updates, and already have the latest drivers.
In your event logs, do you have any Windows System log events that are red-flagged as Errors around the time of the failures? Often there will be a cluster of these just prior to and including a crash point, and they may point toward the actual triggering element(s).
-
Often there will be a cluster of these just prior to and including a crash point, and they may point toward the actual triggering element(s).
That's surely true for BSODs (they are triggered by the OS to protect itself) but a sudden freeze usually doesn't give the time to write anything to the logs.
Anyway checking them doesn't hurt for sure.
-
My earlier reply didn't seem to get posted.
I am not using Windows insider. I don't know how to use the Event Viewer to find CPU temperatures.
I see red flag events at
[ol]- 20:20:55: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
- 20:20.24: The TeamViewer9 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
- 20:20.24: A timeout was reached (30000 milliseconds) while waiting for the TeamViewer9 service to connect.
- 20:19:58: A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 3
The details view of this entry contains further information. - 20:19:54: The NetTcpActivator service depends on the NetTcpPortSharing service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
- 20:19:58: A fatal hardware error has occurred.
- 20:19:29: Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
- 20:19:49: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff970c9739d8f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\101216-23953-01.dmp. Report Id: 1b835046-bf36-477b-b4ad-3326254fe973.
- 20:19:48: The previous system shutdown at 8:15:09 PM on 10/12/2016 was unexpected.
[/ol]
-
You're most likely dealing with a hardware-related issue. The most common cause of a Cache Hierarchy Error associated with a Machine Check Exception has to do with power regulation issues related to a failing/weak power supply or voltage regulation over-sensitivity on the motherboard/CPU, and it's also not uncommonly encountered by folks who overclock their CPU. However, there are other possible causes (drivers, BIOS, etc), and to quote an Intel document regarding machine check exceptions:
Diagnosing the cause of machine check exceptions can be challenging and time consuming. They are often difficult to reproduce in a timely manner. There are also many potential suspects involved, such as: platform design issues, the CPU operating out of specification, overloading of power supplies, software applications, and BIOS. This makes the debugging process extremely challenging.
In your case, I'm wondering if Vivaldi is loading your system in such a way that a marginal p/s voltage condition or low-voltage over-sensitivity in a component is triggering an error. As the Intel comment notes, and as you've observed, the cause of such an error can be very difficult to systematically isolate.
The APIC ID #3 denotes which local Advanced Programmable Interrupt Controller on the multiprocessor CPU directed and sent the error interrupt.
-
When his (random restarts) first happened to me, it was a bad power supply. Always happened when I was browsing. The next time it happened to me, it was a bad hard disk. That also threw BSODs often, but not always.
-
20:19:49: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff970c9739d8f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\101216-23953-01.dmp. Report Id: 1b835046-bf36-477b-b4ad-3326254fe973.
-