Explorer.exe/Post-Mortem Debugger w/Dual Core enabled

[praeses]

This problem has been perplexing me for some time now. Originally I was having some instabilities with my system along with this one, however I nailed it down to a power supply problem. Upon acquring a new powersuply (OCZ GameXStream 700) all the other instabilities disappeared, however this last one still remains. When I enable dual-core support in my BIOS (default enabled), and view directories in Windows explorer, it crashes. Most of the time, Post-Mortem debugger comes up as well, with Dr-Watson and my system becomes completely useless until I reboot.

I have reformatted in hopes that it may have been a corrupt file, but to no avail. I have installed the newest driver from AMD's website, and have tried enabling and disabling Cool&Quiet support. It does not exibit these problems under other situations. I have dual Prime95'ed for 72hrs straight, then got bored of it, but no problems occured. Also memtest86's for a 24hrs, and of course, gamed a ton, including setting the affinity to the second core only. Also 3dmark, etc just for kicks, with no quirks either.

With that one exception, my system appears stable, anyone have any ideas?

My system is currently configured with the following:
AMD Opteron 165
ASRock 939Dual-SATA
2x1gig Crucial PC3200
ATI x800XL AIW AGP
Segate 120gig 7200.7 (had other harddrives connected, disconnected to see if it would help but nadda)
Windows XP Pro SP2

Chassis/Cooling altho not really relevant is:
Zalman HD-160
Zalman CNPS 9500LED (in this case, huge increase over the tight space with a XP-120)
Zalman VF900
OCZ GameXStream 700

 

[LiLithTecH]

This may be of help.

Microsoft KB896256

 

[praeses]

Thanks. I have just made the changes, will be testing them shortly (currently encoding, cannot reboot to re-enable the second core quite yet).

 

[praeses]

Okie,


Well after a decent amount of testing, it has not solved it yet, however it has reduced the occurances significantly. I have also been suggested to disable the "Launch folder windows in a separate process" and am testing that out as well. I have not had a crash since I disabled that but I have not done nearly as much multi-media moving around and whatnot. Typically when I load a heavy directory (well about 30-200gigs of small clips) it will load the files first then fetch the data for the dimensions, length, and so fourth. When its doing that, is usually when explorer locks up, or if I move one to a new folder and its just about finished writing it. I will post back after a few days with the results.

Thanks once again.

 

[praeses]

Sadly it has errored once in the last 24hrs, although considerably less, the problem still exists. The registry settings in the article provided seems to have made the most signficant impact with the reduction in errors and if I revert it (or change the final value to 1) the errors appear to occur much more frequently, almost entirely predictable. I currently am running as the KB article states, and looking for more alternative solutions.

Considering the registry setting made such a signficant impact I am thinking it is a software, or software configuration issue at this time.

 

[praeses]

I'm running a little batch file to set the affinity of explorer.exe to core 0 everytime I reboot (not often) and am running it now. I am grasping at straws for any work around I can. Also, setting my encodes to core 1 and WoW to core 0 when doing both <_< >_>;;
(Shh, I'm working, its just behind the orc's and dorc's).

 

[praeses]

FFDShow was the culprit. Rather annoying, removed and everything is peachy.