Dell Laptop Windows 10 Blue Screen of Death CRITICAL_PROCESS_DIED when restarting - crash

Dell Laptop was upgraded to Windows 10 from Windows 8.1. Recently been having an issue with Blue Screen of Death (BSOD) crash at random times.
Only error information is:
CRITICAL_PROCESS_DIED
:(
with a very obnoxious :(.
Dell Warranty expired three months ago.
After checking forums and attempting to reinstall drivers decided the best thing to do is just restore the laptop to factory state. The problem is that during the built in restore to factory process the computer must restart. During restart a BSOD crash will occur every time. Even attempting a regular restart will result in a BSOD, "CRITICAL_PROCESS_DIED" error. So the goal now is just to restore the PC to factory settings, but the impasse is the required restart for this or a driver update is the required restart will always result in a BSOD "CRITICAL_PROCESS_DIED."
Is there a way to restore to factory settings without having to restart? If not, then what are some alternative paths to just getting a clean restore?
Thanks.

Windows 10 offers many Recover Options such as the Reset you PC options which includes the following sub-options:
Keep my files
Reinstalls Windows 10 and keeps your personal files.
Removes apps and drivers you installed.
Removes changes you made to settings.
Removes any apps your PC manufacturer installed. (If your PC came with Windows 10, apps from your PC manufacturer will be reinstalled.)
Remove everything
Reinstalls Windows 10 and removes all your personal files.
Removes apps and drivers you installed.
Removes changes you made to settings.
Removes any apps your PC manufacturer installed. (If your PC came with Windows 10, apps from your PC manufacturer will be reinstalled.)
If you're planning to donate, recycle, or sell your PC, use this option and choose to fully clean the drive. This might take an hour or two, but it makes it harder for other people to recover files you've removed.
Restore factory settings
Reinstalls the version of Windows that your PC came with (either Windows 8 or Windows 8.1) and removes your personal files.
Removes apps and drivers you installed.
Removes changes you made to settings.
Reinstalls any apps your PC manufacturer installed on your PC.
This option isn't available on all PCs.
I would suggest starting with the "Keep my files" option and then moving on to the "Remove Everything" option if the first doesn't work; one of these two should solve this.

Related

Developer unlocked windows phone gets locked for no reason

I have 2 windows phone devices on my account that I use for testing. But they get locked for no reason.. I have to unlock it almost everyday. It even happened twice in one day. I haven't figured out what is causing this...
Is anyone experiencing this same issue?
**** UPDATE MESSAGE ****
This is the latest bizzare update on this bug... I've pasted my post in Microsoft Forum below:
I'm experiencing a very strange bug that I don't know if it is on the Windows Phone SDK or in Visual Studio.
I have 2 WP 8.1 devices to test an app that I'm developing. This was the sequence of events that led to this lock down:
Suddenly one phone that I used the most started to ask, almost everyday, to develop unlock the device...
Then the other phone started to do the same.
Now everytime I make a release version and run it targeting Device in Visual Studio, VS 2013 crashes... And the phone gets developer locked again.
Then I found a workaround that was to use the Application Deployment tool from the SDK only to test the release version. (Debug version it deployed without any problems on the device)
Today I forgot the manually deploy the XAP and clicked run in VS. VS crashed... Then I tried to deploy using the SDK tool it said that phone was locked... I unlocked it and clicked on the Deploy button again. Then the error: The maximum number of developer applications on this phone has been reached appeared.
I've uninstalled the app from the Windows Phone device manually and tried again and the same error occured.
I tried the other test device and had to register it again and got the same error.
Now I can't deploy any release version and I don't know how to fix this issue.
Do you know how can I fix all this Visual Studio bugs? I can't seem to find anyone else with the same problem as I'm having.
No, i have three unlocked devices in my account but one wp8.1 and other two win10, if you can upgrade your wp8.1 devices to windows 10 do that using that app because windows has inbuilt feature to developer unlock device, so your device won't get locked again automatically.
if you don't want to upgrade to and need assistance go to this link
this link requires you to login with your outlook account or may require you to login with your windows developer account.
and extra information if don't have windows developer account and want to publish your app go to this link from your windows mobile device or directly search for "Dev Share" App in windows store.

Use of Hyper Visor to run the Windows Phone Emulator

I am really new to Windows Phone 8 App development. I would be grateful to you if you can answer my question. I have a machine with Intel(R) Core(TM) i3 processor and when checked I found out that my virtualization setting enabled.
I installed Windows Pro 8.1 in to my machine and then it indicates that my Hyper Visor is default switched off and I had to run it. But when I run it after making some of the changes by restarting the machine, suddenly for some unknown reason it undoes every change made finally leaving the machine with no Hyper Visor running.
I come across the same process when I am to run the Windows Phone emulator to test Windows Phone 8 Apps.
I hope my issue is clear to you all, can someone help me to fix this issue or tell me the exact reason behind this?
I would look at my Windows Event log and see if you perhaps there's a problem with Hyper-V being incompatible with a driver or something like that. It may be failing to reboot and the doing a system restore to get the machine back to a bootable state (by rolling back Hyper-V). I've had problems with Hyper-V and my HP laptop's blue tooth drivers:
Here's the thread where I found out about that:
HP Bluetooth / Hyper-V woes
Updating the driver to the newest version on HP's site fixed my computer for a while, but then I had problems with Windows Update hosing my machine with an update to the Bluetooth driver.
I seem to have fixed it for good by going to RA Link's website and downloading a version of the driver that's newer than the one on HP's website. I'm not at my personal computer right now, but if you'd like I can see if I can find the driver version that seems to have fixed my Bluetooth/hyper-v problems for good.
-Eric

Processing affects current directory of Arduino environment

I have my processing code in dev/processing and my Arduino code put itself in Documents/Arduino.
However, whenever I get into one environment, it changes the most recent directory for the other because Arduino is written in processing.
Is there any quick way to disconnect the two environments so that they don't use the same location for "most recent directory?" I don't know whether the mechanism is a file, a registry entry or what, but I'm on Windows 8.1
I am using both Arduino IDE as well as Processing 2.1.2 in Windows 7 environment. It doesn't change the directory.
Since you are using Windows 8.1 (which is recently released), you may face very weird problems as those softwares are not tested on those OS. You will find errors for even other softwares that are designed before Windows 8.

Powerbuilder 10 Windows 8 compatibility

Does anyone know if Powerbuilder 10 is compatible with Windows 8 (Both the IDE and the runtime module)?
It seems like 11.5 is officially supported, but I couldn't find any info on PB 10's compatibility on Windows 8.
If it isn't, any tips on the migration process from 10->Further version? (Anything particular we have to watch out for?)
You should have no problem with running PB10 applications on Windows 8, appart perhaps not being not fully compliant with Win8 standards (concerning the placement of application data files, access rights on files, and so on mostly related to UAC file virtualization).
Neither you should have big problems with running the IDE, but maybe some minor issues (I think about an issue on the retrieval argument editor on PB11.5 that could also address PB10).
This is one of those things where you just have to try it yourself. The number of PowerBuilder developers with Windows 8 is likely very small.
I am supposed to be getting a Surface Pro 2 when they come out Oct 22nd which will run Windows 8.1. Hopefully there won't be any issues.
I am not sure about PB10 but I have used PB 10.5 in Win8 with no problem.
We have serious issues with running a PB10 application on Windows 8 computers.
Application runs fine until user enters text in datawindow fields, the application "stopped working". The problem is that it happens randomly, 10 fields can be entered without a problem but at the next field the "stopped working" pops up en the application is closed the next time it might happen after entering 2 fields.
The same application runs already for years on many computers unders XP, Vista, Windows 7 without any issue.
Until now we still have no clou what is causing it. Also we have no idea where to start searching.
The application is developed andf deployed under XP.
Next week we are going to setup a development environment under Windows, hopefully this will give us some more light on the issue.
Two things you need to realize:
PB10 was built (and support development stopped) before before Win8 was conceived, so obviously Sybase couldn't do anything in PB to help with Win8 compatibility. You're relying on MS's ability to maintain a backward compatible environment. IME, they do a pretty good job (better than my experience upgrading in the Unix world, but I'd imagine YMMV), but it's never perfect.
PowerBuilder is powerful enough to allow you to build an application that will break under any operating system. PB10 may have been supported on XP, but I guarantee you that I could have written something that violated an XP rule, or corrupted memory, or whatever, and would have been broken under XP. (I've seen memory corruptions that didn't manifest themselves until after an OS upgrade or some other change; so "broken" may not even manifest symptoms yet.) Is that Sybase's fault? I don't think so. They're the rope manufacturer; if you hang yourself....
Bottom line is what's already been said: no matter what the manufacturer or anyone else says, the only answer worth anything is the results of your own testing. My "Hello World" app may run in Win8 just fine, but your app that taps into the TCP/IP stack, leverage protected mode calls, sending printing language codes directly to the point-of-sale bar code printer, etc....
Good luck,
Terry.

Jelly-Bean updated Galaxy Tab 2 7" can't connect to Windows 8

I've just updated my Galaxy Tab 2 7" to OS v4.1.1 (Jelly Bean). Since that I can't connect to my device (from my Windows 8 PC, via USB) anymore.
Most relevant to me is the fact that I can't even debug my Android apps using the tablet (which is actually the reason why I bought it). Eclipse does show it among the adb devices, but in an offline status.
The Android SDK is updated. I've tried to force the install of the drivers via the android_winusb.inf located in the\android-sdk-windows\extras\google\usb_driver folder, but it doesn't seem to carry the right pieces of information. Tampering the file by manually adding 'em seems to conflict with the along-coming .cat files.
I've also tried by installing Kies, but even that piece of software can't connect to the device.
What do you suggest? Thanks in advance.
Magically, a new OTA update has come "from above" right to my device just a couple of minutes ago. That fixed the whole thing (no action made on the PC side).
Looking at the "about device" data sheet, Android version is still 4.1.1.
I haven't tracked the previous kernel version nor build number, so I can't see if and how they've changed; but I can write 'em down now, just in the case it may matter for someone else to check against:
Kernel version
3.0.31 - 523998
Build number
JRO03C.P3110XXCLK7