Windows 10 BSOD every day, maybe hardware problem

  • Thread starter Thread starter chacha3
  • Start date Start date
C

chacha3

Guest
Hi, we buy a new computer, and faced a problem with BSOD's. And every time there is different reasons.

Can you say what a problem with this computer?

Windows Debugger shows this information:

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\Загрузки\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred cache*c:\myCache
Deferred SRV*Symbol information
Symbol search path is: cache*c:\myCache;SRV*Symbol information
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`78a00000 PsLoadedModuleList = 0xfffff801`78e475b0
Debug session time: Mon Oct 7 21:01:31.692 2019 (UTC + 3:00)
System Uptime: 3 days 5:45:44.891
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols

Loading unloaded module list
......
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff801872215a0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: B250M-D2V

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F8

BIOS_DATE: 04/10/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: B250M-D2V-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff801872215a0

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP:
intelppm!AcpiCStateIdleCancel+0
fffff801`872215a0 c20000 ret 0

EXCEPTION_PARAMETER2: ffffffffffffffff

BUGCHECK_STR: 0x1E_c0000005_R

CPU_COUNT: 4

CPU_MHZ: e70

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-MG

ANALYSIS_SESSION_TIME: 10-09-2019 16:29:29.0733

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

BAD_STACK_POINTER: fffff8017d641138

LAST_CONTROL_TRANSFER: from fffff80178ca660e to fffff80178bc10a0

STACK_TEXT:
fffff801`7d641138 fffff801`78ca660e : 00000000`0000001e ffffffff`c0000005 fffff801`872215a0 00000000`00000000 : nt!KeBugCheckEx
fffff801`7d641140 fffff801`78bc9ecf : fffff801`78f10000 fffff801`78a00000 0005e554`00ab5000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff801`7d641180 fffff801`78ac3555 : 00000000`00000000 00000000`00000000 fffff801`7d6416f0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff801`7d6411b0 fffff801`78ac7aee : fffff801`7d62b498 fffff801`7d641e30 fffff801`7d62b498 fffff801`7469a180 : nt!RtlDispatchException+0x4a5
fffff801`7d641900 fffff801`78bc1f22 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
fffff801`7d641fb0 fffff801`78bc1ef0 : fffff801`78bd3016 00000000`00000003 00000000`00000002 fffff801`789cc101 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff801`7d62b358 fffff801`78bd3016 : 00000000`00000003 00000000`00000002 fffff801`789cc101 fffff801`7469a180 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff801`7d62b360 fffff801`78bceda2 : ffffcd8f`d96b31b0 ffffcd8f`d96b3040 fffff801`7d62b5e0 fffff801`78a48ff8 : nt!KiExceptionDispatch+0x116
fffff801`7d62b540 fffff801`872215a0 : fffff801`78a22091 ffffe000`fd1c0180 0003ad12`7d838a42 ffffcd8f`d9678000 : nt!KiGeneralProtectionFault+0x322
fffff801`7d62b6d8 fffff801`78a22091 : ffffe000`fd1c0180 0003ad12`7d838a42 ffffcd8f`d9678000 00000000`00000000 : intelppm!AcpiCStateIdleCancel
fffff801`7d62b6e0 fffff801`78a2158e : 00000000`00000003 00000000`00000002 fffff801`7d62bb00 00000000`00000000 : nt!PpmIdleExecuteTransition+0x961
fffff801`7d62ba00 fffff801`78bc4ba8 : 00000000`00000000 fffff801`7469a180 ffffcd8f`ddb7f080 00000000`00000420 : nt!PoIdle+0x36e
fffff801`7d62bb60 00000000`00000000 : fffff801`7d62c000 fffff801`7d625000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48


THREAD_SHA1_HASH_MOD_FUNC: 4f7e5af95e899f874a4e57045dda53fc3cb2290c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d001c59a0b9cdddea610a3b853214bb0870fb1b1

THREAD_SHA1_HASH_MOD: 046352e3c8c2a39a08cf3c5bde6e439515d9c3d2

FOLLOWUP_IP:
intelppm!AcpiCStateIdleCancel+0
fffff801`872215a0 c20000 ret 0

FAULT_INSTR_CODE: cc0000c2

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: intelppm!AcpiCStateIdleCancel+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 78d96350

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_intelppm!AcpiCStateIdleCancel

BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_intelppm!AcpiCStateIdleCancel

PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_STACKPTR_ERROR_intelppm!AcpiCStateIdleCancel

TARGET_TIME: 2019-10-07T18:01:31.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 377e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_stackptr_error_intelppm!acpicstateidlecancel

FAILURE_ID_HASH: {c4d0bcc2-db88-ecdf-e343-e11de8c7e34a}

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

More...
 
Back
Top