The Event Log Error 6008 typically appears after an application uses the InitiateSystemSHutdownEx function due to an unexpected scenario. If your machine has previously shut down unexpectedly and you just discovered the Event Log Error 6008 error inside Event Viewer, there are quite a few potential causes that you should investigate.
Although in most cases, the 6008 error is rooted in some hardware issue (failing HDD, SSD, or RAM), the problem can also be indirectly caused by a bad windows update, a missing GPU driver dependency, or a scenario where there’s an extra sound driver conflicting with the main driver.
This behavior can also occur if you’ve previously disabled the paging file, if you’re still using a grounded VGA monitor or if you’re dealing with system file corruption that makes your OS unstable enough.
Here’s a short list of methods that you can use to troubleshoot the 6008 error and prevent any further unexpected shutdowns:
1. Update Windows Version to the latest
If you noticed that the 6008 Event Viewer error started appearing after you installed a pending update (or Windows did so automatically),
In this case, start this troubleshooting journey by checking if Microsoft has already released a hotfix for this issue on the WU deployment channels that you’re part of:
Here’s a quick guide that will allow you to check for a hotfix and install it on your PC:
Note: The instructions below are applicable on both Windows 10 and Windows 11.
- Use the Windows key + R shortcut to open the Run dialog box.
- Enter “ms-settings:” in the search box and press Enter to open up the Settings menu on your Windows PC.
Access the Settings menu Note: If the User Account Control prompts you, click Yes to grant admin access.
- From the Settings screen, find Windows Update and select it from the menu on the left of the screen.
Access the Windows Update screen - Check the following screen to determine if there are any updates that need to be installed. Click the Download & Install all button if the driver is already available for installation.
Download and install all Note: If the update scan doesn’t happen automatically, you can trigger it manually. To do this, click the Check for Updates button and wait.
- Be patient and wait until all pending updates are installed. Your computer might need to restart for the updates to take effect.
- Utilize your PC normally and see if you’re still experiencing the same unexpected crash with the 6008 Event error.
If the problem is still not fixed, move to the next method below.
2. Revert the latest installed update
In case the issue is still fresh, and Microsoft didn’t get the chance to release a hotfix, you can fix the issue yourself by uninstalling the bad update that caused this issue in the first place.
Note: This method will only work if you start getting this error after installing a pending update.
You can enforce this fix by going to the Programs and Features screen and selecting the View installed updates tab to start the removal process.
We advise doing it straight from the recovery menu because this will let you roll back feature updates and cumulative updates and postpone their installation until Microsoft releases a hotfix.
To remove the most recent update from the Recovery menu, follow the instructions below:
Note: The steps in the following paragraphs will demonstrate how to enter the Recovery menu forcibly without utilizing appropriate installation discs.
- Stop your computer from booting up by turning it on and pressing and holding the power button as soon as it gets past the initial screen.
Interrupt the normal startup procedure Note: Most of the time, you’ll need to hold down the power button for 5 seconds to complete a force shutdown.
- Restart your PC and carry out steps 1 and 2 above two more times until the Recovery menu successfully appears.
Note: If you repeatedly force your Windows computer to interrupt the boot process, the system won’t complete the boot and will instead boot directly into the Recovery menu. - Select Troubleshoot from the list of choices when you arrive at the Advanced Options screen. The Troubleshoot tab can be selected.
Access the Troubleshoot tab - Select Uninstall Updates under Troubleshoot.
Uninstall updates - Select the most recent update, click Uninstall, and then click Confirm on the Uninstall Updates screen.
Note: Find out which kind of update—cumulative, feature, or optional—was applied most recently and uninstall it. - After removing the feature update, restart your Windows machine and let it boot normally.
- Utilize your PC normally and see if you still get the same unexpected system shutdowns causing the Event Log Error 6008.
If the problem is still unresolved, move to the next method below.
3. Update GPU drivers
It turns out that an outdated GPU driver or a missing physics module can also cause this type of behavior with Windows 10 and Windows 11.
This issue is even more likely if you only experience this problem while your PC or laptop performs a resource-demanding task. If this scenario is applicable, you should be able to fix the problem by updating your GPU drivers to the latest version.
If you haven’t updated your GPU drivers recently, perform the steps below to uninstall your outdated GPU drivers and install the most recent ones in an attempt to fix the 6008 error:
- To launch the Run dialog box, use the Windows key + R.
- To launch Device Manager, enter the command “devmgmt.msc” in the execute text box and press Enter.
Open Device Manager - Expand the drop-down box for Display Adapters after launching Device Manager by scrolling down the page’s list of installed devices.
- To update the driver, right-click the GPU driver you wish to update in the following menu and select it from the context menu.
Update the GPU driver Note: You must upgrade your computer’s dedicated and integrated GPU drivers.
- Select Search Automatically for New Driver Software from the menu that appears.
Search automatically for drivers - When the initial scan is finished, follow the steps to install the most recent GPU driver found.
- Once the procedure is complete, restart your computer to check if the problem is now fixed.Note: If Device Manager cannot update your current graphics drivers, you must use the proprietary software your graphics card manufacturer provided. Depending on the GPU maker, the following software might be required:Nvidia’s GeForce Experience
AMD: Adrenalin
Intel: Intel Driver
Continue to the next step in the procedure below if the same problem is still present or your GPU drivers are already up to date.
4. Roll-back display driver
Suppose the issue started immediately after you updated your GPU version. In that case, there’s a chance this problem is indirectly caused by a bad graphics card driver that’s somehow producing general system instability that triggers the unexpected system shutdown.
Many impacted users have claimed that after reverting their dedicated graphics driver to an earlier version, the problem was ultimately fixed. If you have an NVIDIA or AMD GPU, there’s a good chance you’ll be able to fix the problem after rolling back your GPU driver to a previous version.
Here is a simple tutorial on reverting your GPU drive to a previous version:
- To bring up the Run dialog box, press Windows key + R. After that, enter “devmgmt.msc” to launch Device Manager.
Open Device Manager - Select Yes if the UAC (User Account Control) asks you to provide administrative rights.
- Open up the drop-down selection for Display adapters in Device Manager.
- Next, select Properties by performing a right-click on your dedicated GPU driver.
Access the Properties screen - Click on Roll Back Driver under the Driver tab in the Properties screen.
Rolling back the driver - To start the rolling back process, choose a reason (it doesn’t matter) in the confirmation box and click Yes.
- Restart your computer and check if the issue is fixed after reverting the GPU driver.
Continue to the next solution below if you still get the same error after your Windows computer crashes unexpectedly.
5. Replace the grounded VGA Monitor (if applicable)
Suppose you’re still using a grounded VGA monitor. In that case, this hardware may be causing unexpected system crashes as it produces little shocks due to bad insulation that ends up restarting your PC unexpectedly.
Note: This scenario is only possible with grounded legacy VGA monitors produced before 2010.
If you’re still using a grounded VGA monitor, connect a different display and normally utilize your PC to see if the same issue repeats.
If the same issue is still occurring or this method is not applicable, move down to the next method below.
6. Disable or Uninstall the extra sound driver (if applicable)
If you have two or more sound drivers installed on your PC, this is likely the conflict producing the 6008 error, as both drivers run simultaneously.
If this scenario is applicable, you can fix the issue by disabling or uninstalling the extra sound drivers that are not needed.
For example, if you have both the Nvidia High Definition Audio Driver and the Realtek HD Audio driver, disable or uninstall one or the other to fix the issue.
Start by disabling the secondary audio driver and resort to uninstalling only if the first method doesn’t work.
Follow the sub-guides below for complete instructions on how to do this:
6.1. Disable the Extra Sound Driver
To disable the extra sound driver, you need to access the Sound, video, and game controllers tab in Device Manager and disable one of the audio drivers that are currently installed.
Here’s how to do this:
- Press the Windows key + R to open up a Run dialog box.
- Next, type ‘devmgmt.msc’ and press Ctrl + Shift + Enter to open up Device Manager.
Open Device Manager - At the User Account Control (UAC), click Yes to grant admin access.
- Inside Device Manager, scroll down to Sound, video, and game controllers and expand the drop-down menu.
- Right-click on the unnecessary audio driver and click on Disable Device.
Uninstall the secondary audio driver - Confirm the operation at the next prompt.
- Reboot your PC and see if the issue is fixed once the next startup is complete.
6.2. Uninstall the Extra Sound Driver
If disabling the secondary driver didn’t make a difference, your only option is to uninstall one of the two sound drivers that can be potentially conflicting.
To do this, use Device Manager and eliminate the unnecessary driver.
Here’s a quick guide that will show you how to do this:
- Press the Windows key + R to open the Run dialog box.
- After that, open Device Manager by typing “devmgmt.msc” and press Ctrl + Shift + Enter.
Open Device Manager - When User Account Control asks you whether you want to grant admin access, choose Yes (UAC).
- Scroll down the list of installed drivers in Device Manager to expand the drop-down menu for Sound, video, and gaming controllers.
- Right-click the audio driver you wish to uninstall and choose Properties to open the context menu.
Access the Properties screen - From the Properties menu of your audio driver, click Driver and Uninstall Device.
- When prompted, select “Uninstall” after checking the box next to “Try to delete the driver for this device.”
- After removing the driver, restart your computer and see if the issue is fixed.
7. Disable the Paging file
The final thing you can do if you’ve tried the steps above and still get the same 6008 error as your system is experiencing unexpected shutdowns is to turn off the Windows Paging file.
Although this might make some native Windows apps malfunction, many Windows users experiencing this problem on low-end PC settings have reported that this workaround eventually allowed them to stabilize their PC.
If you decide to use this strategy, disable the Windows Paging file by following the steps listed below:
Note: The instructions will work on both Windows 10 and Windows 11.
- To bring up the Run dialog box, press the Windows key + R.
- To enter the System Properties page with admin access, put “sysdm.cpl” into the text box and click Ctrl + Shift + Enter.
Access the system Properties screen - When in the System Properties window, select the Advanced tab from the menu at the top, then click on the Performance Settings button.
Access the Settings menu of Performance - Select the Change button under Virtual Memory from the Performance Options menu’s Advanced tab at the top.
Accessing the paging file - After you’ve reached the Virtual Memory menu, deselect the box next to Automatically control paging file size for all drives.
Disabling the paging file - Select the No paging file option to save the changes and click Ok.
- After the next startup is finished, restart your computer to determine if the issue has been resolved.
8. Use System Restore
If you’ve followed every method above and come up empty-handed, you should look into a potential 3rd party interference causing the unexpected system shutdowns with the 6008 error.
Since the list of potential culprits is virtually endless, a quick way to eliminate a conflicting 3rd party process, service, or startup item from your culprit list is to use System Restore.
This built-in tool will allow you to restore your machine to a timestamp when this conflict was not present (a new driver installation, a driver swap, the installation of new software, etc.).
IMPORTANT: System Restoration is configured to create and save new restore snapshots when a significant system event occurs. If you don’t alter this default behavior, you should have many restoration pictures to choose from.
Follow this article for specific instructions on deploying a System restore operation and reverting your PC to a healthy state where the issue was not present.
If the problem is still not resolved, switch to the method below.
9. Perform Memtest and replace RAM (if applicable)
Defective RAM may also factor in this 6008 Event Id error, as it can cause memory leaks and serious system crashes. If you frequently experience severe system crashes, try to run a Memtest to check the integrity of your RAM stick(s).
Note: If you have dual-channel RAM installed, you can try removing just one stick at a time to see if the issue is still present.
In addition, you should test the integrity of your RAM stick using a program like Memtest.
Important: If your RAM has ever been overclocked, we advise reversing any voltage overclocked frequency and monitoring your temperatures while running a stress test using a program like HWMonitor.
Your only choice is to look for a replacement if the Memtest tool on your RAM has revealed a memory problem.
If this method fails to identify a simple RAM problem, move on to the next potential solution below and eliminate this potential offender from your list.
10. Deploy the CHKDSK scan
Some Windows 10 and Windows 11 users using conventional HDDs claim that this issue might also arise from defective sectors on your HDD, which may be causing general system instability.
Your system might generate 6008 event id errors each time the integrity of your drive is tested for faulty sector data.
The good news is that we discovered user reports indicating that performing a CHKDSK scan completely resolved their problem.
To run a CHKDSK scan on your Windows 11 PC, follow these steps:
- To enter the Run dialog box, first press Windows key + R.
- To open an elevated Command Prompt, type “cmd” in the box and hit Ctrl + Shift + Enter.
Open an elevated CMD window - To give someone administrative rights, select Yes when prompted by UAC (User Account Control).
- To start an offline scan, enter the following command at the elevated Command Prompt and click Enter.
chkdsk /f
- After the procedure is finished, restart your computer and check to see if the problem is fixed when the system starts up again.
- After running a CHKDSK scan, use your PC normally and see if the same issue is still occurring.
If it is, move down to the next method below.
11. Check HDD or SDD health
If you’ve come this far without a viable fix, it’s about time you consider a potentially failing drive (especially if you’re using a conventional HDD).
Your disk may start to fail if it occasionally maintains 100% utilization, and it tends to trigger a system crash during tasks involving data transfer.
Fortunately, there is this free third-party tool called Speccy that you can use to determine whether your HDD or SSD is failing.
Use this tool to receive a summary of roughly 30 SMART points that gauge the condition of your drive.
Note: Your drive is not malfunctioning if all the measurements are within the normal range.
The steps listed below will help you install and use Speccy to determine whether a failing drive is causing the 6008 error:
- Start by launching your preferred browser and going to the Speccy download page.
- Select the Download option for the Speccy free version when you are there.
Downloading the Speccy software Note: As of right now, you can check out the SMART parameters without purchasing the premium (Professional) edition, so avoid doing so unless you will utilize it.
- Double-click spsetup.exe after the download is finished, and then select Yes when User Account Control (UAC) is prompted to give the necessary admin access.
Download to install - After entering the installation prompt, follow the instructions to finish installing Speccy. When requested, restart your computer.
- After your computer has restarted, launch Speccy and wait until the preliminary scan is finished before selecting Storage from the menu on the left.
- Scroll down to the Smart Attributes area in the right-hand corner.
Note: Examine each attribute name’s status to determine if any values differ from what is anticipated. If you discover several characteristics that are not marked as Good and are above the threshold, you can infer that the drive in question is starting to malfunction.
The only option at this point, if your examination has revealed that you are dealing with a failing disk, is to look for a replacement and back up your current data while you can still boot normally.
If you’ve just determined that the issue is unrelated to a failing drive, continue to the next possible solution below.
12. Clean install or repair install
You might be dealing with a systemic issue if none of the above solutions have been able to help you fix the issue. The last resort is to reset every Windows component to fix the system file corruption causing the 6008 event ID error.
You have two choices when it comes to resetting every system component of your Windows installation:
- Repair install – The repair install option is the best for fixing any corruption on Windows 10 or 11. Although you’ll need appropriate installation CDs, the main advantage is that all of the games, apps and personal files currently on the OS disk can be kept.
- Clean install – Because you don’t need to use any installation CDs, this is the easiest procedure (you can initiate this procedure directly from the GUI menu). The main drawback is that unless you back up your C: disk beforehand, you will lose all of your media, games, apps, and user preferences.
Всем привет! Сегодня мы будем разбирать одну из самых загадочных ошибок под номером 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.
Видео
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.
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.
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!!