Win xp funky problem

[ThE_MaD_ShOt]

I have a very weird problem I can't seem to figure out. I have one of my systems running Win xp pro sp3. The problem is that when I view pictures with Microsoft Picture and Fax Viewer the Gpu will freeze. Most of the time it will recover and pop up the box in the pic at the bottom of this post. Other times it will lock the whole system and the monitor will shut off. Now the kicker is that is the only time I have a problem. Under gaming and such it is fine. I can view pics just fine like on this site and such. I just have the problem when I use the Microsoft program to view pics. I can use IrfanView with no problem. Also it doesn't matter which drive in the system I try to view pictures from. System specs as follows

Asus A8n Sli Premium
A64 x2 4200+
3 gb ( 2x 1gb and 2 x 512 mb ) pc3200
Radeon Hd 3650 Cat 11.12
Win Xp pro sp3.

 

[OnePostWonder]

If you go to the Administrative Tools and open Event Viewer, does anything come up there?

 

[ThE_MaD_ShOt]

Okay I didn't see anything sticky out to me in there, so I cleared eveything. now I am going to run the program till it crashes and see what pops up.

 

[ThE_MaD_ShOt]

That time it locked and screen shut off. had to do a hard reset. Nothing in event viewer relating to it.

 

[OnePostWonder]

That time it locked and screen shut off. had to do a hard reset. Nothing in event viewer relating to it.

Wow, that's quite a hiccup it's having.

I'm not sure if this will help, but it's worth a try until you get someone a bit more versed in that problem in this thread.

Go to the volume with your OS on it in My Computer. Right click that volume, go to Properties then Tools. Under Error-checking, click Check Now.

 

[ThE_MaD_ShOt]

Gotta restart. Needs full access to the drive. brb

 

[OnePostWonder]

Gotta restart. Needs full access to the drive. brb

Sorry, forgot to mention Admin privs are required

 

[ThE_MaD_ShOt]

Well that didn't help. Now the other thing is sometimes it locks of the first pic ( not often) other times it could be the 20th or so pic before it locks. Also I can click on a pic and let it open that pic and it can stay on that one all day and not lock. Just when I am using the program to scroll through to find a certain pic is when it decides to lock. But like I said if I use another program all is good with no locks.

 

[OnePostWonder]

When did this problem start?

 

[ThE_MaD_ShOt]

About 3 days ago. I haven't installed any new hardware or software except updated Boinic to the Wcg version. Other then that everything is as it was when Windows was installed on here.

 

[Norton]

Did you check your memory utilization?

Check Task Manager and GPUZ (new GPUZ version tracks memory)- sounds like your memory is filling up causing a lockup.... had a problem like this when I tried scanning a large photo at high resolution a while back on a much older system

 

[OnePostWonder]

I was actually debating whether or not to tell you to run a pass on MemTest to see if it comes up with anything when I saw Norton's response.

That will take a bit more time than the other things I've mentioned, so let Norton or others run through it with you for a bit; they too may suggest MemTest.

 

[ThE_MaD_ShOt]

I try that and see whats going there. This is going to be no simple cure I can feel it. The only way to actually "reinstall" the program is to kill windows and do a fresh install, which I am not going to do. Everything else works fine so i'll keep using the other program for now and if I find a cure great of not oh well. I don't think it's a mem problem due to the fact that I have no problems anywhere else with the system. Also I can use another program to do the same job and it works fine. The problem seems to only be with that program.

 

[OnePostWonder]

I try that and see whats going there. This is going to be no simple cure I can feel it. The only way to actually "reinstall" the program is to kill windows and do a fresh install, which I am not going to do. Everything else works fine so i'll keep using the other program for now and if I find a cure great of not oh well. I don't think it's a mem problem due to the fact that I have no problems anywhere else with the system. Also I can use another program to do the same job and it works fine. The problem seems to only be with that program.

Yeah, I agree with that. Since the problem is central to that program, it's unlikely it would be a hardware issue.

Maybe you should just run MemTest to give yourself a break from it

 

[ThE_MaD_ShOt]

Lol if I run memtest it may pop up another problem and break the whole system

Maybe I will try a different vid driver since it does pop up the vpu recover box.

 

[Norton]

I try that and see whats going there. This is going to be no simple cure I can feel it. The only way to actually "reinstall" the program is to kill windows and do a fresh install, which I am not going to do. Everything else works fine so i'll keep using the other program for now and if I find a cure great of not oh well. I don't think it's a mem problem due to the fact that I have no problems anywhere else with the system. Also I can use another program to do the same job and it works fine. The problem seems to only be with that program.

I just opened 15 or 20 photos in rapid succession with photo viewer on my rig- GPU Memory Usage (dedicated) went up from 200MB to 400MB (increase w/each photo) and stayed there- it dropped steadily back to 200MB as I closed each photo.... don't know if this is causing your crash but maybe with that AGP card and its memory it's an issue?

*note- I used GPUZ 0.5.8 to check it with

 

[ThE_MaD_ShOt]

My card isn't Agp, It's a Pci-e with 1gb of mem. I think that box is a generic box. Heres a screen for this system.

 

[Norton]

Check sensors page in GPUZ

 

[Mussels]

did you disable page file or any tweaks like that?

 

[ThE_MaD_ShOt]

Well new drivers didn't help.
I'll check the mem now.





I don't have a memory load under sensors just gpu load.


Mussels, no I didn't. There are no tweaks to this system.

 

[temp02]

Probably not the best news but I've seen a system doing that ever since Catalyst 10.8, everything is fine except viewing pictures with the default XP viewer (small pictures work, large ones sometimes appear corrupt and /or transparent, and ultimately a BSOD or driver recovery).
No other drivers newer than the 10.7 fixed this issue (not even the latest betas), so I'm pretty sure you had this issue for longer than you know, you just didn't noticed it before.

As a side note, the latest betas resolve the issue with windowed applications not being V-Synced, but introduce the bug of pop-up/on-top windows lag everything.

 

[ThE_MaD_ShOt]

Probably not the best news but I've seen a system doing that ever since Catalyst 10.8, everything is fine except viewing pictures with the default XP viewer (small pictures work, large ones sometimes appear corrupt and /or transparent, and ultimately a BSOD or driver recovery).
No other drivers newer than the 10.7 fixed this issue (not even the latest betas), so I'm pretty sure you had this issue for longer than you know, you just didn't noticed it before.

As a side note, the latest betas resolve the issue with windowed applications not being V-Synced, but introduce the bug of pop-up/on-top windows lag everything.

You know you could be onto something there. It could have been doing that for awhile. Think I will try dropping the driver back and see what happens.

On a side note. I was thinking about it last night and came to the conclusion that it can't be the system memory or anything related to the mb. I just remembered I have done some hardware changes. (small one) I swapped out the motherboard and mem due to the system wasn't powering down. It would shut down ( get to the windows is now shutting down screen) but wouldn't power off. Done some investigating and found that was a common problem with the mb I had in this system (A8n-e). So I rip out the other motherboard and swapped this one in and booted back up with the same windows install. It actually worked great and I didn't even have to reactivate. And that took care of the powering down issue. I haven't really used this system much until the swapping around. Maybe that's why I never noticed the problem before.


Also if that is what it is, then i'll just stick to using IrFanview.