Windower or PoL Instant DC/Crash

[Mafai]

You know now that i think about it. I've been in dynamis-valk and when the manticores used heat breath, i have seen over 50% of the people there dc'd.

it was a common problem and eventually lead to us not farming those stupid ass manticores, and targeting the good shit like hippos and cactaur fulltime.

[Scorp]

Amusingly, installed process manager and POL viewer has stopped working message pops up...

I'm seeing a lot of information but nothing points at files accessed as far as I can see.

... the monitor thing seems to be an issue still. I went to print screen some of the information and when i pasted i got 2 complete desktops side by side. One showing only my background.

[Day]

I'll try to help more when I can get home and show you what you're looking for in PE.

Theres a way to enable a "bottom pane" and down there you can see current files accessed.

[Scorp]

I've got that open, its interpreting the information where I fall down.

Top line ~ WerFault.exe (4700)
next ~ pol.exe(2712): 740

Those are the names, I have the handles to. Top one is a process and bottom is a thread.

[Day]

One sec let me see if I have this on my work PC.

Ok you want to do CTRL+L or View > View lower pane.

Then highlight the POL.exe line.

In the lower pane you'll see a shitton of info, but you're looking at the lines starting with "file".

When POL crashes next some of those lines should turn red, and be on a certain .dat file.
Hopefully it wont just disappear from the list.

[Scorp]

Thanks for the help much appreciated.

At the rate I've seen today it shouldn't be long before I'll know.

[Scorp]

Two crashes later and I haven't found .dat file broken. >< Going to bang my head into stuff and consider a full re-install.

[Kohan]

Have you ever actually tried using a different 3D application? I know I asked a second time, but in scanning through the thread, I didn't see that acknowledged. Correct me if I'm wrong.

[Scorp]

Sorry for the delayed response, the problems became worse and needed a full restore back to basic vista install.

Yes it was across all 3d applications. It was 100% not a hardware fault as i've now tested everything through OCCT without errors.

Software wise I'm still not 100% sure how but it appears that Catalyst Control Centre (March and April versions) was in conflict with another driver on my system.

I've got the system stable after clearing all trace of it from my pc and running without it and a driver only install off amd's site for the gfx card.

Thanks for the help, if you know of any better work around or way to check conflicts I'm all ears.

[Day]

Good to hear =)