RE: IDE error
From: Carl Gross (anonymous_at_discussions.microsoft.com)
Date: 05/19/04
- Next message: daave: "service.exe"
- Previous message: Beamz: "playing wmv/asf files"
- In reply to: Jason Hall [MSFT]: "RE: IDE error"
- Next in thread: Jason Hall [MSFT]: "RE: IDE error"
- Reply: Jason Hall [MSFT]: "RE: IDE error"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 19 May 2004 11:29:15 -0700
The machine generated a file system structure error and
said it was corrupt and unusable. Event ID: 55.
Shortly after that, the machine posted a new bugcheck
error: 0x00000024 with an Event ID: 1001.
I think your idea of third party drivers might be really
close to the mark. I have the driver disk that came with
the motherboard. Should I use it?
>-----Original Message-----
>
>--------------------
>>From: "Carl Gross" <anonymous@discussions.microsoft.com>
>>Subject: RE: IDE error
>>Date: Mon, 17 May 2004 15:03:20 -0700
>>
>>Thanks for the help. I replaced the hard drive last
>>Friday (5/14/04) and it worked beautifully.
>>
>>HOWEVER, the machine was re-booted this morning with the
>>following error:
>>
>>The computer has rebooted from a bugcheck. The bugcheck
>>was 0x0000001e (0xc0000005, 0x804624e5, 0x00000001,
>>0x00000000) Microsoft Windows 2000 [v15.2195]. A dump
was
>>saved in C:\WINNT\Minidump\Mini051704-01.dmp.
>>
>>Any ideas (Anyone? Anyone?)
>-----------------------
>
>If I had a dime for every 0x0000001e posting I saw..... ;-
)
>
>You see, 0x0000001e bugchecks are almost always caused
by a third-party
>driver that has a little bug (or corruption) in it.
Because these errors
>often appear randomly and/or infrequently, it is
difficult to troubleshoot
>using the most widely known methods.
>
>Oftentimes (and yes, even I used to do this) the
resolution for the
>home-user is to simply "format the hard drive".
>This is a STRONGLY discouraged step, because of two
reasons (at least):
>1) An enormous amount of time and effort is spent to
rebuild the machine to
>get rid of an error that is often caused by ONE driver
>2) Rebuilding the machine generally results in re-
installing all of the
>drivers that were there before, potentially setting up
the machine for
>another BSOD
>
>If you equip yourself with a LITTLE BIT of debugging
knowledge, you will
>save yourself many hours in the long run....and be the
envy of all of your
>friends.
>(or, you can search through all KB articles
with "0x0000001e" in them and
>hope you find something that relates to your situation)
>
>**** LINKS ****
>Bugcheck Codes and Info:
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/ddtools/hh/
>ddtools/bcintro_3dkj.asp
>
>Debugging Tools Download:
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=7c6ec49c-a8f7-4323-
>b583-6a7a6aeb5e66&displaylang=en
>
>Debugging Tools and Symbols: Getting Started
>http://www.microsoft.com/whdc/devtools/debugging/debugstar
t.mspx
>
>ENJOY!
>
>--
>~~ JASON HALL ~~
>~ Performance Support Specialist,
>~ Microsoft Enterprise Platforms Support
>~ This posting is provided "AS IS" with no warranties,
and confers no
>rights.
>~ Use of included script samples are subject to the terms
specified at
>http://www.microsoft.com/info/cpyright.htm
>~ Note: For the benefit of the community-at-large, all
responses to this
>message are best directed to the newsgroup/thread from
which they
>originated.
>
>.
>
- Next message: daave: "service.exe"
- Previous message: Beamz: "playing wmv/asf files"
- In reply to: Jason Hall [MSFT]: "RE: IDE error"
- Next in thread: Jason Hall [MSFT]: "RE: IDE error"
- Reply: Jason Hall [MSFT]: "RE: IDE error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
