Windows 7 Shuts down unexpectedly.

Extra information about the problem

OS Version: 6_1_7600

Service Pack: 0_0

Bucket ID: 0x116_TdrBCR:2_Tdr:2_IMAGE_atikmdag.sys

Server information: b1a06975-c600-4c30-ab11-8a9ccb82f8fa

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.256.1

Thank you for using Microsoft Windows forum.

a) Did you make any changes to your computer recently for this issue to occur?

b) Does it shut down on start up?

c) Does it shut down unexpectedly when you open a particular application or a page?

This can also happen if RAM sticks are faulty.

.ExternalClass .ecxhmmessage P Here are few troubleshooting steps you could perform in order to resolve the issue

.ExternalClass .ecxhmmessage P .ExternalClass body.ecxhmmessage Try Booting the computer in Safe Mode

Here is how you do it :

1. Restart your computer and start pressing the F8 key on your keyboard. On a computer that is configured for booting to multiple operating systems, you can press the F8 key when the Boot Menu appears.

2. Select Safe Mode when the Windows Advanced Options menu appears, and then press ENTER

If it works with Safe Mode you may want to perform Clean Boot .

You can start Windows Vista or Windows 7 by using a minimal set of drivers and startup programs. This kind of startup is known as a «clean boot.» A clean boot helps eliminate software conflicts.

Note When you perform a clean boot, you may temporarily lose some functionality. When you start the computer as usual, the functionality returns. However, you may receive the original error message, or you may experience the original behavior.

Follow the below steps to put your computer in clean boot state:

Note If the computer is connected to a network, network policy settings may prevent you from following these steps. We strongly recommend that you do not use the System Configuration utility to modify the advanced boot options on the computer unless a Microsoft support engineer directs you to do this. Doing this may make the computer unusable.

1. Log on to the computer by using an account that has administrator rights.

2. Click Start button, type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration Utility.

If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

3. On the General tab, click Selective Startup , and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.)

4. On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.

Note Following this step lets Microsoft services continue to run. These services include Networking, Plug and Play, Event Logging, Error Reporting, and other services. If you disable these services, you may permanently delete all restore points. Do not do this if you want to use the System Restore utility together with existing restore points.

5. Click OK, and then click Restart.

Check the below link for more details on clean boot:

After you have finished troubleshooting, follow these steps to reset the computer to start as usual:

1. Click Start button, type msconfig.exe in the Start Search box, and then press ENTER.

If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

2. On the General tab , click the Normal Startup option, and then click OK.

3. When you are prompted to restart the computer, click Restart .

Also see : http://support.microsoft.com/default.aspx/kb/958233 on how to fix BlueScreen (STOP) errors that cause Windows 7/Vista to shut down or restart unexpectedly

Hope this helps
Azeez Nadeem — Azeez Nadeem

Terminated unexpectedly windows is shutting down

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I am getting this error continuously : The Windows log on process has unexpectedly terminated.

Server Configuration is

OS:Windows Server 2008 Standard Edition 64 Bit with Service pack 2

If anyone have solution pl. share

Answers

Thank you for posting in Windows Server Forum.

This error might be caused by one of the following conditions:
• System resources are inadequate or unavailable.
• The Windows registry is corrupted.
• A service failed to start.

Please check below article for solution to implement in this case.

• Marked as answer by Dharmesh S Microsoft employee Monday, June 9, 2014 8:25 AM

All replies

Thank you for posting in Windows Server Forum.

This error might be caused by one of the following conditions:
• System resources are inadequate or unavailable.
• The Windows registry is corrupted.
• A service failed to start.

Please check below article for solution to implement in this case.

• Marked as answer by Dharmesh S Microsoft employee Monday, June 9, 2014 8:25 AM

Thank you for posting in Windows Server Forum.

This error might be caused by one of the following conditions:
• System resources are inadequate or unavailable.
• The Windows registry is corrupted.
• A service failed to start.

Please check below article for solution to implement in this case.

This is of course not the solution to the problem. This is the real solution to the problem (in my case):

1. Uninstall following Windows Updates: KB2621440 and KB2667402. Restart computer
2. scannow /sfc + restart computer again. Tada!

Ошибка установки Windows 10 : Компьютер неожиданно перезагрузился или возникла непредвиденная ошибка. Решение.

В некоторых случаях во время чистой установке системы, выполнении обновления предыдущей версии Windows или при установке очередного билда (версии) Windows 10 может появиться ошибка « Компьютер неожиданно перезагрузился, или возникла непредвиденная ошибка. Невозможно продолжить установку Windows ». При нажатии кнопки OK, компьютер опять перезагружается, и снова появляеться окно с этой же ошибкой, и так по кругу… Что делать в таком случае, как продолжить установку Windows 10?

Данная проблема может появится после очередной перезагрузки системы в процессе одного из этапов установки (или обновления) ОС и выглядит следующим образом:

В русской версии Windows 10: Компьютер неожиданно перезагрузился, или возникла непредвиденная ошибка. Невозможно продолжить установку Windows. Чтобы установить Windows нажмите кнопку «ОК» для перезагрузки компьютера, а затем перезапустите установку.

В английской:The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click “OK” to restart the computer, and then restart the installation.

Как я уже говорил, при появлении этой ошибки не помогает ни нажатие на кнопку OK, ни повторный запуск установки системы – ошибка все равно зацикливается.

Чтобы исправить проблему нужно:

• Прямо на экране с ошибкой нажать сочетание клавиш Shift + F10

В открывшемся окне командной строки нужно запустить редактор реестра, выполнив команду regedit

• В окне редактора нужно перейти в раздел HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\ChildCompletion

В правой панели нужно найти параметр setup.exe . Скорее всего он равен 1. Меняем его значение на 3 и сохраняем изменение. Примечание. Тем самым мы принудительно указываем установщику Windows, что нужно перейти на следующую фазу установки системы.

• Нужно закрыть редактор реестра и перезагрузить компьютер коммандой: shutdown -r -t 0

После перезагрузки процесс установки/обновления Windows 10 должен нормально продолжиться.

Данная проблема характерна не только для Windows 10. Этот способ решения проблемы с прерванной установки системы одинаково эффективно работает и Windows 7 и Windows 8.1

Ошибка при установке Windows

Во время обновления Windows 10 до Creators Update, моргнул свет и отключился компьютер, после чего вышла ошибка:
The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click “OK” to restart the computer, and then restart the installation.

Дословно текст ошибки можно перевести так:
Компьютер неожиданно перезапускается или возникла непредвиденная ошибка. Невозможно продолжить установку Windows. Чтобы установить Windows, нажмите кнопку “ОК” для перезагрузки компьютера, а затем перезапустите установку.

В следствие чего машина ушла в циклическую перезагрузку и не стартовала. Для решения проблемы, можно поковырять реестр, предварительно сделав его копию, через “Файл”-“Экспорт”.

Замена значения в реестре

• после появления ошибки жмите Shift + F10 (если ноутбук, возможно дополнительно нужно нажать Fn), откроется командная строка;
• в командной строке введите “regedit” (без кавычек) и нажмите ввод, откроется редактор реестра;
• сделайте копию реестра;
• в редакторе реестра проходим по ветке HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\ChildCompletion;
• в правой части окна дважды кликните на setup.exe, значение 1 изменяем на 3;
• закрывайте редактор реестра, закрывайте командную строку, кликайте на кнопку “OK” в окне ошибки;
• после перезагрузки установка должна продолжиться.

Способ работает с Windows 7, 8 и 10. В комментариях пишите помог ли способ, если нет, попытаюсь помочь советом.

Авторизуясь, вы даете согласие на обработку персональных данных.

Windows shuts down my computer unexpectedly

Replies (24) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Does the same behavior happen in Safe Mode. If not, then do thorough scanning for malware.

If the same behavior happens in Safe Mode you probably have hardware failure.

MS-MVP — Elephant Boy Computers — Don’t Panic!

10 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have the same problem as above but with some differences. My computer shuts down unexpectedly only when the power cord is plugged in. It works fine when running on battery. However, such problem is not present while running the computer in safe mode with networking. I scanned my computer with Windows malicious software removal tool (full scan) and it reported no malware. Please help me with this.

97 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

If I were you, I would start a new thread/topic with only your information about your issue. This previous session may not have had a happy ending.

Please provide additional information about your system:

What is your system make and model?

What is your XP Version and Service Pack?

Describe your current antivirus and anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.

Does the afflicted system have a working CD/DVD drive?

Do you have a genuine bootable XP installation CD (this is not the same as any Recovery CDs that came with your system)?

If your system is overheating, XP will usually just crash with no warning. There will be no blue screen of death (BSOD), nothing in the Event Log, not too many clues. You will have to use the power button to restart and it may start up fine right away and run for a little while (since it has cooled off a bit) or sometime you may have to wait a little while for things to cool off enough for XP to restart.

It will help if you can determine what exactly it is you need to do to make it crash anytime you want. Then if you make any adjustments, you can apply your failure scenario to the system and see if it crashes again or not. That is the best way to be sure you have actually fixed the problem — that would be when your failure scenario doesn’t make it fail anymore.

Can you think of anything like that? Are you watching videos, playing a game, listening to music, using a particular program, etc. Is there anything that makes it fail every time?

You can look in the Event Log after a crash and see if there are any clues, but for overheating, you will probably not see any. Here is how to do that:

Look in the Event Viewer for clues around the time of the incident

Here is a method to post the specific information about individual events.

To see the Event Viewer logs, click Start, Settings, Control Panel, Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box enter:

Click OK to launch the Event Viewer.

The most interesting logs are usually the Application and System.

Some logs such as Security and Internet Explorer may be completely empty or have only a few items. The default settings for XP is not to log all that activity unless you need to troubleshoot some issue in those areas. If you enable the logging for them the logs fill up quickly and could negatively effect your system performance with all the extra (usually unnecessary) activity.

If you have Microsoft Office installed, it has its own logs and they may be empty or occasional boring activity or very little activity if there is no problem with your Office applications. This is normal.

Not every event is a problem, some are informational messages that things are working okay and some are warnings.

However, no event should defy reasonable explanation.

Each event is sorted by Date and Time. Errors will have red Xs, Warnings will have yellow !s. Information messages have white is. Not every Error or Warning event means there is a serious issue. Some are excusable at startup time when Windows is booting. Try to find just the events at the date and time around your problem.

If you double click an event, it will open a Properties window with more information. On the right are black up and down arrow buttons to scroll through the open events. The third button that looks like two pages on top of each other is used to copy the event details to your Windows clipboard.

When you find an interesting event that occurred around the time of your issue, click the third button under the up and down arrows to copy the details and then you can paste the details (right click, Paste or CTRL-V) the detail text back here for analysis. Remove any personal information from your information after pasting if you are compelled to do so.

If you paste an Event, it will look something like this boring system startup event:

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 7/14/2010
Time: 5:54:18 PM
User: Jose
Computer: Computer

Description:
The Remote Access Connection Manager service was successfully sent a start control.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

To get a fresh start on any Event Viewer log, you can choose to clear the log (backing up the log is offered), then reproduce your issue, then look at just the events around the time of your issue and troubleshoot the events that are happening when you have your issue.

XP is set up to automatically reboot on some system failures, so you need to disable that feature so if your system crashes in such a way, the Blue Screen of Death (BSOD) information will stay on the screen for you to see it.

You should also configure XP to create a small memory dump file for each BSOD.

If your system crashes later, the information you need will still be on the screen and then you can use the information in the memory dump files to figure out what the problem is and fix it.

Configure your system to not automatically restart on system failure (that is what it wants to do):

Right click My Computer, Properties, Advanced, Startup and Recovery Settings.

In the System failure section:

Put a check mark in the «Write an event to the system log» box

Put a check mark in the «Send an administrative alert» box

Uncheck the «Automatically restart» box

In the Write debugging information section, choose:

Small memory dump (64 KB)

Set the Small dump directory to:

Restart your computer.

Do, or do not. There is no try.

I decided to save up points for a new puppy instead of a pony!

2 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks for replying and sorry about not starting a new thread.

Laptop: Toshiba satellite pro L300. Processor: Intel core 2 Duo. The system has a cd/dvd drive and it’s working well.

Operating System: Windows XP Professional. Version : 2002. Service pack 3. I don’t have an XP installation CD. The OS was installed by the college authorities. College provided the laptop.

Antivirus: avast v.4.7 home edition.

The system is failing only when the power cord is plugged in and windows is running in normal mode. The failure can happen at any time, even when logging in. It does not fail when the power cord is plugged in and windows is running in «safe mode with networking». The system works fine when running on batteries and in whichever mode XP is running in. So, most of the time I run windows in «safe mode with networking».

Here are some errors and warnings from the application log: (I removed the name of the computer in the post and replaced with wherever necessary).

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 1/12/2011
Time: 8:53:16 AM
User: N/A
Computer: Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 52 54 57 52 54 49 43 WRTWRTIC
0008: 32 31 34 39 00 00 00 00 2149.
0010: 57 52 54 57 52 54 49 43 WRTWRTIC
0018: 32 31 31 31 00 00 00 00 2111.

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 1/12/2011
Time: 8:53:16 AM
User: N/A
Computer:
Description:
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 80070422 from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 1/11/2011
Time: 9:41:40 PM
User: N/A
Computer:
Description:
Faulting application explorer.exe, version 6.0.2900.5512, faulting module divxdec.ax, version 7.1.1.14, fault address 0x000b9290.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 78 70 ure exp
0018: 6c 6f 72 65 72 2e 65 78 lorer.ex
0020: 65 20 36 2e 30 2e 32 39 e 6.0.29
0028: 30 30 2e 35 35 31 32 20 00.5512
0030: 69 6e 20 64 69 76 78 64 in divxd
0038: 65 63 2e 61 78 20 37 2e ec.ax 7.
0040: 31 2e 31 2e 31 34 20 61 1.1.14 a
0048: 74 20 6f 66 66 73 65 74 t offset
0050: 20 30 30 30 62 39 32 39 000b929
0058: 30 0d 0a 0..

Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 1/11/2011
Time: 8:19:50 PM
User: N/A
Computer:
Description:
Hanging application vlc.exe, version 1.0.1.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 76 6c 63 2e 65 78 vlc.ex
0018: 65 20 31 2e 30 2e 31 2e e 1.0.1.
0020: 30 20 69 6e 20 68 75 6e 0 in hun
0028: 67 61 70 70 20 30 2e 30 gapp 0.0
0030: 2e 30 2e 30 20 61 74 20 .0.0 at
0038: 6f 66 66 73 65 74 20 30 offset 0
0040: 30 30 30 30 30 30 30 0000000

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 1/11/2011
Time: 2:39:15 PM
User: NT AUTHORITY\SYSTEM
Computer:
Description:
Windows saved user \User registry while an application or service was still using the registry during log off. The memory used by the user’s registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 1/10/2011
Time: 9:09:42 PM
User: N/A
Computer:
Description:
Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x05249290.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 78 70 ure exp
0018: 6c 6f 72 65 72 2e 65 78 lorer.ex
0020: 65 20 36 2e 30 2e 32 39 e 6.0.29
0028: 30 30 2e 35 35 31 32 20 00.5512
0030: 69 6e 20 75 6e 6b 6e 6f in unkno
0038: 77 6e 20 30 2e 30 2e 30 wn 0.0.0
0040: 2e 30 20 61 74 20 6f 66 .0 at of
0048: 66 73 65 74 20 30 35 32 fset 052
0050: 34 39 32 39 30 49290

Some errors and warnings from the system log

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 1/12/2011
Time: 1:38:22 PM
User: N/A
Computer:
Description:
The following boot-start or system-start driver(s) failed to load:
Aavmker4
Fips
intelppm
sptd

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: sptd
Event Category: None
Event ID: 4
Date: 1/12/2011
Time: 1:36:27 PM
User: N/A
Computer:
Description:
Driver detected an internal error in its data structures for .

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 52 00 . R.
0008: 00 00 00 00 04 00 04 c0 . À
0010: ef 00 00 00 00 00 00 00 ï.
0018: 00 00 00 00 00 00 00 00 .
0020: 00 00 00 00 00 00 00 00 .

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 1/12/2011
Time: 9:08:28 AM
User: N/A
Computer:
Description:
The following boot-start or system-start driver(s) failed to load:
Aavmker4
Fips
intelppm

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: USER32
Event Category: None
Event ID: 1073
Date: 1/11/2011
Time: 1:28:04 PM
User: NT AUTHORITY\SYSTEM
Computer:
Description:
The attempt to power off failed

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 .

After reading your post, I have disabled the «Automatic restart» option but still it’s restarting after system failure. Also, there was no BSOD. It simply restarts even after disabling automatic restart.

I am posting screen shot of my system failure settings.

Also, I am using portable laptop power scheme. I believed the problem started when I tampered with the power schemes. I changed my power scheme from portable laptop to max battery and then back to portable laptop. Also, I performed clean boot and found that no service was the culprit.