This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy.
Symptoms
When you restart the computer after a program that uses the InitiateSystemShutdownEx function shuts it down automatically, the following event may be logged to the System event log:
Event ID: 6008
Source: Event Log
Type: Error
Description:
The previous system shutdown at Time onDate was unexpected.
Cause
This problem may occur if both of the following conditions are true:
-
The computer is locked or is configured with a password-protected screensaver.
-
The shutdown operation is initiated automatically by a program that uses the InitiateSystemShutdownEx function with the force flag.
For example, you use the Remote Shutdown tool (Shutdown.exe) from the Microsoft Windows 2000 Resource Kit to force a shut down of the computer from a remote computer or you schedule a shutdown of the local computer by using Shutdown.exe in combination with the at command or Task Scheduler.
In this situation, the Event Log service is not notified about the shutdown event, and as a result, the shutdown operation is incorrectly considered by the Event Log service as an unexpected event.
Resolution
Hotfix information
A supported feature that modifies the default behavior of the product is available from Microsoft. However, this feature is intended to modify only the behavior that this article describes. Apply this feature only to systems that specifically require it.
If the feature is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the feature.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific feature. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the feature is available. If you do not see your language, it is because the feature is not available for that language.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Date Time Version Size File name
—————————————————————
15-Aug-2002 08:34 5.0.2195.5265 42,256 Basesrv.dll
15-Aug-2002 08:34 5.0.2195.5907 222,992 Gdi32.dll
15-Aug-2002 08:34 5.0.2195.6011 708,880 Kernel32.dll
15-Aug-2002 08:34 5.0.2195.4733 332,560 Msgina.dll
15-Aug-2002 08:34 5.0.2195.6000 379,664 User32.dll
15-Aug-2002 08:34 5.0.2195.5968 369,936 Userenv.dll
08-Aug-2002 15:23 5.0.2195.6003 1,642,416 Win32k.sys
15-Aug-2002 08:30 5.0.2195.6013 179,472 Winlogon.exe
15-Aug-2002 08:34 5.0.2195.5935 243,472 Winsrv.dll
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about how to use the Remote Shutdown tool (Shutdown.exe) to shut down shut down and restart a local or remote Windows 2000-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
317371 How to use the Remote Shutdown tool to shut down and restart a computer in Windows 2000
For more information about how to install multiple hotfixes while only restarting one time, click the following article number to view the article in the Microsoft Knowledge Base:
296861 How to install multiple Windows updates or hotfixes with only one reboot
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Всем привет! Сегодня мы будем разбирать одну из самых загадочных ошибок под номером 6008, которую можно увидеть в системном журнале «Просмотр событий» в столбце EventLog. Обычно ошибку можно увидеть после полного зависания ПК. Причем комп может зависать совершенно в разные моменты – при серфе в интернете, во время игры или даже просто в простое. Почему же она загадочная?
Да потому что однозначной причины и ответ, из-за чего она возникает – нет. По сути, ошибка возникает тогда, когда операционная система не может нормально функционировать и зависает. Из-за чего это происходит? Причин может быть несколько:
- Поломаны системные файлы.
- Кривое обновление Windows.
- Битая плашка памяти.
- На жестком диске много битых секторов.
- Неправильно работающий драйвер, а вот какого железа? Тут вам ни один экстрасенс не скажет. Нужно проверять будет все.
- Проблема в блоке питания.
- Некоторые вирусы аналогично могут влиять на это.
- Перегрев процессора или видеокарты во врем нагрузки, или в жаркое время года.
Еще можно много чего сюда приплести, но мы начнем решение проблемы с самого простого, а именно с системы. Кстати, ошибка 6008 (EventLog) может появляться в любой версии Windows 10, 11, 7 или 8. Сразу хочу предупредить, что вам потребуется терпение, чтобы решить эту проблему. Поэтому запаситесь им и дополнительным временем, а я постараюсь в этом помочь.
Содержание
- Способ 1: Проверка целостности системных файлов
- Способ 2: Откат обновлений
- Способ 3: Проверка ОЗУ и жесткого диска
- Способ 4: Быстрая загрузка
- Способ 5: Восстановление системы
- Способ 6: Драйвера
- Способ 7: Дополнительные советы
- Видео
- Задать вопрос автору статьи
Способ 1: Проверка целостности системных файлов
Запускаем консоль с правами администратора. Далее поочередно вводим две команды. Начнем с проверки и восстановления:
sfc /scannow
Если вы увидите сообщение, что некоторые файлы были повреждены и надо их восстановить – возможно проблема именно в этом. После восстановления на всякий пожарный используем еще одну команду:
dism /Online /Cleanup-Image /ScanHealth
Способ 2: Откат обновлений
Пишу это решение, потому что оно мне в свое время помогло. Видимо как-то криво прилетело обновление в Windows и после этого начал комп зависать.
- Зажимаем клавиши:
+ R
- Вводим:
control
- Переходим в «Программы и компоненты».
- Кликаем слева «Просмотр установленных обновлений».
- Смотрим только в строку обновлений Windows.
- Посмотрите на столбец по дате и удалите через правую кнопку все недавно установленные обновы.
- Перезагружаем комп и проверяем работу ОС.
Способ 3: Проверка ОЗУ и жесткого диска
Из опыта скажу, что данная причина одна из самых популярных, ведь именно с оперативной памятью и работает ПК. Если есть хоть какая-то битая плашка, то комп постоянно будет виснуть и вываливать синий экран. Нам нужно проверить оперативную память. Я вам настоятельно рекомендую сделать это с помощью флешки и программы MemTest. Встроенная проверка Виндовс иногда ошибается.
Читаем – как проверить оперативную память на компьютере.
После этого обязательно проверяем жесткий диск на наличие битых секторов (ссылка на инструкцию).
Способ 4: Быстрая загрузка
Смотрите, на современных ПК и ноутбуках есть такая штука как функция «Быстрой загрузки». Это когда вы включаете комп, а система быстро загружается не напрямую с жесткого диска, а со специального файла hiberfil.sys. Таким образом Виндовс грузится быстрее. Проблема в том, что файл может быть поврежден. Если у вас ошибка и зависание пропадает после перезагрузки, значит проблема может быть в этом. Попробуйте отключить эту функцию. Инструкции для:
Windows 10
Windows 11
Способ 5: Восстановление системы
Откат системы тоже может помочь, если в ОС есть какие-то побитые файлы, но их восстановить не получается. Также это можно откатить и некоторые ранее установленные программы и драйвера. Для простоты и удобства я аналогично оставлю ссылки на полезные инструкции по восстановлению для:
Windows 10
Windows 11
Способ 6: Драйвера
С подобным я сталкивался именно с драйверами видеокарты. Но на форумах ребята жаловались, и на дрова от материнской платы. То есть какой-то драйвер работает неправильно с железом, система не может этому помочь и зависает. Что же нам делать? Искать рабочий драйвер. Я бы на вашем месте переустановил все драйвера. Если вы до этого обновляли какой-то драйвер, то лучше его удалить, или точнее откатить – об этом подробно написано тут (ссылка на инструкцию).
Если вы ничего сами не устанавливали, то я бы скачал драйвера на все железо с официального сайта, поставщика железа, а потом все разом установил на комп. Читаем – как обновить все драйвера в Windows. Совет: сначала ставим драйвера на материнскую плату, а уже потом на все остальное.
ПРИМЕЧАНИЕ! Один парень на форуме рассказывал, что у него проблема была из-за того, что он нечаянно поставил на Windows 7 драйвера для десятки. В итоге при запуске хоть какой-то игры у него зависал комп. Мораль сей басни такова – проверяйте, для какой системы вы скачиваете драйвера. Ну и не забывайте про битность (разрядность) системы.
Способ 7: Дополнительные советы
Если ничего из вышеперечисленного не дало результата, мы прибегнем к дополнительным советам:
- Полностью проверяем комп на наличие вирусов.
- Попробуйте наоборот установить все доступные обновления. Зайдите в «Свойства» системы потом и проверьте какая версия Windows у вас стоит. Версия должна быть современная, текущего года. Если вы видите старую версию, то, скорее всего, у вас стоит пиратская сборка, которая не дает обновиться вашей ОС. Читаем – как узнать версию Виндовс.
- Проверьте блок питания. Также посмотрите, чтобы его мощности хватало на ваше железо. Может быть, вы поставили мощную видеокарту на старый комп, а в БП просто банально не хватает Ватт.
- Проверьте температуру процессора и видеокарты, как под нагрузкой, так и без. Если температура слишком большая, то ошибка может появляться из-за этого.
- Попробуйте очистить комп от мусора.
Если проблема осталась, но вы перепробовали все – подробно опишите свою ситуацию в комментариях, и мы с командой постараемся вам помочь. До новых встреч на портале WiFiGiD.RU.
Видео
Experiencing an unexpected shutdown on your Windows 10/11 system can be frustrating, and if you find Event ID 6008 in the system event log, it’s crucial to understand its implications and explore effective solutions. The Event Properties indicate that “The previous system shutdown was unexpected” with timing. This log may appear because of a system crash, bug checking, or other fatal errors. We are here with this blog post to fix the issue in Windows 11 and 10, its significance, and step-by-step methods to resolve this issue.
The Windows Event Viewer serves as a valuable tool for diagnosing hardware and software events. Among the common errors encountered is Event ID 6008, often recorded after an automatic and unexpected system shutdown. The accompanying message reads: “The last system shutdown at [Time] on [Date] was unexpected.” Mostly, the problem occurs due to CPU over temperature, Damaged power supply unit (PSU), and Security threats.
Event ID 6008 The previous system shutdown was unexpected
Here is how to fix Event ID 6008 The previous system shutdown was unexpected in Windows:
Close multiple running programs and end processes
Unexpected shutdowns, system crashes, or security concerns are the main occurrences that appear at the time of this issue. In this case, the reason might be too many processes are running, a heavyweight game is eating a big part of system resources, and numerous programs or browser tabs are open. If possible minimize them by closing unnecessary apps, files, and processes.
Furthermore, You can close the background running processes through End Task in Task Manager.
- Press “Ctrl + Shif + Enter” to launch the Task Manager.
- Stay in the Processes tab and find the programs consuming more resources.
- Right-click on the “Process” and select “End task”.
- Repeat the same with other programs and see if the error is fixed.
Read: Fix The System Has Rebooted Without Cleanly Shutting Down First Error in Windows
Running a heavyweight game? Then possibly you have no option except to follow the below-mentioned methods:
Check and install pending Windows Updates
Windows updates are generally aimed to improve system reliability, deal with bugs, and make PC performance better. When The previous system shutdown was unexpected is showing in the Event Viewer, a Windows update may help get rid of.
Therefore, keep your system up to date to potentially resolve the issue:
- Press “Winkey + I” and select “Windows update”.
- Click “Check for updates”, Download and install any available updates, and click on “Restart now”.
See: Fix Event Id 1001 Windows Error Reporting (Solved!)
Roll Back Graphic Driver
This method is based on experiences of some users who reported that after Graphics driver update number of Event ID 6008 in the log suddenly increased. Possible bugs in the update might cause conflicts between Windows System files and the driver’s new version. Rolling back will help you in this case, so:
- Right-click the “Start” icon and select “Device Manager”.
- Expand “Display Adapters” and right-click your graphics driver.
- Select “Properties” and navigate to the “Driver” tab.
- Click “Roll Back Driver” and then confirm the prompt. If any questions are asked reply to them following the instructions.
- Restart your PC to check if the error disappeared.
Uninstall recently installed Windows Updates
Sometimes, a new Windows update may trigger “The previous system shutdown was unexpected” error in the Event Viewer along with system crash.
To confirm this situation, see if any update has been installed recently on the PC. For this, go to Settings > Windows update > Update history and check the dates of installed updates. In case, you find an update, follow the steps:
- Press “Windows + R” to open the Run dialog.
- Type “control.exe” and press “Enter”.
- In Control Panel, click “Uninstall a program” under the Programs section.
- Click “View installed updates”.
- Right-click the recent Windows update causing Event ID 6008, and select “Uninstall”.
- Finally, confirm the prompt and let the PC reboot.
Check Your Hardware
If the above solutions fail to work and the Event Viewer is consistently displaying the error then there might be something wrong with the hardware. Address potential hardware issues by following these essential steps:
- Check CPU temperature for overheating. – Monitor PC Temperature, Memory, Network Usage to Boost Performance
- Confirm the Sink Fan is working properly
- Clean the heat sink fan
- Verify the condition of your PSU
Conclusion:
Addressing the vexing Event ID 6008 in Windows 11 and 11 is crucial for a seamless computing experience. This blog elucidates the significance of this error, offering practical solutions to troubleshoot unexpected system shutdowns. By comprehensively exploring potential causes and implementing step-by-step methods, users can effectively mitigate issues related to CPU temperature, damaged PSU, and security threats. Keep your system updated, check hardware components, and consider uninstalling problematic updates for a smoother, error-free operation. Resolving the issue ensures a more stable and reliable Windows environment.
Methods:
Close multiple running programs and end processes
Check and install pending Windows Updates
Roll Back Graphic Driver
Uninstall recently installed Windows Updates
Check Your Hardware
That’s all!!
Shutting down a PC is a normal activity. However, many users often use third-party software to remotely shut down a PC or the PC itself shuts down forcefully because of another third-party program. In either case, users have complained about Event ID 6008.
What Happens When Event ID 6008 Occurs?
The Event ID 6008 occurs in the Windows Event Viewer which is a tool that shows information about software and hardware events on your computer. It is further accompanied by the last time and date on which the system was shut down.
How Is Event ID 6008 Caused?
Besides an unexpected or forceful shutdown, there are multiple reasons behind Event ID 6008 some of which include
Overheated CPU
- A damaged power supply unit
- Presence of malware or other security threats
- Damaged hardware such as a malfunctioning Sink Fan
How To Deal With Event ID 6008 in Windows 10/11
Here are some of the best ways to fix Event ID 6008 in Windows 10/11 –
1. Check for Updates
The Event ID 6008 can occur in case you haven’t updated your Windows OS to the latest version. One of the easiest ways to fix the issue is to fetch recent Windows updates. Here are the steps to do that –
1. Press Windows + I and open Settings.
2. Click on Windows Update from the left
3. Click on Check for updates. If there is an update available, install it.
2. Uninstall Feature Update
Contrary to what we discussed in point number 1, it is likely that the Event ID 6008 error has occurred because of some glitches in a recently installed Windows OS update. So, if you have observed the issue after you installed a Windows update, you can uninstall it and check if you have been able to fix the issue –
1. Open Control Panel by typing Control in the Windows search bar and clicking on Open.
2. Select Category in the View by dropdown.
3. Under Programs, click on Uninstall a program.
4. From the left, click on View installed updates.
5. Select the most recent update that you had installed and click on Uninstall.
6. Restart your computer.
3. Roll Back Display Driver
Some users have reported that they received the 6008 error while gaming. Not just that, but a blue screen accompanied the error. If this is happening to you, the fault might be lying with your display driver. How would you figure that out? Ponder whether the error occurred after you updated your display driver and if it has, here is how you can roll it back –
1. Open the Run dialog box by pressing Windows + R keys.
2. In the dialog box, type devmgmt.msc and press Enter.
3. Click on the Display Driver dropdown and double-click on your display driver.
4. Click on the Driver tab and then click on Roll Back Driver.
Writer’s Tip
It is always a wise and more convenient option to use a driver updater tool. For instance, knowing the fact that driver updates can cause unexpected issues like the one in this post, Driver Booster lets you roll back, restore drivers from a backup or even perform System Restore.
– To Roll Back A Driver
Click on the dropdown next to the outdated driver and click on Roll Back to roll back the driver to an earlier version.
– To Restore A Driver
For this step, you must back up the driver before. For this click on the Tools icon from the left-hand side and then click on Driver Backup. To backup, a driver, select the driver that you want to backup and click on the Back Up option from the bottom-right.
Next –
- Click on the Driver Restore tab
- Select the backed-up driver
- Click on the Restore Version dropdown.
- Click on Restore
4. Perform a Clean Boot and Identify The Issue
The intent of performing a clean boot is to identify the program, file, or service which might be the culprit behind the Event ID 6008 error in Windows 10/11.
1. Open the Run dialog box by pressing Windows + R key combination.
2. In the dialog box, type msconfig and press Enter.
3. Click on the Services tab and click on the checkbox that says Hide all Microsoft services from the bottom.
4. Click on the Disable all button.
5. Once you have done that, click on the Startup tab and then click on Open Task Manager.
6. Click on the Disable option next to any Startup program that you think might be creating issues. You may have to click on the Disable button next to individual programs that you think might be creating issues.
7. Close the Task Manager and click on the OK button in the System Configuration window.
8. Restart your computer.
Do you wish to further know the difference between Clean Boot and Safe Mode, check out this post.
Wrapping Up
In most cases, like in our case rolling back the display driver did the trick and if you have been able to fix the issue, which of the methods mentioned in this post worked out for you, do let us know in the comments section below. For more such content, keep reading WeTheGeek.
Readers help support Windows Report. We may get a commission if you buy through our links.
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
The Event ID 6008 error is triggered if the computer was shut down forcefully using a remote shutdown tool or automatically by a third-party program without the user’s request.
This error can affect any version of Windows from Windows XP to Windows 11 and occurs due to several reasons. To fix the Event Viewer error 6008, you should follow the steps below.
What is Event ID 6008?
This event error could be recorded in the System event log if you restart the computer after an application that makes use of the InitiateSystemShutdownEx function has previously caused the machine to shut down automatically.
Event IDs uniquely identify a given event. Each event source can specify its own unique numbered events, as well as the description strings that will be mapped to those events in the message file that it creates.
What can cause an event 6008?
It is possible that you will experience this issue if the computer has been locked or it is set up with a screensaver that requires a password to be accessed.
And if a program that employs the InitiateSystemShutdownEx function with the force flag is the one that is responsible for the automated beginning of the shutdown procedure.
In this scenario, the Event Log service is not informed about the shutdown occurrence, and as a consequence, the shutdown operation is wrongly regarded as an unexpected event by the Event Log service.
How do you see what caused an unexpected shutdown?
- Press the Windows key + S, type event, and select the Event Viewer option.
- Click Windows Logs in the left pane and right-click on the System option.
- Select the Filter Current Log… option.
- Enter the ID of the issue you want to research in the <All event IDs> box and click OK. For example, type the event id 6008 to see the cause of an unexpected shutdown.
- You can now select a log in the next window to confirm the information there.
How do I fix Event ID 6008?
Before moving to any complicated fixes, it is recommended to check your hardware if they are working well. Below are some of the preliminary checks you can carry out:
- Check if your CPU is overheating. You can check the CPU temperature using any third-party app.
- If on a desktop computer, check if the Sink fan is working.
- Try to clean the heat sink fan by removing the dirt using compressed air.
- Check your power supply unit (PSU) for any malfunction.
If the issue still persists after these preliminary steps, you can proceed to the fixes below:
- 1. Right-click the Start icon then select Device Manager.
When clicking on Start icon, a box will expand and you have to select Device Manager.
- 2. Click the arrow next to Display Adapter to expand it, then right-click on your Graphic Card Driver and select Properties.
After you clicked Device Manager, a list with devices will be shown. Just click on Display Adapter, right-click on your Graphic Card, then on Properties where you’ll find the Roll Back option.
- 3. Go to the Driver tab and click the Roll Back Driver button.
Clicking the Driver tab you’ll find the Roll Back Driver button. The roll-back will begin right after pressing the button.
- 4. Restart your PC.
After the driver is rolled back, reboot the system and check if the Event log 6008 error still appears.
1. Use the Roll Back Driver button
If you are facing the event id 6008 while gaming accompanied by a blue screen, it might be caused by your display driver. In case you just updated your driver before noticing the issue, the ideal solution is to roll it back to the previous version.
- Fix: Event ID 1000 application error on Windows 10/11
- Recent Windows 11 update lets you disable profanity filter in voice typing
2. Check for Windows Updates
- Press Windows + I then go to the Update & Security section.
- Next, click the Check for updates button.
If you are getting the Event ID 6008 with qualifier 32768 in the event log, it might be due to an outdated PC. After the update is installed, check if it is triggered again or if your system is freezing.
If the issue is prevalent then it is possible that Microsoft may have released an update to fix the problem. Check for any pending Windows updates, if you haven’t done them already.
3. Uninstall Feature Updates
- Press Windows, input control, and select Control Panel from the results.
- Select Uninstall a program under the Programs option.
- Select the View Installed Updates option.
- Now, select the most recently installed update that caused the problem and Clicking Uninstall.
- Reboot the system and check for any improvements.
You should try this solution if the error 6008 occurred during a previous Windows Update download, so we advise you to uninstall the KB update from the Control Panel. This would also help when encountering Event ID 6008 in Windows 7.
Additionally, make sure that software updates are checked for on a regular basis and that you are using genuine software versions, which are more stable and include fewer bugs.
For more information and ways to avoid this issue, check out our post on what to do if my computer randomly shuts down in Windows 10/11.
As we’ve shown in this article, it is possible to solve the Event ID 6008 and 41 issues by yourself. Though for Windows 10, the solutions here would help fix Event ID 6008 in Windows 11 as well.
Sometimes it can be as easy as downloading the latest Windows updates, while certain situations may require hardware maintenance. We hope that this guide helped you fix the error.
We’d like to hear more from you on this subject, so feel free to drop a comment in the section below.
Tashreef Shareef
Tashreef Shareef is a software developer turned tech writer. He discovered his interest in technology after reading a tech magazine accidentally. Now he writes about everything tech from Windows to iOS and streaming services to IoT at WindowsReport.