danima tražim po netu rešenje za BSOD i izgleda da je to najveći rebus koji postoji.
Čak nigde nisam ni pronašao neko definitivno rešenje.
Da li je to moguće?
Kod mene je situacija da se BSOD ne pojavljuje jedno vreme, a onda, pri paljenju računara, dva tri dana zaredom.
OS je Windows 7 Ultimate
Matična ploča:
GIGABYTE
GA-P55A-UD4
Procesor
INTEL i5-760 2.8GHz 8MB
Memorija
KINGSTON 4GB (2x2GB) 1600MHz DDR3 HyperX
Hard disk
WESTERN DIGITAL (SATA3)
Caviar Black 1TB 7k 64MB SATA300 WD1002FAEX
Grafička karta
Gainward GeForce® GTX 460 1024MB "GS"
Barcode : 4260183361190
Napajanje
CHIEFTEC CFT-650-14CS 650W
to je pto se tiče konfiguracije.
jedan od reporta izgleda ovako, imam još 6 ovakvih reporta, sa manje više istim analizama. S tim što se negde pojavljuje "IRQL_NOT_LESS_OR_EQUAL (a)", a negde "KMODE_EXCEPTION_NOT_HANDLED (1e)"
i negde je uzrok win32k.sys, negde ntkrnlmp.exe
Ima li niko ideju šta i kako..
hvala unapred
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\031211-23992-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03253000 PsLoadedModuleList = 0xfffff800`03490e50
Debug session time: Sat Mar 12 11:35:46.766 2011 (UTC + 1:00)
System Uptime: 0 days 0:00:56.249
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff800032e32b3}
Probably caused by : win32k.sys ( win32k!XDCOBJ::bCleanDC+1ce )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032e32b3, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fb0e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!IopCompleteRequest+ae3
fffff800`032e32b3 488b09 mov rcx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: wmpnscfg.exe
IRP_ADDRESS: ffffffffffffff89
TRAP_FRAME: fffff880092a2210 -- (.trap 0xfffff880092a2210)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880092a2418 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032e32b3 rsp=fffff880092a23a0 rbp=fffff880092a24f0
r8=0000000000000000 r9=fffff880092a24a0 r10=0000000000000002
r11=fffffa8004794840 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!IopCompleteRequest+0xae3:
fffff800`032e32b3 488b09 mov rcx,qword ptr [rcx] ds:c6a8:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032c2ca9 to fffff800032c3740
STACK_TEXT:
fffff880`092a20c8 fffff800`032c2ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`092a20d0 fffff800`032c1920 : fffff8a0`00000000 fffffa80`073a1190 00000000`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`092a2210 fffff800`032e32b3 : fffff880`01c87ee0 fffff880`00c87ec0 fffffa80`00000200 fffff800`032f6f8c : nt!KiPageFault+0x260
fffff880`092a23a0 fffff800`032a00b7 : 00000000`00000001 fffff800`032c2900 00000000`00000000 fffffa80`00000000 : nt!IopCompleteRequest+0xae3
fffff880`092a2470 fffff800`032a0477 : fffff880`092a27c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`092a24f0 fffff960`00136016 : fffff880`092a27c0 00000000`00000001 00000000`00000001 fffff800`0357ef87 : nt!KiApcInterrupt+0xd7
fffff880`092a2680 fffff960`0026c991 : fffff880`092a27c0 00000000`00000001 00000000`00000000 00000000`00000001 : win32k!XDCOBJ::bCleanDC+0x1ce
fffff880`092a2740 fffff960`001376e2 : fffff880`092a27c0 00000000`00000000 fffff900`00000001 fffff960`0013df12 : win32k!bDeleteDCInternalWorker+0x29
fffff880`092a27a0 fffff960`0013d542 : ffffffff`9601095b fffff880`092a2c1f 00000000`00000a18 00000000`ffffffff : win32k!bDeleteDCInternal+0x56
fffff880`092a27f0 fffff960`00134cac : 00000000`00000a18 fffff880`092a2c00 fffff900`c21f1680 fffff900`00000000 : win32k!NtGdiCloseProcess+0xee
fffff880`092a2850 fffff960`001343f3 : fffffa80`057af300 fffff880`092a2c20 00020508`00000000 fffff8a0`00147001 : win32k!GdiProcessCallout+0x200
fffff880`092a28d0 fffff800`035a66f1 : fffffa80`057af380 00000000`00000000 00000000`00000000 fffffa80`0761e660 : win32k!W32pProcessCallout+0x6b
fffff880`092a2900 fffff800`03580735 : 00000000`00000000 fffff800`035bfe01 fffffa80`78457300 00000000`00000000 : nt!PspExitThread+0x561
fffff880`092a29c0 fffff800`032a01cb : fffffa80`05f19501 fffffa80`06fbd870 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`092a29f0 fffff800`032a0610 : 00000000`00389000 fffff880`092a2a70 fffff800`0358084c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`092a2a70 fffff800`032c2a37 : 00000000`00000321 00000000`020ce970 00000000`00000000 0000007f`ffffffff : nt!KiInitiateUserApc+0x70
fffff880`092a2bb0 00000000`7734f9ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`020cefd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7734f9ea
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!XDCOBJ::bCleanDC+1ce
fffff960`00136016 e889c71500 call win32k!DEC_SHARE_REF_CNT (fffff960`002927a4)
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: win32k!XDCOBJ::bCleanDC+1ce
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d23ecb0
FAILURE_BUCKET_ID: X64_0xA_win32k!XDCOBJ::bCleanDC+1ce
BUCKET_ID: X64_0xA_win32k!XDCOBJ::bCleanDC+1ce
Followup: MachineOwner
---------