Windows XP x64 Locks Up

[rabrittain]

One of my computers (BigDog000) is dual boot: XP Pro (32 bit) and XP x64. I'm a "Distributed Computing" geek, and all my computers run 24/7 at 100%. I rarely use the 64 bit OS. I made the one machine dual boot just to see if I could and to learn a few things about 64 bit.

Within the distributed computing realm there is a project called Primegrid ( http://www.primegrid.com/ ).

BOINC (Berkley Open Infrastructure for Network Computing ( http://en.wikipedia.org/wiki/Berkeley_Open_Infrastructure_for_Network_Computing ) is used to attach to Primegrid, and people can participate in the search for very large prime numbers.

On 03/15 there is a race on Primegrid. In order to participate in the race, one must use a 64 bit OS. I would like to join the race, and I have been evaluating Win XP x64 to see if I can. I have discovered that if I boot up the OS and leave the computer on and inactive (just on), it locks up after about half a day. The mouse pointer freezes; it won't move. The is no keyboard action; Ctrl-Alt-Delete does not even work. It is necessary to turn the computer off with the power button. Then, I wait at least 1 minute and reboot the machine.

When I run the 32 bit XP pro on the machine, it can run at 100%, 24/7 for weeks without a problem - I don't think I have a hardware problem. The 2 OS's are installed on different hard drives - maybe it's a hard drive problem.

Any suggestions would be appreciated.

 

[KeypoX]

vista or windows 7 or ubuntu

 

[rabrittain]

Thanks for replying, KeypoX! Because you are a platinum member, I will take your comment to heart. There is also a well respected member on the Distributed Computing forum who uses 64 bit versions of the operating systems that you mentioned.

I would like a little more elaboration on what might be wrong with XP x64 and whether or not there is hope that it will be fixed.

 

[ViRGE]

rabrittain, the fundamental problem with XP64 is that it was basically a test-run of 64bit Windows. It was never released at retail and hence never received retail support from MS, and since it's actually based on Win2K3 (as a companion for 64bit 2K3 Server), it's not quite XP in spite of what the name implies.

Ultimately you're not going to find any support for it. Application developers generally won't test for it unless, and most hardware manufacturers simply skipped it entirely by deciding to write their Vista/7 drivers as 64bit capable rather than porting their 32bit 2K/XP/2K3 drivers to 64bit.

You can still use it of course, but there are very few problems you'll be able to get help for. Any driver problems at this point in time will basically last forever.

You're much better off using the 64bit versions of Vista or Win7, both of which have wide application and driver support.

 

[pcslookout]

Take it from someone who went back to Windows XP 64 bit. It is just not a good idea to use. There is plenty of drivers and programs that will not work or work very well. It not a good OS. It may seem like it at first but in general it is not. There a lot of things that just won't work anymore with Windows XP 64 bit.

Not worth the trouble or time to use Windows XP 64 bit anymore. Even if you can get everything working fine. It would really suck 2 years from now having stuff not supported and not working. Then you will have to start all over again.

 

[Emulex]

you sure XP-64 wasn't a workstation version of windows 2003 server 64bit? it looks awefully similar.

 

[ViRGE]

you sure XP-64 wasn't a workstation version of windows 2003 server 64bit? it looks awefully similar.

That's exactly what it is; it's a workstation distribution of Server2K3 x64.

 

[rabrittain]

Thanks for replying ViRGE, pcslookout, and Emulex! Your comments have given me some real insight.

I don't require much from the XP x64 OS: I would like for it to be reasonably stable. I would like to be able to use it to run some of the 64 bit BOINC projects. I will know in less than a week if that is possible.

The problem I've been experiencing may be hardware related. The associated video card is an ATI All-in-Wonder X1900. Today, I was watching TV on the computer from within the XP Pro 32 bit environment. After a couple of hours, the system locked up. The picture on the monitor froze; the sound stopped, and the keyboard and mouse would not respond. I used the soft reset button to reboot the system. I have continued to watch TV on it for the last 2 hours.

Recently, I had some overheating and stability issues, and, last week, it was necessary for me to remove the heatsink and clean it. It had been running fine for almost 4 years before that. The thermal insulating material had been generic white paste. I cleaned that off the heat sink and cpu, cleaned some dust off the fins, and re-installed the heatsink with Innovation Cooling Diamond 7. I used the ICD7 as recommended: I put a pea-sized glubule in the center of the cpu and smushed it while applying the heat sink with a back-and forth twisting motion. I latched the spring on the heat sink. It's my understanding that it takes a little while for the ICD7 to properly spread out and bond between the cpu and the heat sink.

I booted the x64 OS on Tuesday, 03/09, at noon, and left it on, sitting idle. It was still running when I checked on it on Thursday morning, 03/11, ~0730. I rebooted it and started BOINC. The computer ran at 100% untill the middle of the afternoon.

It could be that the heat sink is not properly seated yet.

I'm going to go ahead and consider installing XP x64 on another machine to try to see if this freezing problem is characteristic of the OS, or if it is a hardware problem.

Thanks again everybody for all your input!

 

[JackMDS]

While the comment mentioned above are the reality of the XP x64 release, your problem does "smell" as an Hardware problem.

To save time you might consider few runs of stress tests.

Otherwise, look at the device manger and get rid of hardware that you do not need. Also look at the StartUp and make sure that there is applications that you do not use that load at StartUp.

BTW. If you are a student you probably can get Win7 Premium x64 for a very good price.

 

[Modelworks]

The problem I've been experiencing may be hardware related. The associated video card is an ATI All-in-Wonder X1900. Today, I was watching TV on the computer from within the XP Pro 32 bit environment. After a couple of hours, the system locked up. The picture on the monitor froze; the sound stopped, and the keyboard and mouse would not respond. I used the soft reset button to reboot the system. I have continued to watch TV on it for the last 2 hours.

Don't use it for things like tv tuners because the drivers are not written properly for the OS.


More from the XP x64 isn't a good OS crowd I see. Ignore them , they are typically people that tried to use it for a gaming OS and it was never designed to be a home user OS. The OS is as solid as any other, I and others have used it on workstations for years without problems. What you have is a hardware issue.
Look in event viewer to see if there are any clues.
If xp 32 runs fine then xp 64 should too.

 

[theevilsharpie]

Windows XP x64 edition is a 64-bit desktop edition of Windows Server 2003. It is still supported, it does have drivers available, and it is a stable and mature OS.

Having run 64-bit operating systems for years (including XP 64-bit), I've found that older ATI cards can be a bit flaky running in a 64-bit environment. Do you have any Nvidia cards you can try?

 

[rabrittain]

Thanks JackMDS, Modelworks, and theevilsharpie for getting back to me! I have started an assessment (to evaluate me as a worker), and I am 3 days in to a 20 day program. If I do well, DVR will haelp me get a steady job. That's a priority; I'm sorry that I didn't get back to you sooner.

I tend to agree with you; I believe that it's a hardware problem.

I haven't had time to install the OS on the other machine yet.

The cpu runs at 100% on most distributed computing projects. It's been a good way to stress test cpus. When I stress the computer this way, it doesn't last more than a couple hours before freezing up.

I don't think that I have a memory problem -- the same memory is used with both OS's.

A respected person on the Distributed Computing forum also suspects the video function. The 32 bit OS locked up the other day while I was watching TV. That doesn't happen often. I used the 64 bit OS some in 2006 for distributed computing projects without a problem. There was a different version of Catalyst and the video driver at that time. I can roll it back without much trouble. I'm not sure I understand it though. BOINC does not tax the video card. ... but you never know. (sorry -- no nvidia cards)

I have days off on Friday and Saturday. I'll be able to focus on the problem then.

Thanks for the suggestions!!