chkdsk

[sag]

I use Win 2k and was told to run chkdsk /r to fix a blue screen problem I am having. How do you run it. I have tried from a DOS box and it says that it can not run. I tried to run from pure DOS and it says the switch is not valid. I can run chkdsk from a DOS box without the switch just fine. It reports no problems...
Any ideas?
SAG

[r8500]

Boot to the windows 2000 cd, and choose the first repair option, the choose the consol. Once in the consol, you will be forced to log into the installation with the admin password.

Once you do that, type chkdsk /? and see what your option are.

One of them is to check and fix all problems, thats the one you want. However, if you tell us that the Blue Screen says, we might be able to help you figure out what is causing it.

[sag]

Thanks for the reponse.

Over the last 3 months I have had 4 BSOD on my Win 2000 professional system.
The first one said:
stop: 0x00000023 (ox0011012f, 0x00006858, 0x00000000, 0x00000000)
Fat_File_system
Beginning dump of physical memory

The second one said:
stop: 0x0000000A (0x00000018, 0x00000002, 0x00000000, 0x8044E395)
IRQL_NOT_LESS_OR_EQUAL
address 8044E395 base at 80400000, datestamp 40d1d19a-Ntoskrnl.exe

The 3rd one said:
Stop 0x00000050 (0xEB824000, Ox00000000, 0x804EB6c9, 0x00000000)
Page_Fault_in_nonpaged_area
Address 804EB6c9 base at 80400000, datestamp 40d1d19a-Ntoskrnl.exe

As you can see, two of them included the ntoskrnl.exe file...is there any significance with that?
This system has run flawlessly for about a year until now.

Any ideas?

[r8500]

is one of these happening more than once, or did these all just happen once, and other than that its been fine?

[sag]

No the first one happened on 9/29,
the second one happened on 10/28
and the last one happened 11/04.

[sag]

So far that has been the order...approximately once per month there about.

[r8500]

Once a month isn't too bad. I would run the check disk. Also go to www.memtest.org and run a memory test on the system

[sag]

You may be right about it being "not so bad" but from a computer that has not had any BSOD since it was built a year ago, this is disconcerting.

[ukulele]

Originally posted by sag
You may be right about it being "not so bad" but from a computer that has not had any BSOD since it was built a year ago, this is disconcerting.
A BSOD with windows XP is no different then other flavors. It's normally a programming glitch but could also be caused by bad ram, a flakey video card (they have ram too) or a faulty PSU (an UPS may help). Test the ram, watch the PSU voltages for a while, update the video drivers and don't overclock anything.

[BipolarBill]

I get BSODs about once a week. It's frustrating, but ultimately only sets me back a little. I know what caused these BSODs - bad drivers. I can't do much about them, so I try to tiptoe around the problems.