BSOD during boot

[monarch684]

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:

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.

 

[Route44]

0x8E errors are almost always caused by hardware. The driver your information cites is too general too be of much help. I have had this issue with corrupted memory. Therefore do the following steps and get back to us with the results.
One good thing about this test is that it takes over as soon as you boot-up.

1. Go to www.memtest.org and download the latest ISO version. It is free and perfectly safe.

2. Burn to a CD.

3. Place CD in your drive and reboot with CD in drive. The test will take over. Sometimes you have to go to the BIOS and make your CD first bootable.

4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

5. If you have errors you have corrupted memory and it needs to be replaced.

6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.

 

[monarch684]

Thanks I will try that.

 

[raybay]

I second the excellent advice of Route44
MemTest86 is superb. If you have trouble with the ISO, or your computer will not work well enough for you to download and create, you can try simple things.
Your 8E error points at RAM problems, and is unique for a <stop> code in that it only points at RAM problems. If your motherboard has two memory modules, you might try removing one to see if your problem persists. Then exhange for the other module.
Or borrow memory known good from a friend or other computer.
BSOD's are nearly always caused by the more simple hardware problems.

 

[monarch684]

Ok so far I have had no errors after 8 passes. Any other ideas.

 

[Route44]

Let it run to 10. As good as memtest is bad memory, for what ever reason, has been known to pass on occasion. If you have time try raybay's suggestion of running your system with one stick at a time and then switch, or you can run this test per stick.

Here is another thing you can try. ChkDsk will only do somuch. Run a harddisk diagnostics by utilizing the free utility from your harddrive manuafacturer.

* Again, let us know of your results. raybay may have some other excellent ideas.

 

[monarch684]

Ok so I let the Memory test run over night. After 89 passes it still had no errors. There is only one stick in there. Any other ideas you might have.

 

[Route44]

Try the following standard diagnostics:

1. Run ChkDsk

2. Do a harddrive diagnostics by using the free utility provided by your HD manufacturer; should find it on their website. Don't skip the extensive test.

3. Scan for infections.

* Let us know the results.

 

[monarch684]

1. I have run chkdsk /f/r and after it is done the computer blues screens and restarts and does chkdsk again in a unendeing cycle.

2. I just got finished running the hard drive diagnostic. No errors were found.

3. I have scanned the computer for infections from my work station and still found nothing wrong.

 

[Route44]

Okay, then Zip together your five latest minidump files (not the folder) and attach on your next post.