Blue Screen during Safe Mode

The blue screen of death appeared when I was working on something on my D drive (slave) and I rebooted and went into Safe Mode. So far, so good. I ran CCleaner and Spybot to clean everything out - it was clean. Suddenly, the blue screen appears while in Safe Mode too. It says:

A process or thread crucial to system operation has unexpectedly exited or been terminated.

If this is the first time you've seen this screen...etc.

Check to make sure any new hardware (haven't installed anything new) or software (nothing new either) is properly installed. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup options and then select Safe Mode.

Technical information:
***STOP: 0x000000F4 (0x00000003, 0x8A38D3E0, 0x8A38DD54, 0x80604418)

Beginning dump of physical memory

I have a master and slave drive installed. I rebuilt the computer about 6 months ago and haven't had any problems until now. It's worked perfectly fine. Here are some of my specs I know offhand (I'm on the blue screen, so I'm concerned about restarting to find the complete specs and making things worse):

Windows XP Home Edition (SP2) - all updates current
Pentium Dual Core 1.60 GHz, 1MB L2 Cache, 800 MHz FSB
Gigabyte S-Series Motherboard GA-945GCMX-S2


About 6 months ago, I bought everything brand new - motherboard, processor, DVD/CD drive, RAM and made sure it was all compatible and it's worked great until now. I've also tried googling my 0x0000000F4 message, but nothing shows up.

Does anyone have any idea how I can go about fixing this? I hate to just jump in and start trying stuff I'm unsure about. I'm kind of scared to do anything at the moment for fear of wiping out some invaluable stuff on my harddrive. I use this for work and have some items I don't even want to consider losing. Any help will be great appreciated!

 

thanks for responding so fast

Here's what's happened since I first posted. I tried to reboot and it wouldn't boot. In the startup screen under IDEs, it didn't list my main C: drive, but did list my D: drive. I shut down and unplugged my tower and went in and unplugged and replugged all my connections, then rebooted again.

This time, on the startup screen, it showed my C and D drives. (was starting to feel a little less queasy) It actually booted up and I could see my desktop and it seemed to be working normally. I quickly went into System Restore and reset my settings back a few days, hoping that would fix things. After the restore, it restarted - everything was looking good. I then went into system tools to run an analyze of disk deframenter to see if i could clean up things further. I received an error message during analyzing that said i needed to run scandisk or chkdsk. (No blue screen of death so far)

I inserted my Windows XP disk and rebooted to run the Recovery Console and chkdsk C: /r. I rebooted and hit 'r' for the recovery console.

I now see "Which Windows installation would you like to log onto (to cancel, press enter)?" but the only option is 1: D:/WINDOWS
Unfortunately, my Windows OS is on my C drive. For some reason, it's not reading that it's on my C drive. The queasiness is back.

I will try to download the data dump collection tool right now and gather the info if I'm able to boot back up. Thanks for you help.

 

Here is the info I got from the data dump. I am able to boot up "normally" for the moment, but it seems very unstable and extremely slow at the moment.

(I just saw your comment on unplugging the D drive, but will wait until you see this info before trying anything else)

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Comment: 'Dr. Watson generated MiniDump'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Debug session time: Sun Mar 16 09:30:24.000 2008 (GMT-5)
System Uptime: not available
Process Uptime: 0 days 0:31:39.000
...................................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(328.400): In-page I/O error ffffffffc0000013 - code c0000006 (first/second chance not available)
eax=7ffd6000 ebx=01eb2008 ecx=00000010 edx=fffffffe esi=00000021 edi=ffffffff
eip=7c96eded esp=00feeb28 ebp=00feebec iopl=0 nv up ei ng nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000286
ntdll!RtlpAllocateAffinityIndex:
7c96eded 8bff mov edi,edi
0:004> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
ntdll!RtlpAllocateAffinityIndex+0
7c96eded 8bff mov edi,edi

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
.exr 0xffffffffffffffff
ExceptionAddress: 7c96eded (ntdll!RtlpAllocateAffinityIndex)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 7c96eded
Parameter[2]: c0000013
Inpage operation failed at 7c96eded, due to I/O error c0000013

DEFAULT_BUCKET_ID: HEAP_CORRUPTION

PROCESS_NAME: explorer.exe

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The required data was not placed into memory because of an I/O error status of "0x%08lx ".

IO_ERROR: (NTSTATUS) 0xc0000013 - {No Disk} There is no disk in the drive. Please insert a disk into drive %hs.

EXCEPTION_STR: 0xc0000006_c0000013

STACK_TEXT:
00feeb24 7c94ef6d 01eb2008 00000000 00090000 ntdll!RtlpAllocateAffinityIndex
00feebec 7c931ab4 00000000 00000000 001020f0 ntdll!RtlpLowFragHeapAlloc+0x103
00feee14 7c8099df 00090000 00140008 00000114 ntdll!RtlAllocateHeap+0x80
00feee60 77f68b37 00000040 00000114 00fef274 kernel32!LocalAlloc+0x58
00feee88 77f68c9f 00feeeac 00000001 00000000 shlwapi!SHRegOpenUSKeyA+0x37
00feefb0 7c9f47ed 00feefe4 00000001 00000000 shlwapi!SHRegOpenUSKeyW+0x59
00fef238 7c9f475d 7007acc7 11d13202 8000d2aa shell32!CRegFolder::_RegOpenCLSIDUSKey+0x74
00fef26c 7c9f42e3 00d2005c 001020f0 40000000 shell32!CRegFolder::_GetPerUserAttributes+0x2f
00fef2a8 7c9f2710 00d2005c 40000000 00fef2cc shell32!CRegFolder::_AttributesOf+0x12b
00fef2e4 7c9f169f 00102100 00000001 00fef30c shell32!CRegFolder::GetAttributesOf+0xd8
00fef534 7c9f15f6 00d20034 00fef9bc 00000002 shell32!SHGetPathFromIDListEx+0xa7
00fef548 7c9f6660 00d20034 00fef9bc 000c210c shell32!SHGetPathFromIDListW+0x12
00fefbc8 7c9f718f 00d20034 00fefbf0 000c2108 shell32!_ILCloneInterruptID+0x38
00fefbe4 7c9f6f50 00d20034 00000000 01f3e140 shell32!CChangeNotify::AddInterruptSource+0x23
00fefc00 7c9f72d2 00000003 00d20034 01f3e170 shell32!CChangeNotify::AddClient+0x44
00fefc2c 7c9f7230 0003008c 00008003 0000100a shell32!CChangeNotify::_RegisterClient+0x87
00fefc5c 7c9f5009 00000478 00000328 7c9f4fa5 shell32!CChangeNotify::_OnChangeRegistration+0x4e
00fefc70 7e418734 00060062 00000401 00000478 shell32!CChangeNotify::WndProc+0x51
00fefc9c 7e418816 7c9f4fa5 00060062 00000401 user32!InternalCallWinProc+0x28
00fefd04 7e41b4c0 000a06f0 7c9f4fa5 00060062 user32!UserCallWinProcCheckWow+0x150
00fefd58 7e41b50c 005613d0 00000401 00000478 user32!DispatchClientMessage+0xa3
00fefd80 7c90eae3 00fefd90 00000018 005613d0 user32!__fnDWORD+0x24
00fefda4 7e4193e9 7e4193a8 00fefe20 00000000 ntdll!KiUserCallbackDispatcher+0x13
00fefdd0 7e419402 00fefe20 00000000 00000000 user32!NtUserPeekMessage+0xc
00fefdfc 7c9f4f98 00fefe20 00000000 00000000 user32!PeekMessageW+0xbc
00fefe3c 7c9f4ea6 00000000 00000000 00000000 shell32!CChangeNotify::_HandleMessages+0x43
00feff4c 7ca0a3b0 77f76f02 00000000 7c80995a shell32!CChangeNotify::_MessagePump+0x52
00feff50 77f76f02 00000000 7c80995a 00090000 shell32!CChangeNotify::ThreadProc+0x1e
00feffb4 7c80b683 00000000 7c80995a 00090000 shlwapi!WrapperThreadProc+0x94
00feffec 00000000 77f76e93 00ebf4d4 00000000 kernel32!BaseThreadStart+0x37


ADDITIONAL_DEBUG_TEXT: Enable Pageheap/AutoVerifer

FAULTING_THREAD: 00000478

STACK_COMMAND: ~4s; .ecxr ; kb

PRIMARY_PROBLEM_CLASS: HEAP_CORRUPTION

BUGCHECK_STR: APPLICATION_FAULT_HEAP_CORRUPTION_STATUS_IN_PAGE_ERROR_STATUS_IN_PAGE_ERROR

FOLLOWUP_IP:
ntdll!RtlpAllocateAffinityIndex+0
7c96eded 8bff mov edi,edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ntdll!RtlpAllocateAffinityIndex+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ntdll

IMAGE_NAME: ntdll.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 411096b4

FAILURE_BUCKET_ID: ntdll.dll!RtlpAllocateAffinityIndex_c0000006_HEAP_CORRUPTION

BUCKET_ID: APPLICATION_FAULT_HEAP_CORRUPTION_STATUS_IN_PAGE_ERROR_STATUS_IN_PAGE_ERROR_ntdll!RtlpAllocateAffinityIndex+0

Followup: MachineOwner
---------

eax=000000c0 ebx=7c910331 ecx=01347838 edx=7c90eb94 esi=00000548 edi=00000000
eip=7c90eb94 esp=0134824c ebp=013482b0 iopl=0 nv up ei ng nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000297
ntdll!KiFastSystemCallRet:
7c90eb94 c3 ret
ChildEBP RetAddr Args to Child
01348248 7c90e9c0 7c8025cb 00000548 00000000 ntdll!KiFastSystemCallRet (FPO: [0,0,0])
0134824c 7c8025cb 00000548 00000000 01348280 ntdll!ZwWaitForSingleObject+0xc (FPO: [3,0,0])
013482b0 7c802532 00000548 000493e0 00000000 kernel32!WaitForSingleObjectEx+0xa8 (FPO: [Non-Fpo])
013482c4 6945ada6 00000548 000493e0 003a0043 kernel32!WaitForSingleObject+0x12 (FPO: [Non-Fpo])
01348da0 6945aff1 0000039c 00000328 00000560 faultrep!InternalGenerateMinidumpEx+0x335 (FPO: [Non-Fpo])
01348dcc 6945b5d9 0000039c 00000328 01348de8 faultrep!InternalGenerateMinidump+0x75 (FPO: [Non-Fpo])
01349734 69456652 0000039c 00000328 01349754 faultrep!InternalGenFullAndTriageMinidumps+0x159 (FPO: [Non-Fpo])
0134af38 69457d3d 0134afa0 01eacd28 00000000 faultrep!ReportFaultDWM+0x4e5 (FPO: [Non-Fpo])
0134b420 694582d8 0134cb54 0134c268 ffffffff faultrep!StartManifestReportImmediate+0x268 (FPO: [Non-Fpo])
0134c48c 7c8633b1 0134cb54 ffffffff 00000000 faultrep!ReportFault+0x55a (FPO: [Non-Fpo])
0134cb2c 7c83ab20 0134cb54 7c839b09 0134cb5c kernel32!UnhandledExceptionFilter+0x587 (FPO: [Non-Fpo])
0134cb34 7c839b09 0134cb5c 00000000 0134cb5c kernel32!BaseThreadStart+0x4d (FPO: [Non-Fpo])
0134cb5c 7c9037bf 0134cc48 0134ffdc 0134cc68 kernel32!_except_handler3+0x61 (FPO: [Uses EBP] [3,0,7])
0134cb80 7c90378b 0134cc48 0134ffdc 0134cc68 ntdll!ExecuteHandler2+0x26
0134cc30 7c90eafa 00000000 0134cc68 0134cc48 ntdll!ExecuteHandler+0x24
0134cc30 7c96eded 00000000 0134cc68 0134cc48 ntdll!KiUserExceptionDispatcher+0xe (FPO: [2,0,0]) (CONTEXT @ 0134cc68)
0134cf30 7c94ef6d 01eb2008 00000112 00090000 ntdll!RtlpAllocateAffinityIndex (FPO: [Non-Fpo])
0134cff8 7c931ab4 01549718 00000112 00000000 ntdll!RtlpLowFragHeapAlloc+0x103 (FPO: [Non-Fpo])
0134d220 774fd023 00090000 00000000 00000112 ntdll!RtlAllocateHeap+0x80 (FPO: [Non-Fpo])
0134d234 774fd05b 77606034 00000112 0134d254 ole32!CRetailMalloc_Alloc+0x16 (FPO: [Non-Fpo])
start end module name
00400000 00409000 normaliz normaliz.dll Thu Jun 29 10:05:42 2006 (44A3EC46)
00d90000 00da2000 browselc browselc.dll Wed Aug 04 02:56:07 2004 (41109697)
01000000 010ff000 explorer explorer.exe Wed Jun 13 05:23:04 2007 (466FC588)
01230000 01241000 igfxsrvc igfxsrvc.dll Wed Dec 19 13:07:30 2007 (47696BF2)
0ffd0000 0fff8000 rsaenh rsaenh.dll Tue Jul 06 21:17:12 2004 (40EB5D28)
20000000 202c5000 xpsp2res xpsp2res.dll Wed Aug 04 02:56:41 2004 (411096B9)
36d30000 36d4a000 MCPS MCPS.DLL Fri Mar 25 16:42:55 2005 (424485DF)
42990000 429d5000 iertutil iertutil.dll Thu Dec 06 20:21:51 2007 (4758AE3F)
42c10000 42cdf000 wininet wininet.dll Thu Dec 06 20:21:48 2007 (4758AE3C)
42cf0000 42e17000 urlmon urlmon.dll Thu Dec 06 20:21:48 2007 (4758AE3C)
42ef0000 434bd000 ieframe ieframe.dll Thu Dec 06 20:21:49 2007 (4758AE3D)
5ad70000 5ada8000 uxtheme uxtheme.dll Wed Aug 04 02:56:43 2004 (411096BB)
5b860000 5b8b4000 netapi32 netapi32.dll Thu Aug 17 07:28:27 2006 (44E460EB)
5ba60000 5bad1000 themeui themeui.dll Wed Aug 04 02:56:46 2004 (411096BE)
5cb70000 5cb96000 shimeng shimeng.dll Wed Aug 04 02:56:42 2004 (411096BA)
5d090000 5d12a000 comctl32_5d090000 comctl32.dll Fri Aug 25 10:45:58 2006 (44EF1B36)
60980000 60987000 msisip msisip.dll Mon Mar 14 23:06:02 2005 (42365F2A)
629c0000 629c9000 lpk lpk.dll Wed Aug 04 02:56:26 2004 (411096AA)
69450000 69466000 faultrep faultrep.dll Wed Aug 04 02:56:05 2004 (41109695)
6f880000 6fa4a000 acgenral acgenral.dll Wed Aug 04 02:55:58 2004 (4110968E)
71aa0000 71aa8000 ws2help ws2help.dll Wed Aug 04 02:57:39 2004 (411096F3)
71ab0000 71ac7000 ws2_32 ws2_32.dll Wed Aug 04 02:57:38 2004 (411096F2)
71b20000 71b32000 mpr mpr.dll Wed Aug 04 02:56:46 2004 (411096BE)
71bf0000 71c03000 samlib samlib.dll Wed Aug 04 02:56:29 2004 (411096AD)
71c10000 71c1e000 ntlanman ntlanman.dll Wed Aug 04 02:57:00 2004 (411096CC)
71c80000 71c87000 netrap netrap.dll Wed Aug 04 02:56:35 2004 (411096B3)
71c90000 71cd0000 netui1 netui1.dll Wed Aug 04 02:56:39 2004 (411096B7)
71cd0000 71ce7000 netui0 netui0.dll Wed Aug 04 02:56:38 2004 (411096B6)
73dd0000 73ece000 mfc42 mfc42.dll Wed Aug 04 02:56:21 2004 (411096A5)
74d90000 74dfb000 usp10 usp10.dll Wed Aug 04 02:56:42 2004 (411096BA)
74ea0000 74eb0000 wshext wshext.dll Wed Aug 04 02:57:45 2004 (411096F9)
754d0000 75550000 cryptui cryptui.dll Wed Aug 04 02:56:06 2004 (41109696)
755c0000 755ee000 msctfime msctfime.ime Wed Aug 04 02:57:31 2004 (411096EB)
75cf0000 75d81000 mlang mlang.dll Wed Aug 04 02:56:29 2004 (411096AD)
75f60000 75f67000 drprov drprov.dll Wed Aug 04 02:57:02 2004 (411096CE)
75f70000 75f79000 davclnt davclnt.dll Wed Aug 04 02:56:08 2004 (41109698)
75f80000 7607d000 browseui browseui.dll Thu Sep 14 03:31:25 2006 (4509135D)
76360000 76370000 winsta winsta.dll Wed Aug 04 02:56:40 2004 (411096B8)
76380000 76385000 msimg32 msimg32.dll Wed Aug 04 02:58:31 2004 (41109727)
76390000 763ad000 imm32 imm32.dll Wed Aug 04 02:56:30 2004 (411096AE)
763b0000 763f9000 comdlg32 comdlg32.dll Wed Aug 04 02:56:32 2004 (411096B0)
76400000 765a6000 netshell netshell.dll Wed Aug 04 02:56:37 2004 (411096B5)
76600000 7661d000 cscdll cscdll.dll Wed Aug 04 02:56:07 2004 (41109697)
76980000 76988000 linkinfo linkinfo.dll Wed Aug 31 20:41:53 2005 (43165C61)
76990000 769b5000 ntshrui ntshrui.dll Wed Aug 04 02:57:09 2004 (411096D5)
769c0000 76a73000 userenv userenv.dll Wed Aug 04 02:56:41 2004 (411096B9)
76b20000 76b31000 atl atl.dll Wed Aug 04 02:56:55 2004 (411096C7)
76b40000 76b6d000 winmm winmm.dll Wed Aug 04 02:57:10 2004 (411096D6)
76bf0000 76bfb000 psapi psapi.dll Wed Aug 04 02:56:58 2004 (411096CA)
76c00000 76c2e000 credui credui.dll Wed Aug 04 02:56:42 2004 (411096BA)
76c30000 76c5e000 wintrust wintrust.dll Wed Aug 04 02:56:41 2004 (411096B9)
76c90000 76cb8000 imagehlp imagehlp.dll Wed Aug 04 02:56:25 2004 (411096A9)
76d60000 76d79000 iphlpapi iphlpapi.dll Fri May 19 07:59:41 2006 (446DC13D)
76e80000 76e8e000 rtutils rtutils.dll Wed Aug 04 02:56:36 2004 (411096B4)
76e90000 76ea2000 rasman rasman.dll Wed Aug 04 02:56:29 2004 (411096AD)
76eb0000 76edf000 tapi32 tapi32.dll Wed Aug 04 02:56:38 2004 (411096B6)
76ee0000 76f1c000 rasapi32 rasapi32.dll Wed Aug 04 02:56:25 2004 (411096A9)
76f50000 76f58000 wtsapi32 wtsapi32.dll Wed Aug 04 02:57:55 2004 (41109703)
76f60000 76f8c000 wldap32 wldap32.dll Wed Aug 04 02:56:43 2004 (411096BB)
76fd0000 7704f000 clbcatq clbcatq.dll Mon Jul 25 23:39:44 2005 (42E5BE90)
77050000 77115000 comres comres.dll Wed Aug 04 02:56:36 2004 (411096B4)
77120000 771ab000 oleaut32 oleaut32.dll Tue Dec 04 12:38:12 2007 (47559E94)
773d0000 774d3000 comctl32 comctl32.dll Fri Aug 25 10:45:55 2006 (44EF1B33)
774e0000 7761d000 ole32 ole32.dll Mon Jul 25 23:39:47 2005 (42E5BE93)
77760000 778d0000 shdocvw shdocvw.dll Mon Sep 04 01:12:56 2006 (44FBC3E8)
77920000 77a13000 setupapi setupapi.dll Wed Aug 04 02:56:32 2004 (411096B0)
77a20000 77a74000 cscui cscui.dll Wed Aug 04 02:56:08 2004 (41109698)
77a80000 77b14000 crypt32 crypt32.dll Wed Aug 04 02:56:01 2004 (41109691)
77b20000 77b32000 msasn1 msasn1.dll Wed Aug 04 02:57:23 2004 (411096E3)
77b40000 77b62000 apphelp apphelp.dll Wed Aug 04 02:56:36 2004 (411096B4)
77be0000 77bf5000 msacm32 msacm32.dll Wed Aug 04 02:57:03 2004 (411096CF)
77c00000 77c08000 version version.dll Wed Aug 04 02:56:39 2004 (411096B7)
77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 02:59:14 2004 (41109752)
77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 02:56:23 2004 (411096A7)
77e70000 77f02000 rpcrt4 rpcrt4.dll Mon Jul 09 08:09:42 2007 (46923396)
77f10000 77f57000 gdi32 gdi32.dll Tue Jun 19 08:31:19 2007 (4677DAA7)
77f60000 77fd6000 shlwapi shlwapi.dll Thu Sep 14 03:31:29 2006 (45091361)
77fe0000 77ff1000 secur32 secur32.dll Wed Aug 04 02:56:49 2004 (411096C1)
7c800000 7c8f5000 kernel32 kernel32.dll Mon Apr 16 10:52:53 2007 (46239BD5)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 02:56:36 2004 (411096B4)
7c9c0000 7d1d6000 shell32 shell32.dll Thu Oct 25 22:36:50 2007 (472160D2)
7d1e0000 7d49e000 msi msi.dll Wed Apr 18 11:12:21 2007 (46264365)
7e410000 7e4a0000 user32 user32.dll Thu Mar 08 09:36:28 2007 (45F02D7C)
Closing open log file c:\debuglog.txt

 

I was connected to the internet while I was debugging. I'm not sure why there was a symbol problem - it's the first time I've downloaded and used that program, so maybe I did something wrong.

I managed to run scandisk (which took about 5 hours total). The only unusual messages I received was during verifying indexes, stage 2 of 5. It stated:
Deleting index entry Double Spiral.ffx in index $I30 of file 21651
Deleting index entry DOUBLE~I.FFX in index $I30 of file 21651

Also I spent the better part of yesterday backing up files from my C drive to D drive while my drive was at least partially functional. It was slow and clunky, but I managed to get a majority of my most important files backed up (hopefully). I was in the process of finishing up my backups when the dreaded BSOD popped up again. Here's what it said this time:

KERNEL_STACK_INPAGE_ERROR

STOP: 0x00000077 (0x0000015, 0xC0000015, 0x00000000, 0x00832000)
Dumping physical memory to disk: 4

Well, that's where I am at the moment. I wanted to try to backup whatever I could while I was able. I will be testing the RAM physically as well as with Windows Memory Diagnostic Tool, if I'm able, and also disconnecting the D drive and seeing the effect. I'll also google the error comments and see if I can find anything useful there.

Thanks for you continuing assistance - I will be back with updates soon, hopefully with happy results.

 

I tried disconnecting the D drive and it wouldn't boot up. On the startup, it didn't show my C drive under IDE drives. Periodically, this has happened during my problems - not showing up under IDE drives during boot, only my slave. So, I switched out my IDE cable and my C drive showed up again (maybe this was the problem all along??)

Anyway, I ran the Windows Memory Diagnostic as suggested and ran it 2 Passes with all success. I also took out the RAM physically and it didn't have a problem either.

Since switching out the IDE cable, I haven't seen the BSOD yet (knock on wood). Are there any other tests I can run to see if my harddrive is working properly other than just using it and seeing if a BSOD pops up? Could it be possible that a bad IDE cable could be the root of all these problems? Thanks again for all you help.

Edit: After all this I am now running a chkdsk. I tried to run it from Start>Run>chkdsk /f/ r and received the message: This type of file system is NTFS. Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time system restarts?

I clicked 'yes' and restarted and it is now running chkdsk, which took several hours last time. Is that error message normal or should I be concerned about it?

 

I ran a chkdsk which took several hours and then downloaded the SeaTools for Windows (which prompted me to download Microsoft .NET Framework 2.0) and ran that. (My C drive is a Maxtor) My drive failed the short test and upon further reading, discovered I should download SeaTools for DOS and create a bootup CD for that and run the long test which could possibly fix any disk errors. Whew!

Ran the long test from DOS and it found 1 bad file and then fixed it. Wow. It seems to be working now, though the bootup seems a lot longer than it used to be. Since I've basically been running tests and working the drive like a rented mule for around a solid 6-7 hours, I checked the CPU temp in the bios and it was 72C, so I've now left the side casing off and shut down for a while to let it rest and cool.

Four days of high blood pressure and a nauseating sense of dread is subsiding as it seems to have fixed the problem (knock on wood). I wanted to thank you once again for helping me out and pointing me in the right direction. You are a life (and work) saver! Thank you so very much!