Jump to content

Blue Screen of Death Problem


marcosgarcia3000

Recommended Posts

Hello everyone! I just got the BSOD on my Compaq Mini 110c I can only access safe mode. Here is the error code STOP: 0x0000008E (0x0000005, 0x806373F1, 0XA770199C,0x00000000). What did do from doing research is scanned the registry, scanned for virus, and spyware while in safe mode, but I still get the BSOD? Also, I tried to access the partition using F11 and Alt-F11 while booting and it does nothing. Any suggestions? Thank You

Link to comment
Share on other sites


I read somewhere that by pressing those keys it will send to the recovery set up on a netbook, but it did not work

It should work indeed if F11 is pressed during Bios screen, unless some changes were made to the partitions and the MBR (using Partition Magic or other similar programs).

Link to comment
Share on other sites

0: kd> kn
# ChildEBP RetAddr
00 9fccfa58 8062faba nt!HvpGetCellMapped+0x5f
01 9fccfa74 80638c4e nt!CmpMarkValueDataDirty+0x44
02 9fccfa90 80638ef3 nt!CmpMarkKeyValuesDirty+0xcc
03 9fccfaac 80638f90 nt!CmpFreeKeyValues+0x17
04 9fccfae8 806397ce nt!CmpSyncKeyValues+0x26
05 9fccfb2c 80639941 nt!CmpCopySyncTree2+0x1f4
06 9fccfb5c 80626042 nt!CmpCopySyncTree+0x4f
07 9fccfccc 8062193a nt!CmpSaveBootControlSet+0x2b0
08 9fccfcdc 8054161c nt!NtInitializeRegistry+0x5e
09 9fccfcdc 8050046d nt!KiFastCallEntry+0xfc
0a 9fccfd58 8054161c nt!ZwInitializeRegistry+0x11
0b 9fccfd58 7c90e4f4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0c 0007fe8c 00000000 0x7c90e4f4

A crash like this, especially in HvpGetCellMapped, is going to be caused by pool corruption, likely by an installed kernel-mode filter driver. You have a bunch loaded that are non-Microsoft, including what appears to be an AVG Intrusion Detection filter. It might be interesting to uninstall that application, or at least keep it's driver from loading, to see if you can't get yourself back into your box. The others all appear to be standard device drivers, and while they could be culprits, I generally like to see Intrusion Detection software removed when a box becomes unbootable before I go blaming device drivers, especially if the system worked fine for a period of time with these drivers installed and then suddenly starts failing. Usually the only thing updated on a system regularly, other than Microsoft components via WU, is definitions for antivirus or ID software. If a device driver was going to cause it, it would likely do so fairly quickly after install. Also, if safe mode works but regular boot does not, it would generally mean it's not a RAM issue either (it should still fail in safe mode if the RAM was really going bad, most likely).

Link to comment
Share on other sites

0: kd> kn
# ChildEBP RetAddr
00 9fccfa58 8062faba nt!HvpGetCellMapped+0x5f
01 9fccfa74 80638c4e nt!CmpMarkValueDataDirty+0x44
02 9fccfa90 80638ef3 nt!CmpMarkKeyValuesDirty+0xcc
03 9fccfaac 80638f90 nt!CmpFreeKeyValues+0x17
04 9fccfae8 806397ce nt!CmpSyncKeyValues+0x26
05 9fccfb2c 80639941 nt!CmpCopySyncTree2+0x1f4
06 9fccfb5c 80626042 nt!CmpCopySyncTree+0x4f
07 9fccfccc 8062193a nt!CmpSaveBootControlSet+0x2b0
08 9fccfcdc 8054161c nt!NtInitializeRegistry+0x5e
09 9fccfcdc 8050046d nt!KiFastCallEntry+0xfc
0a 9fccfd58 8054161c nt!ZwInitializeRegistry+0x11
0b 9fccfd58 7c90e4f4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0c 0007fe8c 00000000 0x7c90e4f4

A crash like this, especially in HvpGetCellMapped, is going to be caused by pool corruption, likely by an installed kernel-mode filter driver. You have a bunch loaded that are non-Microsoft, including what appears to be an AVG Intrusion Detection filter. It might be interesting to uninstall that application, or at least keep it's driver from loading, to see if you can't get yourself back into your box. The others all appear to be standard device drivers, and while they could be culprits, I generally like to see Intrusion Detection software removed when a box becomes unbootable before I go blaming device drivers, especially if the system worked fine for a period of time with these drivers installed and then suddenly starts failing. Usually the only thing updated on a system regularly, other than Microsoft components via WU, is definitions for antivirus or ID software. If a device driver was going to cause it, it would likely do so fairly quickly after install. Also, if safe mode works but regular boot does not, it would generally mean it's not a RAM issue either (it should still fail in safe mode if the RAM was really going bad, most likely).

Thank you but I started to get the BSOD before I installed AVG

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...