Kaj pomeni tale blue screen?
- Ustvarjalec teme Chimay
- Začetni datum
Idi v C:\Windows\Minidump in na to stran uploadaj dump file, ki se je ustvaril takrat ko si dobil ta blue screen. Potem pa prilepi tekst, ki ti ga izpljune ven. Tako bomo lahko ugotovili katera stvar (najverjetneje driver) povzroča BSOD.
Lahko preveriš tudi windows update history, ker v torek so bili novi updajti in možno da se ti je zraven tudi kak gonilnik posodobil.
Lahko preveriš tudi windows update history, ker v torek so bili novi updajti in možno da se ti je zraven tudi kak gonilnik posodobil.
Poskusi s pomočjo orodja Driver Verifier ugotoviti, kateri driver povzroča težave.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
Edit: vidim, da ste že ugotovili, da težave povzroča driver za Wifi mrežno. Probaj torej posodobiti ta driver in ga potem testiraj.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
Edit: vidim, da ste že ugotovili, da težave povzroča driver za Wifi mrežno. Probaj torej posodobiti ta driver in ga potem testiraj.
Nazadnje urejeno:
Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.
Primary 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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03047670
Debug session time: Mon Sep 24 14:58:07.156 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:10.389
*******************************************************************************
* *
* 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: fffff8800651c9e0, (reserved)
Arg3: 0000000000000002, (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
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x74
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800032fd0ba to fffff80002e821c0
STACK_TEXT:
fffff880`0651c928 fffff800`032fd0ba : 00000000`00000074 00000000`00000002 fffff880`0651c9e0 00000000`00000002 : nt!KeBugCheckEx
fffff880`0651c930 fffff800`03118e6a : 00000000`01b9dd6b fffffa80`018e6b50 00000000`00000080 fffffa80`0036d990 : nt!CmpLoadHiveThread+0x23a
fffff880`0651cc00 fffff800`02e72ec6 : fffff880`009eb180 fffffa80`018e6b50 fffff880`009f5fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0651cc40 00000000`00000000 : fffff880`0651d000 fffff880`06517000 fffff880`0651bf50 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpLoadHiveThread+23a
fffff800`032fd0ba 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: 4fa390f3
FAILURE_BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a
BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a
Followup: MachineOwner
---------
Mi lahko kdo pomaga kaj pomeni to?!
Primary 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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03047670
Debug session time: Mon Sep 24 14:58:07.156 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:10.389
*******************************************************************************
* *
* 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: fffff8800651c9e0, (reserved)
Arg3: 0000000000000002, (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
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x74
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800032fd0ba to fffff80002e821c0
STACK_TEXT:
fffff880`0651c928 fffff800`032fd0ba : 00000000`00000074 00000000`00000002 fffff880`0651c9e0 00000000`00000002 : nt!KeBugCheckEx
fffff880`0651c930 fffff800`03118e6a : 00000000`01b9dd6b fffffa80`018e6b50 00000000`00000080 fffffa80`0036d990 : nt!CmpLoadHiveThread+0x23a
fffff880`0651cc00 fffff800`02e72ec6 : fffff880`009eb180 fffffa80`018e6b50 fffff880`009f5fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0651cc40 00000000`00000000 : fffff880`0651d000 fffff880`06517000 fffff880`0651bf50 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpLoadHiveThread+23a
fffff800`032fd0ba 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: 4fa390f3
FAILURE_BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a
BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a
Followup: MachineOwner
---------
Mi lahko kdo pomaga kaj pomeni to?!
Podobne teme
