stalker
July 26th, 2004, 06:32 PM
Uhh, something dreadful happened today.
It is again almoust 100 % related to my hard-disk, and communication between hard-disk and other devices, and OS.
1. It happened today, when I was copying some file from C:\ to E:\ partition. It was some 6 MB file, "encrypted container/volume", containg various personal data (i.e., files and folders), made by well-known and trusted application called Cryptainer PE (from www.cypherix.com). Well, the system just frozen in the middle of copying (similar to when KERNEL_STACK_INPAGE_ERROR BSOD occurs, see number the paragraph number 3.), there was one window with "Disk is full" poping-up for few seconds (and it was/is more than 2 GB still free), and after that windows popup message, something like "External failure/exception, number C00000E4. Please, note that actual message displayed, including number is just for better imagination, I unfortunately didn't wrote it down, not I made screenshot of that window, as I usually do, well I couldn't actually.
After I clicked "Ok" on that error-message window, the system was "blank", meaning, only desktop was displayed, and nothing worked. Shell was terminated, as well as all other programs running at that time. I couldn't even execute Task Manager with Ctrl+Shift+Esc. So, I rebooter with "reboot-button", but here comes the most scary thing.
After rebooting, the pre-login window told me, that there is "no boot-disk available" (or something alike), and something about IDE related problem. I booted from floppy, but there was no disk (i.e. partitons) visible/available. Well, luckily after rebooting again, all seems to work normal again.
And here is log entry from my Windows XP EventViewer:
Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 26.7.2004
Time: 13:38:07
User: N/A
Computer: SYSTEM-F450J
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout period.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0010000f 00640001 00000000 c0040009
0010: 00000100 00000000 00002a4d 00000000
0020: 00000000 00000000 00000000 00000000
0030: 00000000 00000007
2. Let me also mention also one of the most common, resident and obvious problems, the FILE_SYSTEM BSODs (described in details in some other topic, I opened on Winforums:
"low-level format" - whole HD only, or possible only one (the one damaged) partition (http://forums.winforums.org/showthread.php?t=6124)
... which always occurs on these situations/events:
- when RESTARTING computer (and usually not when shutting it down, or logging-off, but sometimes also ...)
- AFTER "Saving your settings", and also few seconds AFTER "Windows is shuting down" popup window appears (yeah, I have set it to classic log-on)
- Strange, if I first log-off (or use "restart only-windows" feature some programs offer), and then reboot/shutdown from that window (Options), BSOD DOESN'T occur.
And it happens that always (one or more) of these files become corrupted (scandisk finds various errors)
Ntuser.dat.log, Default.log, Security.log, Software.log, System.log (and in previous Windows installation also IconCache.db, and sometimes also AppEvent.evt, and SysEvent.evt files)
in: D:\Windows\System32\Config\
Well about all that related to FILE_SYSTEM error on shutdowns - isn't just some API that is "responsible" for shutting down/rebooting computer, so how could this API cause BSODs ??
3. When I was wondering, and trying to figure out the reason/cause for all that troubles, I also try and disabled "disk caching" feature (Device Manager -- Drives -- Policies - !Enable write caching on the disk!), cause I thought, that caching could be the reason for disk corruption every time this BSOD occurs.
Well, I turned it off, but first time copying files without caching feature, I noticed disk operations was just too slow, and as th most important one other BSOD with note: KERNEL_STACK_INPAGE_ERROR occured, right in the middle of copying files (after OS freezing, that "announces" this kind of BSOD), so it seems this feature is better to remain enabled.
I googled a bit for this particular BSOD, and actually found some references, but they were all to general, and nothing to do with my configuration and OS setup in particular ...
But here is the main problem, after this KERNEL_STACK_INPAGE_ERROR occured for the first time (in three years using this computer and hard-disk), it starts occuring also on other situations, usually when copying large files from one partition to another.
Thanks for any hint about, or solution to my problems
It is again almoust 100 % related to my hard-disk, and communication between hard-disk and other devices, and OS.
1. It happened today, when I was copying some file from C:\ to E:\ partition. It was some 6 MB file, "encrypted container/volume", containg various personal data (i.e., files and folders), made by well-known and trusted application called Cryptainer PE (from www.cypherix.com). Well, the system just frozen in the middle of copying (similar to when KERNEL_STACK_INPAGE_ERROR BSOD occurs, see number the paragraph number 3.), there was one window with "Disk is full" poping-up for few seconds (and it was/is more than 2 GB still free), and after that windows popup message, something like "External failure/exception, number C00000E4. Please, note that actual message displayed, including number is just for better imagination, I unfortunately didn't wrote it down, not I made screenshot of that window, as I usually do, well I couldn't actually.
After I clicked "Ok" on that error-message window, the system was "blank", meaning, only desktop was displayed, and nothing worked. Shell was terminated, as well as all other programs running at that time. I couldn't even execute Task Manager with Ctrl+Shift+Esc. So, I rebooter with "reboot-button", but here comes the most scary thing.
After rebooting, the pre-login window told me, that there is "no boot-disk available" (or something alike), and something about IDE related problem. I booted from floppy, but there was no disk (i.e. partitons) visible/available. Well, luckily after rebooting again, all seems to work normal again.
And here is log entry from my Windows XP EventViewer:
Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 9
Date: 26.7.2004
Time: 13:38:07
User: N/A
Computer: SYSTEM-F450J
Description:
The device, \Device\Ide\IdePort0, did not respond within the timeout period.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0010000f 00640001 00000000 c0040009
0010: 00000100 00000000 00002a4d 00000000
0020: 00000000 00000000 00000000 00000000
0030: 00000000 00000007
2. Let me also mention also one of the most common, resident and obvious problems, the FILE_SYSTEM BSODs (described in details in some other topic, I opened on Winforums:
"low-level format" - whole HD only, or possible only one (the one damaged) partition (http://forums.winforums.org/showthread.php?t=6124)
... which always occurs on these situations/events:
- when RESTARTING computer (and usually not when shutting it down, or logging-off, but sometimes also ...)
- AFTER "Saving your settings", and also few seconds AFTER "Windows is shuting down" popup window appears (yeah, I have set it to classic log-on)
- Strange, if I first log-off (or use "restart only-windows" feature some programs offer), and then reboot/shutdown from that window (Options), BSOD DOESN'T occur.
And it happens that always (one or more) of these files become corrupted (scandisk finds various errors)
Ntuser.dat.log, Default.log, Security.log, Software.log, System.log (and in previous Windows installation also IconCache.db, and sometimes also AppEvent.evt, and SysEvent.evt files)
in: D:\Windows\System32\Config\
Well about all that related to FILE_SYSTEM error on shutdowns - isn't just some API that is "responsible" for shutting down/rebooting computer, so how could this API cause BSODs ??
3. When I was wondering, and trying to figure out the reason/cause for all that troubles, I also try and disabled "disk caching" feature (Device Manager -- Drives -- Policies - !Enable write caching on the disk!), cause I thought, that caching could be the reason for disk corruption every time this BSOD occurs.
Well, I turned it off, but first time copying files without caching feature, I noticed disk operations was just too slow, and as th most important one other BSOD with note: KERNEL_STACK_INPAGE_ERROR occured, right in the middle of copying files (after OS freezing, that "announces" this kind of BSOD), so it seems this feature is better to remain enabled.
I googled a bit for this particular BSOD, and actually found some references, but they were all to general, and nothing to do with my configuration and OS setup in particular ...
But here is the main problem, after this KERNEL_STACK_INPAGE_ERROR occured for the first time (in three years using this computer and hard-disk), it starts occuring also on other situations, usually when copying large files from one partition to another.
Thanks for any hint about, or solution to my problems