BSOD on logon
I have a laptop here which suffers a blue screen of death on logon. The minidump file output is below. admin can logon in safemode however not in standard mode. There was nothing installed recently that I am aware of. System restore is diabled by GP so is not an option.
So far I have tried:
1) Replacing the RAM
2) Ran SFC /scannow
3) Performed a full disk check
4) Worked through the event log fixing all errors from the boot process (except 1 error) . Only a ScardSRV error and
5) Checked for malware/viruses - which showed the laptop as clean
6) Checked and confirmed there are no driver error showing in device manager
So far I have tried:
1) Replacing the RAM
2) Ran SFC /scannow
3) Performed a full disk check
4) Worked through the event log fixing all errors from the boot process (except 1 error) . Only a ScardSRV error and
5) Checked for malware/viruses - which showed the laptop as clean
6) Checked and confirmed there are no driver error showing in device manager
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: 8063547f, The address that the exception occurred at
Arg3: aadcc99c, 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!HvpGetCellMapped+5f
8063547f 8b4304 mov eax,dword ptr [ebx+4]
TRAP_FRAME: aadcc99c -- (.trap 0xffffffffaadcc99c)
ErrCode = 00000000
eax=00000d00 ebx=00000d00 ecx=865e8008 edx=00000003 esi=e1037008 edi=00000020
eip=8063547f esp=aadcca10 ebp=aadcca58 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!HvpGetCellMapped+0x5f:
8063547f 8b4304 mov eax,dword ptr [ebx+4] ds:0023:00000d04=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: services.exe
LAST_CONTROL_TRANSFER: from 8062de84 to 8063547f
STACK_TEXT:
aadcca58 8062de84 e1037008 006d0020 e1037008 nt!HvpGetCellMapped+0x5f
aadcca74 80636cdc e1037008 e13c6dec e1037008 nt!CmpMarkValueDataDirty+0x44
aadcca90 80636f81 e1037008 003c59a8 e1560d9c nt!CmpMarkKeyValuesDirty+0xcc
aadccaac 8063701e e1037008 003c59a8 e14059ac nt!CmpFreeKeyValues+0x17
aadccae8 8063785c e1037008 001498c0 e11898c4 nt!CmpSyncKeyValues+0x26
aadccb2c 806379cf e28be000 00000400 00000001 nt!CmpCopySyncTree2+0x1f4
aadccb5c 80624489 e1037008 000001b8 e1037008 nt!CmpCopySyncTree+0x4f
aadccccc 806200da 00010002 aadccd64 aadccce8 nt!CmpSaveBootControlSet+0x2a7
aadcccdc 8054070c 00000004 aadccd64 804ff8c5 nt!NtInitializeRegistry+0x5e
aadcccdc 804ff8c5 00000004 aadccd64 804ff8c5 nt!KiFastCallEntry+0xfc
aadccd58 8054070c 00000004 0007fe8c 7c90eb94 nt!ZwInitializeRegistry+0x11
aadccd58 7c90eb94 00000004 0007fe8c 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0007fe8c 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!HvpGetCellMapped+5f
8063547f 8b4304 mov eax,dword ptr [ebx+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!HvpGetCellMapped+5f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 434c50c7
FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f
BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f
Followup: MachineOwner
Last Comment
nobus
i would run a ram test first (it can be a ram controller error onthe mobo); use memtest86+ from www.memtest.org.
ASKER
I already used WinDIAG, left it running for a few hours and found no problems. forgot to add that to my list.
seems ok to me, but i prefer memtest86+ running from dos...
Generally when I get BSOD on bootup, I can fix the issue by running a chkdsk /r from the recovery console. Otherwise I try to to a windows repair. That fixes 99% of the bootup BSOD I have seen.
can you post the minidumps?
ASKER
The minidump is already shown as a code snippet at the top. All the minidumps have been the same.
I have already tried running a chkdsk /r
If I boot up but sit at the logon screen without entering credentials it is ok, only once logged in it has the BSOD however as stated before nothing is shown in the event viewer.
I have already tried running a chkdsk /r
If I boot up but sit at the logon screen without entering credentials it is ok, only once logged in it has the BSOD however as stated before nothing is shown in the event viewer.
any updates installed recently? try to uninstall the latest
what happens if you log in to another user account?
or try a repair install
what happens if you log in to another user account?
or try a repair install
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Windows XP
Microsoft Windows XP is the sixth release of the NT series of operating systems, and was the first to be marketed in a variety of editions: XP Home and XP Professional, designed for business and power users. The advanced features in XP Professional are generally disabled in Home Edition, but are there and can be activated. There were two 64-bit editions, an embedded edition and a tablet edition.
119K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
