Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I thought win2000 (2128) was supposed to be the end of the Blue screen of death. Well I got 3 yesterday. Twice in the ntoskrnl and the other in win32k. Anyone else had this? Any ideas what may be causing it? One common factor seems to be Outlook2000 hanging momentarily before the crash. By the way its loaded on a Toshiba Tecra 8000 366MHz 128MB with over 350MB of virtual memory.
I have been running Windows 2000 Professional since Decemeber 24, 1999 and I've not see a single BSOD nor has it crashed on me.
Did you upgrade or did a clean install?
If problems persits you can always consider a clean reinstallation.Give more details about your installation and software setup. With that info more help can be provided to you.
0 
Well, I got my BSOD as soon as I installed it :( It was working fine TILL I tried to load the drivers for my modem, little did I know, that NON of my hardware worked properly, it said to upgrade the drivers to the W2K version... which ofcourse non of the vendors have yet... it didn't even go in to safe mode, it always gave it to me on NTOSKRNL till I decided to restore my image of 98 :) thank you Ghost :)
0
You are probably using a PCI modem... they often cause systems to freeze... and by the way... there are NO bluescreens in Windows 2000... If you found one, you probably use an "advanced micro systems" processor (AMD)... They suck...
0
Heh, well, I get the BSOD when I try to use my SB Live drivers. At boot time no less. So, reinstalled Windoze 2K, and of course, it gives me problems with my hardware. Being beta software however, I don't expect much ease of use, hell, I don't expect it after it goes gold either. I will most likely stick to 98 for another year. Oh, and the improvements in 2000 are pretty good, one of which being able to boot from a FAT32 partition. Very cool. Still, for server side apps, I will stick with Unix. Oh, and as far as AMD sucking, someone needs to look at those benchmarks on the Athlons....still I would like to see Intel's Coppermine processors, just for kicks anyhow. Personally, I don't buy Intel. Intel- Pentium III, Big Brother Inside.
0
AMD processors only seem to suck when talking to an Intel owner, which is just them covering up the fact that the realise they've paid far too much for a crappy processor
ATHLONS RULE - Coppermine processors (like every new Intel pentium at the start) are flawed!!
Maybe intel should spend more on R&D and not crappy adverts of guys acting stoned in silver suits - then they might have good processors!
0
Have to agree with David, I am running the Athalon 750 and it is intense. There are indeed BSODs in Win2k. I received one when installing Adaptecs EZCD v3.5 -- Required uninstalling the software and downloading the new ASPI drivers from Adaptec. No more BSOD.
0
Go to the Toshiba web site. They have a special section for W2K. There is new BIOS for your computer there. This BIOS is "beta". It will fix a bunch of W2K problems. I have a Toshiba Portege at work. Updating the BIOS fixes many things.
As far as other processor -- they all work. The Athlon is so new that I would check with my motherboard manufacturer for new BIOS. It is truely amazing what the right BIOS will fix.
0
yes, there are BSODs on W2K. And I have recieved them on clean installs (not with AMD processors). I also recieved them when installing a driver for my modem, however I believe you run the risk of getting them with any non compliant driver.
0
bluescreens of death usually mean something!!! that is to say that they are errors when the computer tries to do something, Write the errors down, that means writing VERMATIM all of the little numbers and letters that appear on the screen. Then go to the MS Site: http:\\support.microsoft.com and do a search of the error. 7 times out of 10, they will tell you what the BSOD is trying let you know. if that doesn't work, start yanking HW that isn't absolutely necessary for the computer to function: modem, sound, NIC, extra vid. cards and anything that is not necesary. If you have done that, flatten the drive and reinstall the OS and see what happens...
:) good luck :)
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
