G
Guest
Hey yall,
Windows explorer crashes consistently and repeatedly for me while I'm
browsing the contents of my computer. It's been going on for quite a while
(Windows Explorer has encountered a problem and needs to close). The problem
*does* occur in safe mode. XP Pro, SP 2.
Below I've pasted the debug results. All the debuggers I've tried either
mention missing symbols or memory corruption. Any help would be appreciated.
Thanks!
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini071906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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 Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Jul 19 02:34:17.890 2006 (GMT-5)
System Uptime: 0 days 3:29:20.477
Loading Kernel Symbols
......................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 77, {c00000b5, c00000b5, 0, 29bc000}
Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+362 )
Followup: MachineOwner
---------
kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: c00000b5, status code
Arg2: c00000b5, i/o status code
Arg3: 00000000, page file number
Arg4: 029bc000, offset into page file
Windows explorer crashes consistently and repeatedly for me while I'm
browsing the contents of my computer. It's been going on for quite a while
(Windows Explorer has encountered a problem and needs to close). The problem
*does* occur in safe mode. XP Pro, SP 2.
Below I've pasted the debug results. All the debuggers I've tried either
mention missing symbols or memory corruption. Any help would be appreciated.
Thanks!
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini071906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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 Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed Jul 19 02:34:17.890 2006 (GMT-5)
System Uptime: 0 days 3:29:20.477
Loading Kernel Symbols
......................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 77, {c00000b5, c00000b5, 0, 29bc000}
Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+362 )
Followup: MachineOwner
---------
kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: c00000b5, status code
Arg2: c00000b5, i/o status code
Arg3: 00000000, page file number
Arg4: 029bc000, offset into page file