Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BSOD

Status
Not open for further replies.

onebigdog

Technical User
Jan 16, 2003
65
US
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.
I have not found anything that specifically points to my BSOD issues in MS.
Any ideas?
onebigdog
 
Thanks for the info Bcastner,
However, when I opened a DOS box in Windows 2k and typed chkdsk /r it came back with this message:
The type of file system is FAT32
Cannot lock current drive.
Chkdsk can not run because the volume is in use by another process.
I also tried it from pure DOS with the statement that the switch is not valid?
Can I not run chkdsk /r with FAT 32?
If I run chkdsk without the /r switch, it runs and reports no errors. Any ideas?
onebigdog
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top