ilcorsaro73 Posted June 10, 2016 Share Posted June 10, 2016 Good evening my pc suddenly today is gone in bsod with the erorr "BAD_SYSTEM_CONFIG_INFO" Fortunately, the PC has restarted so I restored a system image and everything is back to normal but the problem reappears randomly what can I do to solve it? this is my software configuration os windows 10 pro x64 genuine security kis 16 avg tune up 2016 (after bsod unistalled) this is my hardware configuration cpu QuadCore Intel Core i5-6400 power supply corsair vs550 atx mb MSI B150 PC Mate (MS-7971) bios version c.70 ram Kingston 8 GB DDR4-2133 mhz 1°ssd 240gb kingston 2° hdd toshiba 1tb 3° hdd seagate 2 tb graphic card AMD Radeon HD 7750 1 GB ddr5 card reader dvd-rom rewritable Please help me! However thank you to everyone for replies Link to comment Share on other sites More sharing options...
Kalju Posted June 10, 2016 Share Posted June 10, 2016 BSOD is generally a system problem, a very rarely problem with Windows. If I see, there's two very unpleasant things: KIS and AVG! Why? Link to comment Share on other sites More sharing options...
ilcorsaro73 Posted June 10, 2016 Author Share Posted June 10, 2016 1 minute ago, Kalju said: BSOD is generally a system problem, a very rarely problem with Windows. If I see, there's two very unpleasant things: KIS and AVG! Why? infact if you read above avg is uninstalled Link to comment Share on other sites More sharing options...
Israeli_Eagle Posted June 10, 2016 Share Posted June 10, 2016 Link to comment Share on other sites More sharing options...
Kalju Posted June 10, 2016 Share Posted June 10, 2016 This problem is always very individual and you have to try to find the cause itself. First of all, restore all the original settings. If this don't change nothing, make new clean install. But also is recommended to set BIOS setting to their defaults. But it is nice that AVG is removed. Remove also KIS. And then restore all default settings. Link to comment Share on other sites More sharing options...
ilcorsaro73 Posted June 10, 2016 Author Share Posted June 10, 2016 unsuccessful operations update all drivers from device manager (whql) scan pc for viruses reinstall windows os restore bois default values Link to comment Share on other sites More sharing options...
eurobyn Posted June 10, 2016 Share Posted June 10, 2016 just use hirens boot cd goto to file explorer and go to windows directory go to system32 and then go to config open regback folder and copy the default - system - sam - sotware etc to the folder config overwrite the existing files reboot and there you are back. if nothing else is wrong. this will place a backup back of the registry otherwise a clean install could be adviced Link to comment Share on other sites More sharing options...
ilcorsaro73 Posted June 11, 2016 Author Share Posted June 11, 2016 8 hours ago, eurobyn said: just use hirens boot cd goto to file explorer and go to windows directory go to system32 and then go to config open regback folder and copy the default - system - sam - sotware etc to the folder config overwrite the existing files reboot and there you are back. if nothing else is wrong. this will place a backup back of the registry otherwise a clean install could be adviced first of all thanks for reply and for your time... I've followed your council and I've backup regback folder but with lazesoft windows manager Now I'm trying to update realtek driver audio with last build 7841 whql Link to comment Share on other sites More sharing options...
ilcorsaro73 Posted July 8, 2016 Author Share Posted July 8, 2016 the problem has come back I've analyze minidump before with Instant Online Crash Analysis and than with who crashed PLEASE HELP ME!!!! Instant Online Crash Analysis Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 10586 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10586.420.amd64fre.th2_release_sec.160527-1834 Machine Name: Kernel base = 0xfffff800`87609000 PsLoadedModuleList = 0xfffff800`878e7cf0 Debug session time: Fri Jul 8 15:07:26.526 2016 (UTC - 4:00) System Uptime: 0 days 0:00:04.232 ******************************************************************************* * * * 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: 0000000000000001, (reserved) Arg3: 0000000000000003, (reserved) Arg4: ffffffffc000009a, usually the NT status code. Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x74 PROCESS_NAME: System CURRENT_IRQL: 0 BAD_PAGES_DETECTED: 1eb310 LAST_CONTROL_TRANSFER: from fffff80087bd58a3 to fffff8008774b7a0 STACK_TEXT: ffffd000`73547898 fffff800`87bd58a3 : 00000000`00000074 00000000`00000002 00000000`00000001 00000000`00000003 : nt!KeBugCheckEx ffffd000`735478a0 fffff800`876f6b75 : 0000008d`bd9bbfff ffffe000`a38e5840 fffff800`87b22268 00000000`00000003 : nt! ?? ::NNGAKEGL::`string'+0x755a3 ffffd000`73547b10 fffff800`87750946 : ffffd000`71db8180 ffffe000`a38e5840 fffff800`876f6b34 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd000`73547b60 00000000`00000000 : ffffd000`73548000 ffffd000`73541000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 2011920 instance(s) of page corruption, target is likely to have memory corruption. who crashed me pro response Crash dump directory: C:\Windows\MinidumpCrash dumps are enabled on your computer.On Fri 08/07/2016 19:07:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\070816-10484-01.dmp uptime: 00:00:04 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x74 (0x2, 0x1, 0x3, 0xFFFFFFFFC000009A) Error: BAD_SYSTEM_CONFIG_INFO Bug check description: This bug check indicates that there is an error in the registry. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. ps: I've updated realtek driver three days ago and today I've updated amd drivers of sapphire hd770 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.