re: Question about 'Top reasons for random, fatal crashes in Windows XP and Windows 2000'
Wednesday, March 9, 2005 at 8:21 am
Windows XP Annoyances Discussion Forum
Posted by saimhe
(2 messages posted)
> This IS a RAM issue, guaranteed.
If you are so cathegorical, consider this:
I recently experienced the "BCCode: 1000008E ..." multiple times. This is an Intel-based
system (overclocking almost impossible) with 1 G RAM that was extensively stress-tested
about a month ago, a SATA hard disk and Radeon 9600 SE.
The problem occured during defragmentation. O&O Defrag was busy with one of logical
disks (the said disk is moderately partitioned). Then, at some point -- no blue screen,
just an immediate reset; after logon the error codes are presented.
After that I couldn't defragment that logical disk at all -- the computer resets
immediately after defragmenting begins. Because it was an important task, I switched
to Windows defragmenter and it succeeded somehow, though with almost unacceptable
quality.
I will omit further details; however, finally I was able to pin-point the problem.
It is an ordinary file on disk, about 200 KB in size. ANY access to it yields immediate
reset (read its contents with "copy" or console-based text editor, or its access
rights with "cacls", etc.). Scandisk does not find any errors on the disk and I don't
know any alternatives.
Most likely I will try to back the file up with NTFSDOS (contents are unique, old
and precious) and then delete it. If even deleting is impossible, then, I still am
able to copy the remaining files manually and reformat the volume afterwards. (*arrrgh!*)
After all this I begin to believe that a poorly written kernel-space driver can eventually
invoke any error :)
|
All messages in this thread [show all]
 |  | | | | | |  | re: Question about 'Top reasons for random, fatal crashes in Windows XP and Windows 2000' (saimhe: Wed, Mar 9, 2005, 8:21 am) |
| |
| |
Return to the Windows XP Discussion Forum
|
|
