Windows Update causes > 600 errors to show up in MMC

[nullpointerus]

Originally posted by: robisbell
this is sounding like a memory issue now, or hdd not tracking properly when they write data.

When applying the updates manually, I got a STOP 0x0000000A error in module 768_1.

Maybe dclive's website can give me a clue about this error, but I'm too tired ATM.

Sadly, I don't have any other s775/DDR2 parts to swap in and see if the errors go away. No replacement CPU, MB, or RAM. I would order some cheap replacement component to test, but that would just be a total waste of money right now because I really have no idea which one to replace.

After applying the updates manually, I got some of the same events (but much fewer!) during the few automatic updates for which there is no public standalone package.

I'm still not convinced this is a software problem. And what about all the ATI/CCC problems? If I could just replace one HW component and make all these problems go away...eh, life should be so easy!

Given my luck, it'd probably be the *two* HW components I'd *never* guess...







My computer will just have to sit idle except when I can work with MS/ATI tech. support. While I have faith that ATI could do it, I think MS would be clueless when it comes to finding and *identifying specific* HW problems causing errors in their SW.
:roll:

I still have to look into the Windows Setup logs...maybe there's a nice little error...somewhere...

Or maybe if I set everything *way* below stock...absolute slowest clocks/timings...the errors will cease or at least change. Something's gotta change -- at least 7+42 servicing errors every damn time...!!

 

[robisbell]

the memory and whatnot are not running at stock speeds?

what make and model are your HDD's?
what make and model are the memory modules?

 

[nullpointerus]

Originally posted by: robisbell
the memory and whatnot are not running at stock speeds?

Yes, *everything* is running at stock speeds.

what make and model are your HDD's?

Western Digital SE16 320GB SATA

Model:
WDC WD3200AAKS-22SBA0

what make and model are the memory modules?

4x1 GB HP PROMO PC2-5300 5-5-5-15 @ 1.8v

P/N: PX976AT

 

[robisbell]

and you ran the WD diagnostics fully on the HDD, correct?

 

[nullpointerus]

Originally posted by: robisbell
and you ran the WD diagnostics fully on the HDD, correct?

No...just a surface scan w/ chkdsk.

I'll set the WD diagnostics up to run now.

 

[robisbell]

good, let me know the results.

before you do the WU, you have installed all the mobo chipset drivers correct?

 

[nullpointerus]

Originally posted by: robisbell
good, let me know the results.

There will be a delay with the HDD evaluation. I have Vista x64 installed, but I need to run WD's diagnostic program from Vista x86 (or use Vista x86 to run the floppy image writer).

I will call WU support, but first I need to do a clean installation of Vista x64 for them to play around in.

before you do the WU, you have installed all the mobo chipset drivers correct?

I've tried it both ways, and with two different chipset driver versions -- same result.

For kicks, I installed VirtualPC 2007. We will see what happens w/ Vista x86 in there.

 

[robisbell]

get The Ultimate Boot CD, they have the WD diagnostic on it and avoids the OS messing with the tests.

 

[nullpointerus]

Originally posted by: robisbell
get The Ultimate Boot CD, they have the WD diagnostic on it and avoids the OS messing with the tests.

I got a STOP error with the VirtualPC, and a different one (D1 ?? in ndis.sys) while d/l-ing The Ultimate Boot CD. I restarted the download (from scratch) and am burning it now. CloneCD is going nuts...it's taking 8+ minutes to burn a little CD iso, and the progress meter is stuck at 100% (burning lead-out).

 

[robisbell]

can you use another pc to dl and burn the cd?

 

[apoppin]

first of all, dclive thinks it is a Win issue ... DID you contact MS for Tech support?

secondly, it *appears* that your RAM, HD and DVD all check out ...

hmm .. could be the MB ... the BIOS

have you tried flashing to an EARLIER bios? and did you check with Gigabyte to see if there were issues with the one you used?

finally, i would try again ... from the beginning ... with a new OLDER BIOS flash - twice [to make sure it doesn't revert to its backup] ... then 1 HD [not ACHI] - do you have an older IDE drive you can use? - 1 DVD-ROM and 2 sticks of RAM [the other pair you didn't try]
finally ...perhaps try to set up XP [that will rule out the Vista DVD]

 

[dclive]

I got a STOP error with the VirtualPC, and a different one (D1 ?? in ndis.sys) while d/l-ing The Ultimate Boot CD.

Ah, good! So when you debugged the dumpfiles, what was the problem?

 

[nullpointerus]

Originally posted by: robisbell
can you use another pc to dl and burn the cd?

Too much trouble...I made some new partitions, and I will install Vista x86 on one of them anyway for MS WU support. Once in Vista x86, I can use WD's floppy writer to make a bootable floppy that will perform the diagnostic without Windows' interference.

I'm not sure what this will tell us...a different HDD had the same WU problems. But maybe the BSOD's are a related issue.

...more things to do...

first of all, dclive thinks it is a Win issue ... DID you contact MS for Tech support?

Not yet!!!

I will create the floppy, do the diagnostic, etc. as soon as I can.

secondly, it *appears* that your RAM, HD and DVD all check out ...

hmm .. could be the MB ... the BIOS

I'm thinking the little aluminum southbridge cooler is inadequate. I get no temps from it, but there's no fan, no heatpipes (to link to other coolers), and the HD2900XT covers it up completely. That's a very stupid MB design, IMO.

A while ago, I *did* try swapping the HD2900XT for a little X1550 card, which enabled the SB to get plenty of airflow, but the WU problems persisted. I didn't test that long enough to see if there were any BSODs w/ the X1550. They could be power/heat related.

Come to think of it, the occasional random BSODs in Vista x64 (back before this whole mess started) would happen during high HD activity + network transfers + onboard audio.

- Streaming Internet audio while backing up files --> STOP error
- Running Vista Updates in a VM while downloading Ultimate Boot CD --> STOP error
- Vista not installing correctly...CDs no longer burning correctly...on the same HW

It's a theory, at least...
...I'll throw it on the pile.

have you tried flashing to an EARLIER bios? and did you check with Gigabyte to see if there were issues with the one you used?

Yes, and no (to the second question).

I tried F6, F9, F11 -- all the same issue w/ WU. Dunno about the BSODs.

Vista x86 ran fine on F6 for months last year.

finally, i would try again ... from the beginning ... with a new OLDER BIOS flash - twice [to make sure it doesn't revert to its backup] ... then 1 HD [not ACHI] - do you have an older IDE drive you can use? - 1 DVD-ROM and 2 sticks of RAM [the other pair you didn't try]
finally ...perhaps try to set up XP [that will rule out the Vista DVD]

I tried an older BIOS and a minimal setup a while ago (yesterday?) -- same result.

But I will put the X1550 back in, go back to 2 GB, clock down the CPU/RAM (i.e. below stock), and use that as a testing base from now on. Eliminate as many other factors as possible, I guess.

I got a STOP error with the VirtualPC, and a different one (D1 ?? in ndis.sys) while d/l-ing The Ultimate Boot CD.

Ah, good! So when you debugged the dumpfiles, what was the problem?

*sigh*

...debugging BSOD dump files now...?
...didn't get to that yet...
...looks like I'll be up late again tonight...

 

[dclive]

I don't understand. You've got two concrete steps (debugging the dumpfiles and calling Microsoft) which WILL give you definitive answers, yet you've done everything *but* that.

 

[apoppin]

But I will put the X1550 back in, go back to 2 GB, clock down the CPU/RAM (i.e. below stock), and use that as a testing base from now on. Eliminate as many other factors as possible, I guess.

Perhaps you could try to install XP if Vista still has problems ... to rule out the incomprehensible - the DVD


i think you are going to get this fixed - don't toss your rig in the trash yet ... i had a similar type of *impossible* issue as you may well recall
... also you might check Gigabyte's forums to see if it is MB related or even google your issue to see if anyone else on the planet is getting these errors


and yes ... DO call MS .... their tech support might be able to help you ... Vista can log *everything* and an error code or two will possibly narrow it down to *exactly*

 

[nullpointerus]

I'm not sure what you're all confused about.

I said multiple times that I'd call MS on Monday, and that's what I did.

...

I reduced my HW to the bare minimum. Any extra drives were removed. I reflashed the BIOS to a known-stable version, reset the DMI, loaded defaults, and then disabled any unnecessary devices and set the CPU/RAM to the lowest clocks possible (i.e. 1200/400).

Then I created three partitions:

1. Vista x64, 200 GB (primary partition)
2. Vista x64, 034 GB (test #1)
3. Vista x86, 034 GB (test #2, OS not yet installed)

Finally, at ~5:00 p.m., with two clean installations of x64, I was ready to contact MS support and work through the hundreds of errors I would eventually trigger.

...

So...I contact MS, work through the phone system, and finally reach a WU support rep. named John with an Indian accent. I booted partition #2, described the problem in detail, clicked on the Install Now button for the WU client update...

...and then...the impossible happens...

...I run into the same problem that happens everytime I find an expert to witness one of my problems: it worked. The updates succeed with zero errors in event viewer.

Go figure!

:shocked:


Anyway, after explaining what a partition is, I reboot to partition #1 and figure the errors *must* occur there. How would WU possibly succeed twice in a row after dozens of consecutive failures?! With a little of my usual bad luck, I hit Install Now and find the ~50 initial WU errors in event viewer.

Yes!! My PC is failing again! :thumbsup:

:Q

So the rep. loads up something called Easy Assist on my PC, and we go through the long process of explaining the difference between success messages in the WU client and the strange error messages in the event viewer. We find the errors...and he puts me on hold several times to consult with Vista support engineers or something.

By 6:30 p.m., I started getting hungry, so I grabbed supper during one of the (long) hold times. Then he comes back and we try some more updates, with the same results. Then he puts me on hold again, we reboot my computer, and then we check the WindowsUpdate.log file to see what is happening in more detail.

Apparently, the updates are succeeding...but we still have ~300 errors in event viewer.

By 7:00 p.m. he says he will consult with his superiors, and I end up being placed on hold, only to find myself at one of those automated phone menus...? I wait, and eventually I get myself transferred to Vista support on the same case number. This takes about an hour to get the new rep. back up to speed as he takes a long look through the errors and warnings in event viewer.

At long last, he states (very definitively) that these errors are nothing to worry about. I've never experienced them before, nor does anyone else seem to be aware of them. But apparently they're innocuous network errors (e.g. timeouts).

:Q




...




Note that I must still verify that the files are being updated. The threads I linked to earlier showing other people's experiences with this problem stated quite clearly that their files were NOT being properly updated even though WU reported success. I'll leave that for tomorrow.


Well, that doesn't explain the BSODs I was getting on clean installations w/o drivers, or the CD burning problems, or the other wierd issues I'm having with CCC. This WU thing could be a separate issue, of course. Heat/power problems from the power-hungry HD2900XT covering up the southbridge could cause the instabilities. But there's no plausible explanation for the CCC 3D settings problem.


Also, I get this on a clean installation, *randomly* for nearly *any* program:

http://img245.imageshack.us/my...nstallationerroop5.jpg

This includes software like Office 2007, Visual Studio 2008, 7-zip, various games, etc.

Is that a common and harmless Vista warning, or does it indicate a HW fault?

In other words, does anyone else get such notices w/ typical software installations?


Finally...one wierd thing...does anyone else get a completely random default order for their sidebar? Everytime I install Vista, it seems to have a different order. Sometimes the clock is the topmost component; sometimes the MSN News component is the topmost one. It seems like my clean installations from like six months ago always put the clock on the top, except when I overclocked too far, at which point my customized order would get messed up.

 

[nullpointerus]

Yep, as I suspected, the files appear to be the original, nonupdated versions!




Here's the updated file information for tzres.dll.

But here's what's actually on the hard drive:

C:\Windows\System32\tzres.dll

C:\Windows\SysWOW64\tzres.dll

C:\Windows\SoftwareDistributio...ds\(snipped)\tzres.dll

:Q

As you can see, it's in the downloads folder, but it was never actually copied to the system folders, which is where the OS and applications would normally find and load the DLL.


Looks like another "quick" phone call to MS tomorrow.

(At least I can reuse my case ID so we won't have to start from scratch.)


UPDATE:

It appears that there's a WinSxS folder for the XP/Vista feature that supports multiple DLL versions, and an updated tzres.dll file is installed to a WinSxS subfolder. Can anyone tell me if you still have the original tzres.dll in the System32 and SysWOW64 (if running 64-bit Vista) or if the System32/SysWOW64 file is the updated one?

I'd like to put this issue to rest once and for all.

 

[dclive]

Run MPSReports. Send me the resulting computername.cab file.

 

[nullpointerus]

EDIT:

LOL, didn't see it in your sig...I will send the .cab soon.

 

[nullpointerus]

I'm now getting a "side by side" error from Catalyst Install Manager:
http://img163.imageshack.us/my...iuninstallerrorix9.jpg

I don't remember seeing this error before.


UPDATE 1:

Here are the related errors in event viewer:
http://img163.imageshack.us/my...tallerroreventsss6.jpg

Also, I'll try running the sxstrace.exe as the events recommend.


UPDATE 2:

Parsed Output from sxstrace.exe

=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = C:\Users\Mike\AppData\Local\Temp\MSI9E11.tmp
AssemblyDirectory = C:\Users\Mike\AppData\Local\Temp\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Users\Mike\AppData\Local\Temp\MSI9E11.tmp.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\Windows\WinSxS\manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_49e6686552a1bf0a.manifest
INFO: Publisher Policy redirected assembly version.
INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.312".
INFO: Begin assembly probing.
INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_c905b7a4878399c1.manifest.
INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_c905b7a4878399c1.manifest.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.312".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.312_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.312_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Parsing Manifest File C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_c905b7a4878399c1.manifest.
INFO: Manifest Definition Identity is Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.312".
INFO: Activation Context generation succeeded.
End Activation Context Generation.

=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = C:\Program Files\ATI\CIM\BIN64\InstallManagerApp.exe
AssemblyDirectory = C:\Program Files\ATI\CIM\BIN64\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Program Files\ATI\CIM\BIN64\InstallManagerApp.exe.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
INFO: Reference: Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\Windows\WinSxS\manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_49e6686552a1bf0a.manifest
INFO: Publisher Policy redirected assembly version.
INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.312".
INFO: Begin assembly probing.
INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_c905b7a4878399c1.manifest.
INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_c905b7a4878399c1.manifest.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.312".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.312_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.312_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.MFC\8.0.50608.0__1fc8b3b9a1e18e3b\Microsoft.VC80.MFC.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC\Microsoft.VC80.MFC.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC\Microsoft.VC80.MFC.MANIFEST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
ERROR: Activation Context generation failed.
End Activation Context Generation.

=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = C:\Program Files\ATI\CIM\BIN64\InstallManagerApp.exe
AssemblyDirectory = C:\Program Files\ATI\CIM\BIN64\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Program Files\ATI\CIM\BIN64\InstallManagerApp.exe.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
INFO: Reference: Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\Windows\WinSxS\manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_49e6686552a1bf0a.manifest
INFO: Publisher Policy redirected assembly version.
INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.312".
INFO: Begin assembly probing.
INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_c905b7a4878399c1.manifest.
INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_c905b7a4878399c1.manifest.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.312".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.312_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.312_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.MFC\8.0.50608.0__1fc8b3b9a1e18e3b\Microsoft.VC80.MFC.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC.MANIFEST.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC\Microsoft.VC80.MFC.DLL.
INFO: Attempt to probe manifest at C:\Program Files\ATI\CIM\BIN64\Microsoft.VC80.MFC\Microsoft.VC80.MFC.MANIFEST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
ERROR: Activation Context generation failed.
End Activation Context Generati

 

[nullpointerus]

Eh...forget it!

:|

If the txt above tells you anything about the problem, then great, but I'm reinstalling over top of this partition and getting some work done. The rig can either work properly under a normal setup or give out under the strain...and I'll deal with any new errors at that time.

Of course, this means I must now start my ATI support ticket.

...but I can do that on a second partition. :thumbsup:


A big thank you to everyone who participated!

While I'm not 100% sure the issue was resolved, many questions were answered.

 

[robisbell]

did you ever run the WD diagnostics like I asked?

 

[nullpointerus]

Originally posted by: robisbell
did you ever run the WD diagnostics like I asked?

No, I never did get Vista x86 installed.

Thanks for reminding me!

I'm re-downloading the UBCD ISO from a different site and will try burning it once again.

 

[nullpointerus]

I get the UBCD to try loading the WD diagnostics, but it just drops me to a Q:\ prompt.





BTW, I give WesternDigital a big :thumbsdown: for not supporting 64-bit Windows.

 

[robisbell]

it should have autoran, somethings wrong then. the diagnostics on UBCD do not care what OS you are using it tests the drive itself.
I'm concerned that a bootable cd did not boot, that's a concern given the issues ythe system is giving you.
the optical drive is listed as the 1st boot option in bios correct?

okay, keep UBCD, wish my system was not a cobbled together piece of ****. the other option is to get this instead.

http://support.wdc.com/download/?cxml=n&pid=999&swid=30