U posljednjih par tjedana iman problem s Blue Screenom...komp mi se resetira često, ponekad i nekoliko puta dnevno.
Uglavnom, ovo je moja konfiguracija:
Intel Core 2 quad CPU Q8300, 2.50 Ghz
Nvidia GeForce GTS 250
Realtek PCIe GBE family controller
Asus Motherboard
Windows 7 32-bit operativni sustav
Problem koji mi izlista kad se ponovno uspijem ulogirati nakon Blue Screena je:
Potpis problema:
Naziv događaja koji opisuje problem: BlueScreen
Verzija OS-a: 6.1.7600.2.0.0.768.3
ID regionalnih postavki: 1033
Dodatne informacije o problemu:
BCCode: 124
BCP1: 00000000
BCP2: 8636D024
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Dosada sam pokušao updejtati/rerollati drivere za zvučnu karticu, grafičku, matičnu ploču...Pokušao sam s windows updateom, system restoreom, postavljenjem opskrbe energijom na "visoke performanse", čišćenjem registrya...
ali ništa od toga nije pomoglo!
Pokušao sam otvoriti minidump pomoću Debugging Tools for Windows, ali nisam siguran jesam li to dobro napravio, no uglavno piše slijedeće:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122910-34944-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: D:\Symbols
Executable search path is:
Unable to load image 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 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x82a4f000 PsLoadedModuleList = 0x82b97810
Debug session time: Wed Dec 29 01:14:17.922 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:10.748
Unable to load image 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
Mini Kernel Dump does not contain unloaded driver list
Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 8636d024, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8636d024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: 82a4f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8db83cc4 82b1dfc5 8636d008 82bb6c28 82bb6c20 nt+0x322493
8db83ce4 82b1edef 82bb6c20 8636d008 82bb6c50 nt+0xcefc5
8db83d00 82abcf3b 82bb6c20 00000000 8522ea70 nt+0xcfdef
8db83d50 82c5d6d3 00000001 a76cb78c 00000000 nt+0x6df3b
8db83d90 82b0f0f9 82abce2e 00000001 00000000 nt+0x20e6d3
00000000 00000000 00000000 00000000 00000000 nt+0xc00f9
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Čini mi se da ima nekih problema sa simbolima (koje sam skidao s neta), ali nisam siguran kako bi ovo trebalo izgledati, i može li se išta iz ovoga izvući o uzorku problema!
Ako ima neki drugi način da se prikaže minidump file, volio bih ga saznati!
U svakom slučaju, molim za pomoć jer su ovi učestali Bsod-ovi postali neizdrživi! :)
EDIT: evo i direktnog linka na minidump file:
