| Bottom | |
|---|---|
| Author |
Thread : Multiple Stop Errors
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) I would like to thank in advance any help anyone offers to my dilemma. I have scoured the net looking for solutions and could not find any.
|
|
Related Pr oduct
|
Register or
log in to remove.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Almost always a hardware and or driver issue.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Thanks for the tip Dave. Any tips on how to debug the dump files? I've been trying to determine which driver it is (assuming it isn't a hardware problem, which is a BIG assumption). In your experience, have problems like these been more often a hardware failure or a bad third-party driver?
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Thanks Dave! I'll try to determine which driver it is (if it isn't a hardware problem), and report back my findings. Hopefully, it's just a renegade driver.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) This article may help. It really could be either as far as the hardware or
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) I have decided to do a clean install of Windows 2000 Professional, to determine step by step (as tedious as it is) which drivers, when installed, begins this constant barrage of stop errors. However, I've run into a snag. After booting from the Win2K CD and installing the necessary files on a newly formatted partition, the computer reboots and begins loading windows. After the splash screen, the customary screen for entering setup information is displayed. Then the computer unexpectedly reboots itself. Upon the next reboot, the same thing happens again. Could this be indicative of a greater malady other than driver incompatibility?
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) More likely is non-compliant hardware and or system bios.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) I believe I have determined the reboots to be caused by the graphics card. If there is no hardware malfunction, but instead an incompatibility caused by windows attempting to identify the display adapter, what steps should I take to install Win2K when it keep rebooting before the files are copied after the splash screen?
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Try another graphics adapter to get you through the install.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Tried a different graphics card that is Win2K compatible, and the system now reboots by itself when windows is copying files from the CD to the hard drive during install after the splash screen or during the time windows is trying to detect hardware during install. Please advise.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Check that the mother board and system bios are Windows 2000 compatible.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) The 2 seagate baracuda 80GB hard drives are Ultra ATA/100. Integrated RAID function on the motherboard is DISABLED.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) You'll want to boot the Windows 2000 setup disks or CD-Rom. The set of four
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) I loaded the ATA100 drivers and re-installed Win2K. However, during driver install of Win2K setup, I received the following Stop error.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Check that the mother board and system bios are Windows 2000 compatible.
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) The motherboard and bios are windows 2000 compatible. I have switched the hard drives (slave(HD1) -> master, master(HD2) -> slave) to see if they are at fault. When I created a new partition on HD1, the os left 2mb unpartitioned. However, when I've tried to install win2k on HD2 previously, the os left 8mb unpartitioned. What might this mean?
|
|
More Information
|
Archived from groups: microsoft.public.win2000.setup (More info?) Stop errors are almost always caused by incorrect drivers, hardware failure,
|
|
More Information
|
|

