Windows 7: BSOD Again! Also Makes Avast Unusable...

legend86 · 27 Aug 2010

Hello everyone. Been BSOD free for about a week now but I seem to have had an error at start up.

I shut down my computer last night and it was off all day. I started it up about 20 mins ago and it got to the "Loading Windows" screen then restarted and said that Windows failed to boot. Ran a system repair and got it to boot. But for some reason, my computer has categorized this crash as a BlueScreen and created a minidump for it. Checked and it seems to be caused by something called ACPI.sys

Also, my Avast AntiVirus has been shut off and will not turn on. Clicked the "Fix Now" button multiple times and nothing happens.

Could Avast be causing this error? I was using MSE for a while and decided to switch back about 3 days ago because I loved the extra protection that you get with Avast. But if it's messing up my system, I'll gladly go back to MSE.

CarlTR6 · 27 Aug 2010

Sorry to hear of your problem.

Quote:

STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO

Usual causes: System hive corruption, Missing registry keys/values

Have you made any registry changes or used a registry cleaner? Do you have restore points or a system image? If you have either, restore your system to a point previous to the date you had this problem.

You can try running SFC /SCANNOW.

richc46 · 27 Aug 2010

Registry problems.
Get rid of the anti virus and use system restore. Use MSE it is great.
STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO

Usual causes: System hive corruption, Missing registry keys/values

[

Code:

 ding User Symbols
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 00000002, (reserved)
Arg2: 8dbecba8, (reserved)
Arg3: 00000002, (reserved)
Arg4: c000014d, usually the NT status code.
Debugging Details:
------------------
 
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x74
PROCESS_NAME:  System
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 82da2f64 to 82ce9d10
STACK_TEXT:  
8dbecb3c 82da2f64 00000074 00000002 8dbecba8 nt!KeBugCheckEx+0x1e
8dbecd50 82e1b6d3 00000002 a0952cf7 00000000 nt!CmpLoadHiveThread+0x1d5
8dbecd90 82ccd0f9 82da2d8f 00000002 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!CmpLoadHiveThread+1d5
82da2f64 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!CmpLoadHiveThread+1d5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac
FAILURE_BUCKET_ID:  0x74_nt!CmpLoadHiveThread+1d5
BUCKET_ID:  0x74_nt!CmpLoadHiveThread+1d5
Followup: MachineOwner
---------

Did not see you Carl sorry. Your notice was not posted, when I went into the lions den.

CarlTR6 · 27 Aug 2010

No problem, Rich. I got interrupted while I was posting and had to step away. Please add any suggestions you have.

legend86 · 27 Aug 2010

Quote: Originally Posted by CarlTR6

Sorry to hear of your problem.

Quote:

STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO

Usual causes: System hive corruption, Missing registry keys/values

Have you made any registry changes or used a registry cleaner? Do you have restore points or a system image? If you have either, restore your system to a point previous to the date you had this problem.

You can try running SFC /SCANNOW.

Actually now that you mention it, I used to have Registry Mechanic. I did a Google search of this forum just to hear some reviews and I read about one of you guys sayin that Windows 7 handles the registry differently from previous versions and a registry cleaner could actually do more harm than good so I uninstalled the program about 5-7 days ago.

I should have a system restore point from sometime last week. Then I'll just go back and uninstall RM again. And I guess I'll go back to MSE too.

Running SFC now. What does it do?

richc46 · 27 Aug 2010

SFC checks for corruption and can make small repairs to files.

legend86 · 27 Aug 2010

Ok, I think I got everything workin again. I don't know what happened. After I did a system restore, then Mozilla stopped working. Had to do a system restore like 3 times to an even earlier date, uninstalled & reinstalled Mozilla like 6 times and had to clear it's cache so I lost all my bookmarks and preferences.

Also uninstalled Avast and replaced with MSE.

richc46 · 27 Aug 2010

Both Carl and I agree (your lucky 2 for price of one) that it was regsitry problems. System Restore corrects registry. You should be ok.

Windows 7: BSOD Again! Also Makes Avast Unusable...

BSOD Again! Also Makes Avast Unusable... problems?