I'll quote some stuff for later reference:
1. Still a problem with WU:
I just checked again and it still says no updates at this time.
HTML:
9/4/2011 5:17 PM Windows Error Reporting Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.5.7601.17514
P2: 800b0100
P3: B0E36AD5-3D76-4E00-A79F-1A6ED610276C
P4: Download
P5: 106
P6: Unmanaged
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.5.7601.17514_c280bc211de630fc70f2f41fdb4e55e17ed63b7_06b08b4d
Analysis symbol:
Rechecking for solution: 0
Report Id: b6ed5c55-d719-11e0-9fc6-bcaec5dde74f
Report Status: 4
2. Part of the AMD overdrive system is attempting to start but causes an error:
HTML:
Source: Service Control Manager
Date: 2011-09-04T09:54:32.528
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: ERIK-PC
Description:
The AODDriver4.01 service failed to start due to the following error:
The system cannot find the path specified.
How did you delete the Overdrive software? BTW, there are more related message on the same. AMD Fuel mainly.
Is that related to my onboard Radeon 3000? I believe after I downloaded the catalyst 11-8_vista64_win7_64_dd_ccc_ocl(1)
from AMD website, I just used the uninstall from the installer....
Should I try and uninstall and reinstall it? If so what is the proper way of doing so?
And, should I address this problem before doing the clean boot?
3. multiple problems starting certain services:
HTML:
DCOM got error "1084" attempting to start the service EventSystem with arguments "" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
For this one, please see this link and tryout the steps in the second post. It will, through a clean boot procedure, try to identify what third party stuff is troubling you.
DCOM got error "1068" attempting to start service BITS with - Microsoft Answers
If that does not help or look too difficult, we can also try a different angle: Verifier:
Beyond that, please run Verifier with these settings:
On this one do I just do the clean boot procedure,restart, and then run system as normal until "if" or "when" it crashes again?
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Using Driver Verifier to identify issues with Windows drivers for advanced users
I put the stock ps back in......
...... If anyone has freetime and feels like it, here is some new info, Thanks
