• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

System hangup

bassmanjp

Junior Member
Hi,

I'm having a strange problem with my computer. The system stops responding at various point. I don't get a blue screen. There's just no response from my computer, whatever I do (the mouse pointer won't move, ctrl+alt+del doesn't do a thing, but the most important is that the activity lights on my ram modules stop moving, they freeze at about 4 yellow stripes).

This thing happened when I first had my computer. It seemed to stop after a while. I thought it was an overheating problem, so I've changed to thermal paste for some arcticsilver5 and added a new fan to the case (I got 1 in front and 2 in the back). The CPU's running at 55 Celcius and the MB is at about 24 celcius, which is not high at all.

But now, for a few days, it started freezing more often. I used to be able to run my CPU for a week without restarting. Now, it seems to freeze at every 3 hours or so. I did nothing special, as far as I know.

I have no known virus (norton antivirus 2004 running, full scan completed) and no known spyware (ad-aware 1.5 se went through).


Here's a summary of my system:

CPU-Z Report

--------------------------------------------------------------------------------

CPU-Z version 1.28.3.


CPU(s)
Number of CPUs 1

Name AMD Athlon 64 3500+
Code Name NewCastle
Specification AMD Athlon(tm) 64 Processor 3500+
Family / Model / Stepping F F 0
Extended Family / Model F F
Brand ID 4
Package Socket 939
Core Stepping DH7-CG
Technology 0.13 µ
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE, SSE2, x86-64
CPU Clock Speed 2202.8 MHz
Clock multiplier x 11.0
HTT Bus Frequency 200.3 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 2202.8 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 128 bits



Mainboard and chipset
Motherboard manufacturer ASUSTeK Computer Inc.
Motherboard model A8V Deluxe, Rev 1.xx
BIOS vendor American Megatrends Inc.
BIOS revision 1009.007
BIOS release date 12/22/2004
Chipset VIA K8T800 Pro rev. 0
Southbridge VIA VT8237 rev. 0
Sensor chip Winbond W83627THF

Graphic Interface AGP
AGP Status enabled, rev. 3.0
AGP Data Transfer Rate 8x
AGP Max Rate 8x
AGP Side Band Addressing supported, enabled
AGP Aperture Size 64 MBytes



Memory
DRAM Type DDR-SDRAM
DRAM Size 1024 MBytes
DRAM Frequency 200.3 MHz
FSB😀RAM CPU/11
CAS# Latency 2.0 clocks
RAS# to CAS# 3 clocks
RAS# Precharge 2 clocks
Cycle Time (TRAS) 6 clocks
Bank Cycle Time (TRC) 11 clocks
DRAM Idle Timer 16 clocks
# of memory modules 2
Module 0 Corsair DDR-SDRAM PC3200 - 512 MBytes
Module 1 Corsair DDR-SDRAM PC3200 - 512 MBytes



Software
Windows version Microsoft Windows XP Professional Service Pack 2 (Build 2600)
DirectX version 9.0c


HD is a maxtor 300 gig SATA drive
GPU is Asus v9999 ge (geforce 6800std + gddr3)
All my bioses and drivers are the latest.


Great thanks if you have any clue.

Oh, also, I runned memtest86 last spring from some cycles and nothing seemed wrong.

Some friends suggested me either the ram (but the test didn't showed any sign) or the power supply that could be defectuous (it's an Antec True430 (430 Watts), new from August 2004 (as all the other pieces).

Thanks.
 
Could be a HD error. May be as simple as wiggling that SATA cable. At my college we have the H.D. mounts in the front bays so students can just slide their drive in and work. If you take the HD out while the things running, it does the exact same thing. Just a thought...
 
I see nothing particular in the event viewer.

I get this system error in the log:
DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

but it doesn't seem to be linked with the hangup


here's today log:

18 avril, 2005 Microsoft Office 11 Faulting application winword.exe, version 11.0.6502.0, stamp 424d964d, faulting module winword.exe, version 11.0.6502.0, stamp 424d964d, debug? 0, fault address 0x0003da8c.
18 avril, 2005 Microsoft Office 11 Rejected Safe Mode action : Microsoft Office Word.
18 avril, 2005 Applicatio n Error Faulting application iexplore.exe, version 6.0.2900.2180, faulting module unknown, version 0.0.0.0, fault address 0x02a7f880.


18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 Service Control Manager The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
18 avril, 2005 Service Control Manager The EIO service failed to start due to the following error: The system cannot find the file specified.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM got error "%1055" attempting to start the service netman with arguments "" in order to run the server: {BA126AE5-2166-11D1-B 1D0-00805FC1270E}
18 avril, 2005 DCOM DCOM got error "%1055" attempting to start the service winmgmt with arguments "" in order to run the server: {8BC3F05E-D86B-11D0-A 075-00C04FB68820}
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
18 avril, 2005 DCOM DCOM was unable to communicate with the computer PIERRE using any of the configured protocols.
 
Nothing is moving inside the computer..

But I guess it is an HD problem.


Because I can run memtest86 for hours without having any problem..

So, I think that my memory is fine and that my power supply can handle the power demand.


Could an HD problem like this be caused by Windows XP Pro?


When I search for the meaning of the DCOM error I get, it says that my HD may not have been properly installed at first in windows.

And this error is recurrent.

Are there known issues between SATA drives and windows XP?

thank you.


edit:

just to add some info:

1- yesterday, i had the freeze problem at windows log-in screen. First time this happened.

2- I noticed that the system systematicaly freezes faster if I run Seti@Home (in about 1 hour usually).
 
Just to add in my two cents...
But I have the same CPU and mobo and HD...
My CPU is OC'ed and runs at 40C it only hits 50C at full load for long periods of time...
I have 7 case fans and use the stock fan with aritic silver 5...
So you may have more of a heat problem than originaly thought...
Sidenote: I myself do not really know how hot is hot for this CPU but I thought you would appreciate the comparison with mine...
...
..
.
 
thanks for the input...

A new heatsink and fan for the cpu can't be bad for the system.

I might try then.

edit:

just one question:

If it was an overheating problem, wouldn't the system shut down instead of just freezing?
 
Just to add...


I tried to run Prime95 torture test from Windows, but the system freezed after about 35 minutes. But, I could run Prime95 torture test for 12 hours while booting from Ultimate Boot CD.

I guess the CPU and RAM are fine. I always think that the system is not over heating.


What I also noticed:
I cannot play a SNES emulator (ZSNES - windows version) for more than 25 minutes before it freezes.
But I was about to play the ZSNES dos version, while reading the rom from a floppy disk for about 1 hour and 30 minutes without any problem.

So, I think there may be some problem with the HD. I will try later on today playing the ZSNES windows version while booting the ROM from the floppy disk.

I've installed an old version of Windows XP on this computer. The SATA drivers were not on the WinXP disk. I add to manually add them and it was a real trouble. Could it be an issue between SATA HD and WinXP?

Thanks again.
 
Just for follow-up...


After all, It seems it was just a running OS problem (driver probably).

I created a partition and installed WinXP on it, installing only the latest drivers from the web. And everything's working fine since then.

I reinstalled the same software.

I really can't figure out what was exactly the problem, but now it's working just fine !

thanks to everyone who gave me moral support 😉
 
Back
Top