I am getting the BSOD every time I try to boot. I have ran chkdsk /f/r and as soon as it gets through checking it blues screens and reboots and starts the chkdsk again in an unending cycle. Here are the minidumps:
Any help would be appreciated.
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [I:\WINDOWS\Minidump\Mini021309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_qfe.080814-1242
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553dc0
Debug session time: Sun Dec 7 17:16:05.171 2008 (GMT-6)
System Uptime: 0 days 0:00:28.734
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8062561e, f7d28964, 0}
Probably caused by : ntkrnlpa.exe ( nt!CmpParseKey+510 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8062561e, The address that the exception occurred at
Arg3: f7d28964, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!CmpParseKey+510
8062561e ff5604 call dword ptr [esi+4]
TRAP_FRAME: f7d28964 -- (.trap 0xfffffffff7d28964)
ErrCode = 00000000
eax=e259a130 ebx=ffffffff ecx=ffa102c0 edx=00000000 esi=ffffffff edi=c8f54154
eip=8062561e esp=f7d289d8 ebp=f7d28ba0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!CmpParseKey+0x510:
8062561e ff5604 call dword ptr [esi+4] ds:0023:00000003=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: winlogon.exe
LAST_CONTROL_TRANSFER: from 805b47e8 to 8062561e
STACK_TEXT:
f7d28ba0 805b47e8 ffffffff 00013150 ffa0cf30 nt!CmpParseKey+0x510
f7d28c28 805b0cc9 00000000 f7d28c68 000000c0 nt!ObpLookupObjectName+0x56a
f7d28c7c 8061b399 00000000 82dc2628 805b1801 nt!ObOpenObjectByName+0xeb
f7d28d50 8053d428 0006e30c 80000000 0006e25c nt!NtOpenKey+0x1af
f7d28d50 7c90eb94 0006e30c 80000000 0006e25c nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006e2c8 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpParseKey+510
8062561e ff5604 call dword ptr [esi+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpParseKey+510
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlpa.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48a3f869
FAILURE_BUCKET_ID: 0x8E_nt!CmpParseKey+510
BUCKET_ID: 0x8E_nt!CmpParseKey+510
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [I:\WINDOWS\Minidump\Mini021309-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_qfe.080814-1242
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553dc0
Debug session time: Fri Feb 13 09:30:49.656 2009 (GMT-6)
System Uptime: 0 days 0:00:30.218
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8062561e, f7c18964, 0}
Probably caused by : ntkrnlpa.exe ( nt!CmpParseKey+510 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8062561e, The address that the exception occurred at
Arg3: f7c18964, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!CmpParseKey+510
8062561e ff5604 call dword ptr [esi+4]
TRAP_FRAME: f7c18964 -- (.trap 0xfffffffff7c18964)
ErrCode = 00000000
eax=e25a3130 ebx=ffffffff ecx=ff9150b0 edx=00000000 esi=ffffffff edi=c8e54154
eip=8062561e esp=f7c189d8 ebp=f7c18ba0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!CmpParseKey+0x510:
8062561e ff5604 call dword ptr [esi+4] ds:0023:00000003=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: winlogon.exe
LAST_CONTROL_TRANSFER: from 805b47e8 to 8062561e
STACK_TEXT:
f7c18ba0 805b47e8 ffffffff 00013150 ff901a78 nt!CmpParseKey+0x510
f7c18c28 805b0cc9 00000000 f7c18c68 000000c0 nt!ObpLookupObjectName+0x56a
f7c18c7c 8061b399 00000000 823c2628 805b1801 nt!ObOpenObjectByName+0xeb
f7c18d50 8053d428 0006e30c 80000000 0006e25c nt!NtOpenKey+0x1af
f7c18d50 7c90eb94 0006e30c 80000000 0006e25c nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006e2c8 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpParseKey+510
8062561e ff5604 call dword ptr [esi+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpParseKey+510
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlpa.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48a3f869
FAILURE_BUCKET_ID: 0x8E_nt!CmpParseKey+510
BUCKET_ID: 0x8E_nt!CmpParseKey+510
Followup: MachineOwner
---------
Any help would be appreciated.