While trying to speed up my windows 7 a bit, I found the greatest myth on the internet: setting windows to boot with 2 processors (I have an Intel Core 2 Duo T9600). So I set it to 2 and rebooted my system. But while it was booting, it crashed right after the loading windows screen and I got the BSOD with the error: Bad_System_config_info. Is there a way to change this setting without having to boot into windows 7? or is there a different cause to the problem? I can acces all the files of windows 7, since i have a dual boot with XP 32 bit.

If you are unable successfully boot into Windows because of the fatal error, Windows has an option to reload registry information from the last successful boot. To revert to the last successful boot: 1.Reboot the computer. 2.Near the end of the BIOS messages or graphic, but well before anything appears from Windows, press the F8 key. You may only have a few seconds to get the right spot to press F8 before it attempts to go into Windows. If the BIOS complains about a pressed key or asks you to go into BIOS setup, you've pressed F8 too soon (Don't go into BIOS setup). 3.When successful, you should see a black screen with white text "Windows Advanced Options". Use the up or down arrow keys to highlight Last Known Good Configuration and press Enter. For More Information and know how to resolve windows 7 blue screen error

thanks for your reply. I did what you said, but i still get the BSOD at the end of the loading screen. Windows repair (startup repair, system restore, etc) also didn't do anything. Is there another solution to this problem? or is the only option left to do a clean reinstall?

ignore this user, this is SPAM bot, which copies other users post. Please zip and upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps. André [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

I don't see any files in that folder. I can see all system files, since i have disabled the hide option in the menu. Is the MEMORY.DMP file fine also? (located at C:\windows\ ) This is what i get when opening that file in WinDbg: MODULE_NAME: nt FAULTING_MODULE: fffff80002e4b000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x74 CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003339cda to fffff80002ebb740 STACK_TEXT: fffff880`032a1a28 fffff800`03339cda : 00000000`00000074 00000000`00000002 fffff880`032a1ae0 00000000`00000002 : nt!KeBugCheckEx fffff880`032a1a30 fffff800`0315fc06 : 00000000`01f2c3e8 fffffa80`025ac890 00000000`00000080 fffffa80`003dd380 : nt!FsRtlDeleteExtraCreateParameterLookasideList+0x1f8a fffff880`032a1d00 fffff800`02e99c26 : fffff800`03035e80 fffffa80`025ac890 fffffa80`0259a4c0 fffff880`01669a90 : nt!PsCreateSystemThread+0x6f2 fffff880`032a1d40 00000000`00000000 : fffff880`032a2000 fffff880`0329c000 fffff880`032a1390 00000000`00000000 : nt!KeTestAlertThread+0x94a STACK_COMMAND: kb FOLLOWUP_IP: nt!FsRtlDeleteExtraCreateParameterLookasideList+1f8a fffff800`03339cda cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!FsRtlDeleteExtraCreateParameterLookasideList+1f8a FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntkrnlmp.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------

please set the symbol path to SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols and run analyze again. Now post the complete data."A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\Documents and Settings\Sander\Desktop\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50 Debug session time: Mon Aug 16 13:15:19.012 2010 (UTC + 2:00) System Uptime: 0 days 0:00:12.807 Loading Kernel Symbols ............................................................... ............................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 74, {2, fffff880032a1ae0, 2, ffffffffc000009a} Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a ) Followup: MachineOwner --------- 1: 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: fffff880032a1ae0, (reserved) Arg3: 0000000000000002, (reserved) Arg4: ffffffffc000009a, usually the NT status code. Debugging Details: ------------------ DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x74 PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003339cda to fffff80002ebb740 STACK_TEXT: fffff880`032a1a28 fffff800`03339cda : 00000000`00000074 00000000`00000002 fffff880`032a1ae0 00000000`00000002 : nt!KeBugCheckEx fffff880`032a1a30 fffff800`0315fc06 : 00000000`01f2c3e8 fffffa80`025ac890 00000000`00000080 fffffa80`003dd380 : nt!CmpLoadHiveThread+0x23a fffff880`032a1d00 fffff800`02e99c26 : fffff800`03035e80 fffffa80`025ac890 fffffa80`0259a4c0 fffff880`01669a90 : nt!PspSystemThreadStartup+0x5a fffff880`032a1d40 00000000`00000000 : fffff880`032a2000 fffff880`0329c000 fffff880`032a1390 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!CmpLoadHiveThread+23a fffff800`03339cda 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: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a Followup: MachineOwner ---------

This is your Error code: (NTSTATUS) 0xc000009a - STATUS_INSUFFICIENT_RESOURCES- Insufficient system resources exist to complete the API How much RAM do you have? Have you used msconfig to remove the RAM?"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

I'm using 4GB of RAM and i didn't change anything in msconfig.. At least, not that I know about. The only setting I changed before this happened was the amount of CPUs

Hi, After checking this issue, if the system repair method cannot fix it, you can check your memory. Here is the steps: 1. Insert the DVD and boot from it. 2. start the Recovery Console, select Repair your computer. 3. Select your OS, and click Next. 4. Select Windows Memory Diagnostic Tool. Also, Confirm all the memory is of the same type and speed , and check that the memory is fully seated in the sockets. If the issue persists, I suggest you can contact the CSS for further help. Please understand that to solid troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump and analyze the related source code if needed. Unfortunately, debugging is beyond what we can do in the forum. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

Thanks for your reply. the memory diagnostic tool couldn't find anything, and my Windows XP installation is running fine on the same memory. But I was thinking... what if I did changed the amount of RAM in msconfig? Is there a way to undo that? (I remember clicking twice on that checkbox, but my memory can be wrong)

Hi, If you want to check the amount of RAM, you can take the following steps: 1. Go to Start, type msconfig in the search bar and press Enter. 2. System Configuration window will open on the screen. 3. Click on tab Boot. 4. Choose windows 7 system. 5. Click on Advanced Options and uncheck the box for Maximum Memory. Hope it helps. Regards, Alex

I don't see windows 7 in that tab. But the problem is gone. I'm typing this in windows 7. After I tried to get to windows 7 in the boot tab, I had to reboot because of an update. During that reboot, it said that my boot.ini was corrupt, and I had to boot from DVD to restore it. I did that, and it didn't see my XP OS anymore, so i had no choice but to boot to windows 7. Surprisingly, it did fully boot:D I guess it was a corrupt boot.ini or something like that. So thanks all for your time and support! Now i only have to find a solution to get Windows Live messenger BETA 4 up and running again (it says wlidcli.dll is missing, and i can't reinstall wlm because UXCore.dll is missing also:( )

Hi, you can try to repair the windows Live messenger BETA4. Just go to Add/Remove Programs, select Windows Live Essentials and click on Uninstall/Change. Then select the Repair option and Continue. hope it helps. Regards. Alex zhaozx

I tried that several times, but it didn't work. After a lot of effort I managed to uninstall and reinstall the beta. The wlidcli.dll error is gone, but now i get the following error: The procedure entry point ??0CRMImage@@QAE@XZ could not be located in the dynamic link library UXCore.dll . Is this a registry error, since i do see that entry in UXCore.dll?

Hi, You could try to delete the Windows Live program folder in the Safe Mode, and reinstall Windows Live Messenger BETA. If the issue persists, you could try to clean the related invalid Registry.Here is the related link: Removing Invalid Entries in the Add/Remove Programs Tool Note: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. Hope it helps. Regards, Alex zhao