Ecran bleu Win 7 au démarrage [a priori résolu] - Win 7 - Windows & Software
MarshPosté le 21-09-2017 à 15:24:25
Bonjour à tous,
Je suis en train de me battre contre le PC de mon beau père (DELL INSPIRON), j'ai vérifié la mémoire et le disque, et systématiquement un écran bleu peu après l'entrée dans windows...
Restauration au point de sauvegarde.
Du coup j'ai été regarder le dump.
Une idée avant que je refasse une install propre sur un nouveau DD (ce que j'aimerais éviter...)?
Citation :
Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\MEMORY.DMP] Kernel Summary Dump File: Kernel address space is available, User address space may not be available.
************* Symbol Path validation summary ************** Response Time (ms) Location Deferred srv*c:\SymbolsSrvCache*https://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:\SymbolsSrvCache*https://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.23864.amd64fre.win7sp1_ldr.170707-0600 Machine Name: Kernel base = 0xfffff800`0365e000 PsLoadedModuleList = 0xfffff800`038a0750 Debug session time: Wed Sep 20 10:35:00.936 2017 (UTC + 2:00) System Uptime: 0 days 0:01:30.216 Loading Kernel Symbols ............................................................... ................................................................ ........................................... Loading User Symbols PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 51, {1, fffff8a000024410, 1887000, 374}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+96fa )
REGISTRY_ERROR (51) Something has gone badly wrong with the registry. If a kernel debugger is available, get a stack trace. It can also indicate that the registry got an I/O error while trying to read one of its files, so it can be caused by hardware problems or filesystem corruption. It may occur due to a failure in a refresh operation, which is used only in by the security system, and then only when resource limits are encountered. Arguments: Arg1: 0000000000000001, (reserved) Arg2: fffff8a000024410, (reserved) Arg3: 0000000001887000, depends on where Windows bugchecked, may be pointer to hive Arg4: 0000000000000374, depends on where Windows bugchecked, may be return code of HvCheckHive if the hive is corrupt.
Marsh Posté le 21-09-2017 à 15:24:25
Bonjour à tous,
Je suis en train de me battre contre le PC de mon beau père (DELL INSPIRON), j'ai vérifié la mémoire et le disque, et systématiquement un écran bleu peu après l'entrée dans windows...
Restauration au point de sauvegarde.
Du coup j'ai été regarder le dump.
Une idée avant que je refasse une install propre sur un nouveau DD (ce que j'aimerais éviter...)?
Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Kernel address space is available, User address space may not be available.
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\SymbolsSrvCache*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\SymbolsSrvCache*https://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.23864.amd64fre.win7sp1_ldr.170707-0600
Machine Name:
Kernel base = 0xfffff800`0365e000 PsLoadedModuleList = 0xfffff800`038a0750
Debug session time: Wed Sep 20 10:35:00.936 2017 (UTC + 2:00)
System Uptime: 0 days 0:01:30.216
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 51, {1, fffff8a000024410, 1887000, 374}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+96fa )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 0000000000000001, (reserved)
Arg2: fffff8a000024410, (reserved)
Arg3: 0000000001887000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 0000000000000374, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
SYSTEM_MANUFACTURER: Dell Inc.
SYSTEM_PRODUCT_NAME: Inspiron N5110
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: Not Specified
BIOS_VENDOR: Dell Inc.
BIOS_VERSION: A09
BIOS_DATE: 09/30/2011
BASEBOARD_MANUFACTURER: Dell Inc.
BASEBOARD_PRODUCT: 0FXK2Y
BASEBOARD_VERSION: A09
DUMP_TYPE: 1
BUGCHECK_P1: 1
BUGCHECK_P2: fffff8a000024410
BUGCHECK_P3: 1887000
BUGCHECK_P4: 374
CPU_COUNT: 4
CPU_MHZ: 9be
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 2a
CPU_STEPPING: 7
CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x51
PROCESS_NAME: services.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: LAPTOP-DTLED71H
ANALYSIS_SESSION_TIME: 09-21-2017 15:01:42.0083
ANALYSIS_VERSION: 10.0.15063.468 amd64fre
LAST_CONTROL_TRANSFER: from fffff80003a08b8a to fffff800036cd980
STACK_TEXT:
fffff880`03ee82f8 fffff800`03a08b8a : 00000000`00000051 00000000`00000001 fffff8a0`00024410 00000000`01887000 : nt!KeBugCheckEx
fffff880`03ee8300 fffff800`03965705 : 00000000`002a08f3 00000000`0000c437 00000000`00000000 fffff8a0`00000004 : nt! ?? ::NNGAKEGL::`string'+0x96fa
fffff880`03ee8360 fffff800`03965500 : fffff8a0`00024410 fffff8a0`00024410 fffff8a0`00032cc0 00000000`00066b76 : nt!HvMarkDirty+0x176
fffff880`03ee83c0 fffff800`0392ae0b : 00000000`00000001 fffff8a0`070b1384 fffff8a0`07150d04 fffff8a0`00024410 : nt!HvMarkCellDirty+0x150
fffff880`03ee8410 fffff800`0392abe4 : fffff8a0`07150d04 00000000`ffffffff fffff8a0`07150d04 fffff8a0`00024410 : nt!CmpMarkKeyValuesDirty+0x14b
fffff880`03ee84b0 fffff800`0392a2ea : fffff8a0`00024410 00000000`ffffffff fffff8a0`07150d04 fffff8a0`00024410 : nt!CmpFreeKeyValues+0x24
fffff880`03ee84e0 fffff800`0392a018 : fffff8a0`00024410 00000000`01518590 fffff8a0`07150d04 fffff8a0`0152ed00 : nt!CmpSyncKeyValues+0x7a
fffff880`03ee85c0 fffff800`0392bbbe : fffff8a0`04061000 00000000`003fa3b8 fffffa80`00000000 00000000`00000000 : nt!CmpCopySyncTree2+0x2a8
fffff880`03ee8670 fffff800`0392bad7 : 00000000`00000000 00000000`00000002 fffff8a0`0398abe0 fffff8a0`03e65bb0 : nt!CmpCopySyncTree+0x6e
fffff880`03ee86c0 fffff800`0392b6a6 : fffff8a0`0391a560 00000000`00000000 00000000`00000001 00000000`00000000 : nt!CmpSaveBootControlSet+0x307
fffff880`03ee88a0 fffff800`036ccc13 : fffffa80`0b52bb50 00000000`00000000 fffff880`03ee8970 00000000`00000001 : nt!NtInitializeRegistry+0xc6
fffff880`03ee88f0 fffff800`036c91d0 : fffff800`0392b64f 00000000`00000220 00000000`0013f628 00000000`0013f958 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03ee8a88 fffff800`0392b64f : 00000000`00000220 00000000`0013f628 00000000`0013f958 00000000`000a001f : nt!KiServiceLinkage
fffff880`03ee8a90 fffff800`036ccc13 : fffffa80`0b52bb50 fffff880`03ee8b60 fffff880`03ee8b60 00000000`00000002 : nt!NtInitializeRegistry+0x6f
fffff880`03ee8ae0 00000000`7754cada : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0013f8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7754cada
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 68af3893eaeea2b329cd8b5819f31ecea967365a
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 429cc6e8f4ec89db18cc160e9d9144719b269536
THREAD_SHA1_HASH_MOD: 38bc5fec3f0409c265cf5c87da6f8f8859d0711c
FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+96fa
fffff800`03a08b8a cc int 3
FAULT_INSTR_CODE: 9000ebcc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+96fa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 595fa11a
IMAGE_VERSION: 6.1.7601.23864
FAILURE_BUCKET_ID: X64_0x51_nt!_??_::NNGAKEGL::_string_+96fa
BUCKET_ID: X64_0x51_nt!_??_::NNGAKEGL::_string_+96fa
PRIMARY_PROBLEM_CLASS: X64_0x51_nt!_??_::NNGAKEGL::_string_+96fa
TARGET_TIME: 2017-09-20T08:35:00.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-07 16:56:26
BUILDDATESTAMP_STR: 170707-0600
BUILDLAB_STR: win7sp1_ldr
BUILDOSVER_STR: 6.1.7601.23864.amd64fre.win7sp1_ldr.170707-0600
ANALYSIS_SESSION_ELAPSED_TIME: 585
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x51_nt!_??_::nngakegl::_string_+96fa
FAILURE_ID_HASH: {9bbc707b-0728-7873-e127-fe37ddd29da0}
Followup: MachineOwner
---------
Message édité par vandepj0 le 21-09-2017 à 15:31:52