| Author |
Message |
Scott Sheppard
| | Posted on Wednesday, August 21, 2002 - 12:20 pm: | |
I applogize for the length, I just wanted to provide complete information. I am having problems with my Win2k professional freezing, no error message, no event log, just freezing, and I have to press the reset button. I have reformatted 4 times and reinstalled software. I have not added any hardware or software. It worked fine for 1 yr. before this problem. If you can help I will be very greatful!
Here are my hardware specs:
Abit KT7 - motherboard
2 sticks of 256 MB of RAM
3DProphet II MX - Video Card
Soundblaster Live Basic - Sound card
D-link DFE-500TX PCI Fast Ethernet Card
Western Digital 40GB, and 20GB - Hard Drives
Acer 12*8*32 CDRW
A 50X CDROM
AMD Athalon 900MHz Processor
Here software I have had installed:
Sound blaster CD for Win2k
Hercules driver for video card
Adobe 5.0
office 2000 Professional
Roxio CD creater 5.0
Zone Alarm
Norton Antivirus
Via HM - Hardware monitor came with mother board
Frontpage 2000
AOL instant messenger
WinAMP 3.0
ALL windows updates
Winzip evaluation version
I have tried:
-Monitoring the system and chip temp. with the hardware monitor (no overheating problems)
-Opening the case and putting a large box fan blowing right in the case(just in case)
-Reformatting the whole HD four times and replacing windows, programs, and all drivers
-Uninstalling drivers one at a time to see if one is causing the problem
None of this has worked |
win
| | Posted on Wednesday, August 21, 2002 - 12:40 pm: | |
have you tried to fdisk /mbr the master boot record as well? repartition the C: drive as well and format Fat32, just in case it's got something in there? use a win98 boot disk to do that. then try setup on win 2k after pulling out every other piece other than the cpu, memory, video, the hard drives and the cd rom drive, then see if it locks up. add you programs. see if it locks up there, and then add the hardware. 1 at a time. this is difficult to troubleshoot from what you're saying, so if you add all the hardware first, then the software, you don't know where the problem is, normally, i try the hardware first, but in certain cases, i reverse it just as i have described, in order to eliminate the software being an issue with a piece of hardware. once it locks up, i have a good idea which piece is in conflict. but still, it takes time.
if you have not tried the hardware 1 at a time first, then do that first. since it could be one of those failing. then the software method.
notice i have way too much time on my hands, heh. |
|
