BSOD problem z procesorem?

RYCHU9191 · 18 Marzec 2016 21:50

Pomoże mi ktoś dlaczego wywala mi czasem bsod podczas grania?

Microsoft ® Windows Debugger Version 6.11.0001.404 X86Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\GODFATHER\Desktop\031816-7051-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*c:\symbole*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718Machine Name:Kernel base = 0xfffff8000325a000 PsLoadedModuleList = 0xfffff800034a1730Debug session time: Fri Mar 18 22:38:15.425 2016 (GMT+1)System Uptime: 0 days 5:35:00.564Loading Kernel Symbols…Loading User SymbolsLoading unloaded module list…******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 124, {0, fffffa800d0e6028, ff800000, 124}Probably caused by : hardwareFollowup: MachineOwner---------0: kd !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: fffffa800d0e6028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000ff800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------BUGCHECK_STR: 0x124_GenuineIntelCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULTPROCESS_NAME: H1Z1.exeCURRENT_IRQL: fSTACK_TEXT: fffff80003c13a98 fffff80003223a3b : 0000000000000124 0000000000000000 fffffa800d0e6028 00000000ff800000 : nt!KeBugCheckExfffff80003c13aa0 fffff800033e8133 : 0000000000000001 fffffa800cf66af0 0000000000000000 fffffa800cf66b40 : hal!HalBugCheckSystem+0x1e3fffff80003c13ae0 fffff80003223700 : 0000000000000728 fffffa800cf66af0 fffff80003c13e70 fffff80003c13e00 : nt!WheaReportHwError+0x263fffff80003c13b40 fffff80003223052 : fffffa800cf66af0 fffff80003c13e70 fffffa800cf66af0 0000000000000000 : hal!HalpMcaReportError+0x4cfffff80003c13c90 fffff80003222f0d : 0000000000000004 0000000000000001 fffff80003c13ef0 0000000000000000 : hal!HalpMceHandler+0x9efffff80003c13cd0 fffff80003216e88 : fffffa800d93bb50 0000000000000000 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0x55fffff80003c13d00 fffff800032cccac : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x40fffff80003c13d30 fffff800032ccb13 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x6cfffff80003c13e70 fffff800032d2a59 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x153fffff8800b7a8a10 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeSetEvent+0xd9STACK_COMMAND: kbFOLLOWUP_NAME: MachineOwnerMODULE_NAME: hardwareIMAGE_NAME: hardwareDEBUG_FLR_IMAGE_TIMESTAMP: 0FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner---------Coś z procesorem ale co? Chłodzenie boxowe, ale procek nie podkręcany aktualnie, temperatury 70-80* w grze.

Veers · 18 Marzec 2016 22:25

Nie procesor, tylko proces H1Z1.exe, a to oznacza problemy z klientem Steam. Jakie ? Możliwości jest wiele …

RYCHU9191 · 18 Marzec 2016 23:43

Grałem wcześniej w GTA V i też czasem wywalalo bsody, zadko ale też w CS GO się zdarza.

RYCHU9191 · 19 Marzec 2016 10:17

kolejne bsody dziś wywaliło 2x bez obciążenia zostawiłem komputer na kilka godzin po 9 i po 10 nastepny wywalilo… pomoze ktos?

Microsoft ® Windows Debugger Version 6.11.0001.404 X86Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\GODFATHER\Desktop\031916-6801-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*c:\symbole*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718Machine Name:Kernel base = 0xfffff8000320a000 PsLoadedModuleList = 0xfffff80003451730Debug session time: Sat Mar 19 10:34:40.020 2016 (GMT+1)System Uptime: 0 days 0:20:25.159Loading Kernel Symbols…Loading User SymbolsLoading unloaded module list…******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 50, {ffffffff00000000, 8, ffffffff00000000, 5}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.sysCould not read faulting driver nameProbably caused by : nvlddmkm.sys ( nvlddmkm+84154d )Followup: MachineOwner---------0: 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 itis pointing at freed memory.Arguments:Arg1: ffffffff00000000, memory referenced.Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.Arg3: ffffffff00000000, If non-zero, the instruction address which referenced the bad memory address.Arg4: 0000000000000005, (reserved)Debugging Details:------------------Could not read faulting driver nameWRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bb100 ffffffff00000000 FAULTING_IP: +61b3952f04acd834ffffffff00000000 ??              ???MM_INTERNAL_CODE:  5CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x50PROCESS_NAME:  pdiSDKHelper.eCURRENT_IRQL:  0TRAP_FRAME:  fffff8800a4120f0 -- (.trap 0xfffff8800a4120f0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a000ec9010rdx=000000000000006e rsi=0000000000000000 rdi=0000000000000000rip=ffffffff00000000 rsp=fffff8800a412288 rbp=fffffa800d23f170 r8=fffff8a002d0a038  r9=000000000000000c r10=fffff8a0000d35e0r11=0000000000000002 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz na po ncffffffff00000000 ?? ???Resetting default scopeLAST_CONTROL_TRANSFER: from fffff800032f8bda to fffff8000327e3c0STACK_TEXT: fffff8800a411f88 fffff800032f8bda : 0000000000000050 ffffffff00000000 0000000000000008 fffff8800a4120f0 : nt!KeBugCheckExfffff8800a411f90 fffff8000327c4ee : 0000000000000008 ffffffff00000000 0000000000000000 fffff8a002d0a038 : nt! ?? ::FNODOBFM::string'+0x3fe51fffff8800a4120f0 ffffffff00000000 : fffff8800f8bb54d fffff88000000000 fffff88000000000 fffffa8026180000 : nt!KiPageFault+0x16efffff8800a412288 fffff8800f8bb54d : fffff88000000000 fffff88000000000 fffffa8026180000 fffff80003372100 : 0xffffffff00000000fffff8800a412290 fffff88000000000 : fffff88000000000 fffffa8026180000 fffff80003372100 fffff8800a412348 : nvlddmkm+0x84154dfffff8800a412298 fffff88000000000 : fffffa8026180000 fffff80003372100 fffff8800a412348 fffff880031d9300 : 0xfffff88000000000fffff8800a4122a0 fffffa8026180000 : fffff80003372100 fffff8800a412348 fffff880031d9300 0000000000000001 : 0xfffff88000000000fffff8800a4122a8 fffff80003372100 : fffff8800a412348 fffff880031d9300 0000000000000001 fffff8800f0d9587 : 0xfffffa8026180000fffff8800a4122b0 000000400000000c : fffff8a00b037420 0000000500000001 0000100000000000 0000000000000000 : nt!EtwWriteEx+0x170fffff8800a412370 fffff8a00b037420 : 0000000500000001 0000100000000000 0000000000000000 0000100000000000 : 0x400000000cfffff8800a412378 0000000500000001 : 0000100000000000 0000000000000000 0000100000000000 0000200000000001 : 0xfffff8a00b037420fffff8800a412380 0000100000000000 : 0000000000000000 0000100000000000 0000200000000001 0000000200000001 : 0x500000001fffff8800a412388 0000000000000000 : 0000100000000000 0000200000000001 0000000200000001 0000000200000046 : 0x100000000000STACK_COMMAND:  kbFOLLOWUP_IP: nvlddmkm+84154dfffff8800f8bb54d ?? ???SYMBOL_STACK_INDEX: 4SYMBOL_NAME: nvlddmkm+84154dFOLLOWUP_NAME: MachineOwnerMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysDEBUG_FLR_IMAGE_TIMESTAMP: 56de66fcFAILURE_BUCKET_ID: X64_0x50_nvlddmkm+84154dBUCKET_ID: X64_0x50_nvlddmkm+84154dFollowup: MachineOwner---------0: 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 itis pointing at freed memory.Arguments:Arg1: ffffffff00000000, memory referenced.Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.Arg3: ffffffff00000000, If non-zero, the instruction address which referenced the bad memory address.Arg4: 0000000000000005, (reserved)Debugging Details:------------------Could not read faulting driver nameWRITE_ADDRESS: ffffffff00000000 FAULTING_IP: +61b3952f04acd834ffffffff00000000 ??              ???MM_INTERNAL_CODE:  5CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTBUGCHECK_STR:  0x50PROCESS_NAME:  pdiSDKHelper.eCURRENT_IRQL:  0TRAP_FRAME:  fffff8800a4120f0 -- (.trap 0xfffff8800a4120f0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a000ec9010rdx=000000000000006e rsi=0000000000000000 rdi=0000000000000000rip=ffffffff00000000 rsp=fffff8800a412288 rbp=fffffa800d23f170 r8=fffff8a002d0a038  r9=000000000000000c r10=fffff8a0000d35e0r11=0000000000000002 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz na po ncffffffff00000000 ?? ???Resetting default scopeLAST_CONTROL_TRANSFER: from fffff800032f8bda to fffff8000327e3c0STACK_TEXT: fffff8800a411f88 fffff800032f8bda : 0000000000000050 ffffffff00000000 0000000000000008 fffff8800a4120f0 : nt!KeBugCheckExfffff8800a411f90 fffff8000327c4ee : 0000000000000008 ffffffff00000000 0000000000000000 fffff8a002d0a038 : nt! ?? ::FNODOBFM::string'+0x3fe51fffff8800a4120f0 ffffffff00000000 : fffff8800f8bb54d fffff88000000000 fffff88000000000 fffffa8026180000 : nt!KiPageFault+0x16efffff8800a412288 fffff8800f8bb54d : fffff88000000000 fffff88000000000 fffffa8026180000 fffff80003372100 : 0xffffffff00000000fffff8800a412290 fffff88000000000 : fffff88000000000 fffffa8026180000 fffff80003372100 fffff8800a412348 : nvlddmkm+0x84154dfffff8800a412298 fffff88000000000 : fffffa8026180000 fffff80003372100 fffff8800a412348 fffff880031d9300 : 0xfffff88000000000fffff8800a4122a0 fffffa8026180000 : fffff80003372100 fffff8800a412348 fffff880031d9300 0000000000000001 : 0xfffff88000000000fffff8800a4122a8 fffff80003372100 : fffff8800a412348 fffff880031d9300 0000000000000001 fffff8800f0d9587 : 0xfffffa8026180000fffff8800a4122b0 000000400000000c : fffff8a00b037420 0000000500000001 0000100000000000 0000000000000000 : nt!EtwWriteEx+0x170fffff8800a412370 fffff8a00b037420 : 0000000500000001 0000100000000000 0000000000000000 0000100000000000 : 0x400000000cfffff8800a412378 0000000500000001 : 0000100000000000 0000000000000000 0000100000000000 0000200000000001 : 0xfffff8a00b037420fffff8800a412380 0000100000000000 : 0000000000000000 0000100000000000 0000200000000001 0000000200000001 : 0x500000001fffff8800a412388 0000000000000000 : 0000100000000000 0000200000000001 0000000200000001 0000000200000046 : 0x100000000000STACK_COMMAND:  kbFOLLOWUP_IP: nvlddmkm+84154dfffff8800f8bb54d ?? ???SYMBOL_STACK_INDEX: 4SYMBOL_NAME: nvlddmkm+84154dFOLLOWUP_NAME: MachineOwnerMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysDEBUG_FLR_IMAGE_TIMESTAMP: 56de66fcFAILURE_BUCKET_ID: X64_0x50_nvlddmkm+84154dBUCKET_ID: X64_0x50_nvlddmkm+84154dFollowup: MachineOwner---------