Odpowiedz

Częste Bluescreeny w laptopie Samsunga R580 // SO Win7x64

 
zidus
Wdrażany
Liczba postów: 13
Post: #1

Częste Bluescreeny w laptopie Samsunga R580 // SO Win7x64


Witam wszystkich.
Mam do was ogromną prośbę, może ktoś właśnie z waszego grona będzie w stanie mi pomóc bo ja niestety nie mam już sił do mojego laptopa.
Może opowiem tak w skrócie co się dzieje.
Jakiś czas temu oddałem laptopa do serwisu, gdyż zupełnie matryca nie wyświetlała obrazu jak i jeszcze wcześniej kamerka internetowa też padła.
No i już w tamtym czasie miałem problemy z Bsod'ami, ale nie w takich ilościach.
Czekałem ponad 2 tyg na laptopa no i zadowolony ze WSZYSTKO W KOŃCU będzie działało jak należy, zostałem niemile rozczarowany. Ilość bluescreenow jaka sie teraz pojawia na dzień jest niemożliwa. Jak można w ogóle oddać klientowi laptopa, jeżeli takie rzeczy się dzieją. Jestem już własnie trochę uprzedzony co do tego serwisu, i chciałbym jakoś sam sobie dać rade z tym.
Jedna rzecz ze będę zupełnie bez laptopa tyle czasu, a i tak nie wiadomo czy znowu nie oddadzą mi takiego niesprawnego. Jedynie co naprawili to faktycznie ta matryca i kamerka internetowa, ale co mi z tego jeżeli co kilka chwil mi się komp restartuje.
Już próbowałem przeinstalować system i wszystkie sterowniki ze stron producenta. Jednak nadal nic to nie dało.

Mój laptop to NP-Samsung-R580-JSO4PL, wiec specyfikacje możecie zobaczyć na internecie jeżeli będzie do czegoś potrzebna.

System operacyjny to Windows 7 Ultimate x64

Dołączam również screenshot z hdtune

http://imageshack.us/f/34/hdtunet.jpg/

Poniżej zamieszczam kilka ostatnich wycinków z Windbg oraz całość tutaj ===> http://wyslijto.pl/plik/sxdyo30jr2 .


Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\072511-16567-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`0304ee50
Debug session time:  Mon Jul 25 20: 17: 31.028 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 17: 09.589
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {3, 2, 0, fffff8800440af98}

Probably caused by :  dxgmms1.sys ( dxgmms1!VidSchiSwitchContextWithCheck+148 )

Followup:  MachineOwner
---------

2:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1:  0000000000000003, memory referenced
Arg2:  0000000000000002, IRQL
Arg3:  0000000000000000, value 0 = read operation, 1 = write operation
Arg4:  fffff8800440af98, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS:  GetPointerFromAddress:  unable to read from fffff800030b90e0
0000000000000003

CURRENT_IRQL:   2

FAULTING_IP:  
dxgmms1!VidSchiSwitchContextWithCheck+148
fffff880`0440af98 488b742470      mov     rsi,qword ptr [rsp+70h]

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xD1

PROCESS_NAME:   System

TRAP_FRAME:   fffff88005df2a00 -- (.trap 0xfffff88005df2a00)
NOTE:  The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800440af98 rsp=fffff88005df2b90 rbp=fffffa8003a72340
r8=000000000000233e  r9=0000000000000000 r10=0000000000000001
r11=fffffa8003af3330 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms1!VidSchiSwitchContextWithCheck+0x148:
fffff880`0440af98 488b742470      mov     rsi,qword ptr [rsp+70h] ss: 0018: fffff880`05df2c00=0000000000000000
Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff80002e82469 to fffff80002e82f00

STACK_TEXT:  
fffff880`05df28b8 fffff800`02e82469 :  00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000000 :  nt!KeBugCheckEx
fffff880`05df28c0 fffff800`02e810e0 :  00000000`00000000 fffa8003`a72340ff 00000000`00000000 00000000`00000000 :  nt!KiBugCheckDispatch+0x69
fffff880`05df2a00 fffff880`0440af98 :  fffffa80`03a72340 00000000`00000001 fffffa80`07526000 fffffa80`0744b410 :  nt!KiPageFault+0x260
fffff880`05df2b90 fffff880`0440b193 :  fffffa80`0744b410 fffffa80`03a72340 00000000`00000000 00000000`00000000 :  dxgmms1!VidSchiSwitchContextWithCheck+0x148
fffff880`05df2bf0 fffff880`04437e7a :  00000000`00000000 fffffa80`03a72340 00000000`00000080 fffffa80`0744b410 :  dxgmms1!VidSchiScheduleCommandToRun+0xa7
fffff880`05df2d00 fffff800`03126166 :  00000000`019b9d4b fffffa80`071f8b60 fffffa80`036cd740 fffffa80`071f8b60 :  dxgmms1!VidSchiWorkerThread+0xba
fffff880`05df2d40 fffff800`02e61486 :  fffff800`02ffbe80 fffffa80`071f8b60 fffff800`03009c40 fffff880`01427534 :  nt!PspSystemThreadStartup+0x5a
fffff880`05df2d80 00000000`00000000 :  fffff880`05df3000 fffff880`05ded000 fffff880`05df2690 00000000`00000000 :  nt!KxStartSystemThread+0x16


STACK_COMMAND:   kb

FOLLOWUP_IP:  
dxgmms1!VidSchiSwitchContextWithCheck+148
fffff880`0440af98 488b742470      mov     rsi,qword ptr [rsp+70h]

SYMBOL_STACK_INDEX:   3

SYMBOL_NAME:   dxgmms1!VidSchiSwitchContextWithCheck+148

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  dxgmms1

IMAGE_NAME:   dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4a5bc578

FAILURE_BUCKET_ID:   X64_0xD1_dxgmms1!VidSchiSwitchContextWithCheck+148

BUCKET_ID:   X64_0xD1_dxgmms1!VidSchiSwitchContextWithCheck+148

Followup:  MachineOwner
---------

2:  kd> lmvm dxgmms1
start             end                 module name
fffff880`04400000 fffff880`04446000   dxgmms1    (pdb symbols)          c: \symbols\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
    Loaded symbol image file:  dxgmms1.sys
    Mapped memory image file:  c: \symbols\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
    Image path:  \SystemRoot\System32\drivers\dxgmms1.sys
    Image name:  dxgmms1.sys
    Timestamp:         Tue Jul 14 01: 38: 32 2009 (4A5BC578)
    CheckSum:          0004AD44
    ImageSize:         00046000
    File version:      6.1.7600.16385
    Product version:   6.1.7600.16385
    File flags:        0 (Mask 3F)
    File OS:           40004 NT Win32
    File type:         3.7 Driver
    File date:         00000000.00000000
    Translations:      0409.04b0
    CompanyName:       Microsoft Corporation
    ProductName:       Microsoft® Windows® Operating System
    InternalName:      dxgmms1.sys
    OriginalFilename:  dxgmms1.sys
    ProductVersion:    6.1.7600.16385
    FileVersion:       6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:   DirectX Graphics MMS
    LegalCopyright:    © Microsoft Corporation. All rights reserved.

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\072611-26348-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`0304fe50
Debug session time:  Tue Jul 26 16: 17: 41.046 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 04: 53.607
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880101ce40d, fffff880061e61c0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING:  Unable to verify timestamp for nvlddmkm.sys
*** ERROR:  Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :  hardware ( nvlddmkm+13040d )

Followup:  MachineOwner
---------

2:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1:  00000000c0000005, Exception code that caused the bugcheck
Arg2:  fffff880101ce40d, Address of the instruction which caused the bugcheck
Arg3:  fffff880061e61c0, Address of the context record for the exception that caused the bugcheck
Arg4:  0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE:  (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:  
nvlddmkm+13040d
fffff880`101ce40d 4c0900          or      qword ptr [rax],r8

CONTEXT:   fffff880061e61c0 -- (.cxr 0xfffff880061e61c0)
rax=0000000000000000 rbx=0000000000000007 rcx=00000000ffffffff
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa800719a010
rip=fffff880101ce40d rsp=fffff880061e6ba0 rbp=fffffa8007f565d0
r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=0000000000000001 r12=fffffa8006aea000 r13=fffffa80080bfb70
r14=0000000000000000 r15=fffff880061e7600
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x13040d:
fffff880`101ce40d 4c0900          or      qword ptr [rax],r8 ds: 002b: 00000000`00000000=?
Resetting default scope

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0x3B

PROCESS_NAME:   dwm.exe

CURRENT_IRQL:   0

MISALIGNED_IP:  
nvlddmkm+13040d
fffff880`101ce40d 4c0900          or      qword ptr [rax],r8

LAST_CONTROL_TRANSFER:   from 0000000000000001 to fffff880101ce40d

STACK_TEXT:  
fffff880`061e6ba0 00000000`00000001 :  fffffa80`0719a000 00000000`00000000 fffffa80`0719a010 fffff880`061e7100 :  nvlddmkm+0x13040d
fffff880`061e6ba8 fffffa80`0719a000 :  00000000`00000000 fffffa80`0719a010 fffff880`061e7100 fffff880`00000003 :  0x1
fffff880`061e6bb0 00000000`00000000 :  fffffa80`0719a010 fffff880`061e7100 fffff880`00000003 00000000`00000000 :  0xfffffa80`0719a000


FOLLOWUP_IP:  
nvlddmkm+13040d
fffff880`101ce40d 4c0900          or      qword ptr [rax],r8

SYMBOL_STACK_INDEX:   0

SYMBOL_NAME:   nvlddmkm+13040d

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  hardware

IMAGE_NAME:   hardware

DEBUG_FLR_IMAGE_TIMESTAMP:   0

STACK_COMMAND:   .cxr 0xfffff880061e61c0 ; kb

FAILURE_BUCKET_ID:   X64_IP_MISALIGNED_nvlddmkm.sys

BUCKET_ID:   X64_IP_MISALIGNED_nvlddmkm.sys

Followup:  MachineOwner
---------

2:  kd> lmvm hardware
start             end                 module name

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\072811-17487-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`03251e50
Debug session time:  Thu Jul 28 12: 33: 25.364 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 25: 13.550
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000121df6, fffff88002a7fe00, 0}

Probably caused by :  win32k.sys ( win32k!UpdateAsyncKeyState+116 )

Followup:  MachineOwner
---------

3:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1:  00000000c0000005, Exception code that caused the bugcheck
Arg2:  fffff96000121df6, Address of the instruction which caused the bugcheck
Arg3:  fffff88002a7fe00, Address of the context record for the exception that caused the bugcheck
Arg4:  0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE:  (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:  
win32k!UpdateAsyncKeyState+116
fffff960`00121df6 4308941088000000 or      byte ptr [r8+r10+88h],dl

CONTEXT:   fffff88002a7fe00 -- (.cxr 0xfffff88002a7fe00)
rax=fffff900c0580a70 rbx=fffff900c06706d0 rcx=0000000000000002
rdx=0000000000000004 rsi=0000000000000002 rdi=0000000000000002
rip=fffff96000121df6 rsp=fffff88002a807e0 rbp=0000000000000002
r8=0000000000000000  r9=fffff900c220a900 r10=0000000000017c8b
r11=fffffa8007a5d528 r12=0000000000000001 r13=0000000000000002
r14=0000000000000002 r15=00000000016b0303
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!UpdateAsyncKeyState+0x116:
fffff960`00121df6 4308941088000000 or      byte ptr [r8+r10+88h],dl ds: 002b: 00000000`00017d13=?
Resetting default scope

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0x3B

PROCESS_NAME:   csrss.exe

CURRENT_IRQL:   0

LAST_CONTROL_TRANSFER:   from 0000000000000000 to fffff96000121df6

STACK_TEXT:  
fffff880`02a807e0 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  win32k!UpdateAsyncKeyState+0x116


FOLLOWUP_IP:  
win32k!UpdateAsyncKeyState+116
fffff960`00121df6 4308941088000000 or      byte ptr [r8+r10+88h],dl

SYMBOL_STACK_INDEX:   0

SYMBOL_NAME:   win32k!UpdateAsyncKeyState+116

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  win32k

IMAGE_NAME:   win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4df2d94e

STACK_COMMAND:   .cxr 0xfffff88002a7fe00 ; kb

FAILURE_BUCKET_ID:   X64_0x3B_win32k!UpdateAsyncKeyState+116

BUCKET_ID:   X64_0x3B_win32k!UpdateAsyncKeyState+116

Followup:  MachineOwner
---------

3:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1:  00000000c0000005, Exception code that caused the bugcheck
Arg2:  fffff96000121df6, Address of the instruction which caused the bugcheck
Arg3:  fffff88002a7fe00, Address of the context record for the exception that caused the bugcheck
Arg4:  0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE:  (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:  
win32k!UpdateAsyncKeyState+116
fffff960`00121df6 4308941088000000 or      byte ptr [r8+r10+88h],dl

CONTEXT:   fffff88002a7fe00 -- (.cxr 0xfffff88002a7fe00)
rax=fffff900c0580a70 rbx=fffff900c06706d0 rcx=0000000000000002
rdx=0000000000000004 rsi=0000000000000002 rdi=0000000000000002
rip=fffff96000121df6 rsp=fffff88002a807e0 rbp=0000000000000002
r8=0000000000000000  r9=fffff900c220a900 r10=0000000000017c8b
r11=fffffa8007a5d528 r12=0000000000000001 r13=0000000000000002
r14=0000000000000002 r15=00000000016b0303
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!UpdateAsyncKeyState+0x116:
fffff960`00121df6 4308941088000000 or      byte ptr [r8+r10+88h],dl ds: 002b: 00000000`00017d13=?
Resetting default scope

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0x3B

PROCESS_NAME:   csrss.exe

CURRENT_IRQL:   0

LAST_CONTROL_TRANSFER:   from 0000000000000000 to fffff96000121df6

STACK_TEXT:  
fffff880`02a807e0 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  win32k!UpdateAsyncKeyState+0x116


FOLLOWUP_IP:  
win32k!UpdateAsyncKeyState+116
fffff960`00121df6 4308941088000000 or      byte ptr [r8+r10+88h],dl

SYMBOL_STACK_INDEX:   0

SYMBOL_NAME:   win32k!UpdateAsyncKeyState+116

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  win32k

IMAGE_NAME:   win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4df2d94e

STACK_COMMAND:   .cxr 0xfffff88002a7fe00 ; kb

FAILURE_BUCKET_ID:   X64_0x3B_win32k!UpdateAsyncKeyState+116

BUCKET_ID:   X64_0x3B_win32k!UpdateAsyncKeyState+116

Followup:  MachineOwner
---------

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\072811-16052-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`03287e50
Debug session time:  Thu Jul 28 14: 48: 41.239 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 09: 42.800
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {3c00000000, 5, 8, 3c00000000}

Probably caused by :  ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup:  MachineOwner
---------

1:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1:  0000003c00000000, memory referenced
Arg2:  0000000000000005, IRQL
Arg3:  0000000000000008, value 0 = read operation, 1 = write operation
Arg4:  0000003c00000000, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS:  GetPointerFromAddress:  unable to read from fffff800032f20e0
0000003c00000000

CURRENT_IRQL:   5

FAULTING_IP:  
+3063306237376236
0000003c`00000000 ?              ?

PROCESS_NAME:   System

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xD1

TRAP_FRAME:   fffff8800331b090 -- (.trap 0xfffff8800331b090)
NOTE:  The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000331b398 rbx=0000000000000000 rcx=fffffa8003dab000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000003c00000000 rsp=fffff8800331b228 rbp=0000000000000000
r8=0000000000000000  r9=0000000000000002 r10=fffff880109473e0
r11=fffff8800331b398 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
0000003c`00000000 ?              ?
Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff800030bb469 to fffff800030bbf00

FAILED_INSTRUCTION_ADDRESS:  
+3063306237376236
0000003c`00000000 ?              ?

STACK_TEXT:  
fffff880`0331af48 fffff800`030bb469 :  00000000`0000000a 0000003c`00000000 00000000`00000005 00000000`00000008 :  nt!KeBugCheckEx
fffff880`0331af50 fffff800`030ba0e0 :  00000000`00000202 00000000`00000001 fffff800`03234e80 fffffa80`044b8680 :  nt!KiBugCheckDispatch+0x69
fffff880`0331b090 0000003c`00000000 :  00000000`00000001 00000000`00000000 00001580`00000000 00000000`00000000 :  nt!KiPageFault+0x260
fffff880`0331b228 00000000`00000001 :  00000000`00000000 00001580`00000000 00000000`00000000 00000000`0000cf00 :  0x3c`00000000
fffff880`0331b230 00000000`00000000 :  00001580`00000000 00000000`00000000 00000000`0000cf00 fffffa80`00000000 :  0x1


STACK_COMMAND:   kb

FOLLOWUP_IP:  
nt!KiPageFault+260
fffff800`030ba0e0 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:   2

SYMBOL_NAME:   nt!KiPageFault+260

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

IMAGE_NAME:   ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:   4a5bc600

FAILURE_BUCKET_ID:   X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

BUCKET_ID:   X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

Followup:  MachineOwner
---------

1:  kd> lmvm nt
start             end                 module name
fffff800`0304a000 fffff800`03627000   nt         (pdb symbols)          c: \symbols\ntkrnlmp.pdb\F8E2A8B5C9B74BF4A6E4A48F180099942\ntkrnlmp.pdb
    Loaded symbol image file:  ntkrnlmp.exe
    Mapped memory image file:  c: \symbols\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
    Image path:  ntkrnlmp.exe
    Image name:  ntkrnlmp.exe
    Timestamp:         Tue Jul 14 01: 40: 48 2009 (4A5BC600)
    CheckSum:          0054B487
    ImageSize:         005DD000
    File version:      6.1.7600.16385
    Product version:   6.1.7600.16385
    File flags:        0 (Mask 3F)
    File OS:           40004 NT Win32
    File type:         1.0 App
    File date:         00000000.00000000
    Translations:      0409.04b0
    CompanyName:       Microsoft Corporation
    ProductName:       Microsoft® Windows® Operating System
    InternalName:      ntkrnlmp.exe
    OriginalFilename:  ntkrnlmp.exe
    ProductVersion:    6.1.7600.16385
    FileVersion:       6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:   NT Kernel & System
    LegalCopyright:    © Microsoft Corporation. All rights reserved.

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\072811-14211-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0304e000 PsLoadedModuleList = 0xfffff800`0328be50
Debug session time:  Thu Jul 28 22: 10: 37.784 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 48: 43.970
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff800030e535f}

Probably caused by :  memory_corruption ( nt!MiReplenishPageSlist+100 )

Followup:  MachineOwner
---------

0:  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:  0000000000000010, memory referenced
Arg2:  0000000000000002, IRQL
Arg3:  0000000000000001, 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:  fffff800030e535f, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  GetPointerFromAddress:  unable to read from fffff800032f60e0
0000000000000010

CURRENT_IRQL:   2

FAULTING_IP:  
nt!MiReplenishPageSlist+100
fffff800`030e535f f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xA

PROCESS_NAME:   war3.exe

TRAP_FRAME:   fffff88007d6e6c0 -- (.trap 0xfffff88007d6e6c0)
NOTE:  The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=fdffffffffffffff
rdx=000000000000004f rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030e535f rsp=fffff88007d6e850 rbp=fffffa80036006b8
r8=fffff800032f8400  r9=fffffa8003600000 r10=fffffa80036006d8
r11=fffff88007d6e8a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiReplenishPageSlist+0x100:
fffff800`030e535f f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds: c590: 00000000`00000010=?
Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff800030bf469 to fffff800030bff00

STACK_TEXT:  
fffff880`07d6e578 fffff800`030bf469 :  00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 :  nt!KeBugCheckEx
fffff880`07d6e580 fffff800`030be0e0 :  fffff800`0328c728 00000000`00000000 fffff880`07d6e700 fffffa80`036de1c0 :  nt!KiBugCheckDispatch+0x69
fffff880`07d6e6c0 fffff800`030e535f :  00000000`00004698 fffff880`07d6ec01 fffff880`07d6e860 fffff880`07d6e860 :  nt!KiPageFault+0x260
fffff880`07d6e850 fffff800`030e588f :  fffff800`032f8400 00000000`0000002b fffffa80`00073410 fffffa80`001f6410 :  nt!MiReplenishPageSlist+0x100
fffff880`07d6e8b0 fffff800`030dda97 :  00000000`00000002 00000000`00000002 fffffa80`04b0c928 00000000`00000002 :  nt!MiRemoveAnyPage+0x24f
fffff880`07d6e9d0 fffff800`030da1a6 :  00000000`00000001 00000000`18cf001c fffff880`07d6ec20 fffff680`000c6780 :  nt!MiResolveDemandZeroFault+0x577
fffff880`07d6eac0 fffff800`030bdfee :  00000000`00000001 00000000`00000000 00000000`00000001 00000000`08ae2ae8 :  nt!MmAccessFault+0x5c6
fffff880`07d6ec20 00000000`15023f5e :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiPageFault+0x16e
00000000`0018e654 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  0x15023f5e


STACK_COMMAND:   kb

FOLLOWUP_IP:  
nt!MiReplenishPageSlist+100
fffff800`030e535f f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:   3

SYMBOL_NAME:   nt!MiReplenishPageSlist+100

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

DEBUG_FLR_IMAGE_TIMESTAMP:   4a5bc600

IMAGE_NAME:   memory_corruption

FAILURE_BUCKET_ID:   X64_0xA_nt!MiReplenishPageSlist+100

BUCKET_ID:   X64_0xA_nt!MiReplenishPageSlist+100

Followup:  MachineOwner
---------

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\072811-13228-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03006000 PsLoadedModuleList = 0xfffff800`03243e50
Debug session time:  Thu Jul 28 22: 18: 12.118 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 07: 11.304
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000336e682, fffff88007bddee0, 0}

Probably caused by :  ntkrnlmp.exe ( nt!ObpLookupObjectName+4a3 )

Followup:  MachineOwner
---------

0:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1:  00000000c0000005, Exception code that caused the bugcheck
Arg2:  fffff8000336e682, Address of the instruction which caused the bugcheck
Arg3:  fffff88007bddee0, Address of the context record for the exception that caused the bugcheck
Arg4:  0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE:  (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:  
nt!ObpLookupObjectName+4a3
fffff800`0336e682 448bc5          mov     r8d,ebp

CONTEXT:   fffff88007bddee0 -- (.cxr 0xfffff88007bddee0)
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8a000004810
rdx=fffff88007bde960 rsi=fffffa8003b0ccc8 rdi=0000000000000000
rip=fffff8000336e682 rsp=fffff88007bde8c0 rbp=0000000000000040
r8=fffffa800366af30  r9=0000000000000001 r10=fffff8a000004810
r11=fffffa8003978630 r12=fffff8a000004701 r13=fffff88007bdea20
r14=fffff8a000004810 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
nt!ObpLookupObjectName+0x4a3:
fffff800`0336e682 448bc5          mov     r8d,ebp
Resetting default scope

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0x3B

PROCESS_NAME:   war3.exe

CURRENT_IRQL:   0

LAST_CONTROL_TRANSFER:   from 0000000000000000 to fffff8000336e682

STACK_TEXT:  
fffff880`07bde8c0 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!ObpLookupObjectName+0x4a3


FOLLOWUP_IP:  
nt!ObpLookupObjectName+4a3
fffff800`0336e682 448bc5          mov     r8d,ebp

SYMBOL_STACK_INDEX:   0

SYMBOL_NAME:   nt!ObpLookupObjectName+4a3

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

IMAGE_NAME:   ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:   4a5bc600

STACK_COMMAND:   .cxr 0xfffff88007bddee0 ; kb

FAILURE_BUCKET_ID:   X64_0x3B_nt!ObpLookupObjectName+4a3

BUCKET_ID:   X64_0x3B_nt!ObpLookupObjectName+4a3

Followup:  MachineOwner
---------

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [CWindowsMinidump072911-13634-01.dmp]
Mini Kernel Dump File Only registers and stack trace are available

Symbol search path is SRVcsymbolshttpmsdl.microsoft.comdownloadsymbols
Executable search path is
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product WinNt, suite TerminalServer SingleUserTS
Built by 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e50
Debug session time Fri Jul 29 002001.102 2011 (UTC + 200)
System Uptime 0 days 04246.663
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....

                                                                            
                        Bugcheck Analysis                                    
                                                                            


Use !analyze -v to get detailed debugging information.

BugCheck A, {20, 2, 1, fffff800030d0714}

Probably caused by  hardware ( tcpip!TcpRestructureHashTablePartitions+23 )

Followup MachineOwner
---------

0 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 0000000000000020, memory referenced
Arg2 0000000000000002, IRQL
Arg3 0000000000000001, 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 fffff800030d0714, address which referenced memory

Debugging Details
------------------


WRITE_ADDRESS GetPointerFromAddress unable to read from fffff800032fc0e0
0000000000000020

CURRENT_IRQL  2

FAULTING_IP
nt!KeQueryMaximumProcessorCountEx+4
fffff800`030d0714 ff00            inc     dword ptr [rax]

CUSTOMER_CRASH_COUNT  1

DEFAULT_BUCKET_ID  VISTA_DRIVER_FAULT

BUGCHECK_STR  0xA

PROCESS_NAME  System

TRAP_FRAME  fffff80004787300 -- (.trap 0xfffff80004787300)
NOTE The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000020 rbx=0000000000000000 rcx=000000000000ffff
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030d0714 rsp=fffff80004787498 rbp=0000000000000000
r8=fffffa80045cee80  r9=fffffa80046bc000 r10=fffff8000323ee80
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeQueryMaximumProcessorCountEx+0x4
fffff800`030d0714 ff00            inc     dword ptr [rax] dsed4000000000`00000020=
Resetting default scope

MISALIGNED_IP
nt!KeQueryMaximumProcessorCountEx+4
fffff800`030d0714 ff00            inc     dword ptr [rax]

LAST_CONTROL_TRANSFER  from fffff800030c5469 to fffff800030c5f00

STACK_TEXT  
fffff800`047871b8 fffff800`030c5469  00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000001  nt!KeBugCheckEx
fffff800`047871c0 fffff800`030c40e0  00000000`00000000 00000000`00000020 00000000`00000002 fffffa80`03ce4c68  nt!KiBugCheckDispatch+0x69
fffff800`04787300 fffff800`030d0714  fffff880`01a81e23 fffffa80`045d6a60 fffff880`01a763b9 fffffa80`045d6a60  nt!KiPageFault+0x260
fffff800`04787498 fffff880`01a81e23  fffffa80`045d6a60 fffff880`01a763b9 fffffa80`045d6a60 ffff0080`05cef555  nt!KeQueryMaximumProcessorCountEx+0x4
fffff800`047874a0 fffff880`01a75c3a  00000000`00000000 00000000`0003eab6 00000000`00000000 fffffa80`045d6a60  tcpip!TcpRestructureHashTablePartitions+0x23
fffff800`047874f0 fffff800`030d1fa6  fffff800`04787600 00000000`00024e9f 00000000`00000001 00000000`00000000  tcpip!TcpPeriodicTimeoutHandler+0x2db
fffff800`04787570 fffff800`030d1326  fffffa80`045d6b30 00000000`000282b0 00000000`00000000 00000000`00000000  nt!KiProcessTimerDpcTable+0x66
fffff800`047875e0 fffff800`030d1e7e  00000005`f9d9ce7e fffff800`04787c58 00000000`000282b0 fffff800`03242888  nt!KiProcessExpiredTimerList+0xc6
fffff800`04787c30 fffff800`030d1697  00000001`65ba8fc1 00000001`000282b0 00000001`65ba8f54 00000000`000000b0  nt!KiTimerExpiration+0x1be
fffff800`04787cd0 fffff800`030ce6fa  fffff800`0323ee80 fffff800`0324cc40 00000000`00000001 fffff880`00000000  nt!KiRetireDpcList+0x277
fffff800`04787d80 00000000`00000000  fffff800`04788000 fffff800`04782000 fffff800`04787d40 00000000`00000000  nt!KiIdleLoop+0x5a


STACK_COMMAND  kb

FOLLOWUP_IP
tcpip!TcpRestructureHashTablePartitions+23
fffff880`01a81e23 0fb71550c11000  movzx   edx,word ptr [tcpip!PartitionCount (fffff880`01b8df7a)]

SYMBOL_STACK_INDEX  4

SYMBOL_NAME  tcpip!TcpRestructureHashTablePartitions+23

FOLLOWUP_NAME  MachineOwner

IMAGE_NAME  hardware

DEBUG_FLR_IMAGE_TIMESTAMP  0

MODULE_NAME hardware

FAILURE_BUCKET_ID  X64_IP_MISALIGNED

BUCKET_ID  X64_IP_MISALIGNED

Followup MachineOwner
---------

Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\072911-13930-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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`03248e50
Debug session time:  Fri Jul 29 13: 52: 51.565 2011 (UTC + 2: 00)
System Uptime:  0 days 0: 29: 37.126
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff9600000b958, 8, fffff9600000b958, 0}


Could not read faulting driver name
Probably caused by :  dxgkrnl.sys ( dxgkrnl!DXGCONTEXT: Present+15ae )

Followup:  MachineOwner
---------

2:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1:  fffff9600000b958, memory referenced.
Arg2:  0000000000000008, value 0 = read operation, 1 = write operation.
Arg3:  fffff9600000b958, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4:  0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS:  GetPointerFromAddress:  unable to read from fffff800032b30e0
fffff9600000b958

FAULTING_IP:  
+6566653665393636
fffff960`0000b958 ?              ?

MM_INTERNAL_CODE:   0

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0x50

PROCESS_NAME:   war3.exe

CURRENT_IRQL:   0

TRAP_FRAME:   fffff88008bd83c0 -- (.trap 0xfffff88008bd83c0)
NOTE:  The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0085c8810 rbx=0000000000000000 rcx=fffff8a0083d1758
rdx=fffff8a0073fcde0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600000b958 rsp=fffff88008bd8558 rbp=fffff8a0085aa5f0
r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
fffff960`0000b958 ?              ?
Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff800030fc1e4 to fffff8000307cf00

STACK_TEXT:  
fffff880`08bd8258 fffff800`030fc1e4 :  00000000`00000050 fffff960`0000b958 00000000`00000008 fffff880`08bd83c0 :  nt!KeBugCheckEx
fffff880`08bd8260 fffff800`0307afee :  00000000`00000008 00000000`00002ac6 fffffa80`07f73800 00000000`00000000 :  nt! ? : FNODOBFM: `string'+0x42907
fffff880`08bd83c0 fffff960`0000b958 :  fffff880`046c7a32 00000000`00000000 00000000`00000000 fffff880`08bd8930 :  nt!KiPageFault+0x16e
fffff880`08bd8558 fffff880`046c7a32 :  00000000`00000000 00000000`00000000 fffff880`08bd8930 fffff880`08bd8930 :  0xfffff960`0000b958
fffff880`08bd8560 fffff880`046c5e7b :  fffff8a0`40002680 fffff8a0`00000556 fffff880`08bd88c0 fffff880`08bd88f0 :  dxgkrnl!DXGCONTEXT: Present+0x15ae
fffff880`08bd8880 fffff960`0023e524 :  fffffa80`049c8350 00000000`7efdb000 00000000`0000af31 00000000`00000000 :  dxgkrnl!DxgkPresent+0x543
fffff880`08bd8bf0 fffff800`0307c153 :  fffffa80`049c8350 fffffa80`03f2ece0 00000000`00000000 fffffa80`03f2ece0 :  win32k!NtGdiDdDDIPresent+0x18
fffff880`08bd8c20 00000000`737515da :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13
00000000`0008e558 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  0x737515da


STACK_COMMAND:   kb

FOLLOWUP_IP:  
dxgkrnl!DXGCONTEXT: Present+15ae
fffff880`046c7a32 3bd8            cmp     ebx,eax

SYMBOL_STACK_INDEX:   4

SYMBOL_NAME:   dxgkrnl!DXGCONTEXT: Present+15ae

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  dxgkrnl

IMAGE_NAME:   dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4d3fa1a0

FAILURE_BUCKET_ID:   X64_0x50_dxgkrnl!DXGCONTEXT: Present+15ae

BUCKET_ID:   X64_0x50_dxgkrnl!DXGCONTEXT: Present+15ae

Followup:  MachineOwner
---------


Jezeli ktoś miałby jakis pomysł to proszę pisać, z góry serdecznie dziekuje
Notatka została dodana nie znane. Ostatnia edycja dokonana 29.07.2011 19:28 przez peciaq:

Proszę poprawić tytuł na jakiś więcej mówiący o problemie. Samo 'częste bluescreeny' niczego nie wyjaśnia.
Proszę również poprawić cały post pod kątem braku polskich znaków oraz literówek.

(Ten post był ostatnio modyfikowany: 29.07.2011 19:36 przez zidus.)

29.07.2011 13:22

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
thermalfake
Ostatni Mohikanin

Liczba postów: 13.580
Post: #2

RE: Częste Bluescreeny


Żaden serwis nie będzie Ci całego sprzętu sprawdzał od a-z, wpisałeś 2 usterki więc je naprawiono. Podejrzewam, iż nawet nie odpalano twojego systemu tylko jakiś systemik livecd czy cuś podobnego. Nikt się nie będzie nad nim rozczulał, jest przerób masowy, nie jesteś tylko Ty jeden w kolejce.

[Obrazek: 2089620800_1406976151.png]

W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.

29.07.2011 18:39

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
zidus
Wdrażany
Liczba postów: 13
Post: #3

RE: Częste Bluescreeny w laptopie Samsunga R580 // SO Win7x64


Żadnych pomysłów ?

30.07.2011 12:53

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
Odpowiedz

Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
Windows 7 - Częste zawieszenia - Brak Odpowiedzi Programy się długo uruchamiają jackadam 1 1.555 18.01.2017 12:19
Ostatni post: AntrixPL
Problemy z Win7 - częste BSOD-y dominik04u 0 1.062 14.10.2016 09:15
Ostatni post: dominik04u
Win7x64 usługi i narzędzia diagnostyki nie działają. Piotrekop 2 1.732 29.09.2016 18:06
Ostatni post: Piotrekop
Windows 7 - Bluescreeny i crash'e gier. qudelzin 4 1.859 11.03.2016 16:23
Ostatni post: qudelzin
Częste niespodziewane wyłączenie komputera viserion 4 3.199 12.02.2016 01:24
Ostatni post: viserion
"brak odpowiedzi" i częste przywieszanie się systemu rafaln5 1 1.895 01.02.2016 22:43
Ostatni post: thermalfake
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 0 głosów.