Windows 7 - Random BSOD on new build - BAD_SYSTEM_CONFIG_INFO

m00k · 02-08-2012

Hey folks,

New to the forum and looking for some help.

I built a new system last week and all was going well with no problems at all until a random BSOD yesterday.

Here's the relevant specs:

Intel Core i5 2500K Retail (no O/C - CPU sits at around 19oC idle)
Gigabyte GA-Z68AP-D3 Z68 Socket 1155 motherboard
Kingston 8GB DDR3 1600MHz HyperX Blu RAM
Asus HD 6770 Graphics Card (no O/C - can't remember temp but it wasn't high)
160GB WD OS drive
1TB Samsung Media Drive
Windows 7 Home Premium 64bit

All drivers are up to date and the only recent change was a Windows Update for MS Office 2007 on Monday night. I let this download and install before letting this PC shut itself down. Then when I turn the PC on for the first time the next day BSOD strikes.

After the crash it wouldn't start normnally so I chose to revert to Last Know Good Configuration and then everything seemed ok again. I ran CCleaner which found and fixed a number of registry entries. I then shut down and powered on the PC a few times and it started up perfectly every time. One thing I did notice that the Office update I had told it to install the night before was listed again, so this time I chose to hide it. I should have really taken a note of the update number but it was called something along the lines of MS Office File Validation.

The only other thing that might be a concern is that I'm using a 6 year old 160GB SATA drive I took from my old Dell as the OS drive. I was planning to buy a SSD tomorrow when I get paid. I've yet to run chkdsk on the HDD or memtest on the RAM but if the BSOD occurs again I'll defintitely do that.

Sorry I don't have the actual files to attach as I 'm at work and didn't know I would need them, however when I get home I will follow the instructions in the Blue Screen of Death (BSOD) Posting Instructions thread and will then update this thread.

I did email myself some of the Bluescreenview and a WhoCrashed report though, so have attached them as text files in case they're any help in the mean time.

Cheers,

Lee

m00k · 02-08-2012

Ok, so looking for STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO on BSOD Index it points to "Missing registry keys/values" and the solution is to boot Last Known Good Configuration, which is what I did last night and it seemed to fix it. Strange though, as I haven't made any changes to the registry myself recently and as I said, the only other change I am aware of was the Windows update I mentioned above. It's seems the error can also be related to RAM which makes me think I should have done something in the BIOS when building the PC. I assumed, possibly wrongly, that the BIOS would auto-detect the RAM. The fact that everything worked for almost a week meant that I didn't bother going back into the BIOS to change anything. Maybe I should have?

As I said, I will upload the dump files when I get home from work and then hopefully someone can have a look and shed a bit more light on it.

I know it sounds fixed but I want to know why it happened to prevent it happening again.

Cheers,

Lee

writhziden · 02-08-2012

The Windows update may not have installed cleanly and corrupted something in the registry. If the problem returns, let us know and we can pursue troubleshooting steps, but otherwise don't worry about it as it may have just been a one time thing.

m00k · 02-09-2012

Quote: Originally Posted by writhziden

The Windows update may not have installed cleanly and corrupted something in the registry. If the problem returns, let us know and we can pursue troubleshooting steps, but otherwise don't worry about it as it may have just been a one time thing.

Thanks! There was no problems with the PC at all yesterday so here's hoping it is one time thing. I have an SSD arriving tomorrow and I'm going to do a fresh install rather than clone my current drive. Hopefully no update related BSODs this time around!

Dump files attached out of curiosity

Cheers,

Lee

writhziden · 02-09-2012

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\m00k\Windows_NT6_BSOD_jcgriff2\020712-33899-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304b670
Debug session time: Tue Feb  7 09:37:47.145 2012 (GMT-7)
System Uptime: 0 days 0:00:17.347
Loading Kernel Symbols
...............................................................
..........................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 74, {2, fffff88002e269e0, 2, ffffffffc000014c}

Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a )

Followup: MachineOwner
---------

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: 0000000000000002, (reserved)
Arg2: fffff88002e269e0, (reserved)
Arg3: 0000000000000002, (reserved)
Arg4: ffffffffc000014c, 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 fffff80003300d8a to fffff80002e82c40

STACK_TEXT:  
fffff880`02e26928 fffff800`03300d8a : 00000000`00000074 00000000`00000002 fffff880`02e269e0 00000000`00000002 : nt!KeBugCheckEx
fffff880`02e26930 fffff800`0311dfee : 00000000`02a22d0d fffffa80`079bfb60 00000000`00000080 fffffa80`06a22040 : nt!CmpLoadHiveThread+0x23a
fffff880`02e26c00 fffff800`02e745e6 : fffff880`02f65180 fffffa80`079bfb60 fffff880`02f6ffc0 fffff880`01268cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`02e26c40 00000000`00000000 : fffff880`02e27000 fffff880`02e21000 fffff880`02e26050 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpLoadHiveThread+23a
fffff800`03300d8a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!CmpLoadHiveThread+23a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a

BUCKET_ID:  X64_0x74_nt!CmpLoadHiveThread+23a

Followup: MachineOwner
---------

Quote:

Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.

Taken from the crash report itself. While the above is unlikely, it is possible and may have been a result of the update. As I said, it probably is just a one time thing, but it often a good idea to do a clean install when new hardware is added to prevent any conflicts.

See ssd links for useful tutorials to help with your ssd installation.

m00k · 02-10-2012

Thanks again for the reply, and for the SSD tips!

It just arrived so looking forward to installing it after work.

Cheers,

Lee

writhziden · 02-10-2012

You're welcome. Post back how the SSD works out for you. Best of luck!

m00k · 02-13-2012

Quote: Originally Posted by writhziden

You're welcome. Post back how the SSD works out for you. Best of luck!

Wow, what a difference the SSD makes! Boot time is almost non existent and programs load so fast! Definitely a worth while upgrade.

I went for a fresh Windows install then followed the SSD tweaks guide via the link above, but moved the pagefile to HDD instead keeping it on the SSD. I also moved CS5 scratch disk to HDD, moved windows temp folders to HDD and moved Firefox cache to RAM. Everything else was pretty much as the guide suggested.

Only thing I haven't done is update the f/w as it turned out I had no blank disks. I'll pop out for some at lunch time though

writhziden · 02-13-2012

Glad you are enjoying the new drive. Let us know how the firmware update goes. Best of luck!

Windows 7 - Random BSOD on new build - BAD_SYSTEM_CONFIG_INFO

Random BSOD on new build - BAD_SYSTEM_CONFIG_INFO problems?