fatal file error

  • Thread starter Thread starter aixvms
  • Start date Start date
A

aixvms

There is a Dump.txt file on my computer which causes two types of
crashes...The file exists in the Windows directory (not in a
subdirectory)....If I call up a directory of files, the normal response from
Windows if i place the cursor over a file name, is to display a small
rectangular box with file info...If I place the cursor over this Dump.txt
file, the cursor gets stuck and after about two minutes, windows crashes with
a "kernel stack inpage error", necessitating a reboot...Similarly, if McAfee
antivirus software is doing a scan of all files on the computer, when it
reaches this file, it freezes and after about a minute, windows crashes with
the aforementioned error... What to do ? I can't try to delete the file
since windows crashes when i place the cursor over it's name.
 
How does a text file (.txt) cause a crash? Either it's not really a text
file or there's more to the story.
 
aixvms said:
There is a Dump.txt file on my computer which causes two types of
crashes...The file exists in the Windows directory (not in a
subdirectory)....If I call up a directory of files, the normal response from
Windows if i place the cursor over a file name, is to display a small
rectangular box with file info...If I place the cursor over this Dump.txt
file, the cursor gets stuck and after about two minutes, windows crashes with
a "kernel stack inpage error", necessitating a reboot...Similarly, if McAfee
antivirus software is doing a scan of all files on the computer, when it
reaches this file, it freezes and after about a minute, windows crashes with
the aforementioned error... What to do ? I can't try to delete the file
since windows crashes when i place the cursor over it's name.
Click to expand...


Looks like a logical drive error

try this


open a command prompt

then enter


chkdsk /f

you will then be asked if you want chkdsk to run at the next reboot


say yes (y)

then reboot the machine

if there was a logical error...it should be fixed


If that does not fix the problem...
I'd run a harddrive diagnostic...
you should be able to download that from the website of your harddrives'
manufacturer
 
thanks for your input....i ran chkdsk without the /F command and it indicated
there were file problems to be fixed with /F..I then ran /F command to fix
the issues, but a subsequent run of just chkdsk indicated problems were still
present. HOWEVER, via the CMD prompt, i used the DEL command to delete the
file causing my crashes...To my surprise, the file was deleted and now mcafee
can do a full scan of the drive without errors.
 
aixvms said:
thanks for your input....i ran chkdsk without the /F command and it indicated
there were file problems to be fixed with /F..I then ran /F command to fix
the issues, but a subsequent run of just chkdsk indicated problems were still
present. HOWEVER, via the CMD prompt, i used the DEL command to delete the
file causing my crashes...To my surprise, the file was deleted and now mcafee
can do a full scan of the drive without errors.
Click to expand...


I am glad you got it

I think however that chkdsk /f did infact fix the problem

the problem with running chkdsk from a running instance of Windows...
is that due to the dynamic nature of the operating system...
"errors" will often be found simply due to the changing nature of the OS

at any rate...your system will hopefully be OK now
 
Back
Top