Windows has recovered from an unexpected shutdown


Active Member
Jul 31, 2014
Thread starter #1
I'm running Windows 7 premium. After several shutdowns that have happened throught the day i received the following message.

Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000406F8
BCP4: FFFFF88000F10008
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:


Active Member
Jul 31, 2014
Thread starter #3
Cindy. My problem "may" be the result of using two anti-virus programs at the same time. The problem "at this time" has been rectified by uninstalling one of the programs. Nevertheless below are the results from the "Who Crashed" program.

System Information (local)
Computer name: N3-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\windows
Hardware: IdeaCentre K330B, LENOVO,
CPU: GenuineIntel Intel(R) Core(TM) i5-2320 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8430940160 bytes total

Crash Dump Analysis
Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Wed 3/1/2017 6:47:31 PM your computer crashed
crash dump file: C:\windows\Minidump\030117-17206-01.dmp
This was probably caused by the following module: acpi.sys (ACPI+0x11008)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF88000F10008)
file path: C:\windows\system32\drivers\acpi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ACPI Driver for NT
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


Active Member
Jul 26, 2009
Sydney Australia
I don't stress over Windows shutting down sometimes.

Just Windows being weird.

Reboot, and all is well again, normally.
Had one yesterday as a matter of fact, on a new build.


Active Member
Aug 12, 2014
Dorset, England, UK

Sorry for this late entry but I just happened to be browsing and having had a similar experience, I thought I'd mention what caused mine.

My BSOD experience was around about 20 March this year. It turned out the problem, a BSOD about 5 minutes into each startup, was caused by an Avast virus definitions update. This caused much annoyance and frustration among Avast users as Avast were not very forthcoming about the problem. However the next update included a fix.

I thought that the same thing had happened again when I had another BSOD during the last Avast program update. Fortunately on restart the program update continued automatically and completed correctly. There have been no further BSODs.


Active Member
Aug 12, 2014
Dorset, England, UK
Hi Tony,

Initially I had no idea Avast had caused the problem so I posted a query on the Microsoft Community forum. I included a copy of the text from the BSOD in the post:


If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Option and then select Safe Mode.

Technical information:

*** STOP: 0x0000000A (0x00000016, 0x00000002, 0x00000000, 0x8363BAE8)

Collecting data for crash dump ...

Initializing disk for crash dump ...

Beginning dump of physical memory.

Dumping physical memory to disk: 100

Physical memory dump complete.

Contact your system admin or technical support group for further assistance.

Within an hour I had a reply from one of the regular contributors who had recognised the problem earlier (possibly in his own or a client's system) and been in touch with Avast. He provided a link to a thread on the Avast forum ( ). Avast acknowledged there was a problem with the definition update and stated it would be resolved in the next update later that day. A suggested temporary workaround in which part of Avast was disabled had mixed results with users so I chose to wait and used my computer via a live Linux dvd in the interim so I could access my files without any BSOD interruptions.

With the second recent problem, I just assumed Avast was the culprit because the BSOD happened during the Avast program update at the point where the user is asked to restart the computer to complete the operation. I thought "oh here we go again" but after a hard reset, selecting 'Normal startup' rather than one of the 'Safe Mode' choices from the startup options, the system started successfully. The Avast screen appeared so I could complete the update process (basically ensuring that the 'Chrome Browser' was not ticked for installation as Avast push this at every program update or installation). Since then, there have been no more BSODs so I assume Avast was indeed the culprit again.


Active Member
Aug 12, 2014
Dorset, England, UK
Hi Cindy,

In the Avast update case, it would suggest sloppy coding and a failure on Avast's part to run any appropriate checks in house before releasing the update but then haven't Microsoft been guilty of releasing bug-ridden updates for their operating systems and software? It emphasises the need for system image and data file backups for when there are really serious problems.

Happy Easter one and all, cheers, Kick.
Top Bottom