How can I make Windows 7 x64 to reboot automatically after a BSOD?
There is a well-known "Automatically restart" option in the system properties -> Advanced -> Startup and recovery, but it seems it affects boot time only. If BSOD occurs after successful boot, the system hangs with a blue screen.
That's not the expected behavior. The automatic restart should apply in all cases, not just during boot. There are some corner cases where it won't work but these are rare and relate to a very specific scenarios. Better proceed this with MS support.
Related
Recently I build a C# .NET Windows Service, which actually does exactly what it should do. So, no problem there.
BUT... When I start my PC again after a SHUT DOWN (Windows button), and I look immediately in the Services list then I notice every time that my service shows as "running" already.
(Only for this purpose I set my service to "delayed start", which gives me a minute or two)
All other delayed start services in the list are still NOT running at that moment, as it should be.
Obviously my service does NOT work at all in this situation and is completely useless.
However, when I do a Windows RESTART (Windows button), everything works normal and fine.
Even when I shut down the PC by pressing the hardware power button for a few seconds, after a power-up everything works just fine.
I tried the same service on my laptop with exactly the same result.
This latest is not the only service I made. I tried to build several different services, unfortunately all with the same result.
The service is based on this tutorial:
https://learn.microsoft.com/en-us/dotnet/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer
On both my PC and my laptop I use the latest update of Windows10 and the latest update of Visual Studio 2022.
Anyone maybe noticed a similar behavior?
Any help would be greatly appreciated.
Cheers!
Peter
P.S. I start to believe this behavior is due to a Windows bug (thanks Bill), since I also noticed that WakeOnLAN after SHUT DOWN (Windows button) randomly reboots the PC several times at night.
However when I shut down the PC with the hardware power button it keeps quiet.
But that is another issue and doesn't belong here.
By enterprise policy, we have to run Cylance protect antivirus on our workstations. It cannot be suspended or uninstalled.
I can start VisualVM, but when I try to connect to a process, a message is displayed by Cylance protect that the process of VisualVM was stopped because it was "recognized as a threat".
Edit: I see VisualVM's start page where the Java processes, including VisualVM and Eclipse, are displayed. As soon as I select a process and try any action (monitor, profile, etc.) Cylance pops up and hard terminates VisualVM. The Java processes keep running.
The tech team thinks this comes from VisualVM trying to access another process' memory.
My system: Java 11, Eclipse 2022-12, Windows 11.
We tested for a short time with Cylance disabled and then the profiling worked.
(I needed some time to talk my tech team into that so this does not seem to be a practicable solution.)
I don't expect this to change with the Java or Eclipse version. Was already the same with Java 8 and / or elder Eclipse versions.
Has anybody the same constellation and knows how to configure a rule in Cylance that profiling with VisualVM is possible?
-How to handle reboot and power off scenarios while installation like how to roll back the installation if reboot and shutdown happens through install4j.
-How to change name of resource folder
As of install4j 8, there is no functionality to perform rollbacks on power-loss or process crashes.
When I start up my Linux VM (Xubuntu 14.04 aka Trusty) on VMWare Player (v6.0.3), my Windows host (Windows 7 pro x64) makes an IRQL_NOT_LESS_OR_EQUAL blue screen of death.
The fact is that BSOD occurs juste after selecting an entry in my guest's GRUB screen.
How to avoid that?
The problem occurs because somewhere in VMWare drivers, an Interruption Request is made to satisfy guest shared hardware (USB, NAT, ...). The workaround is to uncheck "Connect at power on" checkbox on every device listed in "Virtual Machine Settings > Hardware" menu. You will then be able to boot.
Once the guest is started you can individually connect the pieces of hardware you want.
With my HP laptop, if I add the CD/DVD drive to my Ubuntu VM then this happens every time. So like the doctor says, "Does it hurt when you do that? then don't do it." ;) It'd be nice if VMware Player didn't bomb out for something straightforward like that, but such is life. You can always turn off that hardware before you run the VM.
My general experience as well is that it's better to add/remove hardware to the VM with the VM off. Remember that these are things which you usually wouldn't be able to change with a PC running, so it's not unreasonable for driver authors to assume that what they have on startup will not change.
BTW, don't forget that you'll need to manually delete all the lock files in the VM directory as well. VMware Player does a less-than-perfect job of cleaning up after crashes.
I have been using Eclipse on Mac OS X from home over a VPN to develop GWT and perl code in a local workspace for my employer. Recently a repeatable and severe lockup began occurring whenever I tried to edit Debug (or Run) launch configurations. I got the spinning beachball of death (SBOD) and, if I waited long enough (10-15 minutes) it would eventually stop and I could at least close the dialog.
I tried numerous things until a coworker suggested trying it with VPN turned off. To my surprise (and somewhat delight) it began behaving normally in the above scenario. I have been using Eclipse in this manner for about a year with no problems so naturally I am racking my brain trying to think of recent changes to VPN and/or to my split tunnel script (euphemistically called 'multihome') that could account for this abnormal behavior. This lockup occurs with or without the split tunnel.
I should also point out that the "initializing Java tooling" progress status ALWAYS occurs when starting eclipse and takes about a minute to complete with VPN connection. Normal (<2 seconds) without.
So, I'm starting to learn how to use wireshark and possibly will look into using packetlogger as well in an attempt to find out more about this strange issue.
Anyone have a clue as to what might be causing this?
This is a hard one to answer. Short answer is "I don't know".
However, I did find out that, due to the recently updated JVM, done as part of the Mac OS X update, Eclipse IDE lost its ability to find the src.jar file for the JRE. As a result, it appears that Eclipse, in various places in the code, searched for this file and when not found attempted to find it via the network. When VPN was turned on, perhaps this exacerbated the problem.
This was solved by fixing the Installed JRE configuration of Eclipse (see JDK on OSX 10.7 Lion).