[win7] Bluescreen po uruchomieniu systemu

[zonkinho]

Specyfikację kompa każdy widzi w podpisie, czyli:

CPU: Intel Core i5 2500K @ 4.5GHz + SPC Fortis + 2x SPC Sigma EVO

MOBO: Asrock P67 Pro3

RAM: 2x4GB/1600 Goodram Play

SSD: OCZ Vertex4 128GB

HDD: Samsung 750GB HD753LJ + Seagate 1TB ST31000524AS + Seagate 2TB ST2000DL003

GPU: Asus GTX560 1GB DCII OC @950/1850/1100

DVD-RW: ASUS DRW-24B3LT + Pioneer DVR-215L

Audio: Creative SoundBlaster Audigy 2SE + Logitech X-540 + Steelseries 5XB

PSU: Corsair HX650

BOX: CoolerMaster Silencio 550 + 3x NoiseBlocker XL2 120mm

Dodam od razu, że dzieje się tak też na stockowych ustawieniach procka i płyty. Kontroler SATA na AHCI, Vertex4 ustawiony jako SSD w biosie.

Dzieje mi się w sumie tak od jakiegoś czasu, że po pierwszym włączeniu komputera (po tym jak jest wyłączony), do 10 minut po starcie systemu mam bluescreena. System uruchamia się ponownie, sygnalizuje że został zamknięty po błędzie i wtedy może już działać nawet i tydzień jeśli się go nie wyłączy kompletnie. Gdy da się opcję Uruchom Ponownie, czy nawet zresetuje też działa pięknie. Problem występuje tylko przy włączeniu komputera po tym jak jest jakiś czas wyłączony.

Myślałem, że to może być SSD Corsair F120, więc zmieniłem na OCZ Vertex4. System przeinstalowałem i nadal to samo.

Ktoś wie jakie mogę być tego przyczyny? Płyta główna?

*******************************************************************************

* *

* 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: fffff8a0e6df79a0, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff8000367a9d0, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000005, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038fe100

GetUlongFromAddress: unable to read from fffff800038fe1c0

fffff8a0e6df79a0 Paged pool

FAULTING_IP:

nt!FsRtlCompareNodeAndKey+4

fffff800`0367a9d0 48395130 cmp qword ptr [rcx+30h],rdx

MM_INTERNAL_CODE: 5

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: Dropbox.exe

CURRENT_IRQL: 1

TRAP_FRAME: fffff8800c967a30 -- (.trap 0xfffff8800c967a30)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=00000000ffffffff rbx=0000000000000000 rcx=fffff8a0e6df7970

rdx=006900000001bd56 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8000367a9d0 rsp=fffff8800c967bc0 rbp=fffffa8006a4b420

r8=fffff8800c968058 r9=fffffffff63b75fc r10=fffff8a00dc6c950

r11=fffff8a00dc6c9a6 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

nt!FsRtlCompareNodeAndKey+0x4:

fffff800`0367a9d0 48395130 cmp qword ptr [rcx+30h],rdx ds:fffff8a0`e6df79a0=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003675f0f to fffff800036cf1c0

STACK_TEXT:

fffff880`0c9678c8 fffff800`03675f0f : 00000000`00000050 fffff8a0`e6df79a0 00000000`00000000 fffff880`0c967a30 : nt!KeBugCheckEx

fffff880`0c9678d0 fffff800`036cd2ee : 00000000`00000000 fffff8a0`e6df79a0 00000000`00000000 fffffa80`06f69238 : nt! ?? ::FNODOBFM::`string'+0x43d51

fffff880`0c967a30 fffff800`0367a9d0 : fffffa80`06f69238 fffff8a0`0dc6c8d0 00000000`00000001 fffff8a0`06752600 : nt!KiPageFault+0x16e

fffff880`0c967bc0 fffff800`039dff97 : fffffa80`099aa001 fffffa80`06f69238 fffffa80`06a4b420 fffffa80`00000000 : nt!FsRtlCompareNodeAndKey+0x4

fffff880`0c967c00 fffff880`0150bd40 : fffffa80`06f69238 fffffa80`099aa000 fffffa80`068fccd0 00000000`00000000 : nt!FsRtlFindInTunnelCache+0x9f

fffff880`0c967c70 fffff880`014f53cc : fffffa80`068fccd0 fffffa80`068fccd0 fffff8a0`0d5ee501 00000000`00000000 : Ntfs!NtfsCreateNewFile+0x3a0

fffff880`0c967fb0 fffff880`0145da3d : fffffa80`068fccd0 fffffa80`06a4b420 fffff880`0c968360 fffffa80`06a76c00 : Ntfs!NtfsCommonCreate+0xe9c

fffff880`0c968190 fffff800`036dae48 : fffff880`0c9682d0 00000000`00000000 fffff8a0`052478c0 fffff8a0`05271cd0 : Ntfs!NtfsCommonCreateCallout+0x1d

fffff880`0c9681c0 fffff880`0145e1bf : fffff880`0145da20 fffff880`0145d020 fffff880`0c968300 fffff880`014fef00 : nt!KeExpandKernelStackAndCalloutEx+0xd8

fffff880`0c9682a0 fffff880`014f799c : 00000000`00000000 00000000`00000000 fffff880`0c968500 fffffa80`06a4b420 : Ntfs!NtfsCommonCreateOnNewStack+0x4f

fffff880`0c968300 fffff880`01094bcf : fffffa80`06f68030 fffffa80`06a4b420 00000000`00000000 fffffa80`06e5a8e0 : Ntfs!NtfsFsdCreate+0x1ac

fffff880`0c9684b0 fffff880`010b42b9 : fffffa80`06a4b420 fffffa80`06f67010 fffffa80`06a4b400 fffffa80`06e5a8e0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f

fffff880`0c968540 fffff800`039c8be5 : 00000000`00000005 fffffa80`099aa1c8 fffffa80`06aa3970 00000000`00000000 : fltmgr!FltpCreate+0x2a9

fffff880`0c9685f0 fffff800`039c5488 : fffffa80`06e469d0 fffff800`00000000 fffffa80`099aa010 fffffa80`00000001 : nt!IopParseDevice+0x5a5

fffff880`0c968780 fffff800`039c66a6 : 00000000`00000000 fffffa80`099aa010 00000000`00000000 fffffa80`066eb790 : nt!ObpLookupObjectName+0x588

fffff880`0c968870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByName+0x306

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!FsRtlCompareNodeAndKey+4

fffff800`0367a9d0 48395130 cmp qword ptr [rcx+30h],rdx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!FsRtlCompareNodeAndKey+4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3

FAILURE_BUCKET_ID: X64_0x50_nt!FsRtlCompareNodeAndKey+4

BUCKET_ID: X64_0x50_nt!FsRtlCompareNodeAndKey+4

Followup: MachineOwner

*******************************************************************************

* *

* 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: fffff88003c05ff3, Address of the instruction which caused the bugcheck

Arg3: fffff8800a0a9ca0, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:

EX64+4ff3

fffff880`03c05ff3 ff5010 call qword ptr [rax+10h]

CONTEXT: fffff8800a0a9ca0 -- (.cxr 0xfffff8800a0a9ca0)

rax=fffff88000dc04a0 rbx=0000000000000000 rcx=fffff8a0002bcc60

rdx=fffff8800a0aaa60 rsi=fffff8800a0aa6e4 rdi=fffff8a0002004f0

rip=fffff88003c05ff3 rsp=fffff8800a0aa680 rbp=fffff8800a0aaa60

r8=fffff8800a0aa6e4 r9=fffff8a000dc0830 r10=fffff8a001a00000

r11=0000000000000001 r12=fffff8a0002004f0 r13=fffff8a000dc0830

r14=fffff8800a0aaa60 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202

EX64+0x4ff3:

fffff880`03c05ff3 ff5010 call qword ptr [rax+10h] ds:002b:fffff880`00dc04b0=5553102454894818

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: ccsvchst.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88003c05ff3

STACK_TEXT:

fffff880`0a0aa680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : EX64+0x4ff3

FOLLOWUP_IP:

EX64+4ff3

fffff880`03c05ff3 ff5010 call qword ptr [rax+10h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: EX64+4ff3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: EX64

IMAGE_NAME: EX64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4f97c380

STACK_COMMAND: .cxr 0xfffff8800a0a9ca0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_EX64+4ff3

BUCKET_ID: X64_0x3B_EX64+4ff3

Followup: MachineOwner

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff800039a96b0, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: 0000000034000000, Parameter 1 of the exception

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:

nt!MiPerformFixups+80

fffff800`039a96b0 410fb603 movzx eax,byte ptr [r11]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000034000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003901100

GetUlongFromAddress: unable to read from fffff800039011c0

0000000034000000 Nonpaged pool

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

BUGCHECK_STR: 0x1e_c0000005

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: steamerrorrepo

CURRENT_IRQL: 0

TRAP_FRAME: fffff880104035c0 -- (.trap 0xfffff880104035c0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff8a000544000 rbx=0000000000000000 rcx=fffff880026d3000

rdx=0000000000000ff8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff800039a96b0 rsp=fffff88010403750 rbp=0000000034000000

r8=0000000000000ffc r9=0000000000000fff r10=fffff880026d3000

r11=0000000034000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na po nc

nt!MiPerformFixups+0x80:

fffff800`039a96b0 410fb603 movzx eax,byte ptr [r11] ds:00000000`34000000=??

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000371cd88 to fffff800036d21c0

CONTEXT: 034cc0b60f5778c0 -- (.cxr 0x34cc0b60f5778c0)

Unable to read context, Win32 error 0n30

STACK_TEXT:

fffff880`10402d38 fffff800`0371cd88 : 00000000`0000001e ffffffff`c0000005 fffff800`039a96b0 00000000`00000000 : nt!KeBugCheckEx

fffff880`10402d40 fffff800`036d1842 : fffff880`10403518 fffff880`026d3000 fffff880`104035c0 ffffffff`f98f0000 : nt! ?? ::FNODOBFM::`string'+0x48d3d

fffff880`104033e0 fffff800`036d03ba : 00000000`00000000 00000000`34000000 fffff880`10403700 fffff880`026d3000 : nt!KiExceptionDispatch+0xc2

fffff880`104035c0 fffff800`039a96b0 : 000026d2`00013b62 000026ce`00013b62 fffff880`026d2000 00000000`00001000 : nt!KiPageFault+0x23a

fffff880`10403750 fffff800`039a5827 : fffff6fc`00000000 fffffa80`06acd060 00000000`00000110 fffff8a0`00544000 : nt!MiPerformFixups+0x80

fffff880`104037b0 fffff800`0370102b : ffffffff`ffffffff fffff880`10403938 00000000`00001000 ffffffff`ffffffff : nt!MiRelocateImagePfn+0xf7

fffff880`10403810 fffff800`036f8fff : fffffa80`06e57af0 fffff880`10403940 fffffa80`0b2623f8 fffff880`10403960 : nt!MiWaitForInPageComplete+0x7ef

fffff880`104038f0 fffff800`036df85a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b

fffff880`10403980 fffff800`036d02ee : 00000000`00000000 00000000`7787000c fffffa80`06acd001 00000000`00000001 : nt!MmAccessFault+0x146a

fffff880`10403ae0 00000000`7779cd2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e

00000000`00e0dbc4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7779cd2a

FOLLOWUP_IP:

nt!MiPerformFixups+80

fffff800`039a96b0 410fb603 movzx eax,byte ptr [r11]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!MiPerformFixups+80

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3

STACK_COMMAND: .cxr 0x34cc0b60f5778c0 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1e_c0000005_nt!MiPerformFixups+80

BUCKET_ID: X64_0x1e_c0000005_nt!MiPerformFixups+80

Followup: MachineOwner

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

BUGCODE_USB_DRIVER (fe)

USB Driver bugcheck, first parameter is USB bugcheck code.

Arguments:

Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is

using a physical memory address that was not allocated by

the USBport driver.

Arg2: fffffa80081451a0, Device extension pointer of the host controller

Arg3: 0000000080861c26, PCI Vendor,Product id for the controller

Arg4: fffffa8009295c48, Pointer to Endpoint data structure

Debugging Details:

------------------

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands 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: usbport!_DEVICE_EXTENSION ***

*** ***

*************************************************************************

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8800743ef7e to fffff800036e51c0

STACK_TEXT:

fffff800`00b9c918 fffff880`0743ef7e : 00000000`000000fe 00000000`00000005 fffffa80`081451a0 00000000`80861c26 : nt!KeBugCheckEx

fffff800`00b9c920 fffff880`07405fac : 00000000`00000000 fffffa80`081466a0 00000000`00000000 fffffa80`09295dc0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a

fffff800`00b9c960 fffff880`07405b73 : fffffa80`09295c48 00000000`00000000 fffffa80`09295dc0 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c

fffff800`00b9c9f0 fffff880`0740ad91 : fffffa80`09295c48 fffff800`00b96080 fffffa80`066d6040 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53

fffff800`00b9ca30 fffff880`07412e8b : 00000000`00000002 fffffa80`081451a0 00000000`00000000 00000000`00000010 : usbehci!EHCI_PollEndpoint+0x41

fffff800`00b9ca70 fffff880`074179d1 : 00000000`00000010 00000000`00000004 fffffa80`09295a00 fffffa80`08145050 : USBPORT!MPf_PollEndpoint+0x9b

fffff800`00b9caa0 fffff880`07423077 : fffffa80`081451a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1

fffff800`00b9cb00 fffff880`07413f89 : fffffa80`08145050 00000000`00000000 fffffa80`08145a02 fffffa80`08145a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3

fffff800`00b9cb60 fffff800`036ef8ec : fffff800`03857e80 fffffa80`08145a18 fffffa80`08145a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9

fffff800`00b9cb90 fffff800`036dceca : fffff800`03857e80 fffff800`03865cc0 00000000`00000000 fffff880`07413db0 : nt!KiRetireDpcList+0x1bc

fffff800`00b9cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:

usbehci!EHCI_sMode_PollEndpointSlot+6c

fffff880`07405fac 4533c9 xor r9d,r9d

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+6c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c00

FAILURE_BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c

BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c

Followup: MachineOwner

*******************************************************************************

* *

* 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: fffff960000fa106, Address of the instruction which caused the bugcheck

Arg3: fffff8800a0b0e40, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:

win32k!xxxDestroyThreadInfo+8fe

fffff960`000fa106 488b7118 mov rsi,qword ptr [rcx+18h]

CONTEXT: fffff8800a0b0e40 -- (.cxr 0xfffff8800a0b0e40)

rax=0000000000000dd8 rbx=0000000000000000 rcx=ffffffffffffffff

rdx=0000000000000002 rsi=ffffffffffffffff rdi=fffff900c01aa010

rip=fffff960000fa106 rsp=fffff8800a0b1820 rbp=0000000000000000

r8=0000000000000000 r9=0000000000000000 r10=0000000000000000

r11=fffffa800bfba640 r12=0000000000000dd8 r13=000000000000062f

r14=0000000000000000 r15=fffff960002dd200

iopl=0 nv up ei ng nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286

win32k!xxxDestroyThreadInfo+0x8fe:

fffff960`000fa106 488b7118 mov rsi,qword ptr [rcx+18h] ds:002b:00000000`00000017=????????????????

Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: sidebar.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960000fa106

STACK_TEXT:

fffff880`0a0b1820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxDestroyThreadInfo+0x8fe

FOLLOWUP_IP:

win32k!xxxDestroyThreadInfo+8fe

fffff960`000fa106 488b7118 mov rsi,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!xxxDestroyThreadInfo+8fe

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5006fd0d

STACK_COMMAND: .cxr 0xfffff8800a0b0e40 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!xxxDestroyThreadInfo+8fe

BUCKET_ID: X64_0x3B_win32k!xxxDestroyThreadInfo+8fe

Followup: MachineOwner

[[Ekspert] antros22]

Jeśli tego nie robiłeś, zaktualizuj wszelkie sterowniki oraz Windę. Sprawdź, czy po odłączeniu różnych urządzeń (po kolei wszystkich) od USB, błąd nadal występuje (i czy w ogóle te wejścia poprawnie działają). Sprawdź RAM programem Memtest86+.

[zonkinho]

Ram sprawdzony, jest ok.

Sterowniki wszystkie najnowsze. System z najnowszymi aktualizacjami. Pozostaje sprawdzić czy to któreś peryferia tego nie robią.