Windows 8 bug report: Word crash, Start Screen and charms bar inopperable. BIOS unavailabe on REBOOT.

While writing text into a Word document running on my new ASUA Windows 8 x64 machine, the display screen started flashing and after each flash a character in my document was deleted. This continued until I closed Word. This left me in the Windows 8 desktop, but there was no access to the Start Screen via mouse-to-corner. Nor was the charms bar working or available. The Win 8 desktop icons were non-responsive to mouse clicks.


So I shut the system down, and restarted via power off/on.


Upon restart, the system reported it was unable to find BIOS and failed to reboot into Windows 8.


Instead, a notice was displayed to "insert boot media."


After another power off/on restart, I pressed F2 to reach UEFI bios editor.  In the editor, I found that my system hard drive was unlisted in the boot order. Instead a single drive was listed, but it did not correspond to any drive on the system.  So I entered UEFI bios editor and entered the correct boot drive for UEFI.  Saved the changes. Restarted the system.  And it booted properly and I reached the Space Needle splash and was able to log on.


After using the system for a few hours, and using Word. I can confirm that the system seems ok and there are no evident problems.


This strange behavior I encountered using Windows 8 and Word on a new ASUS desktop with factory installed Windows 8 x64, is concerning.


Windows 8 crashed and then somehow altered the system BIOS in such a way that Windows 8 would not reboot.


I'm looking forward to all the good replies and fixes for this one.


Getting a fresh cup of coffee. 


Good thing I already printed out my tax documents!






Question Info

Last updated March 24, 2018 Views 445 Applies to:
I was able to get the system working by going into UEFI editor and selecting the correct UEFI boot device. Saved new UEFI setup and restarted.  Now Word, Windows 8 Charms Bar and Start Screen are all functional.  I am able to use Word without a repeat of the problem so far today.

Maybe the correction to UEFI boot device order fixed the problem? 

Anyway, as you suggested, we had a look at Event Viewer  ...

As to the Event itself (5/6/2013 10:02AM:  Event viewer shows 40+ entries time marked during the problem period of a few minutes. I confess to not knowing which if any of these is important
Here's a sample:

Initialization status for service objects.
C:\Windows\system32\sppwinob.dll, msft:spp/windowsfunctionality/agent/7.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/phone/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/pkey/detect, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/ActionScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/TaskScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/statecollector/pkey, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/activationinfo/1.0, 0x00000000, 0x00000000

Fault bucket , type 0
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: 2152759308
P2: unspecified
P3: ScanFile
P5: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified

Attached files:

These files may be available here:

Analysis symbol: 
Rechecking for solution: 0
Report Id: 77a2fce5-b678-11e2-bea1-08606e46e126
Report Status: 20


Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.  

 1 user registry handles leaked from \Registry\User\S-1-5-21-215813488-2701518589-753988281-1001:
Process 688 (\Device\HarddiskVolume4\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-215813488-2701518589-753988281-1001\Software\Microsoft\Windows\CurrentVersion\Uninstall

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

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

How satisfied are you with this response?

Thanks for your feedback.