Serious Problem with XP Pro x64

[slim142]

Hi

I have this weird problem with what is suppose to be "faster" than XP 32-bit.

Since the day I installed it, ~wednesday, everything seemed faster. However, after a day, I started noticing that sometimes when navigating through my other hard drives (not C), I would double click a folder and it would take several seconds to show me the content. Sometimes, the entire pc freezes for several seconds, I have to wait ~4 secs for it to show me the content of the folder. This happens with some folders and sometimes only.

At first, I thought it was because the HDD might be "waking up", but it happens repetitive times (at least once each hour).

Also, another problem that I have is freezing while surfing the web. Sometimes Ill be reading let say cnn.com, I would click on a hyperlink (in cnn) and the computer would freeze for ~5 seconds and after that open the new window. Happens with both IE 32 and IE 64.

Now, I thought this was going to be a faster system? XP 32-bit never took 4 secs to access a folder on another drive, maybe a sec or two and that was RARELY. IE never froze when opening a new window.

I dont know what could be wrong here. I have nForce 64-bit, GeForce 64-bit and the only driver I have 32-bit is for the Prelude sound card, it supports Vista 64-bit, but is just installed in the x86 folder. I dont know if this has any effect on my problem, which I hardly believe.
I have fully updated Windows, all patches and security fixes as well as additional components like XML stuff, WMP11, IE7, .Net Framework 3 etc

Any ideas?

[enteon]

maybe it is hardware related. you could thoroughly test the hdd for filesystem errors (scandisk with ALL options enabled, thus a lot of hours before the next boot :D) and have a look at the SMART data. or run prime95 or similar to check for computational errors. maybe they are temperature-related, reading all temperatures with speedfan (can read SMART too) or similar. ram-testing might give you the last pice of assurance, but memtest86 _will_ take _very_ long.

but i think your problem is merely related to a corrupted filesystem ;)

[tiro_uspsss]

well I can garauntee u it aint software/OS related :fact: :yepp:

[slim142]

Well the raptors never gave me any problem. However, will leave them with scandisk probably tomorrow overnight.

On the other side, temps are really high. 79c for the SB (idle) and 60c for the NB (idle), I havent take action because I will be going water cooling soon, but temps are worrying me more everyday. Because of that, I cant prime or linpak my computer.

EDIT: I left the PC off for 30 mins and temps are now 57c for NB and 72c for SB, both in idle. Seems like I been leaving the PC on for too long lol.

[Carson]

No, you should be able to leave your system on forever. It is running too hot because something is not running properly.

The hardware itself is quite likely okay. I'm slow to suspect RAM and mobo problems. However, XP x64 is a tricky beast to tame. It is hard to configure things just right, and something that never caused trouble with x32 might cause trouble now. So I'm saying that your hardware AND your software might be just fine (I really think they are) but you have some sort of synch problem—something you've done wrong yourself.

Of course, you do want to check all your installations: disks, cables, everything you can think of. Be sure everything is nice and tight. But I don't think you'll find anything; it's just good to cover your bases.

You've got SATA and PATA on that? You might try with just SATA to see if you learn anything.

There are a lot of loose reports, not properly authenticated, that AVG is having a lot of trouble right now. For sure you might be bumping into 32-bit software that feels uncomfortable with something on your system, and AVG is a suspect. Or maybe you're running something else totally different. But ask yourself if you might have some 32-bitware that you might disable for experimenting. Any games that you might suspect?

As for speed, I would not expect to see a whole lot of difference unless you were not only heavy into RAM but also using the system in such a way that the RAM was really required, perhaps as on a server. I run 8GB of RAM on my x64, but I never expected it to be very fast just because it was 64-bit OR because of the RAM. I was simply experimenting, and I was also intending that it should NOT be very slow.

I think for sheer speed a lean and mean 32-bit XP system would maybe be best for most casual use. Gaming XPs are fast because of what they DON'T truck around. I was interested more in multi-tasking muscle than in sports-car speed. But good luck. Try for smooth operation and not too much heat. THEN look to speed.

[slim142]

No, you should be able to leave your system on forever. It is running too hot because something is not running properly.

The hardware itself is quite likely okay. I'm slow to suspect RAM and mobo problems. However, XP x64 is a tricky beast to tame. It is hard to configure things just right, and something that never caused trouble with x32 might cause trouble now. So I'm saying that your hardware AND your software might be just fine (I really think they are) but you have some sort of synch problem—something you've done wrong yourself.

Of course, you do want to check all your installations: disks, cables, everything you can think of. Be sure everything is nice and tight. But I don't think you'll find anything; it's just good to cover your bases.

You've got SATA and PATA on that? You might try with just SATA to see if you learn anything.

There are a lot of loose reports, not properly authenticated, that AVG is having a lot of trouble right now. For sure you might be bumping into 32-bit software that feels uncomfortable with something on your system, and AVG is a suspect. Or maybe you're running something else totally different. But ask yourself if you might have some 32-bitware that you might disable for experimenting. Any games that you might suspect?

As for speed, I would not expect to see a whole lot of difference unless you were not only heavy into RAM but also using the system in such a way that the RAM was really required, perhaps as on a server. I run 8GB of RAM on my x64, but I never expected it to be very fast just because it was 64-bit OR because of the RAM. I was simply experimenting, and I was also intending that it should NOT be very slow.

I think for sheer speed a lean and mean 32-bit XP system would maybe be best for most casual use. Gaming XPs are fast because of what they DON'T truck around. I was interested more in multi-tasking muscle than in sports-car speed. But good luck. Try for smooth operation and not too much heat. THEN look to speed.


Well yeah everything worked fine on 32-bit XP. I have 6 SATA devices, no PATA devices.

It might all be coming from the temps? I have also noticed my PSU starts getting loud after 10 mins of turning the pc on, I believe my PC is getting really hot inside even with 4 fans running.

Hopefully, when I get the water cooling stuff running, this problems will be solved.

[informal]

Looks like driver issues to me.Can you verify all is ok in Device Manager?Also check if you have the latest sata/raid drivers for you board.

[Movieman]

Well yeah everything worked fine on 32-bit XP. I have 6 SATA devices, no PATA devices.

It might all be coming from the temps? I have also noticed my PSU starts getting loud after 10 mins of turning the pc on, I believe my PC is getting really hot inside even with 4 fans running.

Hopefully, when I get the water cooling stuff running, this problems will be solved.

That is where I would look first. To make sure that PSU is still "good" and not lessening voltage which would cause an amperage increased draw thru the board circuits itself.
Timeing on the change from 32bit to 64bit could be a coincidence to another problem and when you commented on the PSU my mind went "Bingo"
Try another PSU if you have one or can borrow one.

[slim142]

Looks like driver issues to me.Can you verify all is ok in Device Manager?Also check if you have the latest sata/raid drivers for you board.

I have two unknown devices. One is my Logitech Quickcam 4000 which I havent install the drivers yet, and the other one I have no idea what it could be. I double click it then go to details, it says "ACPI\ATK0110\101010"

Never had that on XP 32-bit

Also, Im using nForce x64 drivers 15.23 WHQL
Im not using PATA devices.

[slim142]

That is where I would look first. To make sure that PSU is still "good" and not lessening voltage which would cause an amperage increased draw thru the board circuits itself.
Timeing on the change from 32bit to 64bit could be a coincidence to another problem and when you commented on the PSU my mind went "Bingo"
Try another PSU if you have one or can borrow one.

Hmmm, I doubt the Corsair TX750 would die that fast, is not even a year old, but maybe who knows. It has also been working great, I have left my PC priming overnight many times on 32-bit and never had an issue. Maybe temps have to do A LOT on this, yesterday it was BURNING down here in FL and my room tends to get really hot.

Is there any program that will let me test the PSU by itself?

[Clint]

The only issues I've had with XP64 is related to "security" software, such as FW and AV. I would try to uninstall the AV and then the FW (disconnect from the net) to see if that changes anything, and then get into hardware issues. Those temps are way too high, so you'll need to look into that anyhow.

[m^2]

Do you have any exhaust fans?
It wouldn't be bad if you posted some pics of your machine.

[slim142]

Ill see if I can post some pics of my rig. It has one back exhaust fan and two intake fans at the bottom. One intake for the HDDs too.
I use ESET Smart Security 64-bit edition.

[Clint]

Ill see if I can post some pics of my rig. It has one back exhaust fan and two intake fans at the bottom. One intake for the HDDs too.
I use ESET Smart Security 64-bit edition.

Try uninstall that before you have a go at the hardware.

[saveus222]

i think its the anti virus.. open task manager and see what ur cpu/memory levels are at and which program is using it the most.. i bet its ESET

[slim142]

i think its the anti virus.. open task manager and see what ur cpu/memory levels are at and which program is using it the most.. i bet its ESET

egui.exe 9,620 Kb
All the other processes are normal (MSN, IE, svghost) however, there is one I have no idea what it is and is using like 46,512 KB, is called ekrn*32.exe
It sounds like the 32-bit emulator?

[Phr0s7]

1. Does it do this in safe mode?
2. It sounds more software related if xp32 worked just fine. Try unplugging every device but your primary HDD, does it still happen? If it doesn't, then try plugging one device in at a time, and see if you can narrow it down to one device.
3. Are you in a RAID?

[m^2]

ekern32.exe is ESET kernel. http://www.whatsrunning.net/whatsrunning/QueryProcessID.aspx?Process=15332

[Clint]

ekern32.exe is ESET kernel. http://www.whatsrunning.net/whatsrunning/QueryProcessID.aspx?Process=15332

Yes. I'm not surprised. I myself run Eset NOD32 v2.71 on all my boxes, x64 and 32. But I stay away from the "allinonewhambamsecurityantispywaredoodleding" packages, they tend to be a bit to ambitious with scanning and analyzing your system files.:shakes: