• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows startup sound broke

Bubbleawsome

Bubbleawsome

Diamond Member
(It's like creepypasta lavendertown music. :ninja🙂

I know it's actually a well known issue, it is on the microsoft support page. I'm just wondering why it only happens when I am on iGPU. Any ideas?




[snip]

No funky text
-ViRGE
 
Last edited by a moderator:
I know the windows 8 drivers for the intel gpu have been through trials, but I thought I read those had been ironed out a while ago.

Have you looked for video/audio driver updates sings the switch?
 
Oh dear.
qt03oiY.png
I guess I'll do a virus scan? IDK
 
Might be. I really haven't run into that many times Windows update didn't work, and half of those were on computers with so much malware it wasn't on top of the priority list anyway.

Here is another direction that works for some:
1. Go to Administrative Tools/Services, and stop the Windows Update service.
2. Go to the folder c:Windows/SoftwareDistribution and delete all of the files and folders.
3. Go back to Services and restart the Windows Update service.
 
I'm not at my PC but I think the update corruption was caused by a BSOD I had while it was updating itself so it could download updates. I might have forgotten to install these updates after a reinstalled last.
 
I am seeing the same error in your logs, 800B0100.

This link shows a couple things you may not have tried:
http://support.microsoft.com/kb/956702

Step 2: Use System File Checker to repair damaged Windows files
If the problem continues, use the System File Checker tool to repair damaged Windows files. To do this, follow these steps:

Open an elevated command prompt.
Run the "sfc /scannow" command.
Try to install update again.

For more information about the System File Checker tool, view Use the System File Checker tool to repair missing or corrupted system files.
Step 3: Run the DISM tool
If the problem continues, use the Deployment Image Servicing and Management (DISM) tool to fix Windows Update corruption errors. To do this, follow these steps:

Open an elevated command prompt.
Run the "DISM.exe /Online /Cleanup-image /Restorehealth" command.
Important When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Note Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, see Repair a Windows Image.
Click to expand...
 
Windows Update is attempting to install a selfupdate (it's a security update):

Code: 
2014-08-04      15:33:23:834    1236    17d4    Setup   Staging setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-04      15:33:35:439    1236    17d4    Setup   Successfully staged setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-04      15:33:35:439    1236    17d4    Setup   Staging setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-04      15:34:01:275    1236    17d4    Setup   Successfully staged setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-04      15:34:01:276    1236    17d4    Setup   Staging setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"

It staged the update, meaning that it trusted the signing of the package (these packages have a trust relationship to the Microsoft root certificate authority.) However, in this process WU crashed for an unknown reason:

Code: 
2014-08-04      15:34:01:276    1236    17d4    Setup   Staging setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-04      15:39:24:044    1236    17b8    Misc    ===========  Logging initialized (build: 7.5.7601.17514, tz: -0500)  ===========
2014-08-04      15:39:24:066    1236    17b8    Misc      = Process: C:\Windows\system32\svchost.exe
2014-08-04      15:39:24:066    1236    17b8    Misc      = Module: c:\windows\system32\wuaueng.dll
2014-08-04      15:39:24:044    1236    17b8    Service *************
2014-08-04      15:39:24:066    1236    17b8    Service ** START **  Service: Service startup
2014-08-04      15:39:24:066    1236    17b8    Service *********

There's no service exit, meaning it didn't exit cleanly. When WU comes back up, it attempts to resume from where it left off, but suddenly the package is no longer trusted.

If you open "View Reliability History", on the bottom, click "View All problem reports", look for Windows Update. If it says "Report Sent" for the crash there, right click it, click "view technical details" and copy/paste that info here (or just screenshot the window.)

---

I see no reason for this to happen, and frankly given you're here posting about other issues I'm tempted to say you have corruption going on, but copy/paste the info here anyway.
 
ketchup79 said:
To answer RampantAndroid:
Click to expand...

Thanks.

I was confused because he said while it was downloading, and mentioned reinstalling.

When specifically did the BSOD happen? During a "Please dont shut down updates are installing" screen? Or at some other point? Maybe try deleting C:\Windows\Software Distribution\Downloads and then checking for updates again?
 
Bubbleawsome said:
It happened during a "checking for updates" IIRC :\
Do you still need that log?
Click to expand...

Sure, with any luck there are some crash dumps to look at. A BSOD during checking for updates shouldn't cause WU to blow up - it won't install a selfupdate automatically if you scanned manually (it'll ask you to begin the install.)
 
Bubbleawsome said:
Um, I think I messed up....
Click to expand...

LOL. Sorry to laugh, but the bottom section reminded me of a friend of mine. This was years ago in college. He will kill any screen that hung for more than two seconds. Needless to say, he was the first person I knew to have an SSD.
 
If you scroll down, is there a Windows update crash listed?

How often does explorer hang (and what are you doing when it hangs?) If you're seeing a lot of other issues, that to me seems suspect of a bigger problem (either corruption on the hard drive, or memory/cpu issues.) Any idea what the crash listed was when you saw the BSOD?

What are the unexpected shutdowns - did you hold down the power button, have an outage, or is that another issue you're seeing? If you took action to turn Windows off while it was running without letting it finish up cleaning, that could absolutely cause problems. If it's shutting down for unknown reasons, that points to a hardware issue (I would think.)
 
Last edited:
RampantAndroid said:
If you scroll down, is there a Windows update crash listed?

How often does explorer hang (and what are you doing when it hangs?) If you're seeing a lot of other issues, that to me seems suspect of a bigger problem (either corruption on the hard drive, or memory/cpu issues.) Any idea what the crash listed was when you saw the BSOD?

What are the unexpected shutdowns - did you hold down the power button, have an outage, or is that another issue you're seeing? If you took action to turn Windows off while it was running without letting it finish up cleaning, that could absolutely cause problems. If it's shutting down for unknown reasons, that points to a hardware issue (I would think.)
Click to expand...

No, that's the farthest it scrolls.

Explorer never hung, it would just stop working. It would usually happen soon after boot about twice a day until around 2 months ago. This install is ~6-8 months old I think. The BSOD was from me overclocking the iGPU too far. It doesn't like 1300Mhz. 😀

Most of the unexpected shutdowns have been unstable overclocks. Very slightly unstable though, might have caused silent corruption. Beyond that I've had maybe 2 power outages.
 
You may want to run system file checker.

If you continue to have issues, considering your past on this onstall, it may be easiest to just do another fresh install.
 
Isn't the Windows 7 Startup Sound just a boring single note? Why not just turn it off? lol. The Windows XP startup/shutdown sounds were so much cooler and funner to remix.

edit: Ahh, you're on Windows 8... and I guess I was wrong anyway.
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top