Win2K: Coping after the dreaded BSOD. Need help!

[mud]

Ok, it finally happened. I was doing some surfing after I threw in a CDR to do some burning, and BAM, I got the dreaded Blue Screen Of Death!

So then it proceeded to perform a memory dump. Afterwards it rebooted and I ran a scandisk on my NTFS drive. I don't know what it had to report since it ended too quickly for me to read.

This is my first time with any variation with an NT OS, so what do I do now to ensure that my system is fine? Should I do anything with the memory dump file or erase it?

Looking through my event viewer doesn't help me much since I don't know what i'm looking for anyway. I see alot of warnings and errors, but related to browers mostly.

Any tips? Can anyone recommend a free online how-to-be-a-sysadmin link? gracias...

 

[Motorheader]

You might want to check out this website:

www.i386.com

One of the best resources for NT out there.

 

[setaanbomb]

Blue Screens come and go. I occasionally see a Blue Screen when I am burning CDs and doing other various tasks. This is most likely due to my Adaptec SCSI drivers not being digitally signed. Of course if the drivers are not signed then you get no guarantees on compatibility.

Most drivers for Win2k are not stable as of yet. Only those drivers that are bundled with the Win2k CD are really guaranteed not to produce blue screens.

 

[WindBoy2000]

I dunno i burned close to 100 CD's and i had no problem
with the plexwriter 8x4x32x. maybe the driver for your CDRW
has conflicts with WIN2K

 

[yazz]

if you are using EZCD Creator then uninstall it and try NERO 5

 

[Supergax]

I turned off memory dumps because I ignore them. I have only had NT crash on me twice, and the time after the first crash the system was unbootable, so memory dump or not, I couldn't get to it on my ntfs hard drive. I usually just run defrag and scandisk, or do nothing at all. People seem so suprised that NT can blue screen, but after working at a computer lab at a college for half a year, I saw more NT blue screens than one could imagine. I figure with the abuse I saw NT take then, I'm sure a blue screen or two doesn't really matter.

 

[syf3r]

without knowing what the error message was, there's really no way to trace it to its source... was it a bsod critical error or was it just a stop error? stop errors aren't *as* bad as critical errors. i'm running 2000 on a home machine, and it's loaded with unsigned drivers (video, audio, cdr, nic, etc) and i've never had a bsod in 2000... did you make any changes to your system recently? did the cd-recording finish, or did it bluescreen in the middle of burning? perhaps a defective cdr disc caused burning to halt, and that crashed the machine.. i've seen stranger things... if you know the error message you got on the bsod, you can search for it on microsloth's technet, or look around win2000mag.com

-syf3r.

 

[mud]

Well, i'm more interested in what you're supposed to do after a BSOD other than run scandisk.

BTW, the report that scandisk goes by so quick in the end, I have no idea if everything was fine! Any got any input on this?


Also, I think i got the BSOD because I disabled cdrom autorun via regedit, which my adaptec ezcd software didn't like.

 

[Doh!]

You can trash that .dmp file. You can set the crash mode to "no memory dump", saving you sometime instead of twidling your thumb waiting for the memory dump to finish (especially if you have lots of memory).