Buongiorno a tutti da un mese a questa parte il mio pc (per altro nuovo) in maniera del tutto casuale va in crash mostrandomi il messaggio in oggetto ovvero BAD_SYSTEM_CONFIG_INFO
questa la mia configurazione software
[FONT=&]
[/FONT]
[FONT=&]cpu QuadCore Intel Core i5-6400[/FONT]
[FONT=&]power supply corsair vs550 atx[/FONT]
[FONT=&]mb MSI B150 PC Mate (MS-7971) bios version c.70[/FONT]
[FONT=&]ram Kingston 8 GB DDR4-2133 mhz[/FONT]
[FONT=&]1°ssd 240gb kingston[/FONT]
[FONT=&]2° hdd toshiba 1tb[/FONT]
[FONT=&]3° hdd seagate 2 tb[/FONT]
[FONT=&]scheda video AMD Radeon HD 7750 1 GB ddr5 (aggiunta separatamente)[/FONT]
[FONT=&]card reader[/FONT]
[FONT=&]dvd-rom rewritable
questa la mia configurazione software
kaspersky internet security 2016
Adavance systemcare 9 pro
Ho già provato SENZA SUCCESSO
a ripristinare windows 10 da un backup
a reinstallare da capo windows 10 e aggiornare da gestione dispositivi uno ad uno i drivers installati tramite il comando aggiorna driver
eseguire una scansione antivirus e anti malware
aggiornare i drivers della scheda madre scaricandoli dal sito del produttore
eseguire un controllo dei file di sistema tramite il comando sfc
eliminare periferiche nascoste fantasma
a testare le ram con memtest
testare l'ssd con crystal disk info
a togliere la scheda video e usare quella integrata
reimpostare i parametri di default nel bios
eseuire aggiornamento bios scheda madre all'ultima versione
funziona per una settimana poi all'improvviso magari dopo aver fatto una pulizia con asc 9 oppure dopo aver aggiornato i driver audio o quelli video BAD_SYSTEM_CONFIG_INFO vi allego anche l'ultimo minidump analizzato con whocrashed me
Crash dump directory: C:\Windows\Minidump
Crash 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.
questo invece l'analisi con
[/FONT][FONT=&]Instant Online Crash Analysis[/FONT]
[FONT=&]Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR ? Windows System Software ? Unique Expertise, Guaranteed Results)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers 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.[/FONT]
[FONT=&]
[/FONT]
questa la mia configurazione software
[FONT=&]
[/FONT]
[FONT=&]cpu QuadCore Intel Core i5-6400[/FONT]
[FONT=&]power supply corsair vs550 atx[/FONT]
[FONT=&]mb MSI B150 PC Mate (MS-7971) bios version c.70[/FONT]
[FONT=&]ram Kingston 8 GB DDR4-2133 mhz[/FONT]
[FONT=&]1°ssd 240gb kingston[/FONT]
[FONT=&]2° hdd toshiba 1tb[/FONT]
[FONT=&]3° hdd seagate 2 tb[/FONT]
[FONT=&]scheda video AMD Radeon HD 7750 1 GB ddr5 (aggiunta separatamente)[/FONT]
[FONT=&]card reader[/FONT]
[FONT=&]dvd-rom rewritable
questa la mia configurazione software
kaspersky internet security 2016
Adavance systemcare 9 pro
Ho già provato SENZA SUCCESSO
a ripristinare windows 10 da un backup
a reinstallare da capo windows 10 e aggiornare da gestione dispositivi uno ad uno i drivers installati tramite il comando aggiorna driver
eseguire una scansione antivirus e anti malware
aggiornare i drivers della scheda madre scaricandoli dal sito del produttore
eseguire un controllo dei file di sistema tramite il comando sfc
eliminare periferiche nascoste fantasma
a testare le ram con memtest
testare l'ssd con crystal disk info
a togliere la scheda video e usare quella integrata
reimpostare i parametri di default nel bios
eseuire aggiornamento bios scheda madre all'ultima versione
funziona per una settimana poi all'improvviso magari dopo aver fatto una pulizia con asc 9 oppure dopo aver aggiornato i driver audio o quelli video BAD_SYSTEM_CONFIG_INFO vi allego anche l'ultimo minidump analizzato con whocrashed me
Crash dump directory: C:\Windows\Minidump
Crash 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.
questo invece l'analisi con
[/FONT][FONT=&]Instant Online Crash Analysis[/FONT]
[FONT=&]Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR ? Windows System Software ? Unique Expertise, Guaranteed Results)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers 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.[/FONT]
[FONT=&]
[/FONT]
Ultima modifica: