Tämä on jo toinen bluescreeni uudella koneella. Tässä on Minidump kansion tiedosto: Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\101112-19905-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Machine Name: Kernel base = 0xfffff800`0324a000 PsLoadedModuleList = 0xfffff800`0348e670 Debug session time: Thu Oct 11 15:16:58.419 2012 (UTC + 3:00) System Uptime: 0 days 0:19:13.231 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000B8, {fffffa800da1e060, fffff80003449cc0, 0, 0} *****turhaatekstiä***** Probably caused by : ntoskrnl.exe ( nt+81e7a ) Followup: MachineOwner --------- Tässä virhe teksti kun käynnistin koneen: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1035 Additional information about the problem: BCCode: 100000b8 BCP1: FFFFFA800DA1E060 BCP2: FFFFF80003449CC0 BCP3: 0000000000000000 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\101112-19905-01.dmp C:\Users\Cacceli\AppData\Local\Temp\WER-38376-0.sysdata.xml Ja sen ensimmäisen bluescreenin tässä: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1035 Additional information about the problem: BCCode: 100000b8 BCP1: FFFFF80003411CC0 BCP2: FFFFFA80069EB040 BCP3: 0000000000000000 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\090912-16957-01.dmp C:\Users\Cacceli\AppData\Local\Temp\WER-30295-0.sysdata.xml
Tässä on käsitelty ongelmaa ja ratkasuja siihen: http://www.sevenforums.com/crashes-debugging/23643-ntoskrnl-exe-bsod.html Ja tässä vielä YouTube video ntoskrnl.exe korjaamisesta http://www.youtube.com/watch?v=j69K9H87j2s OK?
